Bug 443289
| Summary: | grub error 2 on new installation of fedora 9 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rand All <randalla> | ||||||
| Component: | grub | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 9 | CC: | jvalverde | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-05-04 19:01:36 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
Rand All
2008-04-20 09:14:17 UTC
Created attachment 303044 [details]
Fedora 8's copy of menu.lst
Created attachment 303045 [details]
Fedora 9's copy of menu.lst
I confirm this bug. Older grub can't read new partition created by the F9 installer. I am also getting the same error. I currently have Ubuntu installed and it controls grub, so I chose not to install grub during the Fedora 9 installation. Some folks on fedoraforum.org have confirmed that this occurs only when the Fedora 9 installer is told not to install a bootloader. If the default option is selected (install grub) then it will boot properly. The file not being found is the kernel. This can be seen by booting up, pressing 'C' to enter into grub command mode. Entering the "root (hdx,x)" command is fine. When entering the kernel command, it will give state: "Error 2: Bad file or directory type." I have confirmed that this only occurs if the installer is told NOT to write to
the MBR. I went ahead and ran the Fedora 9 installer again (using the live DVD
for x86_64) and told it to install to the MBR. After installation it was able
to boot without any problem. When I put in my Ubuntu live CD and reinstalled
grub like this:
$ sudo grub
> root (hd1,2)
> setup (hd0)
> quit
I was no longer able to boot Fedora 9 using the grub installed by Ubuntu. I
received the same "Error 2" message whenever Fedora was selected in the grub menu.
A workaround for this is possible. Prior to running the Fedora installer, use a
partitioning tool such as gparted to create a separate partition for /boot.
During F9 installation, do NOT let anaconda reformat the /boot partition (and of
course, do NOT write F9 to the MBR).
Since the /boot partition was created by gparted and not anaconda, other
instances of grub should be capable of reading it, and thus, Fedora 9 will boot
even though the installer did not write to the MBR.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I confirm this is happening with the i386 fedora 9 live CD. I use a MBR on another disk to bring up a grub menu. I then select the boot partition I want to run using configfile /grub/menu.lst. Fails with the above error. Found this link on the web that seems to describe the problem accurately. http://www.linuxplanet.com/linuxplanet/tutorials/6480/1/ Also found this link saying it is not a problem because Fedora has patched the version of grub they use to recognize the 256 byte inodes. http://www.fedoraforum.org/forum/archive/index.php/t-187405.html Perhaps, if a patched version is used to do a grub-install on the mbr it will fix the problem? Using older grub created menus is the issue? This is a problem in the non-Fedora versions of grub not supporting the newer kernel features (256 byte inodes) and so there's really not anything that we can do in Fedora to fix it. Instead, you'll have to get fixes to the grub included in the other distributions |