I updated to latest kernel on Jan 30, and after reboot, I have this:
Booting the kernel. /usr/bin/ash: error while loading shared libraries: libc.so.6: cannot open shared object files: No such file or directory [ 1.010168] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
I tried mkinitcpio -p linux but that didn't help. D:
Thanks in Advance!
I updated to latest kernel ...
Did you update everything else as well? Have you been ignoring any package updates?
I have only svn on ignore list because the latest version doesn't work with other software I use. Everything else is up to date.
And thanks for the quick reply!
I noticed that, unlike earlier, I cannot chroot into the Arch Linux partition:
# mount /dev/sda4 /mnt/ # mount /dev/sda1 /mnt/boot/ # mount -o bind /dev/ /mnt/dev/ # mount -o bind /dev/pts/ /mnt/dev/pts/ # mount -t proc none /mnt/proc/ # mount -t proc sysfs /mnt/sys/ # chroot /mnt/ /bin/bash chroot: failed to run command ‘/bin/bash’: No such file or directory
Secondly, both files are very much present there:
File: ‘/mnt/bin/bash’ -> ‘../usr/bin/bash’ File: ‘/lib/libc.so.6’ -> ‘libc-2.16.so’
Last edited by SgrA (2013-02-01 14:36:54)
What does your pacman log show? Maybe you're having problems with the glibc/filesystem update. There's a number of other threads about it.
Last edited by Scimmia (2013-02-01 18:52:06)
Last edited by Scimmia (2013-02-01 18:51:52)
Hmm, I remember vaguely that I had similar problems after a huge update of a netbook I had not used for over a year. I think ld-linux-x86 changed its place in the file system.
Perhaps this can help you with the chroot:
- try chroot /mnt /usr/lib/ld-linux.so /bin/bash
- add a compatibility link, in /lib or /usr/lib or wherever ...
No idea, though, why it's broken in the first place.