System Upgrade Disaster...

Hy Ginsberg · 2009-07-07 00:57:23

So what happened was that during my "pacman -Syu" I ran out of disk space. What followed:

I tried to uninstall some packages, and found that any time I tried to run pacman (any options or no options) I get:

pacman: error while loading shared libraries: /usr/lib/liblzma.so.0: invalid ELF header

I deleted a bunch of accrued garbage, but to no avail, Then I bravely rebooted, and really got the kick in the pants:

ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.

I am ready to sacrifice a goat, if anyone thinks that will help. Or if you have a better suggestion, I would be most grateful...

- Hy

broch · 2009-07-07 01:03:12

not enough information:
1) do you have one or several partitions?
if you have one partition, backup home and delete your files
2) is it ext3/4 or something else (in the case of ext3/4 you can set reserved space to lower value or even 0 which will release ~10-15% of your disk space
3) clean up
/var/log
/tmp
/var/tmp

Last edited by broch (2009-07-07 01:04:34)

Hy Ginsberg · 2009-07-07 01:13:44

Thanks -- Those are good ideas for cleaning up some space (and I do have two partitions), but is there really any hope that they might get Arch to recognize my root filesystem, or pacman to play nicely with the elves...?

I am hoping for some advice on salvaging my system... I will revert to a reinstall if I have to, but it's not going to make my day.

Allan · 2009-07-07 01:41:28

Clean up some space then you can extract "xz-utils" on to your files system. That should get pacman working again. I'd then reinstall xz-utils properly (-Sf might be necessary). Then do a "pacman -S" on all the packages that were updated in your last "pacman -Syu".

broch · 2009-07-07 01:43:35

when you provide information as I asked: disk configuration, file system and so on, then maybe someone will help, I would not count on elves and wizzards who will guess what to do.

rayjgu3 · 2009-07-07 01:48:39

as stated earlier more info needed
but essentially make sure you have enough room via live linux eniroment or arch install cd/usb connect to net then
chroot into your system as stated here>> http://wiki.archlinux.org/index.php/Rei … Install_CD
run pacman -Syu
reboot
should be good

Hy Ginsberg · 2009-07-07 02:16:38

Thank you all for your responses. But: I can't clean up any space -- the system does not recognize my root filesystem. So it doesn't boot. It is booting into the "ramfs", Or, to put it another way, I will gladly clean up my filesystem if anyone has any idea how I might get it mounted...

To recap: upgrading with insufficient disk space caused an inconsistency in my filesystem which annoyed pacman, and on a reboot Arch could not detect the root filesystem.

(Ahh -- I will read all the responses more carefully next time... I will try to clean up space via some other OS and then follow the chroot instructions. Tomorrow...)

Last edited by Hy Ginsberg (2009-07-07 02:19:41)

Hy Ginsberg · 2009-07-07 04:14:18

I cleaned up space via an OS mounted on another partition.

I followed the instructions for chroot'ing into my system, which worked.

I then tried to run "pacman -Sy", and got the same error I reported originally:

pacman: error while loading shared libraries: /usr/lib/liblzma.so.0: invalid ELF header

And then I rebooted and, no surprise, my root file system is still not detected. The error at reboot goes like this:

Attempting to create root device '/dev/disk/by-uuid/<big crazy uuid>
Waiting for devices to settle...done.
ERROR: failed to parse block device name for '/dev/disk/by-uuid/<big crazy uuid>
unknown
ERROR: root fs cannot be detected. Try using the root fstype= kernel parameter

Is there some way to get pacman past the problem it's stuck on?

Allan · 2009-07-07 04:16:27

Hy Ginsberg wrote:

Is there some way to get pacman past the problem it's stuck on?

Look at my post above...

Hy Ginsberg · 2009-07-07 04:21:01

