Azure Stack HCI - Unable to create volume on single node

PANDOLFINO Luigi 20 Reputation points

Good morning everyone, we have a problem deploying a single node solution.
After configuring Azure Stack HCI in single node mode, following the Microsoft documentation, we are unable to create volumes:
Create Volume

The state of the disks is this:Disks state

PS C:\> Get-PhysicalDisk

Number FriendlyName         SerialNumber      MediaType   CanPool OperationalStatus HealthStatus Usage            Size
------ ------------         ------------      ---------   ------- ----------------- ------------ -----            ----
4      DELLBOSS VD          16c5978f86790010  Unspecified False   OK                Healthy      Auto-Select 223.51 GB
1001   ATA HFS960G32FEH-BA1 ENC7N4235I040776Q SSD         False   OK                Healthy      Auto-Select 894.25 GB
1003   ATA HFS960G32FEH-BA1 ENC7N4235I040776K SSD         False   OK                Healthy      Auto-Select 894.25 GB
1000   ATA HFS960G32FEH-BA1 ENC7N4235I040776O SSD         False   OK                Healthy      Auto-Select 894.25 GB
1002   ATA HFS960G32FEH-BA1 ENC7N4235I0407718 SSD         False   OK                Healthy      Auto-Select 894.25 GB

PS C:\> Get-StoragePool

FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly    Size AllocatedSize
------------ ----------------- ------------ ------------ ----------    ---- -------------
Primordial   OK                Healthy      True         False      3.71 TB       3.49 TB
Primordial   OK                Healthy      True         False      3.71 TB       3.49 TB
S2D-DEACL02  OK                Healthy      False        False      3.49 TB          1 GB

PS C:\> Get-StorageTier

FriendlyName TierClass MediaType ResiliencySettingName FaultDomainRedundancy Size FootprintOnPool StorageEfficiency
------------ --------- --------- --------------------- --------------------- ---- --------------- -----------------
MirrorOnSSD  Unknown   SSD       Mirror                1                     0 B             0 B
Capacity     Unknown   SSD       Mirror                1                     0 B             0 B

Even trying to create the volume via PowerShell we encounter an insufficient space error (see the first screenshot with 0 GB available).
We did not find any confirmation in the Microsoft documentation.

Thank you in advance!

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
217 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Trent Helms - MSFT 1,976 Reputation points Microsoft Employee


    Thank you for sharing the command and output. I think I see why this issue is occurring. As noted in the article above for a single-node cluster, S2D will automatically use 2-way mirroring when creating a volume. As their will be two copies of the same data, the footprint of the volume will be two times the size of the useable space. In order to create a 2TB volume, you would need 4TB of free space. Unfortunately, your storage pool only has 3.49TB of space. This is why the volume creation appears to be failing.

    Typically, we recommend always reserving some free space in the pool in case a drive was to fail so that S2D could automatically repair the volume. The amount of space to reserve would be based on the size of the drives that were being used in the pool itself. Using your drives from above, we would typically recommend reserving 894.25GB, the size of one of the drives. If you were to do that in this cluster, that would only leave you with 2,682.75GB of free space to create your volume. And since S2D uses 2-way mirroring for volumes on a single-node cluster, your maximum volume size would be half of that, or 1,341.375 GB.

    Reserving free space is optional. If you don't reserve the free space, it just means that S2D won't be able to automatically repair the volume in case of a drive failure until that drive has been replaced. If you decide not to reserve any free space, then the maximum volume size you could create would be approximately 1.745TB (1,788.5GB). Keep in mind that due to the way the calculations are made at the byte level, you may still have to adjust that number down slightly.

    Hope this helps!