On Mon, 2004-11-15 at 07:06 -0500, Paul Tomblin wrote:
> On Mon, 15 Nov 2004 13:40:59 +0200, Chadley Wilson <chadley@xxxxxxxxxxxx> wrote:
> > On Monday 15 November 2004 13:30, Paul Tomblin wrote:
> > > I woke up this morning to find my computer extremely sluggish. One
> > > terminal window was still responding a bit, so I did an "uptime" only
> > > to find the load average over 230! I'll investigate and report back.
> > Oh !!! OK
>
> Ok, it appears that I'm getting more errors on my second IDE
> controller, even though the problematic /dev/hdc4 wasn't mounted.
> /dev/hdc1 was mounted, and it was ok earlier. But around 2:00, I
> suddenly started to get
>
> Nov 15 02:05:26 allhats kernel: hdc: dma_timer_expiry: dma status == 0x61
> Nov 15 02:05:36 allhats kernel: hdc: DMA timeout error
> Nov 15 02:05:36 allhats kernel: hdc: dma timeout error: status=0xd0 { Busy }
> Nov 15 02:05:36 allhats kernel:
> Nov 15 02:05:36 allhats kernel: ide: failed opcode was: unknown
> Nov 15 02:05:36 allhats kernel: hdc: DMA disabled
> Nov 15 02:05:36 allhats kernel: hdd: DMA disabled
> Nov 15 02:05:36 allhats kernel: ide1: reset: success
> Nov 15 02:05:51 allhats kernel: hdc: lost interrupt
> Nov 15 02:05:51 allhats kernel: hdc: multwrite_intr: status=0x59 { DriveReady Se
> ekComplete DataRequest Error }
> Nov 15 02:05:51 allhats kernel: hdc: multwrite_intr: error=0x00 { }
> Nov 15 02:05:51 allhats kernel: ide: failed opcode was: unknown
> Nov 15 02:05:51 allhats kernel: hdd: status error: status=0x00 { }
> Nov 15 02:05:51 allhats kernel: hdd: status error: error=0x00
> Nov 15 02:05:51 allhats kernel: hdd: status timeout: status=0x80 { Busy }
> Nov 15 02:05:51 allhats kernel: hdd: status timeout: error=0x80LastFailedSense 0
>
> Now this hardware was all working perfectly for the last couple of
> years, and suddenly started throwing these errors after "upgrading" to
> Fedora Core 3 and the new 2.6 kernel. I'm deeply suspicious. I think
> I'm going to download a RedHat 9 ISO and boot from that, and exercise
> that drive to see if it gets errors under 9.
>
Uh? You say it has worked for 2 years.
Is it even remotely possible that the controller or drive may be
failing??
I had one that gave similar errors in the log intermittently over a
period of several months and it suddenly quit accessing the drive
entirely. After investigating and trying a different drive I found the
controller had failed and a new mobo fixed it.
As long as the errors were intermittent I was unable to find the problem
because smartd did not report problems on the drive and the usual
symptom was either the system was totally locked up, or it had rebooted
itself.
> --
> "To announce that there must be no criticism of the president, or that we
> are to stand by the president, right or wrong, is not only unpatriotic and
> servile, but is morally treasonable to the American public." -- Teddy Roosevelt
>
--
The Unix way of sex
# unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ;
sleep
