If you see CannotPoolReason = Insufficient Capacity or Unrecognized Metadata , the disk may have been part of a failed Storage Pool.
In complex environments or failover clusters, the default WinRM (Windows Remote Management) packet size may be too small to transmit all required management data. Resolution Steps
netsh trace start capture=yes provider=Microsoft-Windows-TCPIP tracefile=C:\trace.etl maxsize=256 netsh trace stop If you see CannotPoolReason = Insufficient Capacity or
Go back to Server Manager and click the Refresh icon at the top. Step 2: Repairing WMI Repositories
If you are managing remote servers or Exchange DAG members, the management data might exceed the default 512 KB WinRM limit. PowerShell Command: Run the following as an Administrator on the management server and the target node: powershell Step 2: Repairing WMI Repositories If you are
When standard diagnostics fail:
Run a read-only scan first (never use /f on an online system with suspected hardware failure): If you see CannotPoolReason = Insufficient Capacity or
$FailedDisk = Get-PhysicalDisk -FriendlyName "PhysicalDiskX" Remove-PhysicalDisk -PhysicalDisk $FailedDisk -StoragePoolFriendlyName "YourPoolName"