Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
Azure cluster deployment fails at Config storage step
![](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(233.6, 55.00000000000001%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGD%3C/text%3E%3C/svg%3E)
Gopal Dogra (gdogra)
0
Reputation points
While deploying Azure Kubernetes cluster, SBE package had a wrong Model defined in StorageDisks.xml file. Validation had passed successfully. But cluster deployment failed at the Config storage step.
After that, I have tried multiple things - updating StorageDisks.xml file with correct Model, rebooting server. But the Storage Subsystem remains unhealthy with Reason - Your solution vendor doesn't allow adding this model of drive to storage pool.
What can be done to help unblock this cluster deployment? How to re-trigger the health check for the Storage SubSystem?
Azure Arc
{count} votes
-
![](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(0, 80%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator2025-12-02T14:18:05.08+00:00 To resolve the Azure Kubernetes cluster deployment issue at the Config storage step caused by an unhealthy Storage Subsystem due to a mismatched drive model in StorageDisks.xml, first check the drive model with PowerShell commands like Get-PhysicalDisk or S2D tools to ensure it matches the updated XML entry.
Next, try repairing the storage pool using Repair-StoragePool in PowerShell (as admin), or reset the storage subsystem with Reset-StoragePool if the pool has failed. After these steps, reboot the server to clear cached validation. If you encounter a vendor restriction error, reach out to the SBE solution vendor for policy overrides or firmware updates, as OEM Storage Spaces configurations may block mixed drive models.
Additional Troubleshooting Steps:
- Validate XML syntax and rescan disks: Edit StorageDisks.xml correctly, then run
Update-StoragePooland reboot all nodes. - Check cluster logs: Use
Get-ClusterLogor Azure Activity Log for detailed Config storage failures.
Document:
Troubleshoot the failed deployment of a Kubernetes application offer
I hope the above helps. Please let us know if you have any further questions on this.
Thank You!
- Validate XML syntax and rescan disks: Edit StorageDisks.xml correctly, then run
-
Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator
2025-12-04T09:17:17.46+00:00 Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Thank You!
-
Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator
2025-12-05T10:54:30.2566667+00:00 Just checking in, if you got a chance to review my earlier response, let me know if you're still blocked with the issue.
Thank You!
Sign in to comment
Sign in to answer