[Bug 1438275] Re: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting
*** This bug is a duplicate of bug 1443735 *** https://bugs.launchpad.net/bugs/1443735 ** This bug has been marked a duplicate of bug 1443735 recordfail false positive causes headless servers to hang on boot by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438275 Title: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1438275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438275] Re: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting
If you really want to alter the behavior of grub on failed boot, so that it will non-interactively reboot instead of waiting indefinitely, you can also just set a different value for GRUB_RECORDFAIL_TIMEOUT in /etc/default/grub (instead of the default of -1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438275 Title: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1438275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438275] Re: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting
Maybe instead of 'degrading the experience', you can just document the change so that people using this OS for testing systems can automate around it without having to resort to serial port output scanning and lab wiring contortion. In our test environment, we often see a MCE that forces the system to reboot (even with nomce on the kernel cmdline). This often causes the system to reboot and sit at grub. We worked around the issue by adding this to /etc/default/grub: GRUB_TERMINAL='console serial GRUB_SERIAL_COMMAND=serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 Then we can monitor and automate the serial console for when grub gets stuck. It took a while to figure out the correct grub settings as they too were undocumented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438275 Title: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1438275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438275] Re: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting
The behavior you describe is the result of a deliberate design decision, not a bug. - A power cut after the system has fully booted does not result in a GRUB prompt. - A power cut before the system has fully booted is indistinguishable from any other boot failure. The only thing we can say with certainty is that the system failed to boot. We absolutely do not want to try to boot a second time with the same options without giving the admin a chance to interact with the system. If a power cut on a *booted* system is resulting in the user being thrown to a bootloader prompt, that would be a bug. But that is not the behavior being described here. We are not going to degrade the experience for users who need to debug/recover from a failed boot in exchange for optimizing for the unusual case of someone cutting the power in the middle of the boot and expecting a non-interactive subsequent boot. ** Package changed: grub (Ubuntu) = grub2 (Ubuntu) ** Changed in: grub2 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438275 Title: GRUB_RECORDFAIL_TIMEOUT prevents servers from booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1438275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
