Windows 10: Windows 10 Storage Spaces Mirrored VirtualDisk crashed after single HDD failure

I have suffered yet another fatal Storage Spaces crash after 1 of my 8 HDDs failed. I have a mirrored VirtualDisk which is 1TB and it become detached, lost communication with the failed PhysicalDisk HDD. I have 3 other mirrored VirtualDisks which are still working fine. I cannot connect the unhealthy VirtualDisk and cannot repair the VirtualDisk. Windows 10 SS GUI will not automatically fix this issue, and Powershell commands have not worked. The only difference between the failed VirtualDisk and those that are still running is that the failed VirtualDisk was evidently at almost 100% full, whereas the other VirtualDisks were about 60%. The PhysicalDisk that failed is Lost Communication. Evidently, SS tried to remove data off the HDD which started at about 60% usage and was able to move data off to about 11% usage before the drive totally died.


I have added 2 additional HDDs so I now have 13 TB used out of 30 TB pool. I don't understand how a mirrored VirtualDisk in a pool of 8 HDDs can be taken offline and crash from a single HDD failure. In theory, should there not be a second, complete copy of every file in the mirrored VirtualDisk?


If anyone has any idea of how to work around this failed HDD and get my VirtualDisk back online, at least long enough to move the files, I would be very thankful. Again, the failed PhysicalDisk is dead, not just unhealthy. The VirtualDisk is detached, unhealthy, but I cannot get it back online.

:)

 

Storage Spaces full... Irreparably

I have a mirrored ReFS storage space, in which I am using 2.67TB of the available 4.10TB capacity. (i.e. I've got about 1.3 GB of stuff, but it's mirrored)

476GB drive (SSD, 99.6% used, retired)

931GB drive (HDD, 0.08% used, OK)

931GB drive (HDD, 96.3% used, OK)

1.81TB drive (HDD, 73.6% used, OK)

Windows has decided that something is full, and no longer allows me to access any of the files in the storage space. Attempting to open the drive in Explorer results in an error "S:\ is not accessible.
There is not enough space on the disk"

In the event viewer, I find that ReFSv1 is throwing an error when trying to mount the volume at boot time:

"Volume is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status An operation failed because the disk was full. If this is a thinly provisioned volume the physical storage backing this
volume has been exhausted."

Failure reason: 0xc000007f

I have attempted Repair-VirtualDisk, but Get-StorageJob shows that the repair process is suspended at 0%.

Question: How do I either fix this, or recover the information from the storage pool?

 

Windows 10 Storage Spaces Improvements?

Here is an example where a 3-way mirror space named VDiskMirrorPS is created on an existing storage pool named Pool01

Optimizing Windows Server 2012 storage management via PowerShell for both performance and resiliency

New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Mirror -Size 200GB

-FriendlyName VDiskMirrorPS -ProvisioningType Fixed -NumberOfDataCopies 3 -NumberOfColumns 3

For a 12 column dual parity space his command would be:

New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Parity
-Size 200GB

-FriendlyName
MyNewParitySpace -ProvisioningType Fixed -NumberOfDataCopies 2 -NumberOfColumns 12

If you are unfamiliar with managing storage spaces via PowerShell I suggest you create some virtual disks (Disk Management > Create VHD) of sizes maybe 20GB-50GB and spend a long time researching and testing various dummy
storage space configurations. It is the easiest way to understand where the overhead comes from, what column size to choose, what happens when you mix disk sizes, how much space is gained when you add a new disk to the pool, etc.

 

Storage Spaces Mirror 2 Drives?


Hi,

An excerpt from the link provided by lx07:

Nothing ever is but the setup as described in the quote above sure is a lot more resilient than just a basic disk.

Cheers, *Wink