Issue with VM restoring backup

U

UK SPEED

Member
Dec 23, 2023
74
2
8
Hi
After trying to restore from VM backup, I get this issue, can't help?

root@dell1:/nvme/backups# qmrestore /nvme/backups/vzdump-qemu-103-2024_04_14-15_00_03.vma.zst 203 --storage file222<br>restore vma archive: zstd -q -d -c /nvme/backups/vzdump-qemu-103-2024_04_14-15_00_03.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2579751.fifo - /var/tmp/vzdumptmp2579751<br>CFG: size: 786 name: qemu-server.conf<br>DEV: dev_id=1 size: 540672 devname: drive-efidisk0<br>DEV: dev_id=2 size: 536870912000 devname: drive-scsi0<br>DEV: dev_id=3 size: 536870912000 devname: drive-scsi1<br>DEV: dev_id=4 size: 1048576 devname: drive-tpmstate0-backup<br>CTIME: Sun Apr 14 15:00:03 2024<br>Formatting '/mnt/pve/file222/images/203/vm-203-disk-0.raw', fmt=raw size=540672 preallocation=off<br>new volume ID is 'file222:203/vm-203-disk-0.raw'<br>Formatting '/mnt/pve/file222/images/203/vm-203-disk-1.raw', fmt=raw size=536870912000 preallocation=off<br>new volume ID is 'file222:203/vm-203-disk-1.raw'<br>Formatting '/mnt/pve/file222/images/203/vm-203-disk-2.raw', fmt=raw size=536870912000 preallocation=off<br>new volume ID is 'file222:203/vm-203-disk-2.raw'<br>Formatting '/mnt/pve/file222/images/203/vm-203-disk-3.raw', fmt=raw size=1048576 preallocation=off<br>new volume ID is 'file222:203/vm-203-disk-3.raw'<br>map 'drive-efidisk0' to '/mnt/pve/file222/images/203/vm-203-disk-0.raw' (write zeros = 0)<br>map 'drive-scsi0' to '/mnt/pve/file222/images/203/vm-203-disk-1.raw' (write zeros = 0)<br>map 'drive-scsi1' to '/mnt/pve/file222/images/203/vm-203-disk-2.raw' (write zeros = 0)<br>map 'drive-tpmstate0-backup' to '/mnt/pve/file222/images/203/vm-203-disk-3.raw' (write zeros = 0)<br>_14-15_00_03.vma.zst : Read error (39) : premature end<br>vma: restore failed - short vma extent (76930 &lt; 3801600)<br>/bin/bash: line 1: 2579753 Exit 1 zstd -q -d -c /nvme/backups/vzdump-qemu-103-2024_04_14-15_00_03.vma.zst<br> 2579754 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp2579751.fifo - /var/tmp/vzdumptmp2579751<br>temporary volume 'file222:203/vm-203-disk-1.raw' successfully removed<br>temporary volume 'file222:203/vm-203-disk-3.raw' successfully removed<br>temporary volume 'file222:203/vm-203-disk-2.raw' successfully removed<br>temporary volume 'file222:203/vm-203-disk-0.raw' successfully removed<br>no lock found trying to remove 'create' lock<br>error before or during data restore, some or all disks were not completely restored. VM 203 state is NOT cleaned up.<br>command 'set -o pipefail &amp;&amp; zstd -q -d -c /nvme/backups/vzdump-qemu-103-2024_04_14-15_00_03.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2579751.fifo - /var/tmp/vzdumptmp2579751' failed: exit code 133<br><br><br>root@dell1:/nvme/backups# qmrestore /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst 201 --storage file222<br>unable to restore VM 201 - VM 201 already exists on node 'dell1'<br>root@dell1:/nvme/backups# qm destroy 201<br>root@dell1:/nvme/backups# qmrestore /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst 201 --storage file222<br>root@dell1:/nvme/backups# qmrestore /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst 201 --storage file222<br>restore vma archive: zstd -q -d -c /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2460238.fifo - /var/tmp/vzdumptmp2460238<br>CFG: size: 864 name: qemu-server.conf<br>DEV: dev_id=1 size: 540672 devname: drive-efidisk0<br>DEV: dev_id=2 size: 17408 devname: drive-tpmstate0-backup<br>DEV: dev_id=3 size: 1503238553600 devname: drive-virtio0<br>DEV: dev_id=4 size: 805306368000 devname: drive-virtio1<br>CTIME: Fri Apr 11 10:39:56 2025<br>Formatting '/mnt/pve/file222/images/201/vm-201-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=540672 lazy_refcounts=off refcount_bits=16<br>new volume ID is 'file222:201/vm-201-disk-0.qcow2'<br>Formatting '/mnt/pve/file222/images/201/vm-201-disk-0.raw', fmt=raw size=17408 preallocation=off<br>new volume ID is 'file222:201/vm-201-disk-0.raw'<br>Formatting '/mnt/pve/file222/images/201/vm-201-disk-1.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=1503238553600 lazy_refcounts=off refcount_bits=16<br>new volume ID is 'file222:201/vm-201-disk-1.qcow2'<br>Formatting '/mnt/pve/file222/images/201/vm-201-disk-2.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=805306368000 lazy_refcounts=off refcount_bits=16<br>new volume ID is 'file222:201/vm-201-disk-2.qcow2'<br>map 'drive-efidisk0' to '/mnt/pve/file222/images/201/vm-201-disk-0.qcow2' (write zeros = 0)<br>map 'drive-tpmstate0-backup' to '/mnt/pve/file222/images/201/vm-201-disk-0.raw' (write zeros = 0)<br>map 'drive-virtio0' to '/mnt/pve/file222/images/201/vm-201-disk-1.qcow2' (write zeros = 0)<br>map 'drive-virtio1' to '/mnt/pve/file222/images/201/vm-201-disk-2.qcow2' (write zeros = 0)<br>progress 1% (read 23085514752 bytes, duration 341 sec)<br>progress 2% (read 46170963968 bytes, duration 684 sec)<br>progress 3% (read 69256413184 bytes, duration 1029 sec)<br>progress 4% (read 92341862400 bytes, duration 1374 sec)<br>progress 5% (read 115427311616 bytes, duration 1724 sec)<br>progress 6% (read 138512760832 bytes, duration 2072 sec)<br>progress 7% (read 161598210048 bytes, duration 2419 sec)<br>progress 8% (read 184683659264 bytes, duration 2766 sec)<br>zstd: /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst: premature gz end<br>vma: restore failed - short vma extent (2789297 &lt; 3801600)<br>/bin/bash: line 1: 2460240 Exit 1 zstd -q -d -c /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst<br> 2460241 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp2460238.fifo - /var/tmp/vzdumptmp2460238<br>temporary volume 'file222:201/vm-201-disk-2.qcow2' successfully removed<br>temporary volume 'file222:201/vm-201-disk-0.raw' successfully removed<br>temporary volume 'file222:201/vm-201-disk-0.qcow2' successfully removed<br>temporary volume 'file222:201/vm-201-disk-1.qcow2' successfully removed<br>no lock found trying to remove 'create' lock<br>error before or during data restore, some or all disks were not completely restored. VM 201 state is NOT cleaned up.<br>command 'set -o pipefail &amp;&amp; zstd -q -d -c /nvme/backups/vzdump-qemu-101-2025_04_11-10_39_54.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2460238.fifo - /var/tmp/vzdumptmp2460238' failed: exit code 133
 
