Hi All,
I have a Dell Precision 390 with a SATA HDD on which RHEL4 WS (kernel 2.6.9) has been installed. I built a new 2.6.9 kernel according to the instructions given here -
http://voidmain.is-a-geek.net/redhat...nel_build.html , in short, I executed the following commands:
(I used the configuration of the working kernel)
make oldconfig
(made changes to include Intel SpeedStep drivers)
make menuconfig
make
make modules_install
make install
When I try to boot from this newly built kernel I get the below error messages:
mkrootdev: label /1 not found
mount: error 2 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 am still able to boot using the old kernel.
After googling I found that many people corrected this by setting "root=/dev/sdax" (x is number of the root partition, in my case it is 5) in grub.conf. I tried the same and only the mkrootdev error disappeared, the other errors remain (setting "root=/dev/sdax" shouldnt be required in my case since I am able to boot using the old kernel and the entry for the old kernel in grub.conf also uses "root=LABEL=/1").
contents of grub.conf:
default=1
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux WS (2.6.9-new)
root (hd0,2)
kernel /vmlinuz-2.6.9-new swiotlb=65536 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-new.img
title Red Hat Enterprise Linux WS (2.6.9-5.ELsmp)
root (hd0,2)
kernel /vmlinuz-2.6.9-5.ELsmp swiotlb=65536 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-5.ELsmp.img
title Red Hat Enterprise Linux WS-up (2.6.9-5.EL)
root (hd0,2)
kernel /vmlinuz-2.6.9-5.EL swiotlb=65536 ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-5.EL.img
title Other
Using e2label I found that the partitions are labeled correctly.
How do I solve this problem?
The error messages could probably be because the newly created initrd image does not include SATA drivers for the HDD. I am unable to find out how to build a new initrd image that includes the SATA drivers.
Any help will be greatly appreciated.
Thanks,
shani