Choosing smallest possible partition size for resizing a NTFS partition during installation breaks MBR and install

Bug #155608 reported by AmpliFuzz
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu 7.10 final
Installing on a Dell C400 laptop, 768mb RAM, with 30gb hd, one XP NTFS partition spanning the whole disk.

I tried the 'resize partition' option. It was just a test install, so I've chosen the smallest possible size (100% on the slider bar). Setup begins copying files, but near the end a 'disk full' warning bubble appears and the installer quits/crashes. At this point the MBR and boot sector are already changed, but GRUB is not installed, so I rebooted to a dead XP. The actual data on the disk was fine, so the resizing worked, but the boot sector was FUBARed.

No amount of fiddlin' with the XP recovery console fixed the non-booting XP problem. I just deleted the Ubuntu partitions with it and re-tried an install with a bigger partition size.

Choosing an adequate size for the Ubuntu install completed the install and, installing GRUB successfully, revived the Windows install too.

BTW, the slider bar for the resize option really isn't very clear about what it really is doing, the sizes of the partitions that it will create, if the size refers to the old partition or the new ones, etc. A help button would be nice.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in ubiquity.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can you please add the information requested at [WWW] https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments. Thanks in advance.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
Iulian Udrea (iulian) 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. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thank you,

Iulian

Changed in ubiquity:
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.