Description of problem: Using a SiI 3112A card, I'm getting data corruption and eventually the devices hang. Reproduced with a pair of Hitachi 250Gb disks (7K250). Version-Release number of selected component (if applicable): kernel-2.6.9-22.EL How reproducible: always Steps to Reproduce: 1. mdadm -Cv /dev/md0 -l0 -n2 -c128 /dev/sd{a,b}1 2. mke2fs -m0 -R stride=64 /dev/md0 3. mount /dev/md0 /foo 4. copy lots of data on /foo Actual results: The drives initially produced lots of errors like: ata1: status=0x51 { DriveReady SeekComplete Error } ata1: error=0x04 { DriveStatusError } ata1: status=0x51 { DriveReady SeekComplete Error } ata1: error=0x04 { DriveStatusError } ata2: status=0x51 { DriveReady SeekComplete Error } ata2: error=0x04 { DriveStatusError } ata1: status=0x51 { DriveReady SeekComplete Error } and data written is corrupted. Eventually, the drives ata1: command 0x35 timeout, stat 0xd8 host_stat 0x1 ata1: status=0xd8 { Busy } SCSI error : <0 0 0 0> return code = 0x8000002 Current sda: sense key Aborted Command Additional sense: Scsi parity error end_request: I/O error, dev sda, sector 289145151 ATA: abnormal status 0xD8 on port 0xD082A087 ATA: abnormal status 0xD8 on port 0xD082A087 ATA: abnormal status 0xD8 on port 0xD082A087 ata1: command 0x35 timeout, stat 0xd8 host_stat 0x1 ata1: status=0xd8 { Busy }
Created attachment 119945 [details] /var/log/dmesg
Created attachment 119946 [details] "lspci -v" output
Created attachment 119947 [details] current dmesg output The comment should have read... "eventually the devices hang "
What firmware are you using? I had some problems with software RAID on sata sil card. It worked fine under a lot of stress but I couldn't install software RAID on it until I upgraded to the 5.0.48 firmware.
No idea, how do I tell?
It should say in BIOS post while you boot.
Ah, it says version 4.1.34 on boot; I can find 4.2.50 available from: http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=15&ctid=2& but no 5.0.48. Am I missing anything?
I tried flashing one of the cards to the 4.2.50 firmware and now the machine refuses to boot with any drives attached to that card.
Gah... That really bites. :/ I'm going to hide in the corner. Try pinging support to get the old firmware back.
Well, moving the card to a new machine seems to have fixed it, so I think this was some issue with the creaky old motherboard in the original test box.