Just set up my first unRAID array a few days ago, currently consisting of two 8TB drives (one data, one parity). I wrote all my data (about 2TB) to it without issue, built the parity, everything seemed fine. The last thing I wanted to test was the auto-spin-down feature, so last night I manually spun the drives down before I went to bed, and let it sit overnight.

 

This morning I tested the wakeup functionality by simply copying a small text file to the array, and watching the dashboard to make sure the drives spun up and wrote the data correctly. I opened the array in windows explorer, prompting the data drive to spin up. I copied the text file over, then quickly deleted it. The parity drive didn't spin up when the data drive did, but the data drive accepted the write commands anyway.

 

A minute or two after copying and deleting the file, the parity drive spun up and started to process the two write commands, but it spat out a scary disk write error, prompting the parity disk to go into an error state. The first thing I did was ran a SMART check on both drives, which both came back clean (though, it was a quick test not an extended one).

 

Following some advice online, I stopped the array and rebooted the machine. Then I unassigned the parity drive in the array configuration, started the array, immediately stopped it, re-added the parity drive, and started the array again.

 

Currently I'm running a parity rebuild, no issues so far, with about 8 hours left to go. I've attached the diagnostics file. What do you all think? Does this sound like an intermittent software bug, or something that would warrant replacing the parity drive? Both are brand new.

lcarsalpha-diagnostics-20210510-0917.zip