Allan -- Yeah, I just did. Thanks. Now I understand -- I will replace the xz-utils and then go from there (I hadn't made the connection that the xz-utils package was the one that supplied the broken file). Thanks again.

Hy Ginsberg · 2009-07-07 04:41:44

So, sorry for needing help every step of the way, but it's not clear how to get xz-utils onto my system without pacman. I downloaded the tar file from the "upstream URL"; do the same chroot into the system trick and then run "make" or some such? Or am I way off?

(And might crudely deleting the offending file, /usr/lib/liblzma.so.0, suffice as a quick fix?)

Last edited by Hy Ginsberg (2009-07-07 04:50:26)

wonder · 2009-07-07 09:00:53

cp package /
tar xzf package

reboot

after booting, pacman -Sf package

droog · 2009-07-07 09:24:06

Hy Ginsberg wrote:

I downloaded the tar file from the "upstream URL";

you don't want the upstream source.

go here ftp://ftp.archlinux.org/core/os/ click on your arch and download the package.
extract it to your arch /

this should fix pacman, while still in chroot update the other packages that you installed last.
some of those are probably broke too keeping you from booting.

toad · 2009-07-07 09:52:15

The space problem happened to me, too. In future you will need to keep an eye on /var/cache/pacman/pkg/ - this is by far the biggest space hogger on any system and it just gets bigger with every update/new package installed. Unless kept in check it will harm every system given enough time...

Hy Ginsberg · 2009-07-07 13:24:17

Thanks, droog, for the perfect instructions on how to properly get the package tar file.

So: I extracted xz-utils, and a couple of other packages that had damaged files (libev, lua -- complaints from ldconfig while trying to run pacman -- "not an ELF file; wrong magic bytes").

I chrooted into my system from the LiveCD, and ran "pacman -Sf xz-utils" (and the same for the other two broken packages). Which worked fine. If I run "pacman -Su", pacman says the system is up to date.

If I now reboot, I get the same problem: the system cannot detect the root filesystem (see output in a previous message).

Any thoughts on what that is all about and what one does to fix it? I can run "pacman -Sf ..." for each of the 122 packages I was updating, but I don't have a nice warm feeling that that is going to change anything.

Many thanks.
- Hy

Allan · 2009-07-07 13:32:25

Did your kernel get updated? That might be an issue.

Also, you probably do not need to -Sf any other packages, just -S.

Hy Ginsberg · 2009-07-07 13:38:23

My kernel got updated. I am definitely ready to believe that that's an issue. For what it's worth, here is the full pacman log from the update:

[2009-07-06 19:26] synchronizing package lists
[2009-07-06 19:26] starting full system upgrade
[2009-07-06 20:33] removed portmap (6.0-2)
[2009-07-06 20:34] upgraded kernel-headers (2.6.29.1-1 -> 2.6.29.3-1)
[2009-07-06 20:34] upgraded tzdata (2009f-1 -> 2009j-1)
[2009-07-06 20:34] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2009-07-06 20:34] Generating locales...
[2009-07-06 20:34]   en_US.UTF-8... done
[2009-07-06 20:34] Generation complete.
[2009-07-06 20:34] upgraded glibc (2.9-7 -> 2.10.1-2)
[2009-07-06 20:34] upgraded readline (5.2.013-2 -> 6.0.00-1)
[2009-07-06 20:34] upgraded bash (3.2.048-3 -> 4.0.024-1)
[2009-07-06 20:34] installed libtirpc (0.2.0-1)
[2009-07-06 20:34] installed rpcbind (0.2.0-1)
[2009-07-06 20:34] upgraded glib2 (2.20.1-1 -> 2.20.4-1)
[2009-07-06 20:34] upgraded libxml2 (2.7.3-1 -> 2.7.3-2)
[2009-07-06 20:34] upgraded libgsf (1.14.13-1 -> 1.14.14-1)
[2009-07-06 20:34] upgraded libgsf-gnome (1.14.13-1 -> 1.14.14-1)
[2009-07-06 20:34] upgraded libpng (1.2.36-1 -> 1.2.37-1)
[2009-07-06 20:34] upgraded wv (1.2.4-1 -> 1.2.4-2)
[2009-07-06 20:34] upgraded abiword (2.6.8-1 -> 2.6.8-2)
[2009-07-06 20:34] upgraded dialog (1.1_20080819-1 -> 1.1_20080819-2)
[2009-07-06 20:34] upgraded alsa-utils (1.0.20-1 -> 1.0.20-2)
[2009-07-06 20:34] NOTES On Antiword Integration:
[2009-07-06 20:34] 
[2009-07-06 20:34] * If you use mozplugger, make sure to configure the
[2009-07-06 20:34]   msword section like so (replacing <TERMINAL> with your
[2009-07-06 20:34]   terminal of choice):
[2009-07-06 20:34]       application/msword: doc, dot: Microsoft Word Document
[2009-07-06 20:34]                 ignore_errors exits: antiword-helper <TERMINAL> ""
[2009-07-06 20:34] 
[2009-07-06 20:34] * To properly use antiword in your mailcap settings:
[2009-07-06 20:34]       application/msword; antiword %s; copiousoutput
[2009-07-06 20:34] 
[2009-07-06 20:34] * To enable drag-and-drop support in KDE, use the kantiword script
[2009-07-06 20:34] upgraded antiword (0.37-1 -> 0.37-2)
[2009-07-06 20:34] upgraded libdrm (2.4.9-1 -> 2.4.11-2)
[2009-07-06 20:34] upgraded libgl (7.4.1-1 -> 7.4.4-1)
[2009-07-06 20:34] upgraded ati-dri (7.4.1-1 -> 7.4.4-1)
[2009-07-06 20:34] upgraded binutils (2.19.1-2 -> 2.19.1-4)
[2009-07-06 20:34] upgraded cairo (1.8.6-1 -> 1.8.8-1)
[2009-07-06 20:34] upgraded cpio (2.9-3 -> 2.9-5)
[2009-07-06 20:34] upgraded device-mapper (1.02.31-1 -> 1.02.32-2)
[2009-07-06 20:34] upgraded e2fsprogs (1.41.5-2 -> 1.41.6-1)
[2009-07-06 20:34] upgraded libgcrypt (1.4.4-1 -> 1.4.4-2)
[2009-07-06 20:34] upgraded cryptsetup (1.0.6-2 -> 1.0.6-3)
[2009-07-06 20:34] upgraded gcc-libs (4.4.0-1 -> 4.4.0-4)
[2009-07-06 20:34] ATTENTION DB PACKAGE:
[2009-07-06 20:34] Please consider to run db_upgrade on Berkeley DB databases with a major db version number update.
[2009-07-06 20:34] upgraded db (4.7.25-2 -> 4.7.25.4-1)
[2009-07-06 20:34] warning: /etc/gshadow installed as /etc/gshadow.pacnew
[2009-07-06 20:34] upgraded filesystem (2009.01-1 -> 2009.01-2)
[2009-07-06 20:34] upgraded dbus-core (1.2.4.6permissive-1 -> 1.2.14-1)
[2009-07-06 20:34] upgraded dbus (1.2.4.6permissive-1 -> 1.2.14-1)
[2009-07-06 20:34] upgraded dcron (3.2-3 -> 3.2-4)
[2009-07-06 20:34] warning: /etc/dhcpcd.conf installed as /etc/dhcpcd.conf.pacnew
[2009-07-06 20:34] upgraded dhcpcd (5.0.1-1 -> 5.0.4-1)
[2009-07-06 20:34] upgraded dmapi (2.2.9-1 -> 2.2.10-1)
[2009-07-06 20:34] upgraded libtasn1 (2.1-1 -> 2.2-1)
[2009-07-06 20:34] upgraded gnutls (2.6.6-1 -> 2.8.1-1)
[2009-07-06 20:34] upgraded sqlite3 (3.6.13-1 -> 3.6.15-2)
[2009-07-06 20:34] upgraded heimdal (1.2.1-3 -> 1.2.1-5)
[2009-07-06 20:34] upgraded libthai (0.1.11-1 -> 0.1.12-1)
[2009-07-06 20:34] upgraded pango (1.24.2-1 -> 1.24.4-1)
[2009-07-06 20:34] upgraded gtk2 (2.16.1-1 -> 2.16.2-1)
[2009-07-06 20:34] upgraded gconf (2.26.1-1 -> 2.26.2-2)
[2009-07-06 20:34] upgraded gnome-keyring (2.26.1-1 -> 2.26.3-1)
[2009-07-06 20:34] upgraded libdjvu (3.5.21-1 -> 3.5.22-1)
[2009-07-06 20:34] upgraded poppler (0.10.6-1 -> 0.10.7-1)
[2009-07-06 20:34] upgraded poppler-glib (0.10.6-1 -> 0.10.7-1)
[2009-07-06 20:34] upgraded evince (2.26.1-1 -> 2.26.2-1)
[2009-07-06 20:34] upgraded grep (2.5.4-1 -> 2.5.4-2)
[2009-07-06 20:34] The package is built using sysv ipc. If this causes segfaults
[2009-07-06 20:34] see included README file and rebuild the pkg --with-ipc=tcp
[2009-07-06 20:34] upgraded fakeroot (1.12.2-2 -> 1.12.4-1)
[2009-07-06 20:34] upgraded fam (2.7.0-11 -> 2.7.0-14)
[2009-07-06 20:34] upgraded lame (3.98.2-1 -> 3.98.2-2)
[2009-07-06 20:34] upgraded x264 (20090216-1 -> 20090416-1)
[2009-07-06 20:34] upgraded ffmpeg (20090217-1 -> 0.5-1)
[2009-07-06 20:34] upgraded findutils (4.4.1-1 -> 4.4.2-1)
[2009-07-06 20:34] upgraded foomatic-db (4.0_20090424-1 -> 4.0_20090625-1)
[2009-07-06 20:34] upgraded foomatic-filters (4.0_20090424-1 -> 4.0_20090625-1)
[2009-07-06 20:34] upgraded foomatic-db-engine (4.0_20090424-1 -> 4.0_20090625-1)
[2009-07-06 20:34] upgraded foomatic-db-hpijs (20090424-1 -> 20090625-1)
[2009-07-06 20:34] upgraded gcc (4.4.0-1 -> 4.4.0-4)
[2009-07-06 20:35] upgraded gdbm (1.8.3-5 -> 1.8.3-6)
[2009-07-06 20:35] upgraded glproto (1.4.9-1 -> 1.4.10-1)
[2009-07-06 20:35] upgraded gmp (4.2.4-1.1 -> 4.3.1-2)
[2009-07-06 20:35] upgraded gtk (1.2.10-8 -> 1.2.10-9)
[2009-07-06 20:35] upgraded hwdetect (2009.04-1 -> 2009.06-1)
[2009-07-06 20:35] upgraded libdaemon (0.13-1 -> 0.13-2)
[2009-07-06 20:35] upgraded ifplugd (0.28-4 -> 0.28-6)
[2009-07-06 20:35] upgraded imlib (1.9.15-4 -> 1.9.15-5)
[2009-07-06 20:35] upgraded kernel26-firmware (2.6.29-1 -> 2.6.30-1)
[2009-07-06 20:35] upgraded klibc (1.5.15-2 -> 1.5.15-3)
[2009-07-06 20:35] upgraded klibc-extras (2.5-3 -> 2.5-4)
[2009-07-06 20:35] upgraded klibc-kbd (1.15.20080312-9 -> 1.15.20080312-10)
[2009-07-06 20:35] upgraded klibc-module-init-tools (3.5-2 -> 3.8-1)
[2009-07-06 20:35] upgraded klibc-udev (141-2 -> 141-3)
[2009-07-06 20:35] warning: /etc/modprobe.d/framebuffer_blacklist saved as /etc/modprobe.d/framebuffer_blacklist.pacsave
[2009-07-06 20:35] upgraded udev (141-1 -> 141-3)
[2009-07-06 20:35] warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
[2009-07-06 20:35] upgraded mkinitcpio (0.5.23-1 -> 0.5.25-1)
[2009-07-06 20:35] warning: /etc/modprobe.conf saved as /etc/modprobe.conf.pacsave
[2009-07-06 20:35] upgraded module-init-tools (3.5-1 -> 3.8-1)
[2009-07-06 20:35] upgraded kernel26 (2.6.29.3-1 -> 2.6.30.1-1)
[2009-07-06 20:35] upgraded lftp (3.7.13-1 -> 3.7.14-2)
[2009-07-06 20:35] installed xz-utils (4.999.8beta-4)
[2009-07-06 20:35] upgraded libarchive (2.7.0-1 -> 2.7.0-2)
[2009-07-06 20:35] upgraded libev (3.53-1 -> 3.60-1)
[2009-07-06 20:35] upgraded libgphoto2 (2.4.5-1 -> 2.4.6-1)
[2009-07-06 20:35] upgraded libidn (1.14-1 -> 1.15-1)
[2009-07-06 20:35] upgraded libsasl (2.1.22-7 -> 2.1.23-1)
[2009-07-06 20:35] upgraded libsndfile (1.0.19-1 -> 1.0.20-2)
[2009-07-06 20:35] upgraded libv4l (0.5.9-1 -> 0.5.99-1)
[2009-07-06 20:35] upgraded libxaw (1.0.5-1 -> 1.0.6-1)
[2009-07-06 20:35] upgraded libxt (1.0.5-2 -> 1.0.6-1)
[2009-07-06 20:35] upgraded lua (5.1.4-2 -> 5.1.4-4)
[2009-07-06 20:35] upgraded lvm2 (2.02.45-1 -> 2.02.47-2)
[2009-07-06 20:35] upgraded lzo2 (2.02-3 -> 2.03-1)
[2009-07-06 20:35] upgraded man-db (2.5.5-1 -> 2.5.5-2)
[2009-07-06 20:35] upgraded man-pages (3.20-2 -> 3.21-1)
[2009-07-06 20:35] upgraded mesa (7.4.1-1 -> 7.4.4-1)
[2009-07-06 20:35] upgraded mlocate (0.21.1-1 -> 0.22-1)
[2009-07-06 20:35] upgraded net-tools (1.60-13 -> 1.60-14)
[2009-07-06 20:35] upgraded nspr (4.7.4-1 -> 4.8-1)
[2009-07-06 20:35] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2009-07-06 20:35] upgraded pacman-mirrorlist (20090509-1 -> 20090616-1)
[2009-07-06 20:35] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-07-06 20:35] upgraded procps (3.2.7-5 -> 3.2.8-1)
[2009-07-06 20:35] upgraded psmisc (22.6-2 -> 22.7-1)
[2009-07-06 20:35] upgraded python (2.6.2-1 -> 2.6.2-3)
[2009-07-06 20:35] upgraded qt (4.5.1-2 -> 4.5.2-1)
[2009-07-06 20:36] upgraded ratpoison (1.4.3-2 -> 1.4.3-3)
[2009-07-06 20:36] upgraded tdb (3.3.4-1 -> 3.3.6-1)
[2009-07-06 20:36] upgraded smbclient (3.3.4-1 -> 3.3.6-2)
[2009-07-06 20:36] upgraded sox (14.2.0-2 -> 14.2.0-3)
[2009-07-06 20:36] upgraded sudo (1.7.1-1 -> 1.7.1-2)
[2009-07-06 20:36] upgraded sysfsutils (2.1.0-4 -> 2.1.0-5)
[2009-07-06 20:36] upgraded tcp_wrappers (7.6-8 -> 7.6-10)
[2009-07-06 20:36] upgraded texlive-bin (2008-4 -> 2008-5)
[2009-07-06 20:36] updating the filename database... done
[2009-07-06 20:36] upgraded texlive-core (2008.11906-1 -> 2008.13013-1)
[2009-07-06 20:36] >>> texlive: updating the filename database...
[2009-07-06 20:36] >>> texlive: updating the fontmap files with updmap...
[2009-07-06 20:36]  done.
[2009-07-06 20:36] upgraded texlive-latexextra (2008.11905-1 -> 2008.13015-1)
[2009-07-06 20:36] >>> texlive: updating the filename database...
[2009-07-06 20:36] >>> texlive: updating the fontmap files with updmap...
[2009-07-06 20:36]  done.
[2009-07-06 20:36] upgraded texlive-pictures (2008.10658-1 -> 2008.12984-1)
[2009-07-06 20:36] >>> texlive: updating the filename database...
[2009-07-06 20:36] upgraded texlive-pstricks (2008.11900-1 -> 2008.12873-1)
[2009-07-06 20:36] upgraded unrar (3.9.3-1 -> 3.9.4-1)
[2009-07-06 20:36] upgraded wpa_supplicant (0.6.9-1 -> 0.6.9-2)
[2009-07-06 20:36] upgraded xdg-utils (1.0.2-1 -> 1.0.2-2)
[2009-07-06 20:36] upgraded xfsprogs (3.0.0-1 -> 3.0.1-1)
[2009-07-06 20:37] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
[2009-07-06 20:37] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-3)

