Hi there,
I am am longterm proxmox user and fan and recently installed version 7.2 for the first time.
During testing I stumpled across a huge issue and need to ask you for help.
I restored a backup of a Windows 10 VM i created on a different server. Upon restoring it it crashed.
At first I guessed it was a faulty backup or because it was created with Proxmox 6. But all my tests (fdisk, qemu-img check, vma verify) all indicaded it was fine.
After trying various things I made a test I assumed cannot fail: I created a completely new Windows 10 VM on that maschine, backed it up (zst, stop) and restored it.
This again threw the error I was already familiar with:
The only thing that is swquard is that 8% of the 60GB virtual harddisk is about 5GB which is coincidentally roughly the size of the backup itself.
This is the information on my Test-VM:
My setup process was pretty basic, nothing deviating from defaults or otherwise special except for the dual ZFS SSD mirror, which I use as Boot and System Pool.
I think you might wanna know my storage configuration:
Does someone have an iea where I shall start poking?
What information would you need to get a better picture?
Any help is greatly appreciated!
Thanks in advance and kind regards!
I am am longterm proxmox user and fan and recently installed version 7.2 for the first time.
During testing I stumpled across a huge issue and need to ask you for help.
I restored a backup of a Windows 10 VM i created on a different server. Upon restoring it it crashed.
At first I guessed it was a faulty backup or because it was created with Proxmox 6. But all my tests (fdisk, qemu-img check, vma verify) all indicaded it was fine.
After trying various things I made a test I assumed cannot fail: I created a completely new Windows 10 VM on that maschine, backed it up (zst, stop) and restored it.
This again threw the error I was already familiar with:
Code:
Header
Proxmox
Virtual Environment 7.2-5
Storage 'local-ext-hdd' on node 'proxmox-1-server'
Search:
Logs
()
restore vma archive: zstd -q -d -c /mnt/pve/local-ext-hdd/dump/vzdump-qemu-1013-2022_06_28-16_53_40.vma.zst | vma extract -v -r /var/tmp/vzdumptmp1800767.fifo - /var/tmp/vzdumptmp1800767
CFG: size: 859 name: qemu-server.conf
DEV: dev_id=1 size: 540672 devname: drive-efidisk0
DEV: dev_id=2 size: 64424509440 devname: drive-scsi1
CTIME: Tue Jun 28 16:53:41 2022
Formatting '/mnt/pve/local-ext-ssd/images/1014/vm-1014-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=540672 lazy_refcounts=off refcount_bits=16
new volume ID is 'local-ext-ssd:1014/vm-1014-disk-0.qcow2'
Formatting '/mnt/pve/local-ext-ssd/images/1014/vm-1014-disk-1.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=64424509440 lazy_refcounts=off refcount_bits=16
new volume ID is 'local-ext-ssd:1014/vm-1014-disk-1.qcow2'
map 'drive-efidisk0' to '/mnt/pve/local-ext-ssd/images/1014/vm-1014-disk-0.qcow2' (write zeros = 0)
map 'drive-scsi1' to '/mnt/pve/local-ext-ssd/images/1014/vm-1014-disk-1.qcow2' (write zeros = 0)
progress 1% (read 644284416 bytes, duration 0 sec)
progress 2% (read 1288503296 bytes, duration 1 sec)
progress 3% (read 1932787712 bytes, duration 2 sec)
progress 4% (read 2577006592 bytes, duration 3 sec)
progress 5% (read 3221291008 bytes, duration 4 sec)
progress 6% (read 3865509888 bytes, duration 4 sec)
progress 7% (read 4509794304 bytes, duration 5 sec)
progress 8% (read 5154013184 bytes, duration 6 sec)
_28-16_53_40.vma.zst : Decoding error (36) : Corrupted block detected
vma: restore failed - short vma extent (1208014 < 3801600)
/bin/bash: line 1: 1800769 Exit 1 zstd -q -d -c /mnt/pve/local-ext-hdd/dump/vzdump-qemu-1013-2022_06_28-16_53_40.vma.zst
1800770 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp1800767.fifo - /var/tmp/vzdumptmp1800767
temporary volume 'local-ext-ssd:1014/vm-1014-disk-0.qcow2' sucessfuly removed
temporary volume 'local-ext-ssd:1014/vm-1014-disk-1.qcow2' 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 1014 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/local-ext-hdd/dump/vzdump-qemu-1013-2022_06_28-16_53_40.vma.zst | vma extract -v -r /var/tmp/vzdumptmp1800767.fifo - /var/tmp/vzdumptmp1800767' failed: exit code 133The only thing that is swquard is that 8% of the 60GB virtual harddisk is about 5GB which is coincidentally roughly the size of the backup itself.
This is the information on my Test-VM:
Code:
Header
Proxmox
Virtual Environment 7.2-5
Storage 'local-ext-hdd' on node 'proxmox-1-server'
Search:
Logs
()
#Windows 10 Pro Server
#---------------------
#- System Windows 10 Pro DE 64bit
#
#Historie
#--------
#- 2022-06-28 16h52 ... Minimale Windows-Installation erstellt
balloon: 0
bios: ovmf
boot: order=scsi1;ide0
cores: 2
efidisk0: local-ext-ssd:1013/vm-1013-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: none,media=cdrom
machine: pc-q35-6.2
memory: 4096
meta: creation-qemu=6.2.0,ctime=1656420248
name: viwe-handel-server-neu
net0: e1000=AE:7D:A3:97:8C:74,bridge=vmbr1
numa: 0
ostype: win10
scsi1: local-ext-ssd:1013/vm-1013-disk-1.qcow2,discard=on,size=60G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=40b300fa-82ea-4f03-b724-e6b39bcd407d
sockets: 1
vmgenid: 1600a91c-8400-447d-83f6-5baa00f6a751
#qmdump#map:efidisk0:drive-efidisk0:local-ext-ssd:qcow2:
#qmdump#map:scsi1:drive-scsi1:local-ext-ssd:qcow2:My setup process was pretty basic, nothing deviating from defaults or otherwise special except for the dual ZFS SSD mirror, which I use as Boot and System Pool.
I think you might wanna know my storage configuration:
- "local" (directory, on zfs mirror)
- "local-zfs" (zfs for disk images, on zfs mirror)
- "local-ext-ssd" (ext4, directory, for disk images, used for testing, extra SSD in hotswap bay)
- "local-ext-hdd (ext4, directory, for local backups, ISOs, HDD in hotswap bay)
- nas (cifs, on a Synology diskstation, for remote backups, ISOs)
Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-3-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-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.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1Does someone have an iea where I shall start poking?
What information would you need to get a better picture?
Any help is greatly appreciated!
Thanks in advance and kind regards!
Last edited:
