​
Overview

Titled Block Storage Volumes — “Manage persistent storage volumes attached to this virtual machine”. Everything here is scoped to this one machine.
Navigation: Compute → Virtual Machines → click a machine → Volumes.

​
What each card shows

A type badge reads Root or Data. Filters cover type and state.

​
Root volumes behave differently

A root volume is bound to its machine for life. If the data you care about is on the root volume, it dies with the machine — and the deletion dialog won’t offer to keep it.Move anything important onto a data volume. See Volumes.

​
Row actions

Transient states appear on the card while work is in flight: Creating..., Attaching..., Detaching..., Resizing..., Removing....
Attached and Available are derived labels rather than platform states — Available means the volume exists but isn’t attached to this machine.

​
Adding a volume

There’s no “attach an existing volume” control here. Create Volume creates a new volume and attaches it, in one flow.To attach a volume that already exists, go to Volumes and use Attach to VM from its row.
The flow reports progress in two stages — Creating volume... then Attaching volume... — and confirms with Volume created and attached.
If the create succeeds but the attach fails, you get a specific and recoverable message:
The volume was created but failed to attach. You can attach it manually from the Volumes page.
Nothing is lost, but the volume now exists detached and is consuming storage quota. Finish the job from Volumes rather than creating a second one.

​
Resizing

Resize Volume on a Ready volume.
Two constraints that catch people:Shrinking needs an explicit opt-in and can corrupt data if the filesystem is larger than the new size. Shrink the filesystem inside the machine first.Resizing is blocked entirely while the machine holds VM snapshots. The dialog explains this rather than failing. Delete the VM snapshots first — see VM Snapshots.And growing a volume doesn’t grow the filesystem on it. That’s a separate step inside the machine.

​
Common task: add a data disk and mount it

1

Create and attach it here

Create Volume, size it, and let the flow attach it. Leave Device ID empty for the next free slot.
2

Confirm it reached Ready and is attached

The card should show a Data badge and a real DEVICE value. A volume stuck in Attaching... isn’t usable yet.
3

Find the device inside the machine

4

Create a filesystem — once, and only on the right device

mkfs destroys whatever is on the device. Check lsblk output twice and confirm the device is the new, empty one before running it.
5

Mount it and make that survive a reboot

6

Verify

nofail in /etc/fstab matters. Without it, a machine whose data volume is missing at boot can drop into emergency mode instead of starting — and the only way in then is the console.

​
Empty and error states

Volumes

The full screen: attachment rules and orphaned volumes.

Snapshots

What you can build from a volume snapshot.

Snapshots tab

Why VM snapshots block resizing.