the backup archive is truncated/incomplete..
 
I am not sure what you are referring to.. maybe you could expand your question?
 
if all your backups suffer from this, something is wrong with your backup target storage or PVE node..
 
  • Like
Reactions: lew-adv-sol
For my situation I use a synology connected via smb. Templates restored just fine, VMs did not. I can access that backup storage without issue and it shows in good health. I have used that synology without issue for some time, even the ext drive attached to it. I can not seem to find a cause for this that I can remedy. Proxmox does not say if it was timeout issue, or anything. My node shows no errors, or issues and this issue impacts all 3 nodes ability to restore backups. That leave the storage or PVE has a bug that still persists.
 
Hi,
lew-adv-sol said:
Same issue
Not much on what the cause is but manual restore seems to be the workaround. Not ideal for regular backup and restores but I have not seen any other solutions and ALL my backups seem to suffer from this. So seems like at this moment I will never be able to use the backup options in pve. Looking for alternatives now that I have wasted weeks installing and troubleshooting my 3 nodes and have no backup option built in at this point.
Not trying to vent but it is frustrating.
Click to expand...
please share the full task log of the failed restore operation as well as the output of pveversion -v. What exactly do you mean by manual restore?
 
  • Like
Reactions: lew-adv-sol
fiona said:
Hi,

please share the full task log of the failed restore operation as well as the output of pveversion -v. What exactly do you mean by manual restore?
Click to expand...
L

Post in thread 'error 133 failed backup - unreliable backups?'

Backup task log:
Code: 
2025-05-06 14:25:56 INFO: Starting Backup of VM 104 (qemu)
2025-05-06 14:25:56 INFO: status = stopped
2025-05-06 14:25:56 INFO: backup mode: stop
2025-05-06 14:25:56 INFO: ionice priority: 7
2025-05-06 14:25:56 INFO: VM Name: NTL-PC
2025-05-06 14:25:56 INFO: include disk 'scsi0' 'local-lvm:vm-104-disk-1' 100G
2025-05-06 14:25:56 INFO: include disk 'efidisk0' 'local-lvm:vm-104-disk-0' 4M
2025-05-06 14:25:56 INFO: include disk 'tpmstate0' 'local-lvm:vm-104-disk-2' 4M
2025-05-06 14:25:56 INFO: snapshots found (not included into backup)
2025-05-06 14:25:56 INFO: creating...
 
You must log in or register to reply here.
Top Bottom