Hi all, first time poster. I completed my build recently and upon starting, one of my drives (WD Red Plus 8 TB) is kicking out the UDMA CRC error count error with a value of 273.

 

 

I've already switched SATA cables and moved the drive to a different slot in my case, but the error still persists. I also previously acknowledged the error, but it popped up again. I don't want to start my array if this error persists.

 

Hardware (if interested):
Motherboard + CPU: Asus Prime Z690-A & i7-12700K
RAM: 32GB DDR5

PSU: 1,000W

Case: Jonsbo N5

Drives: WD Red Plus 8 TB

It won't reset, but after you acknowledge it will warn again if it increases. Make sure power connections are good also. No tension in cables, and don't bundle data cables.

I did all of that, including acknowledging the error. No SMART warnings, but the array shows a device warning that I cannot clear. I've also run the wires again, still to no avail with clearing the warning. Is it safe to continue with setting up the array?

If the warning really bugs you, click on the disk and uncheck the box in this screenshot.

if you have aknowledged the error count correctly, the warning will go away and show green light again.

It will be raised again if the error count goes up again which shows that there is a persistant cabling problem.

 

(or you turn it off as @SlackMaster says, but I would not recommend this. Better fix it. Even if the "error" mostly shows that "something went wrong" but has no actual impact on the data, the needed retransmissions eat up time and slow down the whole system)

 

BTW: it is more or less "natural" that a disk has these kinds of error. It happens accidentally if you unplug or move the cables. The annoying thing is that the drives stores these events, though "mostly harmless" permanently and nags you with them if you set up a new system.

 

Edited May 14, 20251 yr by MAM59

273 CRC errors are really not that many.  (I have one disk with 72,300 CRC errors on it.  It also has 67,000+ hours of Power-On time!  The problem was corrected so long I can't remember exactly what caused it!)   Write down on post-it note the current number of errors and the Power-On hours.  If you get another Error notice, compare the two. 

 

Other possible causes.

• Bundling SATA data cables together for 'neatness' allowing for cross-talk between the cables.
• Bundling single cables for 'neatness' without sufficient slack that that there is a tension of the connector and its socket so that it loosens due to vibration.  (I have always said that the SATA connector design is the 'Poster Child' for how NOT to design an connector system!!!) 
• If a backplane is involved, consider the possibility that the backplane connector could have dust or other dirt in it. 

 

So I had a second look at the SMART data and I was unknowingly sold a used drive as new (4 days of power on hours versus ~1 day for my other drives). Fortunately, it looks like the store will exchange it for me for free. 

 

I appreciate all the suggestions and the inevitable CRC error count when the time comes.

4 days of power on?

Thats not really much. Not even "burned in" yet 🙂

But then, if you are able to swap, then swap.