Troubleshooting — Disks
"Size exceeds available quota"
Cause: the requested size exceeds the remaining storage in the project quota. The message indicates the maximum available.
Solution:
- Reduce the Size (GB) to a value lower than or equal to the indicated maximum.
- Free up storage by deleting unused disks or resources (detached disks also consume the quota).
- If needed, have the project's storage quota increased.
"Minimum size is 20 GB" or "This image needs a disk of at least … GB"
Cause: the size is below the minimum.
Solution: enter at least 20 GB; for a system disk, at least 28 GB with Windows Server and 40 GB with Oracle Linux.
The disk stays in "Downloading" or switches to "Error"
Cause: the image import takes a long time (large image) or failed (unreachable URL, unrecognized file).
Solution:
- Follow the percentage progress on the disk page; a large import can take time.
- For a custom image, check that the URL is publicly accessible over HTTPS and points to a valid ISO or QCOW2 file:
curl -I https://example.com/image.qcow2
- If the disk switches to Error, delete it and recreate it with a corrected URL. If the problem persists, contact support with the disk name and identifier.
The disk does not appear in "Select an existing volume"
Cause: the disk is already attached to a VM, it is already selected on another volume, or its type does not match the volume.
Solution:
- Check the Attached to field on the disk page: if it shows a VM, detach the disk first.
- For the System Disk (Boot), only system disks (created from an image) are offered; for data volumes, only data disks.
The disk is not visible in the VM
Cause: the VM has not restarted yet after the storage change, or the disk was not saved on the VM.
Solution:
- On the disk page, check that Attached to shows the right VM and that the status is In Use.
- An attached disk is only taken into account on the next VM restart: click Restart (Actions section of the VM page), wait for the restart to finish, then run
lsblkagain in the VM.
The new size is not visible in the VM after a resize
Cause: the file system has not been extended, or the VM has not yet picked up the new device size.
Solution:
- Check the device size with
lsblk. If it has not changed, restart the VM. - Extend the partition and the file system (see Resize a disk).
Disk deletion fails
Cause: a VM still uses the disk, or the service is temporarily unavailable. The console shows one of these messages:
- "The disk cannot be deleted as it is in use." (disk page) or an equivalent message in the disk list: the disk is attached to a VM;
- "This disk was detached, but its VM still uses it until its next restart. Restart the VM, then try again.": the disk was detached, but the VM has not restarted yet and still uses it;
- "The disk deletion service is temporarily unavailable.".
Solution:
- Attached disk: detach it from the VM edit page (Storage section), click Save, then go to step 2.
- Detached disk: click Restart on the VM page, wait until it is back to the Running status, then a few minutes, and try again.
- Service unavailable: try again a few minutes later.
The disk name is rejected
Cause: the name does not follow the rules, or it ends with a reserved suffix ("This domain is reserved by Hikube").
Solution: use 3 to 16 characters (lowercase letters, digits and hyphens), start with a letter and end with a letter or a digit.