This bug was originally fixed on the basis that by adding
GRUB_RECORDFAIL_TIMEOUT users could work around the issue. The fix
worked as expected, but users are still hitting the issue without having
tuned this value. I thought it would be easier to track a new issue
about the default specifically in
This isssue is still persist on headless Ubuntu 14.04.2 LTS server.
Need to edit and update grub with GRUB_RECORDFAIL_TIMEOUT=2 option to
avoid the boot stuck.
I wish Ubuntu comes with built-in GRUB_RECORDFAIL_TIMEOUT=2 as default.
:)
--
You received this bug notification because you are a memb
--- Releasing grub2 ---
Proposed: 1.99-12ubuntu5.1
Release: 1.99-12ubuntu5
Copied to oneiric-updates
** Changed in: grub2 (Ubuntu Oneiric)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~ubuntu-branches/ubuntu/oneiric/grub2/oneiric-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notificati
fix confirmed for Oneiric as well, with latest grub2 in -proposed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
T
Hello Mikael, or anyone else affected,
Accepted grub2 into oneiric-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/grub2/1.99-12ubuntu5.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
** Branch linked: lp:~ubuntu-core-dev/ubuntu/oneiric/grub2/oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifications about
** Branch linked: lp:~ubuntu-core-dev/ubuntu/precise/grub2/precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifications about
** Branch linked: lp:~louis-
bouchard/ubuntu/oneiric/grub2/grub2-lp669481-oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notif
** Also affects: grub2 (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Oneiric)
Importance: Undecided => Medium
** Changed in: grub2 (Ubuntu Oneiric)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ub
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
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifications abo
Hello Mikael, or anyone else affected,
Accepted grub2 into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/grub2/1.99-21ubuntu3.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Here is the debdiff for the requested SRU of the Quantal fix to Precise
** Patch added: "grub2_1.99-21ubuntu3.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/669481/+attachment/3270453/+files/grub2_1.99-21ubuntu3.3.debdiff
--
You received this bug notification because you are
** Description changed:
Binary package hint: grub2
+
+ SRU justification
+
+ [Impact]
+ 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 clo
** Branch linked: lp:~louis-bouchard/ubuntu/precise/grub2/grub2
-recordfail-timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage not
** Branch linked: lp:~louis-bouchard/ubuntu/precise/grub2/grub2
-recordfail-timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage not
after 'update-grub', you should also run:
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure grub-pc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
For anyone watching this bug, the easy fix here for 12.10 and later (we intend
to backport to 12.04) is:
echo GRUB_RECORDFAIL_TIMEOUT=0 | sudo tee -a /etc/default/grub
sudo update-grub
the 'update-grub' is necessary to make the change take affect, and also
to avoid a config-file prompt on grub
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Tags added: cloud-images cloud-images-build
** Changed in: grub2 (Ubuntu Precise)
Status: New => Triaged
** Changed in: grub2 (Ubuntu Precise)
Importance: Undecided => Medium
--
You received this b
While fixed for Quantal, Precise still suffers from this issue. Since
it's the latest LTS release - and thus used for most of the servers out
there - it would be great to see this backported as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This bug was fixed in the package grub2 - 1.99-22ubuntu1
---
grub2 (1.99-22ubuntu1) quantal; urgency=low
[ Colin Watson ]
* Resynchronise with Debian. Remaining changes:
- Adjust for default Ubuntu boot options ("quiet splash").
- Default to hiding the menu; holding down
** No longer affects: ubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifications about this bug go to:
https://
** Branch linked: lp:~utlemming/ubuntu/precise/grub2/param-recordfail-
timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifica
Submitted merge propsosals that parameterize this behavor.
** Branch linked: lp:~utlemming/ubuntu/quantal/grub2/param-recordfail-
timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
** Branch linked: lp:~utlemming/grub2/param_recordfail_timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notifications about this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should not be -1 if $recordfail
To manage notif
Same issue here. Very annoying and embarrassing when maintaining an
Ubuntu server for a client. I was using the same fix Sean DS posted but
the issue returned after I upgraded the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Temporary fix: in /etc/grub.d/00_header line 242 change the timeout from
-1 to any positive integer for a quick workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669481
Title:
Timeout should
Like others who have commented, I am also affected by this bug, to save
juice I use rtcwake and have been careful to remove recordfail
altogether, however when I left my computer this Christmas something had
reverted and after two hibernates it was back to sitting on the GRUB
screen 200 kilometers
This is also a problem for MythTV. The system automatically powers
on/off to record TV programs. This issue can mean the machine fails to
boot and therefor will miss recordings. It also means the machine will
be stuck in this state for the duration. Particularly bad if you are on
vacation!
--
Same problem here. I've suffered from the servers which are stuck in the
GRUB phase occasionally. Now I know the reason. The recordfail feature
can be a useful, but setting the timeout to -1 is too excessive in my
opinion.
As the above stated, changing it to a reasonable value, or at least
making
Bump - though I don't have to drive 40 miles, I do have to plug a
keyboard and monitor into my robot which otherwise needs neither. If I'm
using it in the field that means I have to lug this extra equipment with
me all the time. :/
--
You received this bug notification because you are a member of
This is a major problem. Some times if there is a power failure, or some
kind of other problem like a kernel oops, you send a reboot request to
the server and it never boots because of this timeout -1 :/
I had to drive 40 miles to plug a keyboard in and press enter because of
this. Please, please,
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
--
Timeout should not be -1 if $recordfail
https://bugs.launchpad.net/bugs/669481
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
--
Timeout should not be -1 if $recordfail
https://bugs.launchpad.net/bugs/669481
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
37 matches
Mail list logo
