Bug 606467

Summary: No initramfs in grub.conf - root device not found at boot
Product: [Fedora] Fedora Reporter: Petr Mejzlík <petrmej>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anton, axjslack, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-30 13:28:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
1. configuration of the boot menu; 2. system info; 3. hardware info
none
photo of the kernel panic
none
kernel.tar.bz2 (log of successful fix of the problem and all 3 grub.conf files that existed during the process) none

Description Petr Mejzlík 2010-06-21 17:44:21 UTC
Created attachment 425703 [details]
1. configuration of the boot menu; 2. system info; 3. hardware info

Description of problem:
Booting the default kernel 2.6.33.5-124.fc13.i686.PAE results in kernel panic. The older kernel 2.6.33.3-85.fc13.i686.PAE works, though.

Version-Release number of selected component (if applicable):
2.6.33.5-124.fc13.i686.PAE

How reproducible:
Install Fedora 13, run the update and then reboot.

Additional info:
See the attachment.

Comment 1 Petr Mejzlík 2010-06-21 17:46:32 UTC
Created attachment 425704 [details]
photo of the kernel panic

Comment 2 Stanislaw Gruszka 2010-06-23 15:40:55 UTC
(In reply to comment #0)
> Created an attachment (id=425703) [details]
> 1. configuration of the boot menu; 2. system info; 3. hardware info

Did you edit /boot/grub/grub.conf by hand or work was done by rpm ? There is lack of initrd entry for 2.6.33.5-124 kernel.

Comment 3 Petr Mejzlík 2010-06-23 17:58:57 UTC
(In reply to comment #2)
> Did you edit /boot/grub/grub.conf by hand or work was done by rpm ? There is
> lack of initrd entry for 2.6.33.5-124 kernel.    

It was done by RPM I guess. I made no edits to /boot/grub/grub.conf since I upgraded to Fedora 13. Before, when I had Fedora 12, I added intel_iommu=off there, that's all.

Comment 4 Stanislaw Gruszka 2010-06-24 07:18:10 UTC
Perhaps you have somehow malformed grub.conf and rpm/grubby scripts do not cope well with it. Let's check it:
Copy your grub.conf somewhere. Then uninstall 2.6.33.5-124 kernel by "rpm -e". Copy grub.conf again.Then install kernel again by rpm or yum. See if there is no initrd entry. If so attach all 3 grub.conf's here. Otherwise we have to assumed initrd line was removed by mistake by you :)

Comment 5 Stanislaw Gruszka 2010-06-24 07:56:31 UTC
Seems we really have a problem with initrd on PAE kernels, Alexjan notes it here:
https://bugzilla.redhat.com/show_bug.cgi?id=605845#c6

Comment 6 Stanislaw Gruszka 2010-06-24 08:04:07 UTC
I just installed PAE kernel and have initrd entry in grub.conf. There must be something special on your system or installation process that make no initramfs, do you have any idea what?

Comment 7 Alexjan Carraturo 2010-06-24 09:07:22 UTC
I don't have the initramfs.... i try to reinstall and to remove and install both version (PAE or not) I don't have the file of initramfs

Comment 8 Stanislaw Gruszka 2010-06-24 09:34:08 UTC
Does below command gives any error: 
> new-kernel-pkg --package kernel-PAE --mkinitrd --dracut --depmod --update 2.6.33.5-133.fc13.i686.PAE

Comment 9 Alexjan Carraturo 2010-06-25 21:56:10 UTC
I have used the command that you have indicated (even if I use the 2.6.33.5-124 and not the 133).... and only with that instruction works perfectly all... thank you a lot...

Now, I'm only worried that the problem will come back in next kernel release.... does it's possibile?

Comment 10 Stanislaw Gruszka 2010-06-26 17:21:27 UTC
(In reply to comment #9)
> Now, I'm only worried that the problem will come back in next kernel
> release.... does it's possibile?  

That's I'm trying to find out, if there is some problem with installation scripts.

Maybe there was no space on /boot partition ?

How do you install kernel before, do you remember command you used, it was performed some kind different?

Could you try remove kernel and them install it again, i.e:
# rpm -e 2.6.33.5-124.fc13.i686.PAE
# yum --enablerepo=updates-testing update kernel
And see if that still initramfs is there.

Comment 11 Alexjan Carraturo 2010-06-26 17:48:27 UTC
I have a lot of space in my boot partition.

Usually I have only update the system..

I Will try your advice

Comment 12 Petr Mejzlík 2010-06-26 19:29:29 UTC
(In reply to comment #4)
> Perhaps you have somehow malformed grub.conf and rpm/grubby scripts do not cope
> well with it. Let's check it:
> Copy your grub.conf somewhere. Then uninstall 2.6.33.5-124 kernel by "rpm -e".
> Copy grub.conf again.Then install kernel again by rpm or yum. See if there is
> no initrd entry. If so attach all 3 grub.conf's here. Otherwise we have to
> assumed initrd line was removed by mistake by you :)    

I did that and it fixed the problem, the new kernel now boots correctly. Thanks a lot!

I'm attaching kernel.tar.bz2, which contains all the 3 grub.conf files and a log of what I did in terminal.

Comment 13 Petr Mejzlík 2010-06-26 19:31:35 UTC
Created attachment 427124 [details]
kernel.tar.bz2 (log of successful fix of the problem and all 3 grub.conf files that existed during the process)

Comment 14 Petr Mejzlík 2010-06-26 19:32:35 UTC
Comment on attachment 427124 [details]
kernel.tar.bz2 (log of successful fix of the problem and all 3 grub.conf files that existed during the process)

Comment 15 Stanislaw Gruszka 2010-06-30 13:28:04 UTC
Not found anything suspicous in Petr grub.conf's provided here.

I'm not sure why initramfs was not created. Perhaps this was some script bug that is now fixed.

I'm closing this bug with WORKSFORME resolution. If this will happen again, please reopen bug.