Search
Join the Technical Preview Program
See how NVMe-oF removes iSCSI
bottlenecks in your HCI
The Best Hyperconverged
Infrastructure
(HCI) for Enterprise
ROBO, SMB & Edge
The Best Virtual SAN
for Enterprise ROBO, SMB & Edge

Step-by-Step: Extend Root Partition in Proxmox with LVM

  • July 22, 2025
  • 5 min read
Cloud and Virtualization Architect and System Engineer. Paolo is the author of nolabnoparty.com. A VCP-DCV and vExpert, he holds elite VMCE and Veeam Vanguard status. Paolo specializes in data protection, disaster recovery, and vSphere infrastructure, delivering high-authority technical guides for enterprise virtualization and backup solutions.
Cloud and Virtualization Architect and System Engineer. Paolo is the author of nolabnoparty.com. A VCP-DCV and vExpert, he holds elite VMCE and Veeam Vanguard status. Paolo specializes in data protection, disaster recovery, and vSphere infrastructure, delivering high-authority technical guides for enterprise virtualization and backup solutions.


In a Proxmox environment, you may need to extend root partition if it runs out of space.

To do this, you must first allocate additional storage on the hypervisor and then configure the system to perform the necessary operations.

During a Proxmox upgrade procedure, you may encounter failures caused by insufficient disk space on the root partition, preventing the upgrade from completing successfully

Select the Proxmox node to upgrade then go to Updates section. Click Upgrade to install all available updates.

Select the Proxmox | Updates section | Click Upgrade

 

The upgrade operation fails with an error due to insufficient disk space:

You don’t have enough free space in /var/cache/apt/archives/

The upgrade operation fails with an error due to insufficient disk space

 

To resolve this issue, you must extend root partition by allocating additional disk space.

How to Extend Proxmox Root Partition Using LVM

Step 1: Check If Your System Uses LVM

Run the command df to verify if you are using a LVM volume. If the root partition shows /dev/mapper/pve-root you are using LVM.

# df -H

Run the command df to verify if you are using a LVM volume | If the root partition shows /dev/mapper/pve-root you are using LVM.

Step 2: Identify the Disk to Resize

Next step is to identify the physical disk to use. In the example the identified disk is the /dev/sda.

# lsblk

Identify the Disk to Resize

Step 3: Resize the Partition with parted

To expand the physical disk the recommended tool to use is parted or fdisk. Run the following command to enter parted:

# parted /dev/sda

Resize the Partition with parted

 

Print the current partition table to identify the number of the LVM partition (3 in the example).

# print

Print the current partition table to identify the number of the LVM partition (3 in the example).

 

Assign all available space on the disk to the selected partition.

# resizepart 3 100%

Assign all available space on the disk to the selected partition.

 

Check the current partition table once again. The size of the partition is now changed with the additional space.

# print

Check the current partition table once again

 

Exit from parted.

# quit

Check the current partition table once again

Step 4: Refresh Partition Table in Kernel

To make the kernel aware of the changes occurred to the partition table, run the command:

# partprobe

Refresh Partition Table in Kernel

Step 5: Resize LVM Physical Volume

After resizing the underlying partition, you need to tell LVM about the new size of its physical volume.

# pvresize /dev/sda3

Resize LVM Physical Volume

 

To know how much free space is available in the pve volume group (VG Size).

# vgdisplay pve

To know how much free space is available in the pve volume group (VG Size).

Step 6: Extend the Logical Volume

Extends the pve-root logical volume to consume all available free extents in the pve volume group.

# lvextend -l +100%FREE /dev/mapper/pve-root

Extend the Logical Volume

Step 7: Resize the Filesystem

Resize the file system to use the newly available space.

# resize2fs /dev/mapper/pve-root

Resize the Filesystem

Step 8: Verify Root Partition Size

Verify that root partition has been successfully extended.

# df -H

Verify Root Partition Size

 

Final Step: Upgrade Proxmox Without Errors

The Proxmox node can now be upgraded without any issue related to disk space.

Upgrade Proxmox Without Errors

When modifying the root partition, ensure all commands are executed carefully to prevent service interruptions or, in extreme cases, complete system failure.

Hey! Found Paolo’s insights useful? Looking for a cost-effective, high-performance, and easy-to-use hyperconverged platform?
Taras Shved
Taras Shved StarWind HCI Appliance Product Manager
Look no further! StarWind HCI Appliance (HCA) is a plug-and-play solution that combines compute, storage, networking, and virtualization software into a single easy-to-use hyperconverged platform. It's designed to significantly trim your IT costs and save valuable time. Interested in learning more? Book your StarWind HCA demo now to see it in action!