Skip to content
Luca Dell'Oca Principal Cloud Architect @Veeam
Virtual To The Core Virtual To The Core

Virtualization blog, the italian way.

  • Media
  • About me
Virtual To The Core
Virtual To The Core

Virtualization blog, the italian way.

Not enough free space to install Veeam worker on Proxmox VE (and how to expand a PVE volume)

Luca Dell'Oca, October 13, 2025

I was installing the other day a new nested lab to play a bit with Veeam Backup & Replication and Proxmox VE. I registered my cluster without any issue, but when I tried to install my first worker in the hypervisor I encountered this error:

The text says:

“Failed to upload the worker image: import failed: cp: error copying ‘/var/tmp/pveupload-1b9a50c497b27e71ecb63f19b76d621c’ to ‘/var/lib/vz/template/iso/PveWorker_13.2.0.457.img’: No space left on device”

“Worker wkr1 test failed: import failed: cp: error copying ‘/var/tmp/pveupload-1b9a50c497b27e71ecb63f19b76d621c’ to ‘/var/lib/vz/template/iso/PveWorker_13.2.0.457.img’: No space left on device”

Apparently, there was not enough free space to upload the Veeam iso file PveWorker_13.2.0.457.img. As said, my nodes are nested VM’s, so indeed I created them with the absolute minimum hardware specs. Specifically for the local disks of each node, I crated a virtual disk with 16 GB of space, and I thought it would have been enough. The problem however was how the PVE installer automatically partitioned it:

As you can see from the picture, the LVM volume where all the root partition is mounted was only 7 GB, and 4 of them were already used by PVE. I went to check the size of this img file, and it was 1.2 GB, but for some reason the upload was failing, maybe because there is a need for extra space for temporary caching or other reasons. Anyway, since it’s a nested server it was much easier and faster to just increase the storage. Here’s a quick recap of the procedure:

  1. I increased the size of the virtual disk on the baremetal hypervisor adding 10 more GB
  2. in PVE shell, rescan the disks:

    echo 1 > /sys/block/sda/device/rescan
  3. check the new space added to the sda disk:
    lsblk
  4. Resize the partition where the LVM volume pve is hosted using the added free space:
    parted /dev/sda
    resizepart sda3 100%
  5. since it’s an LVM volume, first resize the PV (physical volume):
    pvresize /dev/sda3
  6. then, rezise the LV (logical volume):
    lvextend -l +100%FREE /dev/pve/root
  7. Finally, extend the ext4 partition that PVE uses to store the pve-root volume:
    resize2fs /

The volume now has 10 more GB of free space:

I tried again to install the Veeam worker, and this time it completed successfully:

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to email a link to a friend (Opens in new window) Email
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Pinterest (Opens in new window) Pinterest
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on WhatsApp (Opens in new window) WhatsApp
  • Click to share on Pocket (Opens in new window) Pocket
Tech extendno space leftproxmoxpveveeamvolumeworker

Post navigation

Previous post

Search

Sponsors

Latest Posts

  • Not enough free space to install Veeam worker on Proxmox VE (and how to expand a PVE volume)
  • Migrate WSL (Windows Subsystem for Linux) to a new computer
  • Pass keystrokes to a pfSense virtual machine to install it automatically
  • Automatically deploy pfSense with Terraform and Ansible
  • My Automated Lab project: #6 Create a S3 Bucket with Terraform
©2025 Virtual To The Core | WordPress Theme by SuperbThemes
We use cookies to ensure that we give you the best experience on our website, and to collect anonymous data regarding navigations stats using 3rd party plugins; they all adhere to the EU Privacy Laws. If you continue to use this site we will assume that you are ok with it.