1/4
aStor_Block_Storage is in Read-Only State

LCS18 Lv1  Posted 2026-Sep-03 13:14

Hi Team,

Issue: aStor Cluster is in Read-Only State due to critical storage status. Cluster capacity is on 95.01%.

Any recommendation how to fix this is highly appreciated. Thank you!

Muhammad Abid has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Yes. At 95.01% cluster capacity, the first priority should be to free up storage space because aStor may enter Read-Only protection when the storage reaches a critical threshold.

Recommended steps:

Check aStor storage usage and identify which VMs/disks are consuming the most capacity.
Delete unnecessary VMs, snapshots, or unused disks after confirming they are no longer required.
Check for old snapshots — these can consume significant space.
If available, migrate some VMs/storage to another datastore or cluster to bring utilization down.
Do not manually delete aStor/system files to free space; this can cause data corruption.
After reducing utilization, monitor whether the cluster automatically exits Read-Only State. If not, check the aStor/cluster health and critical alerts.

Ideally, bring capacity well below the critical threshold rather than only reducing it by a small amount.

If you can share a screenshot of the aStor Storage/Cluster Health page, I can tell you exactly what to check next
Is this answer helpful?
Muhammad Abid Lv3  Posted 2026-Sep-03 13:57
  
Yes. At 95.01% cluster capacity, the first priority should be to free up storage space because aStor may enter Read-Only protection when the storage reaches a critical threshold.

Recommended steps:

Check aStor storage usage and identify which VMs/disks are consuming the most capacity.
Delete unnecessary VMs, snapshots, or unused disks after confirming they are no longer required.
Check for old snapshots — these can consume significant space.
If available, migrate some VMs/storage to another datastore or cluster to bring utilization down.
Do not manually delete aStor/system files to free space; this can cause data corruption.
After reducing utilization, monitor whether the cluster automatically exits Read-Only State. If not, check the aStor/cluster health and critical alerts.

Ideally, bring capacity well below the critical threshold rather than only reducing it by a small amount.

If you can share a screenshot of the aStor Storage/Cluster Health page, I can tell you exactly what to check next
LCS18 Lv1  Posted 2026-Sep-03 16:25
  
Thanks for the response Muhammad. Appreciate it.
Will try to follow the steps you recommend and update here if this will fix the issue.

Thank you!
Prosi Lv4  Posted 2026-Sep-04 10:12
  
Hi,
If sufficient space is available but the cluster remains Read-Only, don't repeatedly reboot nodes. At that point, the important question is why the storage critical flag hasn't cleared.
Sangfor Jojo Lv5  Posted 2026-Sep-10 16:46
  
For future inquiries about troubleshooting, product capabilities and configuration settings, feel free to use our Solvia Chatbot in the community. Available 24/7 with zero waiting time, it provides instant responses with an 88.6% accuracy rate.

I Can Help:

Change

Trending Topics

Board Leaders