Help.
One of my servers is down and I'm stuck.
It's a FC7 installation that started playing up on Friday. Tried rebooting it yesterday remotely and it wouldn't boot.
Now I'm on-site and I've got the following on-screen.
I've booted up using the DVD, and done an e2fsck on the volume and it gave no errors.
Booting 'Fedora (2.6.23.15-80.fc7)
root(hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.23.15-80.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x2c00, size=0x1df440] initrd /initrd-2.6.23.15-80.fc7.img [Linux-initrd @ 0x1dc7f000, 0x36cef4 bytes]
Uncompressing L:inux... Ok, booting the kernel. ACPI: Invalid PBLK length [5] Red Hat nash version 6.0.9 starting Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "Volgroup00" now active /sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: no such file or directory Kernel panic - not syncing: Attempting to kill init!
At this point it hangs. If I boot into recovery mode using the DVD I can use lvm to access the volumes, but chroot fails because it cannot start /bin/sh on the chrooted fs for the same reason.
Can anyone give me a clue where to go next.
Cheers
Gary Stainburn wrote:
Uncompressing L:inux... Ok, booting the kernel. ACPI: Invalid PBLK length [5] Red Hat nash version 6.0.9 starting Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "Volgroup00" now active /sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: no such file or directory Kernel panic - not syncing: Attempting to kill init!
At this point it hangs. If I boot into recovery mode using the DVD I can use lvm to access the volumes, but chroot fails because it cannot start /bin/sh on the chrooted fs for the same reason.
Have you done a fsck on the drive yet to verify the drive integrity?
Bradley
On Sunday 04 May 2008 13:19, Bradley Pursley wrote:
Gary Stainburn wrote:
Uncompressing L:inux... Ok, booting the kernel. ACPI: Invalid PBLK length [5] Red Hat nash version 6.0.9 starting Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "Volgroup00" now active /sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: no such file or directory Kernel panic - not syncing: Attempting to kill init!
At this point it hangs. If I boot into recovery mode using the DVD I can use lvm to access the volumes, but chroot fails because it cannot start /bin/sh on the chrooted fs for the same reason.
Have you done a fsck on the drive yet to verify the drive integrity?
Bradley
did:
lvm vgscan lvm vgchange -ay lvm lvs
e2fchk -f /dev/VolGroup00/LogVol00
It didn't report any errors
Gary Stainburn wrote: ...
/sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: no such file or directory Kernel panic - not syncing: Attempting to kill init!
At this point it hangs. If I boot into recovery mode using the DVD I can use lvm to access the volumes, but chroot fails because it cannot start /bin/sh on the chrooted fs for the same reason.
In recovery mode, can you check /mnt/sysimage/lib if there's a libc.so.6 symlink?
On F8, it is a symlink to libc-2.7.so
Mogens
On Sunday 04 May 2008 14:56, Mogens Kjaer wrote:
Gary Stainburn wrote: ...
/sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: no such file or directory Kernel panic - not syncing: Attempting to kill init!
At this point it hangs. If I boot into recovery mode using the DVD I can use lvm to access the volumes, but chroot fails because it cannot start /bin/sh on the chrooted fs for the same reason.
In recovery mode, can you check /mnt/sysimage/lib if there's a libc.so.6 symlink?
On F8, it is a symlink to libc-2.7.so
Mogens
The symlink wasn't there so I re-created it. It then complained about another lib and then another and another.
Even though fsck didn't report anything, I think the fs may be corrupt.
I've managed to revert to the older server that this new one had only just replaced. I'm not going to rebuild from scratch as I think this is the only way be be 100% certain it's right. (I'm going to soak test the drive first)
Thanks everyone for their help.
On Tue, 2008-05-06 at 09:36 +0100, Gary Stainburn wrote:
Even though fsck didn't report anything, I think the fs may be corrupt.
I've managed to revert to the older server that this new one had only just replaced. I'm not going to rebuild from scratch as I think this is the only way be be 100% certain it's right. (I'm going to soak test the drive first)
Thanks everyone for their help.
A bad power supply will give you all kinds of wonky messages. If you have another handy, I'd switch it out, just for ducks. Ric
-
Bradley -
Gary Stainburn -
Mogens Kjaer -
Ric Moore