[Bug 669481] Re: Timeout should not be -1 if $recordfail

Launchpad Bug Tracker 669481 at bugs.launchpad.net
Sat Sep 29 08:57:13 UTC 2012

This bug was fixed in the package grub2 - 1.99-21ubuntu3.4

grub2 (1.99-21ubuntu3.4) precise-proposed; urgency=low

  * Revert 1.99-21ubuntu3.2 again,as it was erroneously included again
    in 1.99-21ubuntu3.3.

grub2 (1.99-21ubuntu3.3) precise-proposed; urgency=low

  [ Ben Howard ]
  * Parameterization of recordfail setting. This allows users to define the
    default time out of GRUB when recordfail has been set. The current
    setting causes hangs on headless and appliances where access to the
    console is limited or prohibited.  (LP: #669481)

grub2 (1.99-21ubuntu3.2) precise-proposed; urgency=low

  * Revert previous SRU. This caused AMI cloud images to prompt about the
    changed configuration file, breaking automated upgrades. (LP: #1009294)
  * This reopens bug #978464, which will break Ubuntu 10.04->12.04 upgrades
    if user does not opt-in to reinstall grub-pc bootloader when prompted.
 -- Clint Byrum <clint at ubuntu.com>   Wed, 12 Sep 2012 12:04:59 -0700

** Changed in: grub2 (Ubuntu Precise)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.

  Timeout should not be -1 if $recordfail

Status in “grub2” package in Ubuntu:
  Fix Released
Status in “grub2” source package in Precise:
  Fix Released

Bug description:
  Binary package hint: grub2

  SRU justification

  If a system fails to boot to the point where it runs /etc/init.d/grub-common, then a subsequent reboot will leave the system  at a grub prompt which waits indefinitely for user input.  Systems such as cloud instances or other headless systems may not be able to provide the necessary input to grub, which results in unavailable system.

  [Test case]
  A thorough test case is mentioned in comment #8 and has been used to confirm that the Quantal fix was applicable.

  One shortcut to testing the fix is to disable execution of /etc/init.d
  /grub-common by doing :

  $ sudo chmod -x /etc/init.d/grub-common

  Without the fix, a reboot will result in the instance waiting at the
  GRUB prompt. With the proposed fix, it will boot normally.

  [Regression Potential]
  There is little potential as without intentional modification of /etc/default/grub, the variable defaults to its previous value of -1.

  My experience is that $recordfail is not always written successfully,
  which is by default tested in grub.cfg (through grub.d/00_header)

  This causes grub2 to set timeout=-1 which removes the timeout for
  bootup in these cases.

  On computers which have not been configured for "USB Legacy" in the
  BIOS but use USB keyboards, this looks as if grub has frozen - because
  the keyboard does not respond. The consequence is that the computer
  won't boot without either knowledge on how to configure BIOS (and
  what) or using a PS/2 keyboard (not always available or possible to

  My suggestion is that Ubuntu recognizes $recordfail but instead of
  disabling timeout (-1) it should be set to a relatively high value
  (such as 10 seconds). This will be enough to alert the user on what
  option is booting, and that the computer hasn't frozen, as well as
  enabling false/known failures to be ignored.

  Maybe a future addition to recognising $recordfail is to have a
  warning on the boot menu, but that is outside the scope of this

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: grub-pc 1.98+20100804-5ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae
  Uname: Linux 2.6.35-22-generic-pae i686
  Architecture: i386
  Date: Mon Nov  1 15:33:30 2010
  InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: grub2

  Related bugs:
   * bug 1035279: instance hangs at grub prompt after reboot followed by euca-reboot-instances
   * bug 872244: grub2 recordfail logic prevents headless system from rebooting after power outage

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list