Bug 65013 - Anaconda dies while checking for bad blocks
Anaconda dies while checking for bad blocks
Status: CLOSED DUPLICATE of bug 64711
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-05-15 20:26 EDT by Jacob Sparre Andersen
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-05-15 20:28:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The stack trace stored by Anaconda after it broke down (65.74 KB, text/plain)
2002-05-15 20:28 EDT, Jacob Sparre Andersen
no flags Details

  None (edit)
Description Jacob Sparre Andersen 2002-05-15 20:26:57 EDT
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-15 20:28:26 EDT
Created attachment 57507 [details]
The stack trace stored by Anaconda after it broke down
Comment 2 Michael Fulbright 2002-05-20 15:16:07 EDT

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

Note You need to log in before you can comment on or make changes to this bug.