WRITE command timeout
Lee Cremeans
lee at lcremeans.homeip.net
Sun Dec 21 20:25:34 PST 2003
Oivind H. Danielsen wrote:
> Hello.
>
> We have been running FreeBSD 4.6-5.1 systems for 1.5 years and are being
> plagued by these:
>
> Dec 18 15:15:39 <> /kernel: ad0: WRITE command timeout tag=0 serv=0 -
> resetting
> Dec 19 15:03:23 <> /kernel: ad0: READ command timeout tag=0 serv=0 -
> resetting
>
>
> In our rack we have 34 identical drives (IBM IC35L080AVVA07).
>
> 24 drives on Windows 2000 : no problems.
> 4 drives on Linux 2.4.x : no problems.
>
> 2 drives on RELENG_4_8
> (VIA 82C686, VIA C3) : no problems
>
> 4 drives on RELENG_4_8
> (nVIDIA nForce, XP 2000+) : r/w timeouts, fs corruption.
>
> (1 drive/system, 6 FreeBSD boxes)
>
> The good systems have been running the 1.5 years without a hitch. The
> four identical RELENG_4_8 systems have all had corrupted filesystems (at
> least once every two months).
>
>
> We have tried the following:
>
> - Changed ATA100 cables (3 diff. types, all 80-wire)
> - Disabled DMA (use PIO4) (hw.ata.ata_dma="0" in loader.conf)
> - Disabled DMA in BIOS setup
> - Changed motherboard (MSI MS6734, VIA KM400, vt8235 ATA)
> - Changed power supply (added 100W)
> - RELENG_5_1.
>
> None of these changes has helped. The only change seen when disabling
> DMA is additional messages: "timeout waiting for DRQ - resetting".
It sounds like that particular drive is on the way out. Have you tried
running IBM/HGST's "Drive Fitness Tools" disk on it? (It's a DOS
program, but it comes on a self-booting diskette image that you can also
burn to a bootable CD if you like.) That program should be able to
detect any problems, and let you know if you need to send the drive back.
-lee
More information about the freebsd-stable
mailing list