Bug 86160
Summary: | Anaconda Unhandled Exception while checking for bad blocks | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Timothy Bowers <tbowers> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:52:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Timothy Bowers
2003-03-15 03:46:59 UTC
*** This bug has been marked as a duplicate of 66181 *** This bug was labeled as a duplicate of #66181, yet no solution to the bug has been presented. All I am asking is how to load RedHat Linux 7.3 onto my machine if my hard drive contains bad blocks. If I turn off bad block checking, the install goes as normal until it tries to write data to the bad blocks, then install crashes out and I am left without linux. If the bug is closed or resolved, all I ask is HOW it was resolved, and WHAT I can do to properly install RedHat 7.3 onto my machine. The error in this case was due to poor handling of the detection of bad blocks on the system. If you want to use the drive despite the detection of bad blocks then you can just partition the drive and choose not to select the 'check for bad blocks' option. Understand this is probably going to cause problems later since the drive appears to be failing. *** This bug has been marked as a duplicate of 66181 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |