I had several VMs and Template VMs on Proxmox 6.4.x on a Dell PowerEdge R610. That version was installed back when 6 first came out. It was problematic so I set out to backup the VM and install Proxmox 7.4. The VMs ran without issue but there seemed to be issues plaguing the system. I know enough about Linux that I couldn't correct it so I decided a new install was in order. I only needed to backup one Template of a VM and it successfully backed up to a network drive without errors. I did two different backups. One full stop, no compression and the other full stop, GZIP. I also moved (copied) the HDD to the network drive, without errors. I installed Proxmox 7.4 (on the same server 6.4.x was on) and updated it as of July 16, 2024. The old install of Proxmox and VMs are destroyed so the back ups and HDD is all I have. I went with Proxmox 7.4 becuase 8.2 was problematic at install. I did some research on the error and decided to go with 7.4, which installed without issue.
I added the network drive to the new Proxmox install and proceeded to restore from the backup. I attempted to restore the uncompressed backup first. This is the configuration...
bootdisk: virtio0
cores: 1
ide2: none,media=cdrom
memory: 4096
name: KOHA-Library
net0: virtio=3E:82: D0:CA:6B:19,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=f01843fb-ef79-4e19-97cc-183a28f99cac
sockets: 1
startup: order=2,up=60
template: 1
virtio0: local-lvm:base-1010-disk-0,
size=32G
vmgenid: 957aaa3f-ec1d-43f9-8e4f-d3ab1374f696
#qmdump#map:virtio0:drive-virtio0:local-lvm:raw:
This is the error I get when I attempt to restore from uncompressed backup...
----
restore vma archive: vma extract -v -r /var/tmp/vzdumptmp156307.fifo /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_01-17_23_51.vma /var/tmp/vzdumptmp156307
CFG: size: 404 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-virtio0
CTIME: Mon Jul 1 12:23:55 2024
Logical volume "vm-200-disk-0" created.
new volume ID is 'local-lvm:vm-200-disk-0'
map 'drive-virtio0' to '/dev/pve/vm-200-disk-0' (write zeros = 0)
progress 1% (read 343605248 bytes, duration 0 sec)
progress 2% (read 687210496 bytes, duration 3 sec)
vma: restore failed - wrong vma extent header chechsum
Logical volume "vm-200-disk-0" successfully removed
temporary volume 'local-lvm:vm-200-disk-0' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 200 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && vma extract -v -r /var/tmp/vzdumptmp156307.fifo /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_01-17_23_51.vma /var/tmp/vzdumptmp156307' failed: got signal 5
----
This is the error I get when I attempt to restore from compressed (gz) backup...
----
restore vma archive: zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601
CFG: size: 404 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-virtio0
CTIME: Tue Jul 2 09:31:00 2024
Logical volume "vm-200-disk-0" created.
new volume ID is 'local-lvm:vm-200-disk-0'
map 'drive-virtio0' to '/dev/pve/vm-200-disk-0' (write zeros = 0)
progress 1% (read 343605248 bytes, duration 1 sec)
progress 2% (read 687210496 bytes, duration 2 sec)
gzip: /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz: invalid compressed data--format violated
vma: restore failed - short vma extent (1778176 < 3801600)
/bin/bash: line 1: 165603 Exit 1 zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz
165604 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601
Logical volume "vm-200-disk-0" successfully removed
temporary volume 'local-lvm:vm-200-disk-0' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 200 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601' failed: exit code 133
----
I did a little research here and on the web but didn't find anything to solve the problem.
Before I try to use the "template" drive backup on a new VM on the new install I thought I would get help with this to see if I can get it corrected.
Thank you!
I added the network drive to the new Proxmox install and proceeded to restore from the backup. I attempted to restore the uncompressed backup first. This is the configuration...
bootdisk: virtio0
cores: 1
ide2: none,media=cdrom
memory: 4096
name: KOHA-Library
net0: virtio=3E:82: D0:CA:6B:19,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=f01843fb-ef79-4e19-97cc-183a28f99cac
sockets: 1
startup: order=2,up=60
template: 1
virtio0: local-lvm:base-1010-disk-0,
size=32G
vmgenid: 957aaa3f-ec1d-43f9-8e4f-d3ab1374f696
#qmdump#map:virtio0:drive-virtio0:local-lvm:raw:
This is the error I get when I attempt to restore from uncompressed backup...
----
restore vma archive: vma extract -v -r /var/tmp/vzdumptmp156307.fifo /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_01-17_23_51.vma /var/tmp/vzdumptmp156307
CFG: size: 404 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-virtio0
CTIME: Mon Jul 1 12:23:55 2024
Logical volume "vm-200-disk-0" created.
new volume ID is 'local-lvm:vm-200-disk-0'
map 'drive-virtio0' to '/dev/pve/vm-200-disk-0' (write zeros = 0)
progress 1% (read 343605248 bytes, duration 0 sec)
progress 2% (read 687210496 bytes, duration 3 sec)
vma: restore failed - wrong vma extent header chechsum
Logical volume "vm-200-disk-0" successfully removed
temporary volume 'local-lvm:vm-200-disk-0' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 200 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && vma extract -v -r /var/tmp/vzdumptmp156307.fifo /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_01-17_23_51.vma /var/tmp/vzdumptmp156307' failed: got signal 5
----
This is the error I get when I attempt to restore from compressed (gz) backup...
----
restore vma archive: zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601
CFG: size: 404 name: qemu-server.conf
DEV: dev_id=1 size: 34359738368 devname: drive-virtio0
CTIME: Tue Jul 2 09:31:00 2024
Logical volume "vm-200-disk-0" created.
new volume ID is 'local-lvm:vm-200-disk-0'
map 'drive-virtio0' to '/dev/pve/vm-200-disk-0' (write zeros = 0)
progress 1% (read 343605248 bytes, duration 1 sec)
progress 2% (read 687210496 bytes, duration 2 sec)
gzip: /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz: invalid compressed data--format violated
vma: restore failed - short vma extent (1778176 < 3801600)
/bin/bash: line 1: 165603 Exit 1 zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz
165604 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601
Logical volume "vm-200-disk-0" successfully removed
temporary volume 'local-lvm:vm-200-disk-0' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 200 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zcat /mnt/pve/Backup/dump/vzdump-qemu-1010-2024_07_02-14_30_59.vma.gz | vma extract -v -r /var/tmp/vzdumptmp165601.fifo - /var/tmp/vzdumptmp165601' failed: exit code 133
----
I did a little research here and on the web but didn't find anything to solve the problem.
Before I try to use the "template" drive backup on a new VM on the new install I thought I would get help with this to see if I can get it corrected.
Thank you!
