recovery faulty vma backup

[sanyi1977]

Hello everyone!


There is a small problem related to restoring a VM.
Namely, that a VM Sector defective hard drive was saved in. In one place it has an error of about 2 megabytes. Backup 250GB, 350 GB unpacked. Includes a 4GB, a 273GB sizes, a 146GB sizes, as well as a 36GB size image. The defective hard drive utility ddrescue saved to another hard disk in compressed backups, then gzrecovery utility unpacked. VMA VMA proxmox tried the file format utility to extract the image. The 4GB and 273GB disk image files ether was successful, but the following file size 146GB stopped expand a program error.
Is it possible that the VMA utility cross the defective parts of the file, or other ideas to expand the file to the VMAs last 36GB probably a good image?

ps.:
sorry my little english, I hope you understand what I wrote

 

[sanyi1977]

vma verify vzdump-qemu-110-2014-11-16-2053.vma.recovered -v
CFG: size: 683 name: qemu-server.conf
DEV: dev_id=1 size: 4294967296 devname: drive-virtio0
DEV: dev_id=2 size: 294205259776 devname: drive-virtio1
DEV: dev_id=3 size: 147102629888 devname: drive-virtio2
DEV: dev_id=4 size: 36507222016 devname: drive-virtio3
CTIME: Sun Nov 16 20:53:59 2014
progress 1% (read 4821155840 bytes, duration 9 sec)
progress 2% (read 9642246144 bytes, duration 28 sec)
.
.
.
progress 79% (read 380866985984 bytes, duration 2370 sec)
progress 80% (read 385688076288 bytes, duration 2394 sec)


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

 

[dietmar]

Technically, it would be possible to skip those bad extents. But the current vma utility does not have such feature (someone would need to implement that).