Attaching a volume connects it to a server so the OS sees it as a disk device (e.g. /dev/vdc). The portal handles the attach itself; you then format and mount the volume inside the guest using the commands on the Mount Instructions tab.
On the Overview tab, scroll to the Attached To section. For an unattached volume you’ll see Not attached to any server with an Attach to Server button.
Click Attach to Server.
After attaching, open the Mount Instructions tab on the volume detail page. It shows a green confirmation panel:
Volume is attached — run these commands inside your server. Device:
/dev/vdcon server<server_id>
Copy the device path from the panel — that’s the placeholder you replace below.
SSH into the server and run the Mounting commands:
Step 2 (mkfs.ext4) erases everything on the volume. Only run it on a brand-new volume. Skip it for any volume that already has data.
If the device path on your Mount Instructions tab is something other than /dev/vdc (e.g. /dev/vdb), substitute it everywhere in the commands above.
Always unmount the volume inside the guest before detaching in the portal. Detaching a mounted volume can cause data corruption or filesystem errors.
SSH into the server and run the Unmounting commands from the Mount Instructions tab:
lsblk should no longer show the device mounted on /mnt/data.
Go to Block Storage and click your volume. The Attached To section shows the server and device path.
After detaching, the volume status returns to Ready and the Attached To section reverts to Not attached to any server. You can now reattach it to any other server in the same region.
The Mount Instructions tab content changes depending on attachment state:
Server dropdown is empty in the Attach dialog You don’t have a running server in the same region as the volume. Either start a server in that region or create a new volume in your server’s region.
Device path not shown in Mount Instructions The device path appears only after the attach completes. Wait a few seconds and refresh the page.
lsblk doesn’t show the new disk
Confirm the attach succeeded (volume status should be In Use). If the platform shows attached but the OS doesn’t see it, reboot the server.
Mount doesn’t persist after reboot
Re-run step 6 of the Mounting script and verify the UUID with sudo blkid /dev/vdc. The line in /etc/fstab should match the actual UUID.
Detach button disabled Tick the unmount confirmation checkbox in the Detach dialog. The button stays disabled until that’s confirmed.
Detach fails or hangs
The volume is still in use by the guest. Run sudo lsof /mnt/data to find processes holding the mount, stop them, then sudo umount /mnt/data again before retrying detach.