Trying to restore from a backup and I keep getting an error

Firecracker048

New Member
Apr 12, 2024
10
0
1
Good Morning,
So recently I had to reinstall proxmox on a new SSD after the last one shit the bed. I tried to clone the drive directly but the MBR was the sector that was broken, so the cloning failed.

After doing a fresh install ive tried to restore from backups and I keep getting this error:
_25-15_16_26.vma.zst : Decoding error (36) : Restored data doesn't match checksum
vma: restore failed - short vma extent (1415168 < 1446400)

Ive tried 3 restores now, and the first two gave me error 133. Now on the 3rd try I get the above error. What is the issue?

Edit: So at the end I did get error 133 again. Here is the full output:
_25-15_16_26.vma.zst : Decoding error (36) : Restored data doesn't match checksum
vma: restore failed - short vma extent (1415168 < 1446400)
/bin/bash: line 1: 107547 Exit 1 zstd -q -d -c /mnt/pve/Backup/dump/vzdump-qemu-155-2024_11_25-15_16_26.vma.zst
107548 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp107536.fifo - /var/tmp/vzdumptmp107536
Logical volume "vm-155-disk-1" successfully removed.
temporary volume 'local-lvm:vm-155-disk-1' successfully removed
Logical volume "vm-155-disk-0" successfully removed.
temporary volume 'local-lvm:vm-155-disk-0' successfully removed
Logical volume "vm-155-disk-2" successfully removed.
temporary volume 'local-lvm:vm-155-disk-2' 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 155 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/Backup/dump/vzdump-qemu-155-2024_11_25-15_16_26.vma.zst | vma extract -v -r /var/tmp/vzdumptmp107536.fifo - /var/tmp/vzdumptmp107536' failed: exit code 133
 
Last edited:
Sounds like the backup(s) might be corrupt. Describe the backing storage on the system that houses the backups; also could be a RAM issue, are you using ECC?
 
Sounds like the backup(s) might be corrupt. Describe the backing storage on the system that houses the backups; also could be a RAM issue, are you using ECC?
Backup storage is an SMB file share to my personal PC that is a HDD.

Server uses ECC, personal PC does not
 
Last edited:
Try running a chkdsk and a SMART long test on the Windows box

Also check your powered-on hours with Crystal Disk or similar, most HDs are only warrantied for 3-5 years. Might be less if it's a lightweight WD "blue" drive or similar desktop-class. If uptime is near/past ~43000 hours then it might need replacing

For future backups, might be worth build a small ZFS server with at least a mirror, so you get self-healing scrubs.