rayjgu3 · 2009-07-07 21:48:43

i dont see anything from mkinitcpio in your log
you probably need to update your initrd
chroot back into system & run
mkinitcpio -g /boot/kernel26.img
for more info see here>> http://wiki.archlinux.org/index.php/Con … mkinitcpio

Hy Ginsberg · 2009-07-07 22:35:07

Thanks. At this point I am recording results essentially for posterity; I am pretty sure I am hosed.

I chroot'ed into my system and ran "mkinitcpio -g /boot/kernel26.img". I got errors. I ran it again, redirecting stdout and stderr so I could report the results.

stdout:

:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usb]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating image '/boot/kernel26.img'...SUCCESS

stderr:

find: `/lib/modules/2.6.25-ARCH': No such file or directory
ERROR: module 'pata[-_]acpi' not found
find: `/lib/modules/2.6.25-ARCH': No such file or directory
ERROR: module 'pata[-_]ali' not found
find: `/lib/modules/2.6.25-ARCH': No such file or directory
ERROR: module 'ata[-_]generic' not found
find: `/lib/modules/2.6.25-ARCH': No such file or directory
ERROR: module 'scsi[-_]mod' not found
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
error opening alias file: No such file or directory
find: `/lib/modules/2.6.25-ARCH': No such file or directory
find: `/lib/modules/2.6.25-ARCH': No such file or directory

