Power flickers, system reboots, parity check starts, it stops and I have to hit the power button to actually get the machine to restart.  Today I am tailing the syslog during the parity check and after it finds 4 parity errors I get a bunch of entries in the syslog that appear like errors. 

 

Anyone know what any of the errors below are pointing to?  several ATA ports are being referenced which doesn't help make sense of it possibly being a bad HD.  Anyone know what "EH Complete" is referring to?"

 

At this time, parity check is still running but I am not expecting it to finish as this is the 6th attempt.

 

Thanks in advance!

 

 

Apr 11 15:40:04 BIGHOSS kernel: md: parity incorrect: 757536960

Apr 11 16:37:37 BIGHOSS kernel: md: parity incorrect: 1194648192

Apr 11 16:47:49 BIGHOSS kernel: mdcmd (16): spindown 1

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x380000 action 0x6

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: BMDMA stat 0x5

Apr 11 17:25:04 BIGHOSS kernel: ata2: SError: { 10B8B Dispar BadCRC }

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: failed command: READ DMA EXT

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: cmd 25/00:60:a7:4b:df/00:03:62:00:00/e0 tag 0 dma 442368 in

Apr 11 17:25:04 BIGHOSS kernel:          res 51/84:60:a7:4e:df/84:00:62:00:00/e0 Emask 0x10 (ATA bus error)

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: status: { DRDY ERR }

Apr 11 17:25:04 BIGHOSS kernel: ata2.00: error: { ICRC ABRT }

Apr 11 17:25:04 BIGHOSS kernel: ata2: hard resetting link

Apr 11 17:25:04 BIGHOSS kernel: ata2: nv: skipping hardreset on occupied port

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x380000 action 0x6

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: BMDMA stat 0x5

Apr 11 17:25:04 BIGHOSS kernel: ata4: SError: { 10B8B Dispar BadCRC }

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: failed command: READ DMA EXT

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: cmd 25/00:60:a7:4b:df/00:03:62:00:00/e0 tag 0 dma 442368 in

Apr 11 17:25:04 BIGHOSS kernel:          res 51/84:c7:40:4e:df/84:00:62:00:00/e0 Emask 0x10 (ATA bus error)

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: status: { DRDY ERR }

Apr 11 17:25:04 BIGHOSS kernel: ata4.00: error: { ICRC ABRT }

Apr 11 17:25:04 BIGHOSS kernel: ata4: hard resetting link

Apr 11 17:25:04 BIGHOSS kernel: ata4: nv: skipping hardreset on occupied port

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x380000 action 0x6

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: BMDMA stat 0x5

Apr 11 17:25:04 BIGHOSS kernel: ata3: SError: { 10B8B Dispar BadCRC }

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: failed command: READ DMA EXT

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: cmd 25/00:50:07:46:df/00:03:62:00:00/e0 tag 0 dma 434176 in

Apr 11 17:25:04 BIGHOSS kernel:          res 51/84:a0:b7:48:df/84:00:62:00:00/e2 Emask 0x10 (ATA bus error)

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: status: { DRDY ERR }

Apr 11 17:25:04 BIGHOSS kernel: ata3.00: error: { ICRC ABRT }

Apr 11 17:25:04 BIGHOSS kernel: ata3: hard resetting link

Apr 11 17:25:04 BIGHOSS kernel: ata3: nv: skipping hardreset on occupied port

Apr 11 17:25:05 BIGHOSS kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Apr 11 17:25:05 BIGHOSS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Apr 11 17:25:05 BIGHOSS kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Apr 11 17:25:05 BIGHOSS kernel: ata4.00: configured for UDMA/133

Apr 11 17:25:05 BIGHOSS kernel: ata4: EH complete

Apr 11 17:25:05 BIGHOSS kernel: ata2.00: configured for UDMA/133

Apr 11 17:25:05 BIGHOSS kernel: ata2: EH complete

Apr 11 17:25:05 BIGHOSS kernel: ata3.00: configured for UDMA/133

Apr 11 17:25:05 BIGHOSS kernel: ata3: EH complete

 

Ohh!  Just found a great wiki page about the drive messages!

 

http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_Interface_Issues

Notices something else odd.  A Smart report shows that every drive in the array has a UDMA_CRC_Error_Count value greater than one.  The parity drive has a 528 count!!!  According to the wiki, "One user reported a value other than zero", which makes it sound unusual.

 

The cheapest and easiest test for this is some brand new cables.  I highly doubt that I have 5 bad cables, however.  I'm starting to suspect the SATA interface on the mobo (ASUS A8N-SLI Deluxe).

 

Anyone else with non-zero values for their drives?

This last time partity check was successful so I don't have a syslog showing error messages (of course!).

 

Has anyone else experienced similar behaviour where to took several attempts to finish a parity check?

 

I'm running 4.7 Plus, btw.