I have seen such error messages below before too.....it was when I decided to enable dma support for the hd via hdparm....check to see whether that that has been enabled (hdparm /dev/hda). Anyway, after that incident, my hardisk had bad cluster/sectors!
Patrick Cheong Information Systems Assurance Measat Broadcast Network Systems e-mail: mailto:[EMAIL PROTECTED] Visit us at: http://www.astro.com.my > -----Original Message----- > From: ktb [SMTP:[EMAIL PROTECTED] > Sent: Thursday, September 07, 2000 10:12 AM > To: Debian list > Subject: Re: Please help with some harddisk error > > On Wed, 06 Sep 2000, Shao Zhang wrote: > > Hi, > > I am getting some harddisk errors on one of our production > > servers. We also have the same hardware for two other > > servers(web/proxy) running 2.0.36/hamm with no problems. > > > > Hardware: > > 4 x 9GB Fujisu > > Mylex Accelerate 250 > > > > Software: > > Kernel 2.2.16/with latest DAC960 comes with kernel(will try out > > 2.2.17) > > Current Potato > > > > Errors: > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=34431, > sector=34368 > > end_request: I/O error, dev 03:01 (hda), sector 34368 > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=34431, > sector=34368 > > end_request: I/O error, dev 03:01 (hda), sector 34368 > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=34431, > sector=34368 > > end_request: I/O error, dev 03:01 (hda), sector 34368 > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=279631, > sector=279568 > > end_request: I/O error, dev 03:01 (hda), sector 279568 > > > > We are gettting thounsands of these messages. However, the > > server still runs ok, but some files are damaged randomly. > > > > Thanks for any help in advance. > > I've had errors such as { DriveReady SeekComplete Error } twice and > both times it just got worse to the point the drives crashed. > One of the drives I quit trying to use for a couple weeks and > accidently booted into it, and it worked fine, I copied what I wanted > and kept using it and then it crashed again. I've read that happening > to other people also. At any rate if I were you I would copy that drive > pronto. Search the archives for a fix. I've seen people post them but > they never worked for me. > hth, > kent > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null
