[Bug 69176] Re: No notification in Ubiquity for bad sectors
Marcus Tomlinson
marcus.tomlinson at canonical.com
Thu Mar 5 11:52:51 UTC 2020
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/69176
Title:
No notification in Ubiquity for bad sectors
Status in ubiquity package in Ubuntu:
Incomplete
Status in ubiquity package in Baltix:
New
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/69176/+subscriptions
More information about the foundations-bugs
mailing list