Help with disk crash (long)

[mike at bilow.com (Michael Bilow)]

Seek errors and such are likely not occuring here as a result of a
hardware problem, at least not in the sense that something has gone wrong
with the hardware.  Rather, what is more likely happening is that the
partition tables or other data on the disk got messed up, and the result
is that the kernel is being told to access some sector off in never-never
land which does not exist.  Asking for a disk sector beyond the end of
physical media will usually be reported as a seek error.

This could be a real hardware error, but sector 0 is the master boot
record which contains the partition table.  It might be possible to
recreate this synthetically by hand, but who knows?  You would have to
figure out the valid data by trial and error.

-- Mike


On 2001-07-08 at 12:17 -0400, Derek Martin wrote:

> On Sun, Jul 08, 2001 at 11:32:11AM -0400, root wrote:
> 
> > Jul  7 22:20:50 ppro kernel:  hdc:hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } 
> > Jul  7 22:20:50 ppro kernel: hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0 
> > Jul  7 22:20:50 ppro kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 
> 
> I'm neither a hardware nor kernel expert by any means, but these
> errors suggest to me that your drive is no good.  I've seen errors
> like these before on an old system of mine, and that particular drive
> was toast.  Had to have it replaced by my vendor.  Fortunately, it was
> under warranty.


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).