S2D cluster SSD wear and replacement

I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!

Hello HAILEY PORTER,

In Storage Spaces Direct (S2D), zero‑downtime drive replacement can be tricky when wear metrics fail or firmware updates don’t apply. Normally, the supported workflow is to retire the disk gracefully and let the cluster rebuild data onto healthy drives before physically swapping it out.

If Set-PhysicalDisk -Usage Retired does not succeed, another option is to use Remove-PhysicalDisk in combination with Repair-ClusterStoragePool to trigger data redistribution. This ensures the pool maintains redundancy while the faulty drive is being removed. You can also use Suspend-ClusterNode temporarily to drain workloads before maintenance, though this is more disruptive. For firmware or health checks, Get-StorageReliabilityCounter remains the best way to confirm endurance statistics before deciding on replacement.

Best practice is to always validate that sufficient capacity exists in the pool before retiring a disk, otherwise repair jobs may stall. It’s also recommended to stagger replacements and monitor Get-StorageJob to confirm completion before proceeding with additional changes. In environments where live replacement consistently fails, scheduling maintenance windows and scripting retire/repair operations is often the most reliable path.

I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

Jason