Red Hat Bugzilla – Bug 237321
Latest fc5 kernel doesn't boot!
Last modified: 2008-02-27 02:38:29 EST
Description of problem: Version-Release number of selected component (if applicable): 2.6.20-1.2312.fc5 How reproducible: ALWAYS Steps to Reproduce: 1. beginning from kernel version 2.6.18-1.2239.fc5, use yum update and install the version 2.6.20-1.2312.fc5 2. try to boot from selected kernel version 3. doesn't work!!! Actual results: After the lines "Found volume group "VolGroup00" using metadata type lvm2" "2 logical volume(s) in volume group "VolGroup00" now active" we get the messed-up messages, mkrootdev: expected fs options mount: missing mount point setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Expected results: Booting from init, with kernel 2.6.18-1.2239.fc5 we get INIT: version 2.86 booting etc, etc.. instead of the stuff above starting with "mkrootdev..." Additional info: Here is my fstab file, looks normal, /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/sda1 /mnt/windows ntfs ro,defaults,umask=0222 0 0 /dev/VolGroup00/LogVol00 / ext3 defaults 1 2
Please upload your initrd file. The name of the file is in /etc/grub.conf, on the "initrd" line.
Created attachment 153212 [details] initrd file for non-booting kernel as requested.
Created attachment 153215 [details] initrd file for ok (older) kernel
That's the strangest initrd I've seen. Please upload the working one. Last few lines of broken init script: echo Activating logical volumes lvm vgchange -ay --ignorelockingfailure VolGroup00 resume /dev/VolGroup00/LogVol01 echo Creating root device. mkrootdev -t ext3 ext3 -o defaults,ro defaults,ro /dev/VolGroup00/LogVol00 /dev/VolGroup00/LogVol00 echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot
So instead of: mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00 the new initrd has mkrootdev -t ext3<newline>ext3 -o defaults,ro<newline>defaults,ro ...
(In reply to comment #3) > Created an attachment (id=153215) [edit] > initrd file for ok (older) kernel > OK, can you post contents of /etc/fstab? Somehow the parsing of that file has gone wrong.
Here is my fstab file, looks normal, /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/sda1 /mnt/windows ntfs ro,defaults,umask=0222 0 0 /dev/VolGroup00/LogVol00 / ext3 defaults 1 2
Note: The above is with the working kernel version. I cannot access the fstab file with the kernel which won't boot ???!!!?
(In reply to comment #8) > Note: The above is with the working kernel version. I cannot access the fstab > file with the kernel which won't boot ???!!!? Never mind this comment...the fstab file is permanent. I was thinking about the mtab file.
(In reply to comment #7) > Here is my fstab file, looks normal, There are two entries for your root filesystem there. Remove one and everything should work OK after rebuilding the initrd. (And do you have any idea how that happened?) mkinitrd will put both sets of options from both fstab entries into the mkrootdev command it builds. This is the real bug.
Hi, Thanks for the suggestion...unfortunately it still leads to the same result. (I removed the last line from the fstab file I quoted above). Incidentally, I guess that extra mount line for the top filesystem appeared when I looked up how to mount my other partition and cut and pasted the directions. In any case, it hasn't caused any problems thus far.
(In reply to comment #11) > Hi, Thanks for the suggestion...unfortunately it still leads to the same result. > (I removed the last line from the fstab file I quoted above). You need to rebuild your initrd with mkinitrd. (Or just uninstall and reinstall the kernel.)
Thank you very much. It boots fine now !!! There are other issues that I need to resolve though...
This bug seems to have been fixed.