Bug 448255
| Summary: | Unreported GRUB installation failure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sam Varshavchik <mrsam> | ||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 11 | CC: | bruno | ||||
| 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: | 2009-10-15 12:39:20 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
Sam Varshavchik
2008-05-25 02:07:34 UTC
Created attachment 306594 [details]
Screen capture of the Anaconda grub install failure
Can you please retest with F11 when it is release and let us know if this is still an issue for you? There's been a significant amount of work involving storage, RAID, and bootloader installation for this release. Thanks. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Retested with F11, problem still exists. After upgrading from F10 to F11, the subsequent reboot threw me into the grub shell. I had to manually mount the partition and load the config file from the grub shell, boot, and rerun /sbin/grub-install, to restore normal boot configuration. After rebooting, I see no errors in /root/upgrade.log. I'll be upgrading more machines from F10 to F11, in the coming weeks, let me know if you want me to grab something while anaconda is still doing its thing. Repeating F10 -> F11 upgrade on another machine, grub failed to install again. I captured the following output on tty5, at the end of the installation process:
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
grub>
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,1)/grub/grub.conf
Error 12: Invalid device requested
grub>
That's the error that's causing grub installation to fail.
Could you please test if http://rvykydal.fedorapeople.org/updates.upgf11.img fixes the issue? What's that -- a replacement installer initrd image? I presume it's 32bit. I do have one more 32 bit machine to upgrade, but I also have several 64 bit machines too, that I need to do. It is runtime updates image (http://fedoraproject.org/wiki/Anaconda/Updates) When installing/upgrading, add boot option: linux updates=http://rvykydal.fedorapeople.org/updates.upgf11.img Tried to upgrade my next machine. * Booted with the given option * Got the "Retrieving update from <url>" message * Grub got installed without errors, however: * On the ALT-F5 screen I spied two messages, verbiage is approximate: Retrieving update from <url> Error mounting /dev/loop7 on /tmp/update.img: (null) This updates.upgf11.img file reads as a gzipped cpio archive. If I did not actually end up loading this update, there was no indication to that effect in the actual anaconda GUI, and on this specific laptop the original bug was not reproduced, but I still have several more machines to upgrade. The alternative explanation is that after failing to loopback-mount the update, anaconda's plan B was to try read the update as a gzipped cpio archive, in which case the update might have worked. (In reply to comment #9) > The alternative explanation is that after failing to loopback-mount the update, > anaconda's plan B was to try read the update as a gzipped cpio archive, in > which case the update might have worked. Yes, that's what happened I think. You can check for the presence of update files during install on tty2 by looking into /tmp/updates directory. Bug from comment #5 should be fixed in version 12.0-1 of anaconda (F12). Thanks for the report. |