Messages in this thread |  | | Subject | Re: IDE errors with 2.0.11 | Date | Thu, 08 Aug 1996 11:01:29 +0900 | From | Tohru Yagi <> |
| |
In article <Pine.LNX.3.94.960806232725.7432A-100000@brando> kmb203@psu.edu writes:
>> These critters appeared on all the open VC's (or is it VT's?) >> today. This is with 2.0.11 and a Maxtor 520 MB (about) hard >> drive, a few years old, IDE. >> >> hda: write_intr: status=0x51 { DriveReady SeekComplete Error } >> hda: write_intr: error=0x04 { DriveStatusError } >> >> I have had this happen with recent kernels.. (I may have >> mentioned it before on here). These are very intermittent, and >> at least the recent ones haven't shown visible (to e2fsck) >> filesystem corruption. >> >> Is this a harmless error? Does it mean corruption? Is my drive >> creeping towards the ancient IDE burial ground? >> >> How do I tell if my MB has a CMD640 on it?
I've had the same problem with a IDE drive(Western Digital).
I'm using three IDE drives:
hda: ST5660A, 504MB w/256kB Cache, LBA, CHS=1024/16/63 hdb: WDC AC2540H, 515MB w/128kB Cache, LBA, CHS=524/32/63 hdc: ST51080A, 1033MB w/128kB Cache, LBA, CHS=2100/16/63
And the kernel version is 2.0.11. IDE interface is PCTECH RZ1000.
My proplem is that the second drive showed an error message in /var/log/syslog a while ago. The error is as folloews:
hdb: write_intr: status=0x61 { DriveReady DeviceFault Error } hdb: write_intr: error=0x04 { DriveStatusError } hdb: status error: status=0x69 { DriveReady DeviceFault DataRequest Error } hdb: status error: error=0x04 { DriveStatusError } hdb: no DRQ after issuing WRITE
But I've not had any errors like this since then. I would like to know if the error like this is harmful or not.
Tohru Yagi Osaka University, JAPAN yagi@comm.eng.osaka-u.ac.jp
|  |