Here are the bugs however, I think I found my problem. I'm booting my OS root partition in read-only mode, so the script can not change the value in /boot/grub/grubenv. If I manually change it, I'm guess it will work.
Last edited by cmcginty; March 28th, 2010 at 10:07 PM.
I think you solved it for yourself.
The first bug report is pretty old. The problems in both is not a timer problem but a problem generating a "recordfail" event. When Grub2 finds a problem, the default is to prevent automatic booting so the user has to make a decision as to what to do next. So the menu is displayed and Grub 2 awaits further input from the user.
Finding the cause of a "recordfail" event can be difficult, but if it's a one-time issue resetting the grubenv may solve things. In your case, the read-only mode may have been causing the problem.
For others with 'recordfail' events, the problem either has to be tracked down or, failing that, the 'recordfail' check has to be disabled. The second option of course isn't the desired one but can get a system booting again without the menu displaying.
I ran into something interesting. Of course you know that grub2 now uses UUID's even for Windows partitions, whereas legacy grub only used the device name, eg: root (hd0,0).
Well here's someone that's cloned an XP and has two Win partitions with the same UUID:
I'm wondering if /etc/grub.d/30_os-prober can be edited in some manner to not use UUID's only for Windows????????????
I wonder if there is an entry possible for MS like the symbolic entries I use for Debian based OS'. It calls for a particular partition. That might work if it is possible.
Dell 480 XPS 3G ram Quad Core 2.40GHz, Radeon HD 2400 PRO, Audigy1, 3x320G HDD, 320G External, Debian Testing for use, Debian Squeeze for secure use, Debian Sid for FUN
Hmm. Just a thought.. if I make the grubenv file RO will grub2 observe it?
Create a custom script and disable the offending script file by removing the executable bit. For instance, if it's writing to a Windows partition, create a 40_custom menuentry for Windows, then disable /etc/grub.d/30_os-prober if you don't have any other OS's on your computer.
Some users use only a 40_custom script, in which case 10_ and 30_ can both be deactivated. In 40_ you can use "/vmlinuz" and "/initrd.img" so that it continues to use the most recent kernel without needing any updates.
If you tell us the target of the disk writes and which script is producing the inputs we might be able to give you more specific ways to alter the scripts.
great guide to Grub 2! Problem is in the "saved" setting for grub_default in Lucid doesn't even work.....how did they screw that up? Linux Mint has Grub all decked out, and saved works....Ubuntu still can't even add graphics to grub, let alone even implement grub with a working SAVED OPTION!!!! I love Ubuntu, I just wish they would stop screwing up the packages, and concentrate on implementing them AS IS!!!!!
PS. Great Guide to Grub 2. Hope to see more updates in the future cuz I'll be watching
As I understand it, "GRUB_DEFAULT=saved" only enables two commands to work: grub-set-default and "grub-reboot".
To get the last selected OS to be 'saved' and used on future boots, you have to use "GRUB_SAVEDEFAULT=true".
Have you tried that second setting?
Glad you like the guide.