No notification in Ubiquity for bad sectors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Baltix) |
New
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Installing Edgy on an IBM A22m Thinkpad, Ubiquity would seemingly hang when either:
a) attempting to resize an NTFS partition for the install or
b) halfway though copying files if / partition already created before running desktop installer
Looking in syslog I noticed ubiquity was detecting bad sectors on the HDD, but it does not relay this information to the end user. Using the alternate CD for the install, a large red box will appear telling the user that the HDD is bad, as opposed to just hanging.
I think notifying the user via the UI that bad sectors have been found would at least help the user know why the installer has hung.
Oddly enough Windows will happily install and run on this HDD, even though chkdsk will consistently find errors/bad sectors.. I guess Linux is a little more picky on what it will install on?
tags: | added: ubiquity-1.2.5 |
tags: | added: edgy |
Changed in ubiquity (Ubuntu): | |
status: | Confirmed → Triaged |
attached is the syslog from an install that attempted to resize the NTFS partion of /dev/hda1