Then I tried to reboot, and got something like:

kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: kinit not tainted 2.6.30-ARCH #1

followed by a stack trace which was (modulo offsets) panic, called from do_exit, called from complete_and_exit, called from syscall_call.

The moral of the story, as far as I can tell, is that "pacman -Syu" can completely destroy your system. I admit I should be more on top of things and realize I don't have enough disk space, but capital punishment seems a bit harsh for my negligence. I'm surprised, and a bit disappointed. Not that I'm going to replace Arch with anything else -- tomorrow morning I will be reinstalling from scratch. Still, I would have bet that running pacman would be safe...

Thanks to all who tried to help, and if anyone has any last ditch ideas, or is interested in an autopsy, let me know.

Thanks again.

- Hy

mandog · 2009-07-08 06:04:16

How can you blatantly blame Pacman in 2 years pacman has behaved impeccably on 3 Systems 1 of which only gets updated every 6 months the others on a daily basis.
Read the forums for possible problems and the Wiki on how to set things up correctly, do not use symbolic links as they come back to haunt you at a later date, remember Arch Linux is do it yourself, A bad workman always blames his tools?

rayjgu3 · 2009-07-08 21:29:21

chroot
run
pacman -Sy base
reboot

Hy Ginsberg · 2009-07-09 18:50:31

