exit code 133 while restoring Win10 VM

[nekodesew]

Hello,

I broke my WIN10 VM (2TB worth of data), so I wanted to restore it. But during the restore process, it only goes up to 47% then errors out. During the restore process, I used LZO as compression. I only have one backup so I can't lose this backup. During the backing up process, I don't think I saw any issues.

restore vma archive: lzop -d -c /mnt/data/dump/vzdump-qemu-100-2021_12_19-22_07_08.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp2666509.fifo - /var/tmp/vzdumptmp2666509
CFG: size: 834 name: qemu-server.conf
DEV: dev_id=1 size: 540672 devname: drive-efidisk0
DEV: dev_id=2 size: 2147483648000 devname: drive-scsi0
CTIME: Sun Dec 19 22:07:12 2021
new volume ID is 'HDD4TB:vm-100-disk-0'
new volume ID is 'HDD4TB:vm-100-disk-1'
map 'drive-efidisk0' to '/dev/zvol/HDD4TB/vm-100-disk-0' (write zeros = 0)
map 'drive-scsi0' to '/dev/zvol/HDD4TB/vm-100-disk-1' (write zeros = 0)
progress 1% (read 21474902016 bytes, duration 87 sec)
progress 2% (read 42949738496 bytes, duration 247 sec)
progress 3% (read 64424574976 bytes, duration 434 sec)
progress 4% (read 85899411456 bytes, duration 609 sec)
progress 5% (read 107374247936 bytes, duration 780 sec)
progress 6% (read 128849084416 bytes, duration 976 sec)
progress 7% (read 150323920896 bytes, duration 1151 sec)
progress 8% (read 171798757376 bytes, duration 1327 sec)
progress 9% (read 193273593856 bytes, duration 1496 sec)
progress 10% (read 214748430336 bytes, duration 1666 sec)
progress 11% (read 236223266816 bytes, duration 1867 sec)
progress 12% (read 257698103296 bytes, duration 2034 sec)
progress 13% (read 279173005312 bytes, duration 2255 sec)
progress 14% (read 300647841792 bytes, duration 2450 sec)
progress 15% (read 322122678272 bytes, duration 2620 sec)
progress 16% (read 343597514752 bytes, duration 2806 sec)
progress 17% (read 365072351232 bytes, duration 2987 sec)
progress 18% (read 386547187712 bytes, duration 3179 sec)
progress 19% (read 408022024192 bytes, duration 3364 sec)
progress 20% (read 429496860672 bytes, duration 3560 sec)
progress 21% (read 450971697152 bytes, duration 3739 sec)
progress 22% (read 472446533632 bytes, duration 3909 sec)
progress 23% (read 493921370112 bytes, duration 4082 sec)
progress 24% (read 515396206592 bytes, duration 4262 sec)
progress 25% (read 536871043072 bytes, duration 4435 sec)
progress 26% (read 558345945088 bytes, duration 4609 sec)
progress 27% (read 579820781568 bytes, duration 4782 sec)
progress 28% (read 601295618048 bytes, duration 4953 sec)
progress 29% (read 622770454528 bytes, duration 5126 sec)
progress 30% (read 644245291008 bytes, duration 5300 sec)
progress 31% (read 665720127488 bytes, duration 5471 sec)
progress 32% (read 687194963968 bytes, duration 5647 sec)
progress 33% (read 708669800448 bytes, duration 5819 sec)
progress 34% (read 730144636928 bytes, duration 5997 sec)
progress 35% (read 751619473408 bytes, duration 6173 sec)
progress 36% (read 773094309888 bytes, duration 6349 sec)
progress 37% (read 794569146368 bytes, duration 6525 sec)
progress 38% (read 816044048384 bytes, duration 6698 sec)
progress 39% (read 837518884864 bytes, duration 6873 sec)
progress 40% (read 858993721344 bytes, duration 7057 sec)
progress 41% (read 880468557824 bytes, duration 7233 sec)
progress 42% (read 901943394304 bytes, duration 7412 sec)
progress 43% (read 923418230784 bytes, duration 7591 sec)
progress 44% (read 944893067264 bytes, duration 7770 sec)
progress 45% (read 966367903744 bytes, duration 7950 sec)
progress 46% (read 987842740224 bytes, duration 8129 sec)
progress 47% (read 1009317576704 bytes, duration 8319 sec)
lzop: /mnt/data/dump/vzdump-qemu-100-2021_12_19-22_07_08.vma.lzo: Checksum error
vma: restore failed - short vma extent (2621952 < 3801600)
/bin/bash: line 1: 2666511 Exit 1                  lzop -d -c /mnt/data/dump/vzdump-qemu-100-2021_12_19-22_07_08.vma.lzo
     2666512 Trace/breakpoint trap   | vma extract -v -r /var/tmp/vzdumptmp2666509.fifo - /var/tmp/vzdumptmp2666509
