wrong vma extent header chechsum

[lordhanuman]

Hi all
during the restore i have this error
(process:1842): ERROR **: restore failed - wrong vma extent header chechsum
in dmesg i have this error
traps: vma[1842] trap int3 ip:7fc67848bd30 sp:7ffed72d2630 error:0

my storage is nfs

 

[lordhanuman]

the backup log it's ok but it's impossible to restore the backups... I have a big big problem...

 

[wolfgang]

Hi,
can you copy the backup file to you local storage and try again.

 

[lordhanuman]

same result
ihave tried to decompress
vma verify vzdump-qemu-102-2017_04_07-06_36_00.vma

** (process:5271): ERROR **: verify failed - wrong vma extent header chechsum

the backup logs i'ts ok


the problem is that they have taken a ransomware, I was calm because backups were ok and yet now I'm really in trouble

 

[wolfgang]

What you get if you call this programm?

vma verify <path to backup file.vma> -v

 

[lordhanuman]

vma verify vzdump-qemu-102-2017_04_07-06_36_00.vma -v

CFG: size: 327 name: qemu-server.conf
DEV: dev_id=1 size: 10737418240 devname: drive-virtio0
CTIME: Fri Apr 7 06:36:01 2017

** (process:10512): ERROR **: verify failed - wrong vma extent header chechsum
Trace/breakpoint trap

 

[wolfgang]

sorry to tell you but your Backup is corrupt.

the problem is that they have taken a ransomware, I was calm because backups were ok and yet now I'm really in trouble

The point is files can corrupt on many reasons like Network transfer problems, bit rot, fs corruption, ...

 

[lordhanuman]

ok great, but how can you tell me that the backup logo tell me "ok" when it is corrupt, the problem is that even the backup you were the day before yesterday have the same problem, so the log backup that ok it's not too reliable,

there is no way to force the extraction of files?

 

[tukiyo3]

see also:
https://forum.proxmox.com/threads/c...re-failed-wrong-vma-extent.33820/#post-166109