How to Expand Your Proxmox Disk to Full Size on a Virtnet.bond VPS

Important Note from Virtnet.bond

At Virtnet.bond, we intentionally do not automate the disk expansion process inside your VPS. While it may seem convenient to automatically resize partitions and filesystems after a disk upgrade, doing so can interfere with custom setups used by many of our advanced users.
Some customers may prefer to:

• Maintain multiple partitions for data separation
• Use ZFS, LVM-Thin, or encrypted volumes
• Allocate extra space to secondary disks or containers manually

Automatically expanding partitions could override or break those custom configurations. By keeping this step manual, we ensure that you stay in full control of your system’s storage layout. This approach reflects our philosophy: Virtnet.bond gives you the flexibility of choice — not automation that makes assumptions on your behalf.

How to Expand Your Proxmox Disk to Full Size on a Virtnet.bond VPS 

When you resize your VPS storage at Virtnet.bond, the new space becomes available to your virtual disk—but Proxmox doesn’t automatically expand the partition and filesystem to use it.
This quick guide shows you how to safely expand your Proxmox root volume to use 100% of your disk.

Prerequisites

• You’ve already increased the disk size from the Virtnet.bond control panel.
• You’re logged in to your Proxmox host via SSH as root.
• Your Proxmox installation uses the default LVM layout on /dev/vda.

Step 1: Re-check your current disk layout

Run this command to see your disk and partition structure:

lsblk

You should see something like this:

NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda               252:0    0   64G  0 disk
├─vda1            252:1    0  100M  0 part /boot/efi
├─vda2            252:2    0    1G  0 part /boot
└─vda3            252:3    0    8G  0 part
  ├─pve-swap      253:0    0    1G  0 lvm  [SWAP]
  └─pve-root      253:1    0    7G  0 lvm  /

Notice how /dev/vda3 (the main LVM partition) is smaller than the total disk size. That’s what we’ll expand.

Step 2: Grow the partition to fill the full disk

Use the growpart utility to safely expand the 3rd partition (vda3) to fill the remaining space on your virtual disk:

growpart /dev/vda 3

This command is non-destructive—it simply adjusts the partition table to include all unallocated space on the disk.
If growpart is missing, install it first:

apt update && apt install -y cloud-guest-utils

Step 3: Resize LVM and the filesystem

Now that the partition is larger, expand the physical volume, the logical volume, and finally the filesystem:

pvresize /dev/vda3 && lvextend -l +100%FREE /dev/pve/root && resize2fs /dev/pve/root

Here’s what each command does:

• pvresize /dev/vda3 — Expands the physical volume to include the new space.
• lvextend -l +100%FREE /dev/pve/root — Allocates all remaining space to the root logical volume.
• resize2fs /dev/pve/root — Resizes the ext4 filesystem to match the new volume size.

Step 4: Verify the results

Run:

df -h /

You should now see the full expanded disk size reflected under /.

Example output:

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/pve-root   64G  3.6G   60G   6% /

Congratulations — your Proxmox root volume is now using 100% of your allocated disk space on your Virtnet.bond VPS!