Ubiquity crashes during partitioning on Intel Imac and wipes out MBR and renders machine unbootable

Bug #532484 reported by Robbt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Basically the Lucid 10.4 desktop install has been crashing and wiping out my entire hard-drive while trying to install besides OSX.

So it happened first that I already had a partition and something similar to this bug happened https://bugs.launchpad.net/bugs/222126

Basically I couldn't get into the system and rEfit didn't see a MBR.

In order to get my machine to boot I had to reinstall OS X and I made more room for Ubuntu and tried again.

This time it crashed during the partitioning and formatting. I had sent in a report but I don't see it on here, so I wanted to follow up with a bug report.

What appears to be happening is even when I have already created the partition and formatted it, ubiquity tries to do something special for the partitions due to it being an apple. It creates a 1 meg BIOS partition and then it can't read the partitions as /dev/sda1 or whatever partition is unreadable by Linux.

It is also unreadable by Mac. So there is something going extremely awry during the partitioning process on the Apple Intel Imac hardware.

If it will help I might go through and do this again, but I also have to figure out the strategy for restoring my backup. Luckily I was able to copy the HFS partition using parted.

Revision history for this message
Timofey Solomko (timofey-solomko-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Timofey Solomko (timofey-solomko-deactivatedaccount) wrote :

Maybe a duplicate of #222126

Revision history for this message
Monkey (monkey-libre) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Monkey (monkey-libre) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. 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 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.