grub2 fails to launch
Bug #391028 reported by
Goh Lip
This bug report is a duplicate of:
Bug #391044: Fresh karmic install does not boot due to grub2 adding --no-floppy to "search " lines.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grub2 (Ubuntu) |
Confirmed
|
Critical
|
Unassigned | ||
Bug Description
karmic 64
linux 2.6.30-9
grub2
Grub2 fails to launch any OS.
Rectified by modifying grub.cfg of the lines
search --no-floppy --fs-uuid --set 4afcadf1-
to
search --fs-uuid --set 4afcadf1-
ie., by removing "--no-floppy"
Note: this was done by launching my hardy partition through a dedicated boot partition(grub legacy)
and modifying the grub.cfg of the karmic partition.
Revision history for this message
| Roderick B. Greening (roderick-greening) wrote | #1 |
| Changed in ubuntu: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
| affects: | ubuntu → grub2 (Ubuntu) |
To post a comment you must log in.
I can confirm this bug. It re-appears, even when editing the grub.cfg (and we shouldn't have to).
This is definitely a critical bug, as it presents the general user with a basically unbootable system (without knowing how to edit grub from the boot menu).