I am getting this over and over,  Does any body know what may be the root cause?

Started when trying to install a 250 gig. cache drive.  The cache drive would not install at all.  Tried to format within unraid and it thrashed around for 2 hours. I finally took it out and went back to original configuration and then the program said that I had a new Parity drive and proceeded to rebuild itself, along with numerous time-outs? with resulting data spit out to the log file.

The log data is below. This occurs over and over.

Thanks in advance.

Vic

 

Jul  7 10:42:13 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x1b80000 action 0x6 frozen

Jul  7 10:42:13 Tower kernel: ata1: SError: { 10B8B Dispar BadCRC LinkSeq TrStaTrns }

Jul  7 10:42:13 Tower kernel: ata1.00: failed command: WRITE DMA EXT

Jul  7 10:42:13 Tower kernel: ata1.00: cmd 35/00:00:e0:73:42/00:04:39:00:00/e0 tag 0 dma 524288 out

Jul  7 10:42:13 Tower kernel:          res 40/00:ff:00:00:00/84:00:00:00:00/40 Emask 0x4 (timeout)

Jul  7 10:42:13 Tower kernel: ata1.00: status: { DRDY }

Jul  7 10:42:13 Tower kernel: ata1: hard resetting link

Jul  7 10:42:13 Tower kernel: ata1: nv: skipping hardreset on occupied port

Jul  7 10:42:14 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Jul  7 10:42:14 Tower kernel: ata1.00: configured for UDMA/33

Jul  7 10:42:14 Tower kernel: ata1.00: device reported invalid CHS sector 0

Jul  7 10:42:14 Tower kernel: ata1: EH complete

 

Have a look at http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues

 

Probably Drive interface issue #4