grub installation fails [cdrom open failed]

Bug #67801 reported by Todd Larason on 2006-10-23
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

I'm trying to install onto a drive with an existing Windows XP install; the partitioning and formatting appears to go smoothly, but grub installation fails.

I can't cut & paste from the traceback, but essentially
/usr/bin/ubiquity line 130
/usr/bin/ubiquity line 55
gtkui.py line 264
gtkui.py line 553
RuntimeError: "Install failed with exit code 1"

Todd Larason (jtl-launchpad) wrote :
Todd Larason (jtl-launchpad) wrote :

Trying again with 6.10 RC gave the same error. Looking in the log file, this time I was able to find the command which had failed; running that command by hand gave an error message to the effect "hdi is not a BIOS drive" (sorry, I didn't keep good notes and that wording proabably isn't quite right). Googling for that gave some hints that device.map might be involved. Trying one more time, I created /target/boot/grub/ as soon as /target was mounted, then created device.map inside that directory with the contents:

(hd0) /dev/hdi

and let installation progress. This time, grub installation succeeded and the rest of the install went smoothly.

I don't know what if anything was supposed to create device.map, or whether it wasn't supposed to be needed, but maybe this is helpful in figuring out the root cause.

Matthew Woerly (nattgew) wrote :

 apologize that no one has gotten back to you about this yet.
Is this problem still present?

Matthew Woerly (nattgew) wrote :

I apologize that no one has gotten back to you about this yet.
Is this problem still present?

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in ubiquity:
status: New → Incomplete
Magnus S (magnuss) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers