Troubleshooting

Volume Group Issues

Volume group not reaching Ready

1. Navigate to Storage → Volume Groups and click the volume group
2. Read the status message

A volume group is only reported Ready once its storage is actually usable. Operations stalled on the storage backend recover on their own within minutes.

Volume group creation is rejected

Message	Cause	Action
Insufficient storage / limit reached	The cluster's volume-group ceiling or per-node capacity is reached. The message names the current maximum and the bottleneck.	Delete unused volume groups, or add capacity
Size below the minimum	The requested size cannot satisfy all storage requirements	Use the minimum the dialog shows
Label conflict	Another volume group already uses that label — possibly one that was force-deleted and not yet reclaimed	Pick another label, or reclaim the orphan first
Busy, retry later	Too many create requests arrived at once	Retry shortly

Storage capacity is lower than expected

Check Hardware → Drives first — every data drive should be Healthy and In Cluster. Then compare Analytics → Capacity: allocated capacity comes from the requested sizes of your volume groups, so unallocated space is capacity you have not reserved yet.

Volume Issues

Volume stuck in Provisioning

1. Navigate to Storage → Volumes and click the volume
2. Monitor the status message — provisioning normally completes within a few minutes

A volume that cannot finish provisioning is marked Failed with a message rather than staying stuck.

Mount fails: no such volume, or the volume is unreachable

Mounting checks that the storage backend is reachable first, so an unreachable backend fails fast with a clear message instead of hanging.

1. Confirm the volume is Ready in Storage → Volumes
2. Confirm the parent volume group is Ready
3. Check Hardware → Nodes for a node in a non-Ready or Unreachable state

Mount fails: permission denied or access denied

Verify that:

1. Your identity is Active — check Identity & Access → Users & Groups (or Machines)
2. An access policy grants the permissions you need on this volume — check Identity & Access → Access Rules
3. Your client certificate is current. mass-ctl login certificates are valid 24 hours by default; run mass-ctl login again if it expired.
4. If you recently changed the policy, remount — permission changes only reach an existing mount after a remount

Mount fails on a host with several network cards

mass-ctl stops immediately with an error naming the mismatch when no network card on the host sits on the storage network's subnet. Connect the client to the storage fabric, or check that the correct interface has an address on that subnet.

Volume deletion does not complete

• A mounted volume is rejected up front — unmount it and the delete proceeds automatically
• A volume whose client crashed hard (power loss, forced shutdown) completes on its own within a few minutes
• Otherwise use force delete, then reclaim the leftover storage from Storage → Orphan Storage