For me... solved it by noticing that after I use
sudo umount /boot
the command
ls /boot
still showed directory content. Therefore, every adjustment to the file
/etc/default/grub would be written to the directory on /dev/sda1 that is
mounted over my boot directory on /dev/sda3. However, during
Same issue for the first time now on
Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-46-generic x86_64)
Do I have to change
GRUB_CMDLINE_LINUX_DEFAULT=
and why ?
Power Penguin
below my config
--
# If you
and again ..we are not alone ?
http://askubuntu.com/questions/580082/ubuntu-14-04-rebooting-not-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for keystroke
Same issue but different answer ...why ?
http://michalorman.com/2013/10/fix-ubuntu-freeze-during-restart/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for
Not sure if this will help but the start of my /etc/default/grub looks
like this:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
Just rebooted with a screen on it and it reboot with out touching the
keyboard.
I have Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-39-generic
x86_64)
Not sure what I did to fix it because I did not test a reboot right
after the fix.
-Raymond Day
--
You received this bug notification
Running a (headless) Ubuntu 12.04.1 server too. Looks like after a
update have to press enter for it to boot up.
Any one know of a fix?
-Raymond Day
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We are also having this problem on 14.04.1 LTS.
Extremely frustrating and completely pointless for a (headless) server-
OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits
I just want to add my voice that I spent hours of intense frustration
dragging a headless server back and forth between the desk where I have
a keyboard and screen and the room in lives in, all because of this
issue. This looks like a totally random bug if GRUB isn't communicating
to you why its
Some machine with 2 different VM ,
debian 7.6 wheezy 3.2.0.-4 works fine but
on ubuntu 14.04 server 3.13.0-12 manually boot :/ .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
Still happens with 14.04
The default should be... the system boots.
It should be hard, if not impossible, to change that default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2
14.04 hangs and waits for key stroke. A headless server is not supposed
to do that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for keystroke before booting
/manualy work/ = key stroke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for keystroke before booting default OS. headless
server. hang.
To manage
Yes this issue still happons in 14.04.
We have an issue with our storage on an ESX enviroment ~100+ guest systems were
forced to hard reboot.
All the windows and centos systems had no issues, ubuntu was stuck at the grub
screen and required manualy work.
This is crap and is bad for the ubunut
I don't understand what the status with 14.04 is.
Are there still cases where that might wait for a key stroke?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for
I spent about 15 hours trying to figure out why my headless Ubuntu 14.04
Beta server wasn't booting. No IPMI or remote hands were available in
this case, unfortunately. I finally got on the right track when I
noticed in my identical test VM that grub2 wasn't always automatically
booting the
And the reason for my troubles? I imaged my Ubuntu VM (for remote
deployment elsewhere) after powering it off during the earliest stages
of a boot. A strange form of a power outage. I would've never
guessed a feature designed to avoid reboot loops would come into play.
--
You received this
Just to follow-up on my last comment.
I was unable to try the solution as grub would not see the Linux OS after a
grub-install on /dev/sda, and omitting to run update-grub right afterwards.
I struggled with a live-USB to fix grub, but after several hours, I ended just
re-installing the whole
This is still an issue on Ubuntu 12.10
I used the XBMCBuntu iso, which installs a custom version of 12.10, and
this issue persists regardless of clean/forced reboot.
I have tried editing the /etc/grub.d/00_header, but it did not help.
I will try the suggestion in post #11 and let you know how
The default should be... the system boots.
It should be hard, if not impossible, to change that default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for
This feature makes no sense to me. I've been using Linux on servers
since Slackware came on a stack of floppies. Any sysadmin worth their
salary will tell you it's an extremely bad decision to let the server
hang if it was improperly shut down. I want my servers to come back
online after an issue,
This has been fixed with 12.10 and a SRU for 12.04 landed today.
To apply the fix, simply put:
GRUB_RECORDFAIL_TIMEOUT=5 in /etc/default/grub
And then run: update-grub
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: grub2 (Ubuntu)
Milestone: None =
Horrible. We do not see this idiocy on Debian Systems, it is an UBUNTU
problem. Apparently they re-packaged it without knowing what they are
doing. Mint exists because why. Please make your changes much miloder,
and concern yourself with the source. If they aren't doing it, then
your new ideas
*milder ... sorry for the rant too but I've been venting awhile. I
think many people have. Stop reinventing the wheel please and follow
your own upstream - they already do most of the work for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In my case, i'm convinced that recordfail is set due to an issue with
the SD-MMC card reader of my HP Pavilion g6, which persists even after
installing grub with --recheck. Changing timeout on 00_header solved the
problem.
Thanks!
--
You received this bug notification because you are a member
To work around problem 2), see this: bug 872244
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for keystroke before booting default OS. headless
server. hang.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (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/797544
Title:
grub2
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797544
Title:
grub2 waits forever for keystroke before booting default OS. headless
4) you have a serial port
# cat /etc/grub.d/03_serial
#!/bin/sh
echo serial --unit=0 --speed=115200
echo terminal_input --append serial\; terminal_output --append serial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See also
http://serverfault.com/questions/243343/headless-ubuntu-server-machine-sometimes-stuck-at-grub-menu
http://ubuntuforums.org/showthread.php?t=1312798highlight=grub
http://ubuntuforums.org/showthread.php?p=10940949#post10940949
http://ubuntuforums.org/showthread.php?p=10940951#post10940951
Versions:
grub-common 1.98+20100804-5ubuntu3
grub-pc 1.98+20100804-5ubuntu3
Again, asking for urgent on this one, as it really affects servers in
a major way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See also
https://help.ubuntu.com/community/Grub2#Boot Display Behavior
Which more or less documents part of this behavior. But remember I get this on
clean boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SOLVED (sort of):
We found three causes of the headless server waits forever for someone
to press a key problem with grub2:
1) apt-get updgrade can trigger grub-setup. If by chance there happens to
be a USB drive attached with Linux on it... grub will find it. And suddenly
you have two OS's
33 matches
Mail list logo
