Hey guys, I started having serious stuttering issues last night while watching a movie streaming from my unraid box.  I pulled up myMain and saw a bunch of errors (shown below).  After some wiki browsing I found a page saying these errors usually indicated a loose cable but I wanted to be sure as this is my first issue with my unraid system ever.  Also, other files work fine from this same disk.  I ran a smart test on disk3 and have attached that as well as the syslog.  Could someone be so kind and give it a once over?  Many thanks.

 

Version 4.7

 

Aug 30 20:37:56 nas kernel: md: disk3 read error (Errors)

Aug 30 20:37:56 nas kernel: handle_stripe read error: 3401188232/2, count: 1 (Errors)

Aug 30 20:37:56 nas kernel: md: disk3 read error (Errors)

Aug 30 20:37:56 nas kernel: handle_stripe read error: 3401188240/2, count: 1 (Errors)

Aug 30 20:37:56 nas kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen (Errors)

Aug 30 20:37:56 nas kernel: ata2.00: irq_stat 0x08000000, interface fatal error (Errors)

Aug 30 20:37:56 nas kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } (Errors)

Aug 30 20:37:56 nas kernel: ata2.00: failed command: READ DMA EXT (Minor Issues)

Aug 30 20:37:56 nas kernel: ata2.00: cmd 25/00:00:d8:03:ba/00:04:ca:00:00/e0 tag 0 dma 524288 in (Drive related)

Aug 30 20:37:56 nas kernel: res 50/00:00:d7:ff:b9/00:00:ca:00:00/e0 Emask 0x50 (ATA bus error) (Errors)

smart.txt

syslog.txt

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

 

Drive interface issue #2

 

ata3: SError: { UnrecovData HostInt 10B8B BadCRC }

These errors are usually related to a bad cable or cable connector. The presence of BadCRC is a pretty good indicator of a poor quality SATA cable.

Smart looks fine.

 

Is the drive already red-balled ?

 

I've had the same problems, and they were fixed by replacing the sata cable. Sometimes reseating helps, but just to be safe replace the sata cable as well as the power connector (bad y-splitter?)

 

Other time I had this problem it was with an SFF-8087 cable which forced one of the sata connectors to "creep" out of the hdd after 1~2 weeks. It was barely noticable but it was not plugged in to the drive cage straight anymore.

 

 

No Red ball, but a lot of errors in the error column.

 

Cool thanks, this is what I was hoping...a painless $3 fix.  But I am a bit worried no other files on this drive gives me badCRC errors...