Bug 65013

Summary: Anaconda dies while checking for bad blocks
Product: [Retired] Red Hat Linux Reporter: Jacob Sparre Andersen <sparre>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-16 00:28:31 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:
Attachments:
Description Flags
The stack trace stored by Anaconda after it broke down none

Description Jacob Sparre Andersen 2002-05-16 00:26:57 UTC 
Asked Anaconda to check for bad blocks during installation.
While the checking for bad blocks took place, Anaconda
broke down.

It appears to be caused by an unexpected format of the
output from `fsck -c` when there are two bad blocks next
to each other on the disk.
Comment 1 Jacob Sparre Andersen 2002-05-16 00:28:26 UTC 
Created attachment 57507 [details]
The stack trace stored by Anaconda after it broke down
Comment 2 Michael Fulbright 2002-05-20 19:16:07 UTC 

*** This bug has been marked as a duplicate of 64711 ***