How do I recover/repair my storage space?

I apologize if this is not in the correct forum.

I have a storage space on my personal computer that consists of 3 drives. My storage space is setup as parity. Last night I rebooted my machine and allowed it to install new Windows Updates and this morning when I came back to my system it had rebooted and my storage space has died!



As you can see in the image, this is my current status. 2 of my 3 drives are showing this warning status and the storage space has been rendered inaccessible. I am very skeptical that both of those drives actually physically became inoperable at the same moment and I do not hear any clicking or other signs of hardware failure. I desperately want to recover the data from my storage space but I am unsure how to proceed safely and I don't want to make things worse than they already are. If I can even just bring the storage space online long enough to copy the data off to another source that would be perfectly fine.

I've tried running Repair-VirtualDisk in Powershell with admin rights but it seems the job does nothing. When I run Get-StorageJob I can see the repair op in the list and just instantly appears as "Completed".



Can anyone provide me with some guidance?

dalchina said:

Hi, could you state what these were please? (You could post a screenshot of your Update History e.g.).

If your PC has upgraded to 1709, you might have some luck by going back to the previous build. But I'd emphasise that's no more than a thought. I've not noted a post related to storage space for some time, but there may have been...

Do you have a full backup?

I don't know if this is relevant but indicates changes in this area:
Microsoft to remove full ReFS support from Windows 10 Pro, push Workstation SKU | Ars Technica UK
Microsoft removes ReFS file system create option from Windows 10 Pro - gHacks Tech News

Here is my recent update history which covers the incident. If there's another view that shows more detail / history I'm not sure how to find it in Win 10. Interestingly I'm not sure what all the 11/17 updates are about as a definitely did not knowingly update my NVidia driver. Perhaps these are the result of me attempting to restore back? Definitely
appears that the big update was the 1709 and I noted once I was able to get back into Windows that I had more junk in my start menu and system tray per the usual MS upgrade.



Unfortunately, no, I do not have a full backup. I'd lose about a month or so worth of data so I definitely want to avoid that.

I tested upgrade v1511 -> v1709 with two Parity virtual disks, formatted NTFS and even ReFS (yes, it is possible to create ReFS volume on Parity space but it is complicated and unsupported in any way). Both volumes survived without problems, data are still acessible.

Status before upgrade:


Status after upgrade:


So possible causes are:
- upgrade installed improper disk controller driver; installing of right driver or reverting back to older build may solve the problem
- upgrade changed physical disk health evaluation method; reverting back may help (but disks probably are not OK)
- both disks really failed during upgrade (or one failed before and one during upgrade); no simple way to recover data.

The last option is to ask some company specialized in (expensive) data recovery; but before it please give us some info as I wrote before.

@dalchina: upgrading (healthy) pool is an option, not necessary to do it.

muchomurka said:

Hi, please run the following commands and paste result here:

get-storagepool -isprimordial 0
get-storagepool -isprimordial 0 | get-physicaldisk
get-storagepool -isprimordial 0 | get-virtualdisk
get-storagepool -isprimordial 0 | get-volume

Them run Crystal Disk Info and check SMART status of your disks. Also check Administrative Events in Event Viewer for Disk and Storage Spaces errors/warnings.

Here is the output from the PS commands:



Here is the info on the 3 disks from Crystal Disk:



I checked the event viewer for errors and there are nearly 259 just from 11/16 through today but nothing jumps out at me as being necessarily storage related.

Here is my current Storage Spaces view:



I believe this is unchanged from yesterday.

I find it interesting that 2 of the 3 disks in the pool appear to have errors in Storage Spaces but only 1 of those appears to have errors in Crystal Disk Info.