Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

When previous boot was failed. (because of power failure, hardware failure) booting will hang at the grub menu for human prompt.

Can you set option to force boot up no matter what happened?

share|improve this question

migrated from stackoverflow.com May 13 '11 at 13:05

This question came from our site for professional and enthusiast programmers.

add comment

3 Answers

up vote 5 down vote accepted

Ok I found solution myself via shlug mail list.

what you do is to modify the /etc/grub.d/00_header and find:

if [ "${recordfail}" = 1 ]; then
  set timeout=-1
else
  set timeout=3
fi

change timeout = -1 to 0.

-1 means manual selection.

also remember to update-grub afterward, to generate the actual grub.cfg

share|improve this answer
add comment

This was reported as bug #841009 for ubuntu. I tried setting -1 to 0, but didn't work for me. So i tried another solution given here: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/841009

Quote:

[...] solution is to set GRUB_HIDDEN_TIMEOUT=-1 as suggested on ubuntu forums at this page http://ubuntuforums.org/showthread.php?t=1403517 but i've not tried this solution yet.

Quote:

grub2 in ubuntu 9.10 server is configured by default with GRUB_HIDDEN_TIMEOUT=0. If there is no keyboard attached (as in my headless setup), this causes grub2 to go to menu and stay there. Setting it to -1 gives me the desired sequence of menu, timeout and default choice.

I don't know if this is a grub2 bug or not, but if this is intended grub2 behavior, the default config for a server distro such as ubuntu server (which you would expect to function headless out of the box) should be different.

It worked for me.

share|improve this answer
    
Sure sir. The thing is, that link belongs to launchpad that is why i dint tried to illustrating the problem more and pasted the link. But i will surely keep that in mind from the next time. Thanks. –  streak Jul 17 '13 at 8:25
add comment

Add

GRUB_RECORDFAIL_TIMEOUT=0

to /etc/default/grub and that is solved my problem on Ubuntu Server 12.04.4

share|improve this answer
    
This answer would be better if it contained some information about what the possible values of GRUB_RECORDFAIL_TIMEOUT mean, and what the default is, if it is not specified. –  kasperd May 27 at 14:19
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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