Azure cluster deployment fails at Config storage step

Question

Azure cluster deployment fails at Config storage step

Gopal Dogra (gdogra) 25

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?

Anonymous

2025-12-02T14:18:05.08+00:00
Hi Gopal Dogra (gdogra),

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-StoragePool and reboot all nodes.

Check cluster logs: Use Get-ClusterLog or 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!
Anonymous

2025-12-04T09:17:17.46+00:00

Hi Gopal Dogra (gdogra),

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!
Anonymous

2025-12-05T10:54:30.2566667+00:00

Hi Gopal Dogra (gdogra),

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!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-08T04:40:07.6133333+00:00

Hi, Storage SubSystem became healthy after these steps.

But I was not able to proceed with the deployment, because the servers were connected via HBA controller and it is not supported by Azure cluster deployment. After removing the HBA controller, deployment remained unhealthy with Get-PhysicalDisk call showing Hardware not compliant error.. I am planning to cleanup the setup and start the deployment again.
Anonymous

2025-12-08T08:30:33.8866667+00:00

Sure Gopal Dogra (gdogra),

Let me know the updates once done with cleanup.

Thank You!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-09T13:09:34.1+00:00

After cleanup, deployment proceeded further. But it is now failing at Stage hardware updates via Solution Builder Extension (SBE). SBE folder itself is missing in the CSV location in the error message. I had copied my custom SBE build with minimal changes to C:\SBE folder before starting cluster deployment.

Error message:

Type 'SBECopyFromSeedNode' of Role 'SBE' raised an exception: SBE: Before SBE SeedNode->CSV copy, content failed integrity check in 'C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\CloudMedia\SBE\Staged\Metadata' at SBECopyFromSeedNode

Can you share your thoughts on what can be done to unblock this?
Anonymous

2025-12-10T07:21:46.7866667+00:00

Hi Gopal Dogra (gdogra),

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!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-11T02:54:05.0666667+00:00

Update: A fresh Azure cluster deployment succeeded, when tried without putting SBE related files in C:\SBE folder.

Thanks for the help.

Answer accepted by question author

0 additional answers

Your answer

Anonymous

2025-12-02T14:18:05.08+00:00

Hi Gopal Dogra (gdogra),

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-StoragePool and reboot all nodes.

Check cluster logs: Use Get-ClusterLog or 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!
Anonymous

2025-12-04T09:17:17.46+00:00

Hi Gopal Dogra (gdogra),

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!
Anonymous

2025-12-05T10:54:30.2566667+00:00

Hi Gopal Dogra (gdogra),

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!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-08T04:40:07.6133333+00:00

Hi, Storage SubSystem became healthy after these steps.

But I was not able to proceed with the deployment, because the servers were connected via HBA controller and it is not supported by Azure cluster deployment. After removing the HBA controller, deployment remained unhealthy with Get-PhysicalDisk call showing Hardware not compliant error.. I am planning to cleanup the setup and start the deployment again.
Anonymous

2025-12-08T08:30:33.8866667+00:00

Sure Gopal Dogra (gdogra),

Let me know the updates once done with cleanup.

Thank You!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-09T13:09:34.1+00:00

After cleanup, deployment proceeded further. But it is now failing at Stage hardware updates via Solution Builder Extension (SBE). SBE folder itself is missing in the CSV location in the error message. I had copied my custom SBE build with minimal changes to C:\SBE folder before starting cluster deployment.

Error message:

Type 'SBECopyFromSeedNode' of Role 'SBE' raised an exception: SBE: Before SBE SeedNode->CSV copy, content failed integrity check in 'C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\CloudMedia\SBE\Staged\Metadata' at SBECopyFromSeedNode

Can you share your thoughts on what can be done to unblock this?
Anonymous

2025-12-10T07:21:46.7866667+00:00

Hi Gopal Dogra (gdogra),

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!
Gopal Dogra (gdogra) 25 Reputation points

2025-12-11T02:54:05.0666667+00:00

Update: A fresh Azure cluster deployment succeeded, when tried without putting SBE related files in C:\SBE folder.

Thanks for the help.

Answer 1

Hi @Gopal Dogra (gdogra)

This error usually means the cluster’s SBE “seed” content and the CSV copy no longer match what the deployment engine expects, often because of a manual/custom SBE drop or missing files in the SBE path.

To resolve this, restore a clean and expected SBE payload and allow the deployment process to re-stage it, instead of using content manually copied to C:\SBE.

Stop the current deployment action plan so no further SBE steps run against the corrupted content.
On the seed node, obtain the correct SBE package from the OEM/Microsoft‑provided source (for DataON, use the SBE download/manifest endpoint or OEM guidance) and extract it under the standard CloudDeployment path, not C:\SBE with custom edits.
Delete or rename any existing content under C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\CloudMedia\SBE\Staged so that Metadata/Content will be freshly repopulated on the next run.

Correct staging steps

Follow the documented “Later deployment” SBE flow: copy SBE from the extracted location (for example C:\CloudDeployment\ExtractedSBE or OEM‑documented equivalent) to the CSV path ...\CloudMedia\SBE\Staged using the provided scripts/workflow, not a manual folder copy or custom build.
Ensure that once the ...\SBE\Staged\Content and ...\SBE\Staged\Metadata folders are populated on CSV, they are not modified; any edits or missing files will cause the integrity check (hash/manifest validation) to fail again.

What to check if it still fails

Confirm on the seed node that the SBE you are deploying exactly matches the OEM version validated for your Azure Local/Azure Stack HCI build and hardware; mixing versions or editing files is unsupported and will trigger integrity failures.
If the integrity check still fails with a clean SBE package and fresh Staged folder, collect the metadata files from ...\SBE\Staged\Metadata and the cluster deployment logs, then open a support case; these files are specifically referenced in Microsoft’s Azure Local SBE troubleshooting guides for deeper triage.

Documents:

Please let me know if the steps above were helpful, or if you have any questions feel free to reach out to me.

Thank You!

Share via

Azure cluster deployment fails at Config storage step

0 additional answers

Your answer