Troubleshooting

VolumeGroup Issues

VolumeGroup stuck in CreationScheduled

The system could not find eligible storage nodes. Check:

1. Navigate to Storage → VolumeGroups and click the stuck VolumeGroup
2. Check the Status panel for a message explaining why scheduling failed

Common causes:

• No storage nodes in Ready phase — check Hardware → Nodes
• Insufficient free capacity across nodes — check used vs. total capacity per node

VolumeGroup in Failed phase

1. Navigate to Storage → VolumeGroups and click the failed VolumeGroup
2. Read the Status message for the failure reason
3. Check Hardware → Nodes to verify the selected nodes are in Ready state

Volume Issues

Volume mountPoint is empty in accessInfo

The Volume may not have reached Ready phase yet:

1. Navigate to Storage → Volumes and click the Volume
2. Monitor the Status panel — provisioning typically completes within a few minutes

If it stays in Provisioning for more than 10 minutes, check the target storage nodes under Hardware → Nodes.

Mount fails: "no such pool"

The underlying storage may have been lost. Check the VolumeGroup status:

1. Navigate to Storage → VolumeGroups and check the phase of the parent VolumeGroup
2. If the phase is Failed, delete and re-create the VolumeGroup

warning

If the VolumeGroup Deletion Policy is Delete, re-creating it will result in data loss.

Mount fails: "permission denied" or "access denied"

Verify that:

1. Your identity is registered and ACTIVE — check Access → Users (or Machines)
2. An AccessPolicy grants read/write on this Volume — check Access → Policies
3. Your TLS certificate CN matches the identity registered in the Dashboard

Capacity Issues

VolumeGroup running out of space

Expand the VolumeGroup via the Dashboard:

1. Navigate to Storage → VolumeGroups and click the VolumeGroup
2. Click Edit and increase the Size field
3. Click Save — expansion requires free capacity on the selected nodes