Bug 831503 - Kernel panic after upgrade with kernel-3.4.0-1.fc17
Kernel panic after upgrade with kernel-3.4.0-1.fc17
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-13 03:15 EDT by Honza Horak
Modified: 2012-06-13 15:08 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-13 15:08:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Honza Horak 2012-06-13 03:15:46 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):
kernel-3.4.0-1.fc17.x86_64

How reproducible:
every-time

Steps to Reproduce:
1. install kernel-3.4.0-1.fc17.x86_64
2. try to boot
3.
  
Actual results:
kernel panic

Expected results:
no panic

Additional info:
kernel-3.4.2-1.fc17.x86_64 installed right from koji works fine

My smolt profile:
http://www.smolts.org/client/show/pub_7992309d-a97b-47e1-accb-7091267c0084
Comment 1 Josh Boyer 2012-06-13 08:55:00 EDT
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?
Comment 2 Honza Horak 2012-06-13 15:08:25 EDT
(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.

Note You need to log in before you can comment on or make changes to this bug.