Expand guest-cluster S2D storage without resizing its existing disks

Source facts

Microsoft documents Storage Spaces Direct guest clusters as shared virtual storage built across multiple VMs. The exposed virtual disks must keep their existing size and characteristics. Its capacity-expansion procedure adds more virtual disks to each VM and then to the pool, recommending disks with the same size and characteristics as the existing ones. Microsoft Learn.

Applicability

Confirm the guest-cluster platform, underlying VM placement, and current virtual-disk layout. Review the guest-cluster requirements for the actual hypervisor before making a storage change. Keep a host-level disk expansion and a guest-cluster pool expansion as separate operations.

DSE recommendation

Prepare a disk inventory for every guest node with identifiers, capacity, and presentation settings. Have the storage owner review the additional-disk plan against that inventory. Record the expected new pool capacity and the assignment of every added disk before execution. Preserve a recoverable configuration record and schedule the change with the application owner rather than resizing an existing disk as an informal shortcut.

Verification

After the approved addition, inspect the disks presented to each guest and compare their characteristics with the plan. Confirm pool membership, health, and the expected capacity increase. Exercise a representative application transaction and record any asymmetric node configuration. Resolve missing or unexpected disks before creating or extending workloads on the new space.

Official references

Microsoft Learn: Using Storage Spaces Direct in a virtual machine. Source reviewed September 8, 2026.