You can manage your cloud server’s configuration in the Plan tab.
Here, you can:
Operations with disks are not available if a snapshot is created for the server.
You can only upgrade your server’s plan. Downgrading is not possible as reducing the disk size can damage the file system.
To change your server's plan:
Go to the Plan tab.
Click Select plan.
Choose a new plan for the server.
Click Save and reboot to apply the changes.
Confirm the action.
To add an additional disk to your server:
Go to the Plan tab.
Click Add disk.
Set the desired disk size and click Add and reboot.
Confirm the action.
You will see the new disk in the control panel.
Now you have to add the disk in the operating system.
On Linux, disk setup typically consists of the following steps:
Create a partition on the disk
Create a filesystem
Mount the disk (if needed)
Add an entry to /etc/fstab
If your server was created before May 2025, disks will be named like vd*. On servers created after May 2025, disks will be named sd*. Keep this in mind when following the steps below.
In the examples, we’ll prepare the sdb disk, as sda is the main system disk, and vda is reserved for cloud-init by default.
Replace sdb in the commands with the actual disk name on your system.
You can check disk names on your system with:
lsblk
Example output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 63.9M 1 loop /snap/core20/2318
loop2 7:2 0 87M 1 loop /snap/lxd/29351
loop3 7:3 0 50.9M 1 loop /snap/snapd/24505
loop4 7:4 0 63.8M 1 loop /snap/core20/2599
loop5 7:5 0 89.4M 1 loop /snap/lxd/31333
loop6 7:6 0 50.9M 1 loop /snap/snapd/24718
sda 8:0 0 15G 0 disk
└─sda1 8:1 0 15G 0 part /
sdb 8:16 0 10G 0 disk
vda 252:0 0 1M 1 disk
Here, sdb is the newly added disk.
To create a partition, use fdisk:
fdisk /dev/sdb
Inside fdisk:
n to create a new partitionp for a primary partitionw to write the changes and exit
Run the command again to verify the partition was created:
lsblk
In our example, the new partition will be sdb1.
Next, create a filesystem on the new partition. In this example, we’ll use EXT4:
mkfs.ext4 /dev/sdb1
The filesystem is now ready.
To start using the disk, mount it to a directory. Each disk should have its own mount point.
For example, if you later add another disk (sdc), it should be mounted to a different directory.
Create a mount directory:
mkdir /mnt/disk2
Mount the disk:
mount -o barrier=0 /dev/sdb1 /mnt/disk2
You can now store files in /mnt/disk2, and they will be written to the new disk.
To make the mount persistent after a reboot, add an entry to /etc/fstab.
You can reference the disk by its device name (e.g. sdb1), but this name may change if disks are reattached or other disks are removed. Using a UUID is recommended, as it is unique and stable.
To find the UUID, run:
lsblk -o NAME,UUID
Example output:
sda
└─sda1 fcafbb78-fd6c-4083-82d8-3c06bd6ad4b1
sdb
└─sdb1 534c6694-d2b0-4867-843b-b8a934bf0e5d
vda 041E-4E90
In this case, the UUID of our disk is 534c6694-d2b0-4867-843b-b8a934bf0e5d.
Edit /etc/fstab:
nano /etc/fstab
Add the following line (replace the UUID with your own):
UUID=<disk-uuid> /mnt/disk2 ext4 defaults 0 2
We recommend creating a server backup before resizing disks.
You can only increase the disk’s size. Decreasing the size is not possible as it can seriously damage the file system.
In most cases, after you resize the disk in the control panel, the disk will be repartitioned automatically.
However, if you have previously partitioned the disk yourself and now it has two or more logical partitions, you will need to repartition manually.
To resize your main disk, simply change your server plan:
To change the size of an additional disk:
In most cases, after you resize the disk in the control panel as described above, the disk will be repartitioned automatically.
However, if you have previously partitioned the disk yourself and now it has two or more logical partitions, you will need to repartition manually, following the steps described below.
Step 1. Boot the server in the recovery mode:
Go to the Access tab.
Click Change in the OS boot mode section.
Select Booting from the recovery disk.
Click Save and reboot.
Step 2. Go to the Console tab and enter the following command using your disk name:
parted /dev/vda
You can check disk names in your system with the command:
fdisk -l
Step 3. Execute the print command and view the list of partitions in its output.
If you want to extend the last partition so it takes all the free space on the disk, go to step 4a.
If you want to create a new partition, proceed to step 4b.
We do not cover in this article the cases when you need to create several new partitions, but you can find those guides online.
If at this point you need to delete a partition, you can do it with the rm command, specifying the partition number, for example:
rm 3
Step 4. Partition the disk.
Step 4a. To extend the last partition, run the resizepart command, specifying the desired partition number and size. If you enter 100%, the partition will take up all available space on the disk.
resizepart 3 100%
Next:
Run print to check the result.
Enter q to exit the partitioning program.
Proceed to Step 5.
Step 4b. To create a new partition in a free disk space, run the mkpart command, specifying the partition type (primary or extended), its number and size. If you enter 100%, the partition will take up all available space on the disk.
mkpart primary 4 100%
Next:
Enter yes when prompted to confirm the new partition size.
Run print to check the result.
Enter q to exit the partitioning program.
Create a file system in the new partition with the command below, specifying the partition name.
mkfs.ext4 /dev/vda4
Proceed to Step 5.
Step 5. Check for errors and correct the file system structure.
To do this, run the e2fsck command in the console, specifying the name of the partition from the Step 4 (/dev/vda3, /dev/vda4, etc.):
e2fsck -yf /dev/vda3
Step 6. Resize the file system, specifying the partition name:
resize2fs /dev/vda3
Step 7. Check the file system after expansion.
Mount the partition that was modified (/dev/vda3, /dev/vda4, etc.):
mount /dev/vda3 /mnt
Check that the size was successfully changed:
df -h
If the disk size has remained the same, we recommend going back to Step 1 and repeating the procedure once again.
If the disk size has changed, unmount the system disk:
umount /mnt
8. Boot the server in the standard mode.
To delete a disk:
Go to the Plan tab.
Hover over the disk and click on the bin icon.
Confirm deleting the disk.
You also need to delete the disk from the operating system by removing the entry from the /etc/fstab file.
If the server has only one additional disk:
Open the file:
nano /etc/fstab
Delete or comment out the disk entry:

Save changes (Ctrl + X, then Y and Enter).
If there are several additional disks on the server and the one you are deleting is not the last one:
Open the file:
nano /etc/fstab
Delete or comment out the disk entry:

Check the disk names on your system, for example with the lsblk command. They should have moved one step up. Say, you had additional disks vdc and vdd. Then after deleting the vdc disk, you should see the following:

This is actually your third disk (vdd), which has been mounted to the /mnt/disk3 directory.
Mount the disk to the same directory, specifying its updated name (in our case, vdc1):
mount -o barrier=0 /dev/vdc1 /mnt/disk3
/etc/fstab file with the updated data:nano /etc/fstab

To change the CPU and RAM parameters of your server, change the server plan:
Go to the Plan tab.
Click Select plan.
Select a plan with the required parameters.