Topic: kernel panic - not syncing

[dub]

i recently need to change my machine
old was Athlon 3000 xp
new is celeron 2.4 ghz

i do an upgrade of my server disks after installing them in the new but after reboot i received the same message

Unable to find volume group
ERROR: /bin/lvm exited abnormaly ( pid192)

mount: error 6 mounting ext3
mount: error 2 mounting none

switchroot: mount failed:22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init


i've try :

Boot from CD typed text rescue
selected option to mount system as
/mnt/sysimage

chroot /mnt/sysimage
mkinitrd -v -f /boot/initrd-2.6.9-22.0.1.EL.img
2.6.9-22.0.1.EL
mkinitrd -v -f /boot/initrd-2.6.9-22.0.1.ELsmp.img 2.6.9-22.0.1.ELsmp
//ok for this first step//
cp /etc/lilo.conf.rpmsave /etc/lilo.conf
lilo -v
exit
// no directory for this one//

Any ideas will be appreciated

regards

[AaronG]

Hi,

I am getting the exact same errors with a SME v7 pre1 install.

I did a manual yum update at the CLI. There were no updates however I thought i might still do a signal-event post-upgrade and post-reboot

On doing this my server is now not working.

I am getting the error above.

Any ideas PLEASE?

Cheers
Aaron

[gordonr]

I am getting the exact same errors with a SME v7 pre1 install.

This is the same issue as reported in the following thread:

http://forums.contribs.org/index.php?topic=30365.0

That thread has a link to the relevant Bugzilla entry. Follow-up to Bugzilla, and only there, please.

[gordonr]

cp /etc/lilo.conf.rpmsave /etc/lilo.conf
lilo -v
exit
// no directory for this one//

SME7 does not use LILO. See Bugzilla for the details of this issue.

[AaronG]

Sorry... this was a very early post of mine before.

I should have stated that this thread is no longer valid.

I have infact reported this in bugzilla

The problem seems to be that a YUM update has somehow changed the default boot OS.

I now somehow have 4 x Operation system choices.

1. CentOS (2..... ELsmp)
2. CentOS (2..... EL)
3. SME Server (2..... EL)
4. SME Server UP (2..... ELsmp)

YUM soomehow changed the default boot to be CentOS and thus it fails trying to boot up.

I simply change the option back to SME Server Up and VOILA! it works again