[ale] Bad drive?

[Eric Z. Ayers]

Scott,

every time I've seen this message, it's been a bad hard drive.  But it 
could also be :

- wrong DMA settings - try hdparm -d /dev/hda to turn off DMA and see  
if it goes away.
- problem with another drive on the same cable
- interrupt sharing  - cat /proc/interrupts and see if there is another 
device besides 'ide0' on interrupt 14
- some other hardware config problem if you've recently been messing 
with hardware.

You can be almost certain if you run:

dd if=/dev/hda of=/dev/null

several times and get an error after the same number of blocks each time.

-Eric.

<mailto:ale at ale.org> Subject: [ale] Bad drive? Am I looking at a bad 
drive? Or is this more of a kernel problem? I'm running kernel 2.4.1. 
Feb 28 17:44:02 ws6 kernel: hda: lost interrupt Feb 28 17:44:02 ws6 
kernel: hda: lost interrupt Feb 28 17:44:02 ws6 kernel: hda: status 
error: status=0x58 { DriveReady SeekComplete DataRequest } Feb 28 
17:44:02 ws6 kernel: hda: status error: status=0x58 { DriveReady 
SeekComplete DataRequest } Feb 28 17:44:02 ws6 kernel: hda: drive not 
ready for command Feb 28 17:44:02 ws6 kernel: hda: drive not ready for 
command - Scott

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