I have an Intel NUC with Windows 10 64bits, I connected with USB3.0 (UASP) an 8-bay HDD enclosure that contains 2 new HDD WD Red 6Tb, and 1 old HDD WD Green 2Tb (99% full but healthy, formatted with ReFS). With the two WD Red I created with Storage Spaces a 2-way mirrored volume of 6Tb (thick provisioning) formatted with ReFS. Then I want to migrate the content of the WD Green to the empty Storage Spaces volume with the following command as administrator:
robocopy "E:\data" "D:\data" /COPY:DAT /DCOPY:DAT /E /J /B /MT:4 /W:5 /R:50 /UNILOG:log.txt /TEE
I made 2 attempts and both given the same result: Everything seems to work fine for roughly 30 minutes, then Storage Spaces suddenly thinks the two disks failed simultaneously and kill the pool. But if I take them back online, everything work again flawlessly!
I don't think the disks are faulty as they perform well when I do anything other than this 2Tb file transfert. The first HDD enclosure I received WAS clearly faulty and I sent it back for a replacement, now the new enclosure seems fine as I also don't have any problem with it except with this transfert.
From what I found on the Internet the best guess I have for two healthy disks to be declared dead at the same time is maybe a 30 minute timer that put the HDD enclosure or the HDD themselves in idle mode, and when the next access happens by the time everything go back online Windows already marked both disks as unresponsive. But why would this happens in the middle of a big copy? So I'm a little lost...
What can be wrong with this Storage Spaces volume? What should I check to identify the root cause of this problem?