[ale] HD errors

[Ken Nagorski]

Well,

	The bad news is that your drive is hosed. This means that there is
some sort of problem reading the drive that is not because of bad blocks
as far a I know. Feel free to correct me if I am wrong.

	Also if the motherboard is having some sort of trouble this can
cause this as well. Do you have a really large drive in an older
motherboard?

Ken


 On Thu, 19 Apr 2001, Chris Fowler wrote:

> Help,
> 
> I have a section on my HDD that reports the following error when I try to
> read the data that is there.
> 
> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=24942521,
> sector=24765806
> end_request: I/O error, dev 03:03 (hda), sector 24765806
> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=24942521,
> sector=24765806
> end_request: I/O error, dev 03:03 (hda), sector 24765806
> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=24942521,
> sector=24765806
> end_request: I/O error, dev 03:03 (hda), sector 24765806
> 
> 
> I've booted in single user mode and tried to issue 'e2fsck -c /dev/hda3' to
> mark these blocks as bad.  But after a long scan,
> I get shot read errors and e2fsck ask me if I wish to ignore.  Should I
> answer 'y' or 'n'?  Also, what do I need to do to 
> keep from running into these blocks on disk?  Can I use badblocks to
> manually mark these areas as bad?
> 
> 
> 
> Thanks,
> Chris
> 

-- 
 I couldn't quite remember what I was going to say 
           so I causally tip another sip of whatever it was I was drinking,

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.