Default grub2 configuration won't boot through to default OS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub |
Unknown
|
Unknown
|
|||
grub2 (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Karmic |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: grub-common
The default settings for /etc/default/grub won't allow the machine to boot through automatically to the default OS -- someone must hit <Enter> on the console, which is almost never an appropriate configuration for a server. Here is the default /etc/default/grub:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
GRUB_DEFAULT=0
GRUB_
GRUB_
GRUB_TIMEOUT="2"
GRUB_
GRUB_
GRUB_
with just a bit of trial and error I discovered that a non-zero value must be set for GRUB_HIDDEN_TIMEOUT in order for the machine to boot through to the first OS after timeout; e.g.
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT="2"
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
Looking over the documentation for grub2, it seems clear that GRUB_HIDDEN_TIMEOUT shouldn't have anything to do with whether or not the machine boots through after timeout. I'm guessing this is a grub2 bug? Ubuntu/package versions listed below:
root@ibis:
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
root@ibis:
ii grub-common 1.97~beta2-2ubuntu2 GRand Unified Bootloader, version 2 (common
ii grub-pc 1.97~beta2-2ubuntu2 GRand Unified Bootloader, version 2 (PC/BIOS
Changed in grub2 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub2 (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in grub2 (Ubuntu): | |
assignee: | Colin Watson (cjwatson) → nobody |
Changed in grub2 (Ubuntu Karmic): | |
assignee: | Colin Watson (cjwatson) → nobody |
Patrick: can you update to the current version of grub2 in karmic and do grub-install on your boot device (likely /dev/sda, but possibly not). I am unable to reproduce the behavior you see with the current version of grub2, but I did see it with an earlier install, and updating and installing the newer grub version made that behavior go away. There's also been a fair amount of changes in the handling of GRUB_HIDDEN_TIMEOUT since 1.97~beta2- 2ubuntu2, and I suspect those changes addresses your issue. Thanks.