vzdump failed: Exit code 2 (PVE 5.4-3)

[james3126]

Hi all, I've run into a situation where my server (running 5.4-3) shutdown, and when booting again, had no network access at all (despite attempts to change IPs etc..)

Thus, I've decided to call it quits and start again, on the latest 6.1 PVE version.

I've thrown a USB stick into the machine, mounted to '/mnt/USBOffload/' and I'm looking at exporting some of the VMs so I don't have to recreate EVERYTHING from the start.

(Warning, I'm a noob at command line usage) I've gathered the correct command to run is: vzdump <VMID> --mode stop --dumpdir /mnt/USBOffload/dump --compress gzip

However, I've been met with the following error:

root@<HostName>:~# vzdump 100 --mode stop --dumpdir /mnt/USBOffload/dump/ --compress gzip
INFO: starting new backup job: vzdump 100 --compress gzip --dumpdir /mnt/USBOffload/dump --mode stop
INFO: Starting Backup of VM 100 (qemu)
INFO: status = stopped
INFO: unable to open file '/etc/pve/nodes/<HostName>/qemu-server/100.conf.tmp.3109' - Permission denied
INFO: update VM 100: -lock backup
ERROR: Backup of VM 100 failed - command 'qm set 100 --lock backup' failed: exit code 2
INFO: Backup job finished with errors
job errors
root@<Hostname>:~#

I get the same error for all VM's.

Could anyone help me here? I'm a major noob so please be gentle.

Thanks in advance

 

[aaron]

Is the proxmox cluster file system running?

systemctl status pve-cluster

It provides the fuse file system that is mounted in /etc/pve.

 

[james3126]

Is the proxmox cluster file system running?

systemctl status pve-cluster

It provides the fuse file system that is mounted in /etc/pve.

This thread can be ignored now. I went around another way and just moved the raw files out to an external drive that I mounted, and used qemu-img to convert to vmdk, and imported them to a temporary solution on another host. Wiped the PVE host, and reinstalled with the latest version. Will attempt to reimport the vmdk