Thanks, but I gave up and reinstalled already.

HashBox · 2009-07-10 05:59:03

This is weird, I'm getting the exact same errors that you're getting after chrooting and running mkinitcpio -g /boot/kernel26.img. I'm unable to boot because of the same errors aswell, yet I never ran out of disk space after running "pacman -Syu". I'm currently chrooted into my system using an Arch livecd, but I'm unsure of what to do next :\

Edit: It'll probably help to point out that I'm running testing and am on i686 using ext2 for /boot and ext3 for everything else.

Edit2: Ok mkinitcpio does work but I had to add -k 2.6.30ARCH to the end

Last edited by HashBox (2009-07-10 06:12:35)

Arch Linux

#1 2009-07-07 00:57:23

System Upgrade Disaster...

#2 2009-07-07 01:03:12

Re: System Upgrade Disaster...

#3 2009-07-07 01:13:44

Re: System Upgrade Disaster...

#4 2009-07-07 01:41:28

Re: System Upgrade Disaster...

#5 2009-07-07 01:43:35

Re: System Upgrade Disaster...

#6 2009-07-07 01:48:39

Re: System Upgrade Disaster...

#7 2009-07-07 02:16:38

Re: System Upgrade Disaster...

#8 2009-07-07 04:14:18

Re: System Upgrade Disaster...

#9 2009-07-07 04:16:27

Re: System Upgrade Disaster...

#10 2009-07-07 04:21:01

Re: System Upgrade Disaster...

#11 2009-07-07 04:41:44

Re: System Upgrade Disaster...

#12 2009-07-07 09:00:53

Re: System Upgrade Disaster...

#13 2009-07-07 09:24:06

Re: System Upgrade Disaster...

#14 2009-07-07 09:52:15

Re: System Upgrade Disaster...

#15 2009-07-07 13:24:17

Re: System Upgrade Disaster...

#16 2009-07-07 13:32:25

Re: System Upgrade Disaster...

#17 2009-07-07 13:38:23

Re: System Upgrade Disaster...

#18 2009-07-07 21:48:43

Re: System Upgrade Disaster...

#19 2009-07-07 22:35:07

Re: System Upgrade Disaster...

#20 2009-07-08 06:04:16

Re: System Upgrade Disaster...

#21 2009-07-08 21:29:21

Re: System Upgrade Disaster...

#22 2009-07-09 18:50:31

Re: System Upgrade Disaster...

#23 2009-07-10 05:59:03

Re: System Upgrade Disaster...

Board footer