libata problems with Promise SATA 300 TX4

["Jan Lübbe" <jluebbe@lasnet.de>]

Hi!

I'm not sure if this is the correct list, as my problem is about sata
and not SCSI...

We run a debian push mirror (debian.tu-bs.de) and have recently switched
from a scsi hardware raid to a SATA linux software raid. 3 Maxtor
Maxline III are attached to a Promise SATA 300 TX4. It worked well for
about one month while we were testing it with low load parallel to the
SCSI raid and it worked flawlessly. One week ago, we move all our data
over to the software raid.

Since about 4 days we get scsi errors about once per day. libata reports
an error about every 30 seconds and after about one hour, the disk is
dropped from the array. It continues in degraded mode without further
problems until another disk shows errors.

After rebooting the server, all disks are accessible again and i can
perform a resync (which completes without errors). Then sata works
without problems until the same errors appear again.

This happens with a 2.6.13.4, today we tried 2.6.14.3, but it froze
completely after 22 hours. So we only have logs when the error happend
with 2.6.13.4 :(

This shows up in the logs:

Dec  2 17:01:05 apmsrv01 kernel: ata2: command timeout
Dec  2 17:01:05 apmsrv01 kernel: ATA: abnormal status 0xFF on port 0xF881229C
Dec  2 17:01:05 apmsrv01 kernel: ata2: status=0xff { Busy }
Dec  2 17:01:05 apmsrv01 kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Dec  2 17:01:05 apmsrv01 kernel: sdd: Current: sense key: Aborted Command
Dec  2 17:01:05 apmsrv01 kernel:     Additional sense: Scsi parity error
Dec  2 17:01:05 apmsrv01 kernel: end_request: I/O error, dev sdd, sector 57303239

The sector differs each time, but the rest is always the same.

What could cause this error? Which information should i try to gather?

Thanks,
-- 
Jan Lübbe <jluebbe@lasnet.de>            http://sicherheitsschwankung.de
 gpg-key      1024D/D8480F2E 2002-03-20
 fingerprint  1B25 F91F 9E7B 5D4F 1282  02D6 8A83 8BE4 D848 0F2E

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html