Bug 64847 - Crashed while performing surface scan
Crashed while performing surface scan
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
:
: 64766 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-05-13 11:55 EDT by Need Real Name
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: 2006-02-21 13:48:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Comment (72.72 KB, text/plain)
2002-05-13 11:55 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-05-13 11:55:33 EDT
Created attachment 915049 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 1 Michael Fulbright 2002-05-13 14:45:34 EDT
There appears to possibly be a problem with the code, however these errors:

<4>end_request: I/O error, dev 03:43 (hdb), sector 3712408
<4>hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
<4>hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=4865562, 

are in your error log, indicating the drive appears to be failing.  I would
recommend using a different drive, or at least figure out if the drive is really
dying or not (the drive manufacturer may have a boot floppy which can test the
drive).  Note that sometimes these tests can destrory data.

Comment 2 Michael Fulbright 2002-05-13 15:15:45 EDT
*** Bug 64766 has been marked as a duplicate of this bug. ***
Comment 3 Michael Fulbright 2002-06-12 13:04:24 EDT
Closing due to inactivity - please reopen if you have additional information to add.
Comment 4 Red Hat Bugzilla 2006-02-21 13:48:53 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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