S2D storage resynchronization stuck at 99% after node reboot.

Hello S Kumar,

If a node reboot causes the Storage Spaces Direct resync process to stop at 99% and not complete, the cause is usually stale dirty page tracking records, preventing the Storage Repair Job from committing the final state. This is a phenomenon that Microsoft has noted in S2D clusters. The safe way to handle this is to run Clear-ClusterStoragePoolDirtyPage or the equivalent of clearing stale entries, then restart the repair job using Repair-ClusterStoragePool -Name <PoolName>. If this command is not available in the current build, you can stop the job (Stop-StorageJob) and restart it to force the cluster to recalculate the synchronization state.

It is important not to restart the entire cluster, but you should confirm that all nodes are healthy (Get-ClusterNode) and that no disks are set to Retired. If dirty page tracking cannot be removed using PowerShell, the only solution is to wait for an official hotfix from Microsoft, as this is a logic error in the resync mechanism. In the meantime, the cluster will remain stable thanks to redundancy, but you need to monitor it closely to avoid losing another node.

If my answer is useful to you, please click "Accept the answer" to support me.

Thank you,

HL.