You are not logged in.
Greetings,
After a system upgrade today:
Decompressing Linux... Parsing ELF... done
Booting the kernel
/usr/bin/ash: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[ 0.668073] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
This is on an AMD64 (single-core) with 4G memory. Limiting memory at boot with mem=4gb didn't help.
I booted into another system on the machine and checked for /usr/bin/ash. AFAICT there's no /usr/bin/ash at all.
/lib is linked to /usr/lib, as is /lib64.
I've found various threads re: various kernel panics, but only one looks like mine, hence the new thread.
Any & all suggestions appreciated, I need to get running again asap. I'll d/l a new installation medium too.
TIA,
Dave Phillips
Last edited by davephillips (2012-11-09 15:50:16)
Similis sum folio de quo ludunt venti.
Offline
/usr/bin/ash is part of busybox, which is used in the initcpio image. It sounds like something failed when the kernel upgrade ran the mkinitcpio command.
You may be able to boot your system with the arch install media, and then chroot into your real root drive, and run the "mkinitcpio -p linux" to regenerate the initcpio image. Note you'll have to manually do any mounts to the chroot, like for instance if you have /boot on a seperate partition.
Probably something like:
mount /dev/XXXX /mnt # (XXXX is root partition)
mount /dev/YYYY /mnt/boot # (YYYY is boot partition)
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
chroot /mnt /bin/bash --login
Now that you are in the chroot, regen the initcpio:
mkinitcpio -p linux
exit
Now undo the mounts:
umount /mnt/dev/pts
umount /mnt/dev
umount /mnt/sys
umount /mnt/proc
umount /mnt/boot
umount /mnt
Then try rebooting.
good luck.
Offline
/usr/bin/ash is part of busybox, which is used in the initcpio image. It sounds like something failed when the kernel upgrade ran the mkinitcpio command...
Thanks, johni, the procedure was painless, but it didn't change the situation. I'm still looking into possible solutions. Any other suggestions ?
Best,
dp
Similis sum folio de quo ludunt venti.
Offline
Greetings,
Problem resolved by removing a spurious link to /usr/lib64. Started over with mkinitcpio, rebooted into a working system, no kernel panic.
Thanks to all who pointed me in the right direction.
Best,
dp
Similis sum folio de quo ludunt venti.
Offline