Description of problem: Eversince I upgraded the kernel on my system after 2.6.17-1.2187_FC5, the system cannot boot with the new kernel. I am attaching the photo I took of my screen after trying to reboot with the newest kernel, 2.6.18-1.2257.fc5. It is also at http://otthon.csi.hu/mw/kepernyo.jpeg Version-Release number of selected component (if applicable): kernel-2.6.18-1.2257.fc5 How reproducible: always Steps to Reproduce: 1. make sure grub will boot kernel-2.6.18-1.2257.fc5 2. reboot 3. Actual results: Kernel panics, and so the computer cannot boot. Expected results: Proper reboot. Additional info: The system is an AMD x86_64. The hardware has not changed in more than a year. The output of lshal is at http://otthon.csi.hu/mw/thales_lshal.txt I have a similar system at home, and there there is no problem running the newer kernels. The output of lshal for my homebox is at http://otthon.csi.hu/mw/otthon_lshal.txt As you see, on the homebox I am running kernel 2.6.18-1.2239.fc5 which is not yet the latest, but my office computer panicked with this 2.6.18-1.2239.fc5 also.
Created attachment 144057 [details] picture of screen when trying to boot
It has been a month since I posted this severe problem, and I do not see any reaction. I am just sending this in case people at RH/FC just forgot about it.
Can you remove "rhgb quiet" from the bootup parameters? That gives a lot more details. To do that, hit 'space' when GRUB shows up, hit 'e' on the kernel, scroll down to kernel .. line, and hit 'e' again. Remove the rhgb and quite. Hit Enter and then 'b'.
Created attachment 146211 [details] the last screen of the unsuccessful boot The last screen after I removed the "rhgb quiet" option
Created attachment 146212 [details] movie of the whole unsuccesful boot This is a MOV file taken with my digital camera.
Thx for looking into this. If there is a better way to capture the bootscreen, let me know. Uploading a 16M MOV file does not look very efficient.
Here is a fix to the problem: mkinitrd -v -f --preload=raid456 /boot/initrd-2.6.18-1.2257.fc5.img 2.6.18-1.2257.fc5 The change I noticed after kernel-2.6.17-1.2187_FC5 is that the raid5.ko module did not exist anymore, but only the raid456.ko module. Since my root partition is on a raid5 array, the bug bit me. Of course, I do not want to recompile initrd after every kernel upgrade, so please either use the --preload=raid456 option at RH or let me know of another hopefully permanent fix.
I just installed the latest kernel kernel-2.6.19-1.2288.2.4.fc5 and the bug is still there. So this thing does not bite anybody else with raid5? How are the kernels for FC6? I do not dare to upgrade to FC6 because of the bug. Will I be able to boot into runlevel 1, and run the initrd fix?
*** This bug has been marked as a duplicate of 211030 ***