Red Hat Bugzilla – Bug 142401
Grub doesn't read config file after FC2->Fc3 upgrade
Last modified: 2008-02-03 05:04:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Description of problem:
After I upgraded from FC2 to FC3, grub stopped working. Instead of
presenting me with a menu of options from which to choose, it just
dumps me in the grub shell.
It's obviously getting at least as far as stage 1.5, as it understands
the filesystem. From the grub shell, I can just do:
and I get the menu I expect, and can boot as normal. I've played
around with various grub-install invocations and also with setup
directly in grub-shell, but can't convince it to read the config
file on boot -- I still have to manually specify it each time.
I have grub installed in my boot partition, not in the MBR.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the machine
2. Observe lack of menu...
Obviosuly, since the inital flaw manifested itself during the upgrade
process, I can't reproduce that.
I experience exactly the same problem when upgrading from RHEL 3 to RHEL 4
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA", however if you still
experience this problem after updating to our latest Fedora
release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.