The lines leading up to the error were:
Red Hat mash version 4.1.18 starting
Mounted /proc filessystem
Mounting sysfs
Creating /dev
starting udev
Loading jbd.ko module
Loading ext3.ko module
Creating root device
mkrootdev: label / not found
This means that the volume isn't labeled or doesn't match what's in
grub.conf.
Mounting root filesystem
mount: error 2 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
How do I start to troubleshoot this?
When you put the new kernel in did you create a new ramdisk?
That's done automatically by the post-install scripts for the kernel.
You can see this with:
$ rpm -q kernel --scripts
As for the original poster, let's have a look at /etc/grub.conf. Please
don't tell us you're still running lilo.
Nope... no Lilo for me. Here are grub.conf's contents:
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux AS (2.6.9-5.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.0.3.EL ro root=LABEL=/
initrd /initrd-2.6.9-5.0.3.EL.img
title Red Hat Enterprise Linux AS (2.6.9-5.0.3.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.0.3.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-5.0.3.ELsmp.img
title Red Hat Enterprise Linux AS (2.6.9-5.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-5.ELsmp.img
title Red Hat Enterprise Linux AS (2.6.9-5.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/
initrd /initrd-2.6.9-5.EL.img
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
