My system is not dual boot just single OS UBUNTU 16.04. Prior to making the following changes, the Grub screen would not appear at start-up (OK).

After following these steps from How can I hibernate on Ubuntu 16.04? to enable hibernate in the system menu:

  1. Open terminal and enter;

    sudo nano /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla
  2. add the lines into the empty file;

    [Re-enable hibernate by default in upower]
    [Re-enable hibernate by default in logind]
  3. ^X then Y to save (a filename was suggested and I accepted without taking note).

  4. Reboot for the changes to take effect.

hibernate now works and appears in the menu (OK) but whenever I reboot I now get a Grub menu at start up with a full 30 second timeout (NOK). I tried playing around with the Grub menu timeout settings but still get the full 30 sec timeout. How do I stop the Grub menu from appearing and reduce my boot time to what it was before I made these changes.

Current Grub settings;

GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
  • 1
    Have you tried according to this link, help.ubuntu.com/community/Grub2/Setup#A.2Fetc.2Fdefault.2Fgrub to modify a variable and after that run sudo update-grub
    – sudodus
    Oct 23 '17 at 4:22
  • Thanks sudodus, yes I had tried modifying as suggested in the article. I have noticed that the grub menu appears on some boots and not on others, for this reason it seems like a bug. I am going to continue testing to see if I can isolate the circumstances that contribute to this behaviour.
    – MitchB
    Oct 25 '17 at 11:45
  • If the grub menu appears on some boots and not on others, it can be caused by a mechanism, that causes it to appear because something went wrong during the previous boot (an emergency setting).
    – sudodus
    Oct 25 '17 at 13:54
  • There is a bug report for Ubuntu: bugs.launchpad.net/grub/+bug/1475620 and grub bugtracker:savannah.gnu.org/bugs/?56603
    – Cas
    May 3 '20 at 12:04

I had a 30s Timeout after hibernating, the undocumented setting GRUB_RECORDFAIL_TIMEOUT worked for me:


See this Answer for more Details.

  • 1
    This is what I was looking for with this question askubuntu.com/questions/1090266/…
    – Stewart
    Nov 14 '18 at 20:41
  • 1
    While this answer superficially solves the problem, it creates other problems. See my answer.
    – ysalmon
    Apr 29 '20 at 19:01

I am sorry to downvote the other answer, but the advice there given is unsound as it will change the timeout for when booting failed (due to hardware outage or whatever).

Grub has a special file where it records whether the last boot succeeded or not : initially it records the boot as having failed using a recordfail bit, and the main OS removes that bit when it takes over. That way, if booting failed, on next boot, Grub can detect that its recordfail is still present and give the user more time to check what happens.

But when thawing from hibernation, the OS does not remove that bit. So we have to tell it to by writing a script. A solution would be to put an executable /lib/systemd/system-sleep/10_grub file with content :


case $1 in
                grub-editenv - unset recordfail

Another way is to use a systemd service, as explained there.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.