Hide Forgot
Description of problem: kernel-3.1.0-0.rc9.git0.3.fc17.x86_64 fails to boot; gives kernel panic and call trace. Version-Release number of selected component (if applicable): kernel-3.1.0-0.rc9.git0.3.fc17.x86_64 How reproducible: every time Steps to Reproduce: 1.try to boot 2.fails 3.boot under rc9.0.1 Actual results: Kernel panic - not syncing: VFS: unable to mount root fs on unknown_block(0,0) Call Trace: [<ffffffff814f9e7a>] Panic +0xa0/0x1b9 [<ffffffff81d5402a>] mount_block_root +0x250/0x27b [<ffffffff81d540a8>] mount_root +0x53/0x57 [<ffffffff81d541e9>] prepare_namespace +0x13d/0x176 [<ffffffff81d53106>] kernel_init +0x159/0x15e [<ffffffff8150dd84>] kernel_thread_helper +0x4/0x10 [<ffffffff81505af4>] ? retint_restore_args +0x13/0x13 [<ffffffff81d53bbd>] ? start_kernel +0x3ea/0x3ea [<ffffffff8150dd80>] ? gs_change +0x13/0x13 Expected results: system boots Additional info:
This is almost certainly because no initrd got created for your kernel, or the line specifying the initrd is missing in GRUB.
Interesting. Not sure why/how that could happen since it was installed via rpm using yum so the rpm install updated menu.lst and should have included the initrd or built it on the fly, no?
Interesting. The line: initrd /initramfs-3.1.0-0.rc9.git0.3.fc17.x86_64.img was missing from /boot/grub/menu.lst. Don't know how that could happen since it rc9.git0.3 was installed by the rpm and the menu.lst should have been updated accordingly.
0.3 boots fine now that I've added the initrd line to menu.lst. Perhaps a bug in the rpm, don't know.
I had the same thing occur recently with 0.0.fc16: https://bugzilla.redhat.com/show_bug.cgi?id=746435 I closed the bug once I realized what the issue was and fixed it. I was not able to reproduce it, so I guessed it was something about my config, but it seems like it may be something that is occurring intermittently.
I have same problem with rc9.git0.3.fc17.i686.PAE and rc10.git0.1.fc17.i686.PAE yum doesn't add initrd string to /boot/grub/menu.lst last kernel with initrd string was rc9.git0.0.fc17.i686.PAE
Yes, I had the same problem with the rc10 kernel release as well. However, I seem to remember a yum update about the same time. But it should be the kernel rpm post processing that adds the initrd line, right? And what about grub2's cfg file? Will that be updated if I'm using that or not yet?
This is due to a bug in the "grubby" package, which is what the kernel calls to update the GRUB configuration. Unfortunately the change made to F16 to require a later version of grubby was not made in F17. 3.1-rc10-git1 will require grubby 8.3-1, which does not have this bug.