G
gtaus
Guest
I was advised to post this question here instead of the Microsoft Community forums. Here is my question copied from the other forum.
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.
More...
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.
More...