temporary volume 'HDD4TB:vm-100-disk-0' sucessfuly removed
temporary volume 'HDD4TB:vm-100-disk-1' 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 100 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && lzop -d -c /mnt/data/dump/vzdump-qemu-100-2021_12_19-22_07_08.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp2666509.fifo - /var/tmp/vzdumptmp2666509' failed: exit code 133

There is enough disk space, currently I'm using 1.07TB out of 3.86TB.

Not sure if this will help but this is what happens when I type in "pveversion -v"

root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
root@pve:~#

Please help.

 

[ualex]

There is a problem with your archive:
lzop: /mnt/data/dump/vzdump-qemu-100-2021_12_19-22_07_08.vma.lzo: Checksum error

 

[Penetr8tor]

I have a similar problem:

I f anyone could help - I got a ZSTD error which I think is compression?

restore vma archive: zstd -q -d -c /mnt/pve/NASvaderPVE2-NFS-Backups/dump/vzdump-qemu-100-2022_08_15-03_00_59.vma.zst | vma extract -v -r /var/tmp/vzdumptmp972350.fifo - /var/tmp/vzdumptmp972350
CFG: size: 792 name: qemu-server.conf
DEV: dev_id=1 size: 4194304 devname: drive-tpmstate0-backup
DEV: dev_id=2 size: 68719476736 devname: drive-virtio0
CTIME: Mon Aug 15 03:01:00 2022
Formatting '/mnt/pve/NASvaderPVE2-SMB/images/101/vm-101-disk-0.raw', fmt=raw size=4194304 preallocation=off
new volume ID is 'NASvaderPVE2-SMB:101/vm-101-disk-0.raw'
Formatting '/mnt/pve/NASvaderPVE2-SMB/images/101/vm-101-disk-1.raw', fmt=raw size=68719476736 preallocation=off
new volume ID is 'NASvaderPVE2-SMB:101/vm-101-disk-1.raw'
map 'drive-tpmstate0-backup' to '/mnt/pve/NASvaderPVE2-SMB/images/101/vm-101-disk-0.raw' (write zeros = 0)
map 'drive-virtio0' to '/mnt/pve/NASvaderPVE2-SMB/images/101/vm-101-disk-1.raw' (write zeros = 0)
progress 1% (read 687276032 bytes, duration 3 sec)
progress 2% (read 1374486528 bytes, duration 8 sec)
progress 3% (read 2061762560 bytes, duration 13 sec)
_15-03_00_59.vma.zst : Decoding error (36) : Corrupted block detected
vma: restore failed - short vma extent (452292 < 3801600)
/bin/bash: line 1: 972352 Exit 1                  zstd -q -d -c /mnt/pve/NASvaderPVE2-NFS-Backups/dump/vzdump-qemu-100-2022_08_15-03_00_59.vma.zst
     972353 Trace/breakpoint trap   | vma extract -v -r /var/tmp/vzdumptmp972350.fifo - /var/tmp/vzdumptmp972350
temporary volume 'NASvaderPVE2-SMB:101/vm-101-disk-1.raw' sucessfuly removed
temporary volume 'NASvaderPVE2-SMB:101/vm-101-disk-0.raw' 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 101 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/NASvaderPVE2-NFS-Backups/dump/vzdump-qemu-100-2022_08_15-03_00_59.vma.zst | vma extract -v -r /var/tmp/vzdumptmp972350.fifo - /var/tmp/vzdumptmp972350' failed: exit code 133