grub2 menu stays until I press enter

[BavarianPH]

Binary package hint: grub2

Ubuntu 9.10 Karmic Koala beta

grub2~1.97-beta4-1ubuntu3

grub2 menu stays until I press enter.

grubenv reads: recordfail=1

My understanding is, that it should only read "1" if there was a boot problem

or a "suspend / hibernate" problem.

The OS does put PC into "suspend" mode, & I can awaken it from there.

However, I have set "Never" mode for both PC & Monitor (in Power Management),

so it should not put the PC into "suspend" in the first place.

But Grub2 apparently is told that the PC failed, because if I manually put recordfail=0

it always changes back to recordfail=1, & thus the grub2 menu appears indefinitely,

until I press enter.

I have devised a work-around that fixes the symptom but not the actual bug:

by adding the following to the bottom of the /etc/grub.d/40_custom script:

fi
if [ ${recordfail} = 1 ]; then
  set timeout=3
else
  set timeout=0
fi
# end

in this way if there was a problem with booting or suspend / hibernate

one has whatever timeout one adds to this script,

& if grubenv were set with recordfail=0 it would boot without delay.

As I wrote, it does not fix the actual bug, & perhaps it really is two bugs.

one in ACPI managing, & the other in not resetting grub2 recordfail.

as to "Required input missing": I was unable to use the "Record a problem..."

program, it refused to start, so I used: sudo ubuntu-bug grub2, to report.

I could not find this exact bug described, so a new bug report may help.

I have attached grub.cfg, which of course shows the altered 40_custom.

BavarianPH,

Ubuntu forever!

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 3bb3e9fd3b939fdb7916d5535ab9761d
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Wed Oct 28 14:15:58 2009
DistroRelease: Ubuntu 9.10
Package: grub2 1.97~beta4-1ubuntu3
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
SourcePackage: grub2
Uname: Linux 2.6.31-14-generic-pae i686

[BavarianPH (bavarianph)]

Latest development:

After a clean install of Karmic 9.10 (which deleted the beta version)

grub2 behaves as it should, boot problems solved, for my PC anyway,

Asus P5E-VM HDMI, Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz.

(Suspend / hibernate problem still remains, [thought to have influenced grub2])

I will nominate for release.

BavarianPH,

Ubuntu forever!

[Emmanuel PARANT (emmanuel-parant)]

Hi everyone !

I confirm this bug, which affects me after a clean install of Karmic 9.10 (Xubuntu version)

Just after the install, everything was working fine, the problem appeared when I decided to change the timeout value in /etc/grub/default, and do the update-grub

I temporary modified /etc/grub.d/00_header to temporary solve the problem, but the bug is stil active.

Thanks for reading !

Regards

Emmanuel

[pjw (pjw1965)]

I do have the same problem.
In my case the problem is, that
/etc/init.d/grub-common
is not any more executed, which would recordfail set back to 0.
In fact no init script is executed since last update of upstart!

ii grub-common 1.97~beta4-1ub GRand Unified Bootloader, version 2 (common
ii upstart 0.6.3-11 event-based init daemon

[pjw (pjw1965)]

Could someone please comfirm my expirience. And if so, mark this as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/497299

[pjw (pjw1965)]

In bug #497299, I found out, that /etc/network/interfaces was missing or wrong. Because of this, no "net-device-up IFACE=lo" was generated, which is needed to start all old sysinit scrips, like /etc/init.d/grub-common, which resets recordfail back to 0.
Please confirm, if you have the same.

[chaying (me-buss777)]

"In bug #497299, I found out, that /etc/network/interfaces was missing or wrong. Because of this, no "net-device-up IFACE=lo" was generated, which is needed to start all old sysinit scrips, like /etc/init.d/grub-common, which resets recordfail back to 0.
Please confirm, if you have the same."

I confirm : the lo interface MUST be defined as "iface lo inet loopback" and the eth0 on "auto" : and then evereything works fine.
The modifications in /etc/default/grub are taken.

[Santiago Roland (santiago-roland)]

After a fresh install of ubuntu and all updates and new kernels, grub menu stays forever, i tried to modify this by using startup manager but with no effect, so i'm also affected by this bug.

regards.

[cmcginty (casey-mcginty)]

[SOLVED] If you are having this bug, try running the command in the console to unset the "recordfail" value:

grub-editenv /boot/grub/grubenv unset recordfail

[cristian.tarsoaga (cristian-tarsoaga)]

problem still present in 13.04, one solution is to add this to /etc/default/grub

GRUB_RECORDFAIL_TIMEOUT=2

Grub seems to be using two separate timeouts, one for clean reboot and one for 'recordfail'.
The default for recordfail case is -1 (infinite) it totally unappropriate for a (headless!?) server.

see also bug 65787

[Karin Willers (karin-n)]

I am also affected by this, seing this in 13.10. I can reproduce the behavior by executing an

echo "disk" >/sys/power/state

which always brings me to the Grub menu after waking up the system from S4. If I execute the command from entry #9 above:

grub-editenv /boot/grub/grubenv unset recordfail

before going to suspend-to-disk, the wake-up boots the system works ok. Interestingly enough, /boot/grub/grubenv does NOT have 'recordfail' set before and after the unset command ...

[Karin Willers (karin-n)]

BTW, I had to execute the 'grub-editenv'command for every suspend-to-disk.

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]