Check the changelog for the kernel rpm, you might find support for the Perc 4 controller's been dropped. If that's the case then the initial ramdisk (initrd) won't have a suitable driver it can use to talk to the RAID which is why it can't read the label on the device. $ rpm -qa | grep kernel Find the most recent one, the one you're having problems with then do... $ rpm -q --changelog kernel-smp.blah | less This may shed some light too... https://www.redhat.com/archives/fedora-list/2004-November/msg06164.html Will. On 6/12/05, jan.peuker@xxxxxxxxxxxxxxxxxx <jan.peuker@xxxxxxxxxxxxxxxxxx> wrote: > Hi list, > > I am facing a strange problem when booting the new 2.6.9-11ELSmp Kernel on my DELL PE1800. Actually, the problem occurs on every kernel except the one firstly installed (2.6.9-5). > When booting, I get the following messages: > > Loading ext3.ko module > Creating root-device > mkrootdev: label / not found > Mouting root filesystem > mount: error 2 mount ext3 > mount: error 2 mount none > Switching to new root > switchroot: mount failed: 22 > unmount /initrd/dev failed: 2 > Kernel Panic - not syncing: Attempting to kill init! > > First I thought it may be a naming problem - but grub.conf is configured correctly with the same line for all kernels: > kernel /vmlinuz-<version> ro root=LABEL=/ apic > > And fstab tells me that the drive is configured correctly as well and running ext3 (which is a loaded module). The root(hd0,2) is on a Perc4-RAID5-Logical Volume. Could this be the problem? Am I missing anything on this beautiful sunday? > > Thanks a lot, > > jan > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
