I have a bit of a weird situation that's got me stumped.

About a month ago I built a server using an Optiplex 7050 SFF MB (moved to a midtower case) and two new 10TB WD Red Plus drives (in addition to a 512gb m.2 SSD for cache).

A couple days ago the parity drive showed some write errors and disabled itself. I ran an extended SMART test and there were no issues.

Even after moving the parity drive to its own power cable and new data cable (also moved it to the primary port), the parity build fails about 2 hours in.

Any ideas here? Attaching the diagnostic zip.

Can attach the SMART report as well if needed (though not sure if I need to scrub anything from that)

server1-diagnostics-20251202-1123.zip

23 minutes ago, tnoetz01 said:

the diagnostic zip.

Can attach the SMART report

Diagnostics already includes SMART report for all attached disks.

SMART attributes look OK and extended self-test passed.

Nothing in syslog that would indicate connection problems, and it was buiilding OK for over an hour before write errors started.

Some search results with something similar (IDNF):

https://www.google.com/search?q=Error:+IDNF+site:forums.unraid.net

Do you have another disk you can try?

I don't have another disk at this point... I have 2 more coming from WD, but they're back-ordered and won't ship for a while.

It's very atypical for write errors to show up without any controller issues/timeouts first, though I'm not really sure what this means, since it's extremely rare.

14 minutes ago, JorgeB said:

It's very atypical for write errors to show up without any controller issues/timeouts first, though I'm not really sure what this means, since it's extremely rare.

Yeah, I was stumped, too... for the little it's worth, ChatGPT seemed to think it was either a transient SATA data connectivity or power draw issue (which was why swapped out data cables, switched the parity drive to the other SATA port, and I put the HDD on its own dedicated power cable). None of that helped, unfortunately.

I'm like a week past the retailer return window. Hoping I don't have to go through WD for a replacement. And I'm reluctant to even try given the SMART status.

Just an update here in case anybody stumbles on this... the drive eventually failed (a bunch of Reallocated sector count errors), and WD replaced it via RMA.

So apparently Unraid can notice issues before SMART reports start failing, and write errors can show up prior to any timeouts, SMART errors, etc.