Lucid Lynx install: grub failes with /dev/hda4
Bug #153933 reported by
jdo
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: ubiquity
Using the desktop LiveCD to install Gutsy Gibbin failes when grub is installed in /dev/hda4.
The default is (hd0) for grub, but since I use "gag" as a boot manager, I used the 'advanced' button to select '/dev/hda4', where also Ubuntu is installed to. This causes a fatal error for grub-install.
When I open a terminal and try manually installing grub it complains about a missing /boot.
I have two IDE drives, hda is 120GB.
There a many bugs which look like this one, e.g.: Bug #14135
Revision history for this message
| TerryG (tgalati4) wrote | #1 |
| Changed in ubiquity: | |
| status: | New → Incomplete |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| Changed in ubiquity: | |
| status: | Incomplete → Confirmed |
Revision history for this message
| Przemek K. (azrael) wrote | #3 |
| Changed in ubiquity (Ubuntu): | |
| status: | Confirmed → Incomplete |
Revision history for this message
| Charlie Kravetz (cjkgeek) wrote | #4 |
| Changed in ubiquity (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | Incomplete → Confirmed |
| summary: |
- Gutsy Gibbon install: grub failes with /dev/hda4 + Lucid Lynx install: grub failes with /dev/hda4 |
Revision history for this message
| Phillip Susi (psusi) wrote | #5 |
| Changed in ubiquity (Ubuntu): | |
| status: | Confirmed → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #6 |
| Changed in ubiquity (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Triaged to Incomplete. My understanding of GRUB is that it loads the second stage, kernel, and initrd to the desired partition, but it still must modify the MBR to load the first stage. Since you are using a different boot loader (gag), and I am not familiar with it, it's possible that a bad interaction would occur. I don't see a way around this without using GRUB to manage the bootup or perhaps modifying gag's configuration file.
Since this is a rare use case, I don't see ubiquity being modified to detect and handle a different boot loader other than GRUB. Perhaps a few lines of ubiquity code could check for other boot loaders and then exit gracefully.