[Solved] Kernel panic in early boot - libc.so.6 not found

Question

As per subject. I -Syu'd on Monday, bringing in the new glibc and filesystem, and everything was fine. Another update yesterday brought the latest linux-ck (no, wait: I know it's unsupported, but read on) which won't boot, failing almost immediately at the initramfs stage with that error. Downgrading the kernel doesn't help, which is why I'm posting here rather than in the -ck thread: it looks like a mkinitcpio issue, rather than something inside the package. The stock kernel works, but it hasn't been updated since glibc and the filesystem (and I'm terrified to do anything with it in case that fails too...)
The output from lsinitcpio on my -ck image gives
./VERSION
./buildconfig
./config
./consolefont.psf
./hooks
./hooks/consolefont
./hooks/udev
./init
./init_functions
./sbin
./bin
./lib64
./lib
./usr
./usr/lib64
./usr/lib64/libpthread.so.0
./usr/lib64/libc.so.6
./usr/lib64/librt.so.1
./usr/lib64/libattr.so.1
./usr/lib64/libz.so.1
./usr/lib64/libuuid.so.1
./usr/lib64/libacl.so.1
./usr/lib64/libkmod.so.2
./usr/lib64/libblkid.so.1
./usr/lib64/libmount.so.1
./usr/sbin
./usr/bin
...{cut for brevity}
which looks wrong to me. Surely there shouldn't be anything in /usr/lib64? Looking at my filesystem, /usr/lib64 is a symlink to /usr/lib. Is that normal? As far as I remember, I haven't monkeyed with anything since the first install of this system; it's been straight -Syus all the way.
Last edited by dunc (2013-01-31 22:29:17)

Answer 1

dunc wrote:which looks wrong to me. Surely there shouldn't be anything in /usr/lib64? Looking at my filesystem, /usr/lib64 is a symlink to /usr/lib. Is that normal? As far as I remember, I haven't monkeyed with anything since the first install of this system; it's been straight -Syus all the way.
lrwxrwxrwx 1 root root 7 Ion 27 07:29 /lib -> usr/lib/
lrwxrwxrwx 1 root root 3 Ion 27 07:29 /usr/lib64 -> lib/
I checked two of the libraries you listed and they are under /usr/lib on my system.