Windows 10: How do I recover/repair my storage space?

That at least suggests hope the disk warnings are early indications.

My best guess right now for recovery would be to revert to 1703. But it is only a guess.

Before making any changes I would generally recommend creating a full disk image to preserve what you have- but here you have a complex situation with a lot of data. Plus the possibility the image would fail on the suspect disk.

You could at least image your system disk, then revert ('Go back to the previous build'), then you've access fairly readily to 1703 and 1709.

Ideally someone else here who uses Storage space and has upgraded to 1709 would comment... unfortunately there seems a complete lack of comments after the several tutorials on this- which is unusual. E.g.
Create Storage Space for Storage Pool in Windows 10 Hardware Drivers Tutorials

 

Quick suggestion:
- shutdown
- disconnect the HEALTHY physical disk only
- boot OS
- repeat powershell commands
- paste result

 

Done. Here are the results:





I have not yet attempted to revert to 1703 (not sure how I do that, honestly) so this is all exactly as it was since I posted last.


By the way gents, thank you so very much for working with me on this. Your efforts, however fruitful they end up being, are appreciated. I will be away for the next few hours but I'll try to run any further tests and post back here again by morning.

 

Bad news. Every one of three disks is functionally OK and holds data, but it is splitted from the rest two, so former RAID array falled into three incomplete and nonfunctional pieces (because RAID metadata became inconsistent). No idea why this happened.

I agree with dalchina, the next step should be reverting back to previous build (run PC Settings, click Update & Security, Recovery, Go back to the previous version). A little chance it can help but let's try it.

If it does not help we can try to repair metadata but it may be unrecoverably destructive operation. This option uses reset-physicaldisk command:
"If you run Reset-PhysicalDisk on a physical disk that appears as lost communication or split, this cmdlet attempts to re-integrate the disk into the Storage pool if the disk is discoverable. After you reset a physical disk, use Repair-VirtualDisk to restore its resiliency."
Reset-PhysicalDisk

Update: I am almost convinced that Reset-PhysicalDisk command returns disk into pool as empty (with data loss), so this is not an option. Unfortunately, I am not able to simulate Split disks in pool so I cannot verify it.

Before it, please attach disconnected disk, roll back to previous build, and let us know if the problem persists.

 

Here's a small update. I haven't yet reverted because when reconnected my healthy WD drive and rebooted I noticed something curious; Now in the storage pool screen within Windows the WD drive now shows as having the error where as the Seagate drive that HDS said was fine now still shows as fine just like it did when there were only 2 drives connected. In other words, the second drive error moved from one drive to another! Bizarre

 

Yes, all disks are OK, but cannot successfully form pool with volume because they lost mutual consistence. Now they are independent but only one can register the same pool unique id, and wins that one which registered it last time. You may probably revert it if you can by disconnecting two smaller disks and booting OS.

 

So the good news is that rolling back the 1709 version did magically resolve my issue. The bad news is that I don't know why that worked really. My pool is running NTFS so I've no explanation. VERY HAPPY right now. Backup in process. Thank you so much for the support guys!

 

I guess that makes you one very lucky user.. or unlucky as you need to discover whether Storage Spaces can be migrated to 1709 successfully- and what to do to deal with this problem in general.

Suggest you take it up on technet (MS site) and report via the Feedback Hub app.

Meanwhile you need to consider your possibly dodgy disk - try a surface scan- and of course appropriate backups.

As you have Pro, you can use












to delay 1709 for a year

 

Glad to hear your data are available again, but because we didn't identify the cause of problem, you have to make backup before next attempt to v1709 upgrade. Anyway, you can defer this upgrade for one year.

Regarding cause - personally I suspect either wrong disk controller driver or some inconsistency of existing RAID metadata, which manifests itself in version 1709 only (because I made three successfull OS upgrades with Storage Spaces RAID retained - two 3disks/Parity in test environment and one 4disks/Mirror in my workstation). With all data backed up (twice), you may remove existing RAID and create it again from scratch. All three harddisks IMO are physically OK, but you should monitor possible changes in their SMART state.

 

Haven't left you guys yet. Just an update here, I did try the v1709 upgrade again once my data was well backed up and again I encountered the same problem with my storage pool. Next I may try tearing down the pool, upgrading, then recreating it under the new Win10 build.

 

It seems that there is something wrong with your Parity RAID... Back it up twice on different media, remove existing Storage Space completely, re-create it again, restore data. Then it should survive upgrade to v1709 without problems. (Don't forget to write down which SATA controller driver is used before and after upgrade; it may interfere with Parity RAID too.)