Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 74082 - Unhandled exception while checking for bad blocks
Unhandled exception while checking for bad blocks
Status: CLOSED DUPLICATE of bug 66181
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-09-15 04:04 EDT by tstein
Modified: 2005-10-31 17:00 EST (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description tstein 2002-09-15 04:04:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 

Description of problem:
The installer has an unhandled exception while checking for bad blocks. It 
occurred about halfway through the check on one of the partitions.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run installer
2. choose partitions
3. choose packages
4. wait for bad blocks check

Actual Results:  A window showed the exception and offered me the chance to 
save the dump to a floppy.

Expected Results:  The installer should've continued.

Additional info:

A copy of the dump in its entirety can be found at the URL above 
Comment 1 Michael Fulbright 2002-09-16 13:13:16 EDT
This means that bad blocks were detected and the installer did not handle the

The drive appears to have failed the bad blocks test.

*** This bug has been marked as a duplicate of 66181 ***
Comment 2 tstein 2002-09-16 13:14:43 EDT
Okay, well it installed without the bad blocks check. What can I do to get rid 
of the bad blocks?

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