| 2015-03-30 15:38:17 |
Fred |
bug |
|
|
added bug |
| 2015-03-30 15:40:18 |
Fred |
bug |
|
|
added subscriber Michael Larabel |
| 2015-03-30 15:40:31 |
Fred |
removed subscriber Michael Larabel |
|
|
|
| 2015-03-30 15:40:41 |
Fred |
bug |
|
|
added subscriber Michael Larabel |
| 2015-03-30 15:42:14 |
Fred |
description |
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 |
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 |
|
| 2015-03-30 15:42:59 |
Fred |
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 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 |
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 |
|
| 2015-03-30 16:08:47 |
Steve Langasek |
affects |
grub (Ubuntu) |
grub2 (Ubuntu) |
|
| 2015-03-30 16:08:47 |
Steve Langasek |
grub2 (Ubuntu): status |
New |
Invalid |
|
| 2015-07-07 15:01:48 |
Robie Basak |
marked as duplicate |
|
1443735 |
|
| 2015-07-19 15:05:06 |
Fred |
removed subscriber Fred |
|
|
|
