I have error when I try to restore VM from Promox 6 to Proxmox 7

lattoh

New Member
Dec 5, 2022
4
0
1
Dear,
I have this message when trying to restore VM.

restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2021_11_30-17_51_20.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp1793.fifo - /var/tmp/vzdumptmp1793CFG: size: 386 name: qemu-server.confDEV: dev_id=1 size: 594852970496 devname: drive-ide0CTIME: Tue Nov 30 17:51:21 2021Formatting '/var/lib/vz/images/101/vm-101-disk-0.raw', fmt=raw size=594852970496 preallocation=offnew volume ID is 'local:101/vm-101-disk-0.raw'map 'drive-ide0' to '/var/lib/vz/images/101/vm-101-disk-0.raw' (write zeros = 0)progress 1% (read 5948571648 bytes, duration 48 sec)progress 2% (read 11897077760 bytes, duration 85 sec)lzop: unexpected end of file: /var/lib/vz/dump/vzdump-qemu-100-2021_11_30-17_51_20.vma.lzovma: restore failed - short vma extent (1488896 < 3801600)/bin/bash: line 1: 1795 Exit 1 lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2021_11_30-17_51_20.vma.lzo1796 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp1793.fifo - /var/tmp/vzdumptmp1793temporary volume 'local:101/vm-101-disk-0.raw' sucessfuly removedno lock found trying to remove 'create' lockerror 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 && lzop -d -c /var/lib/vz/dump/vzdump-qemu-100-2021_11_30-17_51_20.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp1793.fifo - /var/tmp/vzdumptmp1793' failed: exit code 133


Please I need your help to have a good restore.


Best regards,
 
Yes, I read that - I want to know which version of Proxmox VE are you now using PVE 7.1 or PVE 7.2 or the latest version, PVE 7.3 (pveversion -v). If the node is not the latest version, I would upgrade to the latest version [0] and then test the restore.


[0] https://forum.proxmox.com/threads/proxmox-ve-7-3-released.118389/
 
lzop: unexpected end of file: /var/lib/vz/dump/vzdump-qemu-100-2021_11_30-17_51_20.vma.lzo

that reads like the backup file is truncated..
 
do you have another backup? how are you accessing it and what kind of storage is it on - from the path it looks like it's a local directory?