Red Hat Bugzilla – Bug 831503
Kernel panic after upgrade with kernel-3.4.0-1.fc17
Last modified: 2012-06-13 15:08:25 EDT
Description of problem:
After I upgraded F16 -> F17 using yum, kernel panics right after boot with message something like:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0, 0)
Pid: 1, comm: mapper/0 Not tained 3.4.0-1.fc17.x86_64 #1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install kernel-3.4.0-1.fc17.x86_64
2. try to boot
kernel-3.4.2-1.fc17.x86_64 installed right from koji works fine
My smolt profile:
I'm guessing you either don't have an 'initrd' line in the grub configuration for that particular kernel, or you didn't get an initramfs generated at all for it.
Do you see an initramfs-3.4.0-1.fc17.x86_64.img file in /boot, and is there a line for it in the grub config file?
(In reply to comment #1)
> I'm guessing you either don't have an 'initrd' line in the grub
> configuration for that particular kernel, or you didn't get an initramfs
> generated at all for it.
> Do you see an initramfs-3.4.0-1.fc17.x86_64.img file in /boot, and is there
> a line for it in the grub config file?
Bingo, both is missing, but I don't understand how it happened.
When I try to reinstall kernel-3.4.0-1 using yum, I get a message, that a newer kernel is installed.
So I tried
# rpm -i --force ./kernel-3.4.0-1.fc17.x86_64.rpm
# grub2-mkconfig -o /boot/grub2/grub.cfg
and now both (line in grub and initramfs file) are installed as expected.
Well, it seems something weird happened, so I'm closing this bug.