What can cause this exception at deployment? "Set up storage pools, file shares, and CSVs."

Question

What can cause this exception at deployment? "Set up storage pools, file shares, and CSVs."

GabeCz 26

hi

full text of exception (without the activity id which i'm happy to shar in private)

Type 'ConfigStorage' of Role 'Storage' raised an exception: The storage pool could not complete the operation because its configuration is read-only. Activity ID: (xyz)

i do have the role assignment "Storage Account Contributor (1)" with the user as user who is deploying the cluster.

That's all i can think of as something would be missing to casue this exception.

Evidently it is not.

What then?

This is a newly created resource group so some necessary permissions may be missing.

Here are the ones i have:

owner, reader, azure connected machine onboarding, azure connected machine resource administrator, azure connected resource manager, azure stack hci administrator, key vault administrator, key vault contributor, key vault data access administrator, key vault secrets officer, storage account contributor

when i'm searching for "storage" in the list of role assignments, there are 70 results, i cannot possibly guess.

thanks

Gabe

Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator

2025-11-28T13:55:30.4933333+00:00
Hi GabeCz,

The exception indicating that the storage pool is set to read-only can happen for several reasons.

Here are the steps you can follow to troubleshoot the issue:

1.Verify all physical drives in the storage pool are connected and healthy.

2.Check storage pool status using PowerShell: Get-StoragePool <PoolName>.

3.If the pool is read-only, set it to read-write:

Get-StoragePool <PoolName> -IsPrimordial $False | Set-StoragePool -IsReadOnly $false

4.If applicable, bring the storage pool online from Failover Cluster Manager.

5.Repair the storage pool if drives had failures, using Repair-StoragePool.

6.Monitor for any automated policies or alerts that could cause storage read-only transitions.

7.Check for and Remove Resource Locks

Navigate: Go to the Resource Group in the Azure Portal.

Locks: Look for the Locks blade/setting on the left-hand navigation.

Check Scope: Check if any locks are applied to:

The Resource Group itself.

The Storage Resource being used for the cluster.

The Cluster Resource (if it exists).

Action: If a lock of type ReadOnly exists, delete it or change its type to CanNotDelete if you still want protection.

Documents:

Storage pool states and troubleshooting

Lock your Azure resources to protect your infrastructure

I hope the above helps. Please let us know if you have any further questions on this.

Thank You!
GabeCz 26 Reputation points

2025-11-28T20:51:13.31+00:00
hi Shraddha

the pool shows

get-storagepool FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize ------------ ----------------- ------------ ------------ ---------- ---- ------------- Primordial OK Healthy True False 8.43 TB 0 B

the locks on the resource group are all Lock Name: DoNotDelete, and Lock Type: Delete on all the nodes, on the cluster, on the key vault, and on the "Storage Account" which i suppose is causing the problem.

Why is it getting locked, if it will cause the deployment to fail?

I am now removing the lock and resume the deployment and let you know if it helped.

Thanks

Gabe

The deployment won't resume it just showing "Waiting for status updates from device." for quite a while now. Any other way to resume deployment but the "resume deployment" button?
GabeCz 26 Reputation points

2025-11-29T19:39:26.32+00:00

when i run get-storagepool on the actual nodes (using a powershell script running from the hyper-v server i get this: i paste a screenshot instead, because pasting the text messes up the looks

I must repeat myself, this script that creates the disks worked just well with my old resource group. so i'm quite sure it is not the cause of the issue here.

<moving personal info >
GabeCz 26 Reputation points

2025-11-30T21:18:51.16+00:00

um

i have waited a day or two, and removed the iso-dvd images from the virtual dvd drive. restarted the deployment now it seems to be ok.

side note: i have never removed the isos before and it worked before. now i will start it from scratch to see if that was the solution.

i must admin the documentation DOES say remove the iso. but as i never did i thought it's ok to leave them in.

i post update on the result later
Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator

2025-12-01T07:49:43.2166667+00:00

Hi GabeCz,

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-02T13:44:17.87+00:00

Hi GabeCz,

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!

1 answer

Your answer

Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator

2025-11-28T13:55:30.4933333+00:00

Hi GabeCz,

The exception indicating that the storage pool is set to read-only can happen for several reasons.

Here are the steps you can follow to troubleshoot the issue:

1.Verify all physical drives in the storage pool are connected and healthy.

2.Check storage pool status using PowerShell: Get-StoragePool <PoolName>.

3.If the pool is read-only, set it to read-write:

Get-StoragePool <PoolName> -IsPrimordial $False | Set-StoragePool -IsReadOnly $false

4.If applicable, bring the storage pool online from Failover Cluster Manager.

5.Repair the storage pool if drives had failures, using Repair-StoragePool.

6.Monitor for any automated policies or alerts that could cause storage read-only transitions.

7.Check for and Remove Resource Locks

Navigate: Go to the Resource Group in the Azure Portal.

Locks: Look for the Locks blade/setting on the left-hand navigation.

Check Scope: Check if any locks are applied to:

The Resource Group itself.

The Storage Resource being used for the cluster.

The Cluster Resource (if it exists).

Action: If a lock of type ReadOnly exists, delete it or change its type to CanNotDelete if you still want protection.

Documents:

Storage pool states and troubleshooting

Lock your Azure resources to protect your infrastructure

I hope the above helps. Please let us know if you have any further questions on this.

Thank You!
GabeCz 26 Reputation points

2025-11-28T20:51:13.31+00:00

hi Shraddha

the pool shows

get-storagepool FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize ------------ ----------------- ------------ ------------ ---------- ---- ------------- Primordial OK Healthy True False 8.43 TB 0 B

the locks on the resource group are all Lock Name: DoNotDelete, and Lock Type: Delete on all the nodes, on the cluster, on the key vault, and on the "Storage Account" which i suppose is causing the problem.

Why is it getting locked, if it will cause the deployment to fail?

I am now removing the lock and resume the deployment and let you know if it helped.

Thanks

Gabe

The deployment won't resume it just showing "Waiting for status updates from device." for quite a while now. Any other way to resume deployment but the "resume deployment" button?
GabeCz 26 Reputation points

2025-11-29T19:39:26.32+00:00

when i run get-storagepool on the actual nodes (using a powershell script running from the hyper-v server i get this: i paste a screenshot instead, because pasting the text messes up the looks

I must repeat myself, this script that creates the disks worked just well with my old resource group. so i'm quite sure it is not the cause of the issue here.

<moving personal info >
GabeCz 26 Reputation points

2025-11-30T21:18:51.16+00:00

um

i have waited a day or two, and removed the iso-dvd images from the virtual dvd drive. restarted the deployment now it seems to be ok.

side note: i have never removed the isos before and it worked before. now i will start it from scratch to see if that was the solution.

i must admin the documentation DOES say remove the iso. but as i never did i thought it's ok to leave them in.

i post update on the result later
Shraddha Pandey 375 Reputation points Microsoft External Staff Moderator

2025-12-01T07:49:43.2166667+00:00

Hi GabeCz,

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-02T13:44:17.87+00:00

Hi GabeCz,

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!

Answer 1

GabeCz 26

it was not the dvd drive that wasn't removed.

it was stuck data somewhere i can't tell where, what, and how.

i wiped the two disks that i used for the vms. (zeroed them out format resulted the same error) which after it works fine.

Share via

What can cause this exception at deployment? "Set up storage pools, file shares, and CSVs."

1 answer

Your answer