Hello,
This behavior may occur if the physical capacity added is not yet reflected as available logical space due to tier alignment or metadata overhead. Additionally, the Resize-StorageTier cmdlet may fail if the tier’s allocation boundaries are not properly updated post-rebalance.
We recommend the following steps:
- Run
Get-StorageTierandGet-StoragePoolto confirm the actual available capacity and tier mapping. - Use
Optimize-StoragePoolto ensure the pool metadata is refreshed. - Try resizing in smaller increments (e.g., 10–20GB) to test allocation thresholds.
- Confirm that the drives added match the media type and resiliency settings of the target tier.
- Review cluster health via
Get-ClusterStorageSpacesDirectfor any latent warnings.
If my answer is useful for you, please vote for it.
Best regards,
Domic Vo.