![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 93%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E5%3C/text%3E%3C/svg%3E)
Hi experts,
Our customer environment is Azure Stack HCI 23H2, configured as a 3-node cluster with 3-way mirror protection.
During a recent online update, we noticed that Storage Pool reserve space check has become a mandatory validation.
From what I’ve learned so far:
If the storage pool has sufficient reserved capacity, the system will automatically use it to rebuild data when one drive fails.
If there is no reserved capacity, it seems we can add a replacement drive into the pool first, allowing the system to rebuild the data, and then retire/remove the failed drive afterward.
Can anyone confirm if this understanding is correct?
In Azure Stack HCI 23H2, is the recommended process still to add the replacement drive first, wait for the repair job to complete, and then remove the failed drive when the pool has no reserved capacity?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Hello 57803309,
Yes, your understanding is correct.
In Azure Stack HCI 23H2, when no reserved capacity is available, the recommended process for replacing a failed drive is as follows:
Add the replacement drive first.
Wait for the repair job to complete.
Then remove the failed drive.
For detailed guidance, refer to the official documentation: Replace failed drives on Azure Stack HCI or Windows Server
If you have any further questions, please let us know.