[SOLVED] Error when backupping Template

cromatn5

Well-Known Member
Mar 26, 2018
77
11
48
39
France
I converted a vm to template and i would like to backup it, to keep a copy on PBS, and had this error.
I can normaly backup all others "standards" vm.

Code:
INFO: starting new backup job: vzdump 104 --storage backup --node pve --remove 0 --mode snapshot
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2021-01-11 20:01:27
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: win16dc
INFO: include disk 'scsi0' 'vm:base-104-disk-1' 32G
INFO: include disk 'efidisk0' 'vm:base-104-disk-0' 4M
INFO: creating Proxmox Backup Server archive 'vm/104/2021-01-11T19:01:27Z'
INFO: starting kvm to execute backup task
kvm: The device is not writable: Permission denied
ERROR: Backup of VM 104 failed - start failed: QEMU exited with code 1
INFO: Failed at 2021-01-11 20:01:29
INFO: Backup job finished with errors
TASK ERROR: job errors

pveversion -v

Code:
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
 
Last edited:
please include the output of 'pveversion -v'
 
and what kind of storage are you using? could you include the full VM config as well? thanks!
 
I use LVM-thin for Proxmox and ZFS for playing with PBS.

Code:
# lvs
  LV              VG   Attr       LSize   Pool Origin          Data%  Meta%  Move Log Cpy%Sync Convert
  base-108-disk-0 pve  Vri---tz-k  32,00g vm
  base-108-disk-1 pve  Vri---tz-k   4,00m vm
  swap            pve  -wi-ao----   4,00g
  vm              pve  twi-aotz-- 872,70g                      14,07  9,23
  vm-100-disk-0   pve  Vwi-aotz-- 100,00g vm                   46,57
  vm-100-disk-1   pve  Vwi-aotz--   4,00m vm                   3,12
  vm-101-disk-0   pve  Vwi-a-tz--   4,00g vm                   76,13
  vm-102-disk-0   pve  Vwi-a-tz--   4,00g vm                   95,80
  vm-103-disk-0   pve  Vwi-a-tz--   6,00g vm                   94,10
  vm-104-disk-0   pve  Vwi-a-tz--   4,00m vm   base-108-disk-1 3,12
  vm-104-disk-1   pve  Vwi-a-tz--  32,00g vm   base-108-disk-0 62,51
  vm-105-disk-2   pve  Vwi-a-tz--   4,00m vm                   3,12
  vm-105-disk-3   pve  Vwi-a-tz--  50,00g vm                   28,25
  vm-106-disk-0   pve  Vwi-a-tz--   8,00g vm                   57,29
  vm-106-disk-1   pve  Vwi-a-tz--   4,00m vm                   3,12
  vm-106-disk-2   pve  Vwi-a-tz--  64,00g vm                   39,07
  iso             tank -wi-ao----  50,00g
  share           tank -wi-ao----   1,46t

Code:
# zpool status
  pool: backup
 state: ONLINE
  scan: scrub repaired 0B in 0 days 00:18:57 with 0 errors on Sun Jan 10 00:42:58 2021
config:

        NAME        STATE     READ WRITE CKSUM
        backup      ONLINE       0     0     0
          sdb       ONLINE       0     0     0

errors: No known data errors

Code:
# qm config 108
agent: 1
bios: ovmf
boot: order=scsi0
cores: 4
cpu: host
description:
efidisk0: vm:base-108-disk-1,size=4M
ide0: none,media=cdrom
machine: q35
memory: 4096
name: win16dc
net0: virtio,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
protection: 1
scsi0: vm:base-108-disk-0,cache=writeback,discard=on,iothread=1,size=32G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=
sockets: 1
tablet: 0
template: 1
vga: qxl
vmgenid:
vmstatestorage: vm
 
Did a fresh PVE installation. Backup of a VM-template to PBS still doesn't work. The VM-template is on a LVM-Thin-partition. Backup of a LVM container template works fine. If the VM-template is on a ZFS drive, the backup works fine, too.

Versions on PVE server:
Code:
root@fujitsu:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.114-1-pve)
pve-manager: 6.4-7 (running version: 6.4-7/04bc8e32)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-3
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Versions on PBS server:
Code:
proxmox-backup: 1.0-4 (running kernel: 5.4.114-1-pve)
proxmox-backup-server: 1.1.8-1 (running version: 1.1.8)
pve-kernel-5.4: 6.4-2 pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.65-1-pve: 5.4.65-1
ifupdown2: 3.0.0-1+pve3 libjs-extjs: 6.0.1-10
proxmox-backup-docs: 1.1.8-1
proxmox-backup-client: 1.1.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-xtermjs: 4.7.0-3
smartmontools: 7.2-pve2
zfsutils-linux: 2.0.4-pve1

Error message from backup task:
Code:
INFO: starting new backup job: vzdump 991 --mode snapshot --remove 0 --node fujitsu --storage PBS
INFO: Starting Backup of VM 991 (qemu)
INFO: Backup started at 2021-06-01 20:59:48
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: w10p-20h2-master
INFO: include disk 'virtio0' 'LVM:base-991-disk-1' 128G
INFO: include disk 'efidisk0' 'LVM:base-991-disk-0' 4M
INFO: creating Proxmox Backup Server archive 'vm/991/2021-06-01T18:59:48Z'
INFO: starting kvm to execute backup task
kvm: The device is not writable: Permission denied
ERROR: Backup of VM 991 failed - start failed: QEMU exited with code 1
INFO: Failed at 2021-06-01 20:59:55
INFO: Backup job finished with errors
TASK ERROR: job errors

LVM layout created by PVE server:
Code:
root@fujitsu:~# lvs -a
  LV              VG  Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  LVM             LVM twi-aotz--   1.60t             0.00   0.15
  [LVM_tdata]     LVM Twi-ao----   1.60t
  [LVM_tmeta]     LVM ewi-ao----  15.81g
  [lvol0_pmspare] LVM ewi-------  15.81g
  base-990-disk-0 pve Vri---tz-k   5.00g data
  base-991-disk-0 pve Vri---tz-k   4.00m data
  base-991-disk-1 pve Vri---tz-k 128.00g data
  base-999-disk-0 pve Vri---tz-k   4.00m data
  base-999-disk-1 pve Vri---tz-k 128.00g data
  data            pve twi-aotz--   1.29t             12.84  0.79
  [data_tdata]    pve Twi-ao----   1.29t
  [data_tmeta]    pve ewi-ao---- <13.49g
  [lvol0_pmspare] pve ewi------- <13.49g

Config of VM:
Code:
root@fujitsu:~# qm config 991
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 512
bios: ovmf
boot: order=virtio0;net0
cores: 2
efidisk0: LVM:base-991-disk-0,size=4M
machine: q35
memory: 4096
name: w10p-20h2-master
net0: virtio=AA:E7:3A:E4:C7:4F,bridge=vmbr6
numa: 1
ostype: win10
rng0: source=/dev/urandom
scsihw: virtio-scsi-pci
smbios1: uuid=9953aa43-ae1c-43cb-85a1-48e675686df5
sockets: 1
template: 1
vga: qxl,memory=128
virtio0: LVM:base-991-disk-1,cache=unsafe,size=128G
vmgenid: 8447516f-0b9c-4eaa-be02-e987eb712d5b
 
Last edited:
this is a new, separate issue with read-only EFI disks.. I'll take a closer look!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!