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

dunc · 2013-01-30 15:41:21

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)

roentgen · 2013-01-30 21:16:40

Save your initramfs-linux.img (that's for the ARCH kernel) as initramfs-linux.img.old and redo your initramfs to rule out an mkinitcpio problem.

If there's a problem with the newly generated initramfs just pass the backup one when booting.

BTW here is my initramfs for the 3.7.5-1-ARCH kernel.

# lsinitcpio initramfs-linux.img | grep lib64
./lib64

Last edited by roentgen (2013-01-30 21:17:32)

dunc · 2013-01-31 01:56:47

Heh. Now why didn't I think of that? (Actually, I did... after I posted. I think kernel panics send me into a panic too.)

Anyway, it's definitely the initramfs. And a diff on the two shows that the only change is those 10 libs appearing /usr/lib64 rather than /usr/lib.

I thought I'd resolved the potential conflicts in the filesystem-2013.01-3 update correctly, but I'm beginning to wonder.

Grr. I've been using Arch for nearly six years. I thought I knew my way around by now. (Angry with myself, by the way, not the devs.)

cfr · 2013-01-31 02:06:20

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.

dunc · 2013-01-31 22:28:45

It struck me that it might be an ldconfig thing. So I ran ldconfig -r again (actually, I reinstalled glibc to make sure I was passing the right arguments to it), and now everything's fine. I've no idea why it was finding those libraries - and only those libraries - in /usr/lib64, when everything else was in its proper place.

Anyway, solved. I suppose.

ADexter · 2013-02-01 23:10:03

Could you please explain exactly what you have done?
It seems like I have the same problem as well. (Same error, same output on lsinitcpio)

Chroot+mkinitcpio did not work
Reinstalling glibc neither

A little help would be great.

neptuneK · 2013-02-02 02:09:01

I had a similar problem. Some spurious file (not part of a package) in ld.so.conf.d was pointing
to /usr/lib64 . Removing the file, running ldconfig, and then doing mkinitcpio did the trick. You can
check the dependencies of the initramfs using lsinitcpio.

ADexter · 2013-02-02 12:00:07

Thank you neptuneK,

in ld.conf.so.d I found a file pointing to /usr/lib64 (it was libowncloud-sync, part of an aur package).
I removed the package and the file, ran ldconfig, mkinitcpio et voilà lsinitcpio showed no sign of lib64.

I feel kind of stupid for not checking ld.conf.so.d thou.

Arch Linux

#1 2013-01-30 15:41:21

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

#2 2013-01-30 21:16:40

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

#3 2013-01-31 01:56:47

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

#4 2013-01-31 02:06:20

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

#5 2013-01-31 22:28:45

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

#6 2013-02-01 23:10:03

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

#7 2013-02-02 02:09:01

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

#8 2013-02-02 12:00:07

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

Board footer