Bug 836695
| Summary: | using grub2-install with grub2-2.00-1.fc18 breaks booting - "error: premature end of file /vmlinuz-3.5..." | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andre Robatino <robatino> | ||||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | alexeypolyakov, bcl, dennis, dsmith, fedora, jayson.rowe, mads, manisandro, mkasik, mschmidt, nphilipp, petersen, pjones, tomek, vserbine | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | grub-2.00-3.fc18 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 838421 (view as bug list) | Environment: | |||||||
| Last Closed: | 2012-07-30 02:58:17 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 752654, 838421 | ||||||||
| Attachments: |
|
||||||||
I'm seeing the same problem. The complete error message from grub looks like this: Loading Linux 3.5.0-0.rc4.git3.1.fc18.x86_64 ... error: premature end of file /vmlinuz-3.5.0-0.rc4.git3.1.fc18.x86_64. Loading initial ramdisk ... error: you need to load the kernel first. As a workaround it is possible to replace "linux" with "linux16" and "initrd" with "initrd16". Then it loads the kernel without problems. In the process of downgrading I ended up removing grub2 before installing the old version. Now the boot menu seems mostly busted (I can't see any of the entries). I think it might be good for testing each grub2 version to fully remove the old version, install the new one, and run grub2-install and grub2-mkconfig, just to catch such problems early. I removed grub2-2.00, removed the leftover /etc/default/grub file, installed the 17 Gold version (grub2-2.0-0.25.beta4.fc17), customized /etc/default/grub, and ran grub2-install and grub2-mkconfig. Booting worked normally at this point. I then updated to grub2-2.00 and ran grub2-mkconfig again (but NOT grub2-install). Booting still works normally. Could you provide information about your install layout? (including filesysems and partitioning info) This is a VirtualBox VM. I used the entire disk when installing, 30 GB image, default partitioning. It should be reproducible on almost any machine. Created attachment 595470 [details]
output of "fdisk -l"
Created attachment 595478 [details]
output of "parted -l"
Easily reproduced immediately after a fresh rawhide install. ie Rawhide installs successfully and then fails to boot as above. A wild shot would be to blame the new grub-2.00-who-trusts-you-and-who-do-you-trust.patch - try to build a grub2 without that patch and see if that shows the same behaviour. (grub-2.00-add-fw_path-search.patch cause other regressions for EFI - but that is probably no the issue here.) A local build of grub2 without grub-2.00-who-trusts-you-and-who-do-you-trust.patch works for me. (In reply to comment #10) > A local build of grub2 without > grub-2.00-who-trusts-you-and-who-do-you-trust.patch works for me. Works for me too, thanks! Wanted to add I got the same trying to install Rawhide on physical hardware. My exact message is: Loading Linux 3.5.0-0.rc5.git3.1.fc18.x86_64 ... error: premature end of file /vmlinuz-3.5.0-0.rc5.git3.1.fc18.x86_64. Loading initial ramdisk ... error: you need to load the kernel first. Press any key to continue... Same here on physical hardware, /boot on ext4, / and /home on xfs. Will check if Mads' suggestion in comment #9 helps me as well. It does help -- asks me for username and password before I'm allowed to boot the kernel, however. As a stop-gap for others affected, here's my scratch build with the patch removed: http://koji.fedoraproject.org/koji/taskinfo?taskID=4230032 This critical issue has been open now for nearly 3 weeks... What is the plan of action?? Still an issue with Rawhide as of today. Will try the grub above if this boot works (been looking at Plymouth with a tty login prompt visible, but not active, for a while). Who votes for untagging grub2-2.00-1.fc18? (In reply to comment #14) > It does help -- asks me for username and password before I'm allowed to boot > the kernel, however. So disabling grub-2.00-who-trusts-you-and-who-do-you-trust.patch? I wonder if the discrepancy with others is due to difference between installing rawhide and just updating kernel for existing install? Anyway really wish something could be done about it this. Breaking rawhide boot for over 3 weeks seems unacceptable to me. (In reply to comment #18) > Anyway really wish something could be done about it this. > Breaking rawhide boot for over 3 weeks seems unacceptable to me. The grub2 package owner rarely (if ever) pays any attention to bugzilla and might not be aware of the issue. Try to contact him directly or through internal channels. (In reply to comment #18) > (In reply to comment #14) > > It does help -- asks me for username and password before I'm allowed to boot > > the kernel, however. > > So disabling grub-2.00-who-trusts-you-and-who-do-you-trust.patch? Yes. (In reply to comment #19) > The grub2 package owner rarely (if ever) pays any attention to bugzilla and > might not be aware of the issue. Try to contact him directly or through > internal channels. How is this acceptable? Please try grub-2.00-3.fc18 , it should be better. (In reply to comment #22) > Please try grub-2.00-3.fc18 , it should be better. Works for me. (Had to grab from Koji since there hasn't been a Rawhide push.) Works for me too from rawhide install. Closing this out. |
Description of problem: If grub2-2.00-1.fc18 is installed, then running grub2-install makes it impossible to boot ("error: you need to load the kernel first."). AFAICT this is the first version of grub2 with this problem. One can recover by booting into rescue mode, downgrading to an earlier grub2 version, and running grub2-install and grub2-mkconfig. Version-Release number of selected component (if applicable): grub2-2.00-1.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. Install grub2-2.00-1.fc18. 2. Run "grub2-install /dev/sda" (or whatever the device is) and "grub2-mkconfig -o /boot/grub2/grub.cfg". Actual results: Can't boot any of the installed kernels.