[Solved] CRC Erros on a new disk - Something to worry about?

[doesntaffect]

Hi folks,

 

still learning how to manage UnRaid as I move towards the end of my trial period and so far I received 4 CRC errors on one of my disks. Today the 4th error has been reported and I am curious whether I should worry. The disks are brand new, all of the same type. Its my main disk where these erros occur.

From the logs below I understand tha there is something going wrong with the disk bus system. I am using WD Red 4TB NAS disks.

 

Any advise? So far I am acknowledging the errors only. I also checked the Sata cables.

Would ECC Memory do any trick here?

 

 

Nov 27 01:58:39 Ryzen kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Nov 27 01:58:39 Ryzen kernel: ata2.00: cmd 61/20:a8:10:89:2a/01:00:e9:00:00/40 tag 21 ncq dma 147456 out
Nov 27 01:58:39 Ryzen kernel: res 40/00:a0:10:89:2a/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 01:58:39 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 01:58:39 Ryzen kernel: ata2: hard resetting link
Nov 27 01:58:39 Ryzen kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 27 01:58:39 Ryzen kernel: ata2.00: configured for UDMA/133
Nov 27 01:58:39 Ryzen kernel: ata2: EH complete
Nov 27 02:01:06 Ryzen kernel: ata2.00: exception Emask 0x11 SAct 0x11f000 SErr 0x680100 action 0x6 frozen
Nov 27 02:01:06 Ryzen kernel: ata2.00: irq_stat 0x48000008, interface fatal error
Nov 27 02:01:06 Ryzen kernel: ata2: SError: { UnrecovData 10B8B BadCRC Handshk }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/f8:60:78:74:b1/00:00:e9:00:00/40 tag 12 ncq dma 126976 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/10:68:38:77:b1/00:00:e9:00:00/40 tag 13 ncq dma 8192 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/20:70:98:77:b1/00:00:e9:00:00/40 tag 14 ncq dma 16384 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/10:78:d8:78:b1/00:00:e9:00:00/40 tag 15 ncq dma 8192 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/10:80:28:86:3f/00:00:e9:00:00/40 tag 16 ncq dma 8192 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 27 02:01:06 Ryzen kernel: ata2.00: cmd 60/20:a0:d0:64:1e/00:00:e9:00:00/40 tag 20 ncq dma 16384 in
Nov 27 02:01:06 Ryzen kernel: res 40/00:a0:d0:64:1e/00:00:e9:00:00/40 Emask 0x10 (ATA bus error)
Nov 27 02:01:06 Ryzen kernel: ata2.00: status: { DRDY }
Nov 27 02:01:06 Ryzen kernel: ata2: hard resetting link
Nov 27 02:01:07 Ryzen kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 27 02:01:07 Ryzen kernel: ata2.00: configured for UDMA/133
Nov 27 02:01:07 Ryzen kernel: ata2: EH complete

Edited November 27, 2020 by doesntaffect

[JorgeB]

First thing to do is to replace the SATA cable

[itimpi]

CRC errors are very rarely a drive problem as they indicate a connection issue.

[doesntaffect]

Thanks guys, I swapped the Sata cable and will monitor this further on.