Red Hat Bugzilla – Bug 148931
grub does not remember last booted option after kernel upgrade
Last modified: 2008-02-06 18:33:29 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5) Gecko/20041110 Firefox/1.0
Description of problem:
By default, grub does not remember the last menu entry that was chosen.
This can be changed by adding the line
in the global section of the grub configuration and adding the line
in every kernel / OS section of the grub.conf file
Having done this though, installation of new Kernel RPM's through yum stops this working. It would appear that the
line is removed from the configuration.
Once a kernel upgrade is performed, grub goes back to not remembering the last menu option until the config file is edited.
This can cause serious trouble if you reboot a machine thinking that it will boot using the last menu option that you used, and it doesn't. You can find the machine booting the wrong kernel image for the work you are trying to do, and this can cause problems such as no remote access to machine, etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure grub to remember the last booted option by adding
to global configuration section of grub.conf and adding the line
to every selection section in grub.conf
2. Reboot machine and select menu entry
3. Reboot machine again and note that previously selected menu entry is still selected
4. Install new kernel
5. Reboot machine and notice that new kernel menu option is the default. Choose a different menu option and boot that instead.
6. Reboot machine again and notice that new kernel menu option is still the default.
Actual Results: The newly installed kernel's menu option is the default after every reboot, no matter which menu option was selected
Expected Results: The last used menu item should be the default menu item on bootup.
Have you tried editting /etc/sysconfig/kernel
so that UPDATEDEFAULT=no and retesting with that setting?
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.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding