Eyal Lebedinsky wrote: > It is in the original thread on linux-raid, but here it is for this list. > This is the full dmesg. There were only MARKs in between. > > I run a raid 'check' every Friday (cron). The last one reported some parity errors. > > *** last week check start: > [927080.617744] md: data-check of RAID array md0 > [927080.630783] md: minimum _guaranteed_ speed: 24000 KB/sec/disk. > [927080.648734] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check. > [927080.678103] md: using 128k window, over a total of 312568576 blocks. > *** last week error: > [937567.332751] ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4190002 action 0x2 > [937567.354094] ata3.00: cmd b0/d5:01:09:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in > [937567.354096] res 51/04:83:45:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) I need full kernel log including the boot messages so that I can tell which controller/driver is involved here and also the result of 'hdparm -I /dev/sdX' of your drives would be nice. BTW, this is SMART read log for page 09 which is SMART self-test log. The device aborted it. Dunno who issued it or why it got aborted. As I wrote in the previous mail, EH discovered that SError has accumulated link level errors and thus treated it as ATA bus error. All transmissions over SATA are checksummed and link errors supposedly don't cause data corruption, so, in theory, the above error message should be irrelevant to your problem. Ah.. please also post the result of 'smartctl -d ata -a /dev/sdX' for your drives. That might reveal something. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
