![](https://it-infrastructure.solutions/content/images/2022/03/image-140.png)
This article has not been completed yet. However, it may already contain helpful Information and therefore it has been published at this stage.
![](https://it-infrastructure.solutions/content/images/2022/03/image-141.png)
![](https://it-infrastructure.solutions/content/images/2022/03/image-142.png)
Mirror-accelerated parity - Two-way mirror:
![](https://it-infrastructure.solutions/content/images/2022/03/image-146.png)
Storage efficiency: 50 percent
Tolerate: One hardware problem
Three-way mirror:
![](https://it-infrastructure.solutions/content/images/2022/03/image-147.png)
Storage efficiency: 33.3 percent
Tolerate: Two hardware problems
![](https://it-infrastructure.solutions/content/images/2022/03/image-143.png)
![](https://it-infrastructure.solutions/content/images/2022/03/image-144.png)
Expected result:
![](https://it-infrastructure.solutions/content/images/2022/03/image-145.png)
If the volume isn't created properly (see screen below), especially in a single node deployment I observed this several times, then you can switch to provisioning via PowerShell.
![](https://it-infrastructure.solutions/content/images/2022/06/image-240.png)
The PowerShell - Way:
# CSV creation directly on the node:
New-Volume -FriendlyName "VMStore" -Size 1TB -ProvisioningType Thin
![](https://it-infrastructure.solutions/content/images/2022/06/image-241.png)
![](https://it-infrastructure.solutions/content/images/2022/06/image-242.png)
![](https://it-infrastructure.solutions/content/images/2022/06/image-243.png)
References:
Fault tolerance and storage efficiency on Azure Stack HCI and Windows Server clusters - Azure Stack HCI
A discussion of resiliency options in Storage Spaces Direct including mirroring and parity.
![](https://docs.microsoft.com/en-us/media/logos/logo-ms-social.png)