How do I recover/repair my storage space?

dc71582 said:

Here is my current Storage Spaces view:
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.

Yes, it is odd. What about event viewer?

@dalchina: I am not sure, unfortunately.

Apologies, I have to leave, will be back later.

dalchina said:

Hard disk sentinel (trial) gives a very clear indication.

(I would guess anyone using storage space needs to run a disk status monitor)

Hard disk sentinel appears to tell the same story as Crystal:



The other two disks in the pool are "PERFECT" according to HDS.

muchomurka said:

Yes, it is odd. What about event viewer?

@dalchina: I am not sure, unfortunately.

Apologies, I have to leave, will be back later.

I'm afraid I'm not sure what to look for in Event Viewer. I don't see anything that is drawing my attention as being storage pool related but there is, I think, a lot of other noise in here.

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

muchomurka said:

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.

muchomurka said:

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

dc71582 said:

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!