Hello, i have proxmox 8.3.0 installed on a I7-8700 32 GB ram, installed on a nvme 1TB.
i connect a USB drive (3.0) for my backup, this one is a 1TB HD. 5400RPM SATA 6Gb/s 3.5-inch Hard Drive.
i have a 2 points.
1. Taking the backup is really slow.
i think the speed backing up very very very slow, i suspect something is not right.
Iv tried 3 different backup : with zStd, gZip and "none".
all 3 where slow as a turtle, i know this machine is not a server by any stretch, but still , i mean they are really slow.
for 500Gb they took
1h.40m for the zStd,
2h.43m for the gzip
1h.38m for the "none"
I know the HD isn't fast, but i can copy files on that drives way faster than this backup can.
Where should i investigate ? iv read many post about that, tried everything, and its still really too much slow to be practical.
These 3 backups did not gave any error when taking them, they all shown TASK OK.
When doing the backup the vm is closed, snapshot mode.
i know some will say "the vm should be running so it will take a snapshot, and it will be faster with subsequent backup."
But my point is : i just want one good backup.
2.The backup have errors.
On a new proxmox install (same pc, same version, just using another nvme as boot disk, the other nvme is removed from pc)
i recreated my vm and trying to restore that backup taken on step 1.
I tried with zstd and got an error on restore, then gzip, got also an error now trying with "none" thinking that maybe its a
encryption/compression emulation or something problem.
zStd error when restoring :
...
progress 10% (read 53687091200 bytes, duration 255 sec)
progress 11% (read 59055800320 bytes, duration 276 sec)
_06-09_29_53.vma.zst : Decoding error (36) : Data corruption detected
vma: restore failed - short vma extent (1255424 < 3277312)
/bin/bash: line 1: 1651 Exit 1 zstd -q -d -c /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-09_29_53.vma.zst
1652 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp1642.fifo - /var/tmp/vzdumptmp1642
Logical volume "vm-100-disk-0" successfully removed.
temporary volume 'local-lvm:vm-100-disk-0' successfully 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 && zstd -q -d -c /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-09_29_53.vma.zst | vma extract -v -r /var/tmp/vzdumptmp1642.fifo - /var/tmp/vzdumptmp1642' failed: exit code 133
so i thought, as some suggestion on forums, try with gzip, so i did :
gzip error when restoring :
restore vma archive: zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339
CFG: size: 640 name: qemu-server.conf
CFG: size: 584 name: qemu-server.fw
DEV: dev_id=1 size: 536870912000 devname: drive-scsi0
CTIME: Sun Apr 6 11:37:44 2025
Logical volume "vm-100-disk-0" successfully removed.
Logical volume "vm-100-disk-0" created.
new volume ID is 'local-lvm:vm-100-disk-0'
map 'drive-scsi0' to '/dev/pve/vm-100-disk-0' (write zeros = 0)
progress 1% (read 5368709120 bytes, duration 25 sec)
progress 2% (read 10737418240 bytes, duration 60 sec)
progress 3% (read 16106127360 bytes, duration 96 sec)
progress 4% (read 21474836480 bytes, duration 137 sec)
progress 5% (read 26843545600 bytes, duration 169 sec)
progress 6% (read 32212254720 bytes, duration 202 sec)
progress 7% (read 37580963840 bytes, duration 236 sec)
vma: restore failed - wrong vma extent header chechsum
/bin/bash: line 1: 5346 Broken pipe zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz
5347 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339
Logical volume "vm-100-disk-0" successfully removed.
temporary volume 'local-lvm:vm-100-disk-0' successfully 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 && zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339' failed: exit code 133
"none" error i got when restoring :
It is like it got stuck @ 22 %, or at least that what it was showing, i waited 1h.40m, but the process was really stuck @ 22%. So i stopped it anyway, got and unexpected state .
And then even proxmox was frozen, i had to reset it all.
When i came back in, i noticed the disk restored was there but the vm config was not ok, the name was not set, etc.
So i copied the original 100.conf, to see if the disk was ok.
Started the VM but it got stuck in, so the disk is not completed.
iv join the complete output in the attachment.
i connect a USB drive (3.0) for my backup, this one is a 1TB HD. 5400RPM SATA 6Gb/s 3.5-inch Hard Drive.
i have a 2 points.
1. Taking the backup is really slow.
i think the speed backing up very very very slow, i suspect something is not right.
Iv tried 3 different backup : with zStd, gZip and "none".
all 3 where slow as a turtle, i know this machine is not a server by any stretch, but still , i mean they are really slow.
for 500Gb they took
1h.40m for the zStd,
2h.43m for the gzip
1h.38m for the "none"
I know the HD isn't fast, but i can copy files on that drives way faster than this backup can.
Where should i investigate ? iv read many post about that, tried everything, and its still really too much slow to be practical.
These 3 backups did not gave any error when taking them, they all shown TASK OK.
When doing the backup the vm is closed, snapshot mode.
i know some will say "the vm should be running so it will take a snapshot, and it will be faster with subsequent backup."
But my point is : i just want one good backup.
2.The backup have errors.
On a new proxmox install (same pc, same version, just using another nvme as boot disk, the other nvme is removed from pc)
i recreated my vm and trying to restore that backup taken on step 1.
I tried with zstd and got an error on restore, then gzip, got also an error now trying with "none" thinking that maybe its a
encryption/compression emulation or something problem.
zStd error when restoring :
...
progress 10% (read 53687091200 bytes, duration 255 sec)
progress 11% (read 59055800320 bytes, duration 276 sec)
_06-09_29_53.vma.zst : Decoding error (36) : Data corruption detected
vma: restore failed - short vma extent (1255424 < 3277312)
/bin/bash: line 1: 1651 Exit 1 zstd -q -d -c /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-09_29_53.vma.zst
1652 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp1642.fifo - /var/tmp/vzdumptmp1642
Logical volume "vm-100-disk-0" successfully removed.
temporary volume 'local-lvm:vm-100-disk-0' successfully 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 && zstd -q -d -c /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-09_29_53.vma.zst | vma extract -v -r /var/tmp/vzdumptmp1642.fifo - /var/tmp/vzdumptmp1642' failed: exit code 133
so i thought, as some suggestion on forums, try with gzip, so i did :
gzip error when restoring :
restore vma archive: zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339
CFG: size: 640 name: qemu-server.conf
CFG: size: 584 name: qemu-server.fw
DEV: dev_id=1 size: 536870912000 devname: drive-scsi0
CTIME: Sun Apr 6 11:37:44 2025
Logical volume "vm-100-disk-0" successfully removed.
Logical volume "vm-100-disk-0" created.
new volume ID is 'local-lvm:vm-100-disk-0'
map 'drive-scsi0' to '/dev/pve/vm-100-disk-0' (write zeros = 0)
progress 1% (read 5368709120 bytes, duration 25 sec)
progress 2% (read 10737418240 bytes, duration 60 sec)
progress 3% (read 16106127360 bytes, duration 96 sec)
progress 4% (read 21474836480 bytes, duration 137 sec)
progress 5% (read 26843545600 bytes, duration 169 sec)
progress 6% (read 32212254720 bytes, duration 202 sec)
progress 7% (read 37580963840 bytes, duration 236 sec)
vma: restore failed - wrong vma extent header chechsum
/bin/bash: line 1: 5346 Broken pipe zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz
5347 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339
Logical volume "vm-100-disk-0" successfully removed.
temporary volume 'local-lvm:vm-100-disk-0' successfully 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 && zcat /media/ProxmoxBackup/Backup/dump/vzdump-qemu-100-2025_04_06-11_37_43.vma.gz | vma extract -v -r /var/tmp/vzdumptmp5339.fifo - /var/tmp/vzdumptmp5339' failed: exit code 133
"none" error i got when restoring :
It is like it got stuck @ 22 %, or at least that what it was showing, i waited 1h.40m, but the process was really stuck @ 22%. So i stopped it anyway, got and unexpected state .
And then even proxmox was frozen, i had to reset it all.
When i came back in, i noticed the disk restored was there but the vm config was not ok, the name was not set, etc.
So i copied the original 100.conf, to see if the disk was ok.
Started the VM but it got stuck in, so the disk is not completed.
iv join the complete output in the attachment.
