Jon Chelton wrote: > Tejun, > > Below is the kernel log from boot to when error occurred. You can see > right when the raid5 array was built and started the recovery process > the exception occurred. Also, its now been 24 hours since I disabled > smartd and have not seen any other exceptions since. (also included is > output from smartd -V) [--snip--] > ata1.03: exception Emask 0x0 SAct 0x2220897f SErr 0x400000 action 0x2 > ata1.03: irq_stat 0x00020002, device error via SDB FIS > ata1.03: cmd 61/88:a8:3f:00:00/00:00:00:00:00/40 tag 21 cdb 0x0 data > 69632 out > res 41/84:38:8f:00:00/60:00:00:00:00/40 Emask 0x410 (ATA bus > error) <F> > ata1.03: soft resetting link > ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1.03: configured for UDMA/100 > ata1: EH complete > ata1.03: exception Emask 0x0 SAct 0x1ffc SErr 0x400000 action 0x2 > ata1.03: irq_stat 0x00020002, device error via SDB FIS > ata1.03: cmd 61/88:10:3f:00:00/00:00:00:00:00/40 tag 2 cdb 0x0 data > 69632 out > res 41/84:78:4f:00:00/00:00:00:00:00/40 Emask 0x410 (ATA bus > error) <F> > ata1.03: soft resetting link > ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1.03: configured for UDMA/100 > ata1: EH complete > ata1.03: exception Emask 0x0 SAct 0x7ff SErr 0x400000 action 0x2 > ata1.03: irq_stat 0x00020002, device error via SDB FIS > ata1.03: cmd 61/70:00:57:03:00/01:00:00:00:00/40 tag 0 cdb 0x0 data > 188416 out > res 41/84:a0:27:04:00/60:00:00:00:00/40 Emask 0x410 (ATA bus > error) <F> > ata1.03: soft resetting link > ata1.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1.03: configured for UDMA/100 > ata1: EH complete > ata1.03: limiting SATA link speed to 1.5 Gbps > ata1.03: exception Emask 0x0 SAct 0x7ff SErr 0x400000 action 0x6 > ata1.03: irq_stat 0x00020002, device error via SDB FIS > ata1.03: cmd 61/88:00:3f:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data > 69632 out > res 41/84:38:8f:00:00/00:00:00:00:00/40 Emask 0x410 (ATA bus > error) <F> > ata1.03: hard resetting link > ata1.03: SATA link up 1.5 Gbps (SStatus 113 SControl 310) > ata1.03: configured for UDMA/100 > ata1: EH complete All errors are interface CRC errors reported by device on FPDMA_WRITE. It doesn't seem to have anything to do with SMART. In all cases, SError DIAG is reporting handshake error too (R_ERR received). I'm fairly sure these were actual hardware problems. You don't have to pay too much attention unless it happens repeatedly. Good cure for the problem is probably to re-seat the harddrive. Bruce, I don't think this is SMART related. Sorry about the noise. Thanks. -- 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
