[Bug 1438275] [NEW] GRUB_RECORDFAIL_TIMEOUT prevents servers from booting

[Fred]

Public bug reported:

On Ubuntu, if there's a power failure or the system is otherwise left in
a bad state on its last boot, GRUB2 will just hang there indefinitely
waiting for user input to select the kernel to boot and any relevant
kernel command-line options. This is annoying since most of the test
systems are headless so when seeing an unresponsive system the server
operator have to go attach a HDMI display and USB keyboard only to find
out there was no serious system error but just the system hanging at
GRUB for whatever reason at that time.

Michael Larabel have problems booting his Ubuntu server farm due to it
GRUB being configured to use GRUB_RECORDFAIL_TIMEOUT.

According to Michael - Ubuntu seems to be the only major distribution
though dealing with GRUB_RECORDFAIL_TIMEOUT and causing the issues on
the failed boot.

If indeed Ubuntu is the only distribution with this setting, then maybe
it should be changed?

http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Common-
GRUB2-Issue

** Affects: grub (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

+ On Ubuntu, if there's a power failure or the system is otherwise left in
+ a bad state on its last boot, GRUB2 will just hang there indefinitely
+ waiting for user input to select the kernel to boot and any relevant
+ kernel command-line options. This is annoying since most of the test
+ systems are headless so when seeing an unresponsive system I have to go
+ attach a HDMI display and USB keyboard only to find out there was no
+ serious system error but just the system hanging at GRUB for whatever
+ reason at that time.
+ 
  Michael Larabel have problems booting his Ubuntu server farm due to it
  GRUB being configured to use GRUB_RECORDFAIL_TIMEOUT.
  
  According to Michael - Ubuntu seems to be the only major distribution
  though dealing with GRUB_RECORDFAIL_TIMEOUT and causing the issues on
  the failed boot.
  
  If indeed Ubuntu is the only distribution with this setting, then maybe
  it should be changed?
  
  http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Common-
  GRUB2-Issue

** Description changed:

  On Ubuntu, if there's a power failure or the system is otherwise left in
  a bad state on its last boot, GRUB2 will just hang there indefinitely
  waiting for user input to select the kernel to boot and any relevant
  kernel command-line options. This is annoying since most of the test
- systems are headless so when seeing an unresponsive system I have to go
- attach a HDMI display and USB keyboard only to find out there was no
- serious system error but just the system hanging at GRUB for whatever
- reason at that time.
+ systems are headless so when seeing an unresponsive system the server
+ operator have to go attach a HDMI display and USB keyboard only to find
+ out there was no serious system error but just the system hanging at
+ GRUB for whatever reason at that time.
  
  Michael Larabel have problems booting his Ubuntu server farm due to it
  GRUB being configured to use GRUB_RECORDFAIL_TIMEOUT.
  
  According to Michael - Ubuntu seems to be the only major distribution
  though dealing with GRUB_RECORDFAIL_TIMEOUT and causing the issues on
  the failed boot.
  
  If indeed Ubuntu is the only distribution with this setting, then maybe
  it should be changed?
  
  http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Common-
  GRUB2-Issue

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub in Ubuntu.
https://bugs.launchpad.net/bugs/1438275

Title:
  GRUB_RECORDFAIL_TIMEOUT prevents servers from booting

Status in grub package in Ubuntu:
  New

Bug description:
  On Ubuntu, if there's a power failure or the system is otherwise left
  in a bad state on its last boot, GRUB2 will just hang there
  indefinitely waiting for user input to select the kernel to boot and
  any relevant kernel command-line options. This is annoying since most
  of the test systems are headless so when seeing an unresponsive system
  the server operator have to go attach a HDMI display and USB keyboard
  only to find out there was no serious system error but just the system
  hanging at GRUB for whatever reason at that time.

  Michael Larabel have problems booting his Ubuntu server farm due to it
  GRUB being configured to use GRUB_RECORDFAIL_TIMEOUT.

  According to Michael - Ubuntu seems to be the only major distribution
  though dealing with GRUB_RECORDFAIL_TIMEOUT and causing the issues on
  the failed boot.

  If indeed Ubuntu is the only distribution with this setting, then
  maybe it should be changed?

  http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Common-
  GRUB2-Issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1438275/+subscriptions