Yeah I generally have avoided storage spaces for this reason. The Microsoft Surface Pro 5 (aka "Surface Pro" and not Surface Pro 6 or 4) used 2 NVME SSDs in a built-in hardware based Storage Space solution crafted by Microsoft. Mind you this was NTFS-based. Still exhibited hard disk corruption problems on multiple models; even new out of the box. Solution was ultimately warranty return for a literal upgrade to the next version of the hardware. Also had a home user running Storage Spaces and it caused nothing but mayhem with around 10 1TB drives. This person ultimately switched to not even running a software based spanned volume and just did separate drives. Software based solutions that involve proprietary architecture has never really been a good replacement for RAID1 or RAID10, although I do understand how convoluted and annoying RAID itself can become. Sorry that you lost data. Like I wrote earlier, whether or not the actual files are worth even trying to recover is really questionable, unless it contained some seriously mission critical stuff. In such a scenario, even under RAID1, I'd consider making monthly backups and keeping them in a safe or off-site somewhere if the data is that extremely important. I'd also seriously just ignore ReFS and stick with what we know works. Really NTFS or ext4 at this point.UPDATE: I ran EaseUS and talked with one of their techs about my situation. The software can read the volume file system structure but, unfortunately cannot recover any files from it. However, it is able to recover nearly all of the files for those file types which it recognizes. Sadly, the most important data I wanted to recover is in file types which are not recognized by EaseUS.
However, on the hardware side, my motherboard utility confirms that the health of the two physical drives is healthy. And, given, that EaseUS can recover files from this volume, they are clearly responding rather than "failed" as indicated in storage spaces.
I am severely regretting having gone with ReFS. It really seemed like a good solution but, clearly, has become a dead end. I should have just stuck with RAID 1.
I'm going to reach out to some data recovery companies and see what they might be able to offer. I'm also going to try moving these drives to other SATA ports on the board. Although, this does not seem to be a hardware issue but simply an instance where ReFS lost its understanding of the drives below it.
laff. these storage spaces do not really "belong to us" . Make sense to always keep 2-3 copies ELSEWHERE, so now this issue is just funny and inconvenientIt's baaaacckkk. Just had this same thing happen again. So much for 'Resilient File System'. What BS.
This time with my other ReFS drive but, again, following the recent cumulative update. Unfortunately, I did not (back in June) replace the ReFS with a standard NTFS. Nor did I do this last fall when I again felt prompted to take this step.
Fortunately, I have a full backup of this drive in the cloud. It could take a while to restore it but it would be faster than trying to manually reconstruct the folder structure and repopulate with the recovered files from EaseUS.