RC Total crash with factory-new HDD that has no "disk label" set

Bug #153418 reported by Grizzly
10
Affects Status Importance Assigned to Milestone
gparted (Baltix)
Invalid
Undecided
Unassigned
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity, gparted

Insert a brand new (s-ata) HDD that has no "disk label" set (as reports gparted-live cd).
When using "manual partitioning" in the live install, the installer of 7.10 RC will crash.
After using gparted live cd, setting the disk label to "msdos" and making one "sda1" partition and rebooting the liveCD, partitioning and installation was possible.

NB: I also had to boot to "safe graphics" because nvidia tend to crash in normal mode, and I used amd64x2 "asus pundit" barebone with onborad nvidia

Tags: hdd new ubiquity
Revision history for this message
Grizzly (sven-witterstein) wrote :

How can I switch "baltix" to "ubuntu" ?

description: updated
description: updated
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Jaunty Jackalope. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

summary: - [gutsy] RC Total crash with factory-new HDD that has no "disk label" set
+ RC Total crash with factory-new HDD that has no "disk label" set
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Changed in gparted (Baltix):
status: New → Invalid
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Hardware test; 400 MHz P2; 256MB RAM; NVidia/SGS Thomsom Riva 128 w/4MB memory

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Lucid Lynx. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Changed in ubiquity (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Grizzly (sven-witterstein) wrote :

Nice to hear that after two years this has been sorted out. Very pleased, indeed. LP rocks (even if I did not have any disks lying around last year to test it with intrepid or the like!

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.