SATA device timeout using libata

[Eamonn Hamilton]

Hi,

I'm currently building a system with ~1TB raid5 array using SATA drives.
Currently, I'm using 3 SiL-3112 dual-port SATA controller, each with 2 x
200GB drives on them.

One controller has 2 X WDC WD2000JD-00G drives which seem to work
perfectly, another has 2 X Maxtor 6Y200M0 which also seem to work fine,
however the the third pair of drives are WDC WD2000JD-00F and these seem
to deliver issues.

Basically, when attempting to stress a RAID-5 array while the array is
synchronising, I get the following after an hour or so:   

ata3: DMA timeout, stat 0x1
ATA: abnormal status 0xD0 on port 0xE087B087
scsi2: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 01 92 8d 47 00
00 08 00
Current sdc: sense key Medium Error
Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sdc, sector 26381639
ATA: abnormal status 0xD0 on port 0xE087B087
ATA: abnormal status 0xD0 on port 0xE087B087
ATA: abnormal status 0xD0 on port 0xE087B087

This is using 2.6.6-rc3-bk4 with the latest update patch from Jeff
Garziks directory for the libata stuff. This is actually much improved
over 2.4.25 using the siimage drive and 2.6.5 stock using both the
siimage driver and libata, which fell over after a few minutes.

The interesting part here is that the hardware checks out fine using the
manufacturers test disk in the same configuration, and having recabled
and moved controllers around, it appears that it always follows these
particular drives. 

Is anybody aware of a firmware update for these beasts, or any known
issues on them? 

Any suggestions gratefully received :)

Cheers,
Eamonn

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/