Fix Storage Spaces Pool Showing Reduced After a Single Disk Removal

After removing a single physical disk from a Storage Spaces pool in Windows 11, the pool might show a reduced capacity even though the remaining disks should provide enough space. This happens because Storage Spaces reserves a portion of capacity for repair operations and does not immediately reclaim space after a drive is removed. This article explains why the pool capacity shrinks, how to manually reclaim the space, and what to do if the problem persists.

Why Storage Spaces Pool Capacity Drops After Removing a Disk

Storage Spaces uses a parity or mirror layout to protect data against disk failure. When you remove a physical disk, the virtual disk loses one copy of some data stripes. To maintain the defined resilience level, Storage Spaces marks the capacity of the removed disk as unavailable until the data is repaired and rebalanced across the remaining disks.

The pool size shown in Windows includes the capacity of all physical disks minus the reserved repair space. After a disk removal, the system reserves additional space to rebuild the missing data stripes. This reservation appears as reduced usable capacity. The pool does not automatically reclaim this space because the repair process is not triggered by a manual removal — it must be started explicitly.

Another factor is the column count of the virtual disk. If the virtual disk was created with a column count equal to the original number of disks, removing one disk leaves the virtual disk with fewer columns than expected. The system then reduces the usable capacity to match the available columns until the repair completes.

Steps to Repair the Virtual Disk and Reclaim Storage Pool Capacity

The following steps use the Storage Spaces graphical interface in Windows 11. If the repair option is not visible, use the PowerShell alternative in the next section.

1. Open Storage Spaces
   Go to Settings > System > Storage. Click Advanced storage settings, then click Storage Spaces. This opens the management page for your storage pools.
2. Identify the affected storage pool
   Under the storage pool name, click Properties. Review the physical drives listed. The removed disk should no longer appear. If it still appears as disconnected, skip to the PowerShell method.
3. Click Manage Storage Spaces
   On the storage pool properties page, click Manage Storage Spaces. This opens a page showing all virtual disks in the pool.
4. Select the virtual disk with reduced capacity
   Click the virtual disk that shows the reduced size. Its details panel opens below.
5. Click Repair
   If the Repair button is available, click it. Windows will start rebalancing the data across the remaining disks. This process can take from minutes to hours depending on disk speed and data volume. Do not shut down or restart the computer during the repair.
6. Verify the pool capacity after repair
   After the repair completes, go back to the storage pool properties. The usable capacity should now reflect the total capacity of the remaining disks minus the resilience overhead.

If the Repair Button Is Missing

In some Windows 11 builds, the Repair button does not appear if the virtual disk is still in a healthy state. In this case, run the repair using PowerShell.

1. Open PowerShell as administrator
   Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin).
2. List virtual disks
   Run Get-VirtualDisk | Format-Table FriendlyName, OperationalStatus, HealthStatus, Size. Note the FriendlyName of the virtual disk that shows reduced size.
3. Repair the virtual disk
   Run Repair-VirtualDisk -FriendlyName "YourVirtualDiskName". Replace the name with the actual FriendlyName from the previous step. If you have multiple virtual disks, run the command for each one.
4. Monitor repair progress
   Run Get-VirtualDisk -FriendlyName "YourVirtualDiskName" | Get-StorageJob to see the repair percentage. Wait for the job to reach 100%.
5. Verify the pool capacity
   Run Get-StoragePool -FriendlyName "YourPoolName" | Format-Table Size, AllocatedSize. The Size value should now be closer to the sum of the remaining physical disks.

If the Pool Capacity Still Shows Reduced After Repair

If the repair completes but the pool capacity remains lower than expected, check the following issues.

Virtual Disk Column Count Mismatch After Disk Removal

When you remove a disk, the virtual disk may still expect the original number of columns. This forces the system to reserve capacity for a column that no longer exists. To fix this, you must reduce the column count. This operation requires PowerShell.

Run Get-VirtualDisk -FriendlyName "YourVirtualDiskName" | Get-ResiliencySetting | Format-Table Name, NumberOfColumns, NumberOfDataCopies. If the NumberOfColumns value is greater than the number of physical disks remaining, run Set-ResiliencySetting -Name "YourResiliencySettingName" -NumberOfColumns (Number of remaining disks). Then run the repair command again.

Storage Pool Capacity Reserved for Repair Operations

Storage Spaces reserves a small amount of capacity per physical disk for metadata and repair operations. This reservation is not reclaimable. If the remaining disks are small, the reservation can be a noticeable percentage. There is no setting to reduce this reservation.

Disconnected Disk Still Claiming Capacity

If the removed disk was not properly ejected from the pool, it may still show as disconnected and reserve capacity. Open PowerShell as administrator and run Get-PhysicalDisk | Where-Object {$_.CanPool -eq $false -and $_.OperationalStatus -eq "Lost Communication"}. If any disks appear, run Remove-PhysicalDisk -FriendlyName "DisconnectedDiskName" to remove it from the pool. Then run the repair again.

Storage Spaces Pool Capacity: Before vs After Disk Removal

Item	Before Disk Removal	After Disk Removal Without Repair	After Disk Removal With Repair
Physical disks in pool	4 x 1 TB	3 x 1 TB	3 x 1 TB
Raw capacity	4 TB	3 TB	3 TB
Usable capacity (two-way mirror)	2 TB	1.5 TB (reserved for repair)	1.5 TB
Usable capacity (parity)	2.67 TB	2 TB (reserved for repair)	2 TB
Repair action needed	None	Yes	Already done

The table shows that the usable capacity after removal is the same whether you run the repair or not. This is because the resilience overhead changes proportionally with the number of disks. The repair does not increase total usable capacity — it only ensures that data remains protected and that the pool can accept new disks or expand in the future.

You can now repair a Storage Spaces virtual disk after removing a physical drive and reclaim the pool capacity that appeared lost. If the pool still shows reduced space, check the column count and remove any disconnected disks using PowerShell. For future disk removals, always run the repair process immediately to avoid confusion about available capacity.