KVM backup error since migrate to 2.3

Hi Dietmar. Many thanks for your kind help.

I am affraid, I have just tried both ways but with no success :-(.

I started with:

Code:
qemu-img check /var/lib/vz/images/550/vm-550-disk-1.qcow2

But I got:

Code:
ERROR: cluster 211458634712447: copied flag must never be set for compressed clusters
Warning: cluster offset=0x120cce857f0000 is after the end of the image file, can't properly check refcounts.
ERROR: cluster 264071044498815: copied flag must never be set for compressed clusters
ERROR: invalid cluster offset=0x2bd4cd857f0000
ERROR: invalid cluster offset=0x2bd4cd85800000

4 errors were found on the image.
Data may be corrupted, or further writes to the image may corrupt it.

1 internal errors have occurred during the check.

An error has occurred during the check: Success
The check is not complete and may have missed error.

Secondly I tried:

Code:
qemu-img convert -p /var/lib/vz/images/550/vm-550-disk-1.qcow2 /var/lib/vz/images/550/vm-550-disk-1-NUEVO.qcow2

And I got:

Code:
qemu-img: error while reading sector 440401920: Input/output error

Again, at 30%.

How can I proceed?

Best regards.
 
Last edited:
Hi Dietmar,

I have just run:

qemu-img check -r all /var/lib/vz/images/550/vm-550-disk-1.qcow2

As a result, I got:

ERROR: cluster 211458634712447: copied flag must never be set for compressed clusters
Warning: cluster offset=0x120cce857f0000 is after the end of the image file, can't properly check refcounts.
ERROR: cluster 264071044498815: copied flag must never be set for compressed clusters
ERROR: invalid cluster offset=0x2bd4cd857f0000
ERROR: invalid cluster offset=0x2bd4cd85800000

4 errors were found on the image.
Data may be corrupted, or further writes to the image may corrupt it.

1 internal errors have occurred during the check.

An error has occurred during the check: Success
The check is not complete and may have missed error.

What else can I do?

Many thanks for your kind support.

Regards.
 
Hi Dietmar,

Last weekly successful backup was on 20-Apr-13, some days BEFORE I made the ProxMox upgrade to 2.3.

After reading your reply, I did a successful restore of such backup, under a different VMID (so the one in production is not at risk). Once it was restored and without starting it, I tried making a vzdump (from WUI) with no success. Stopping at 30% again.

Any advice or recommendation?
Thanks.
 
Hi m.ardito,

Are you meaning to:

- make a backup of the configuration/data files in my server
- build a new VM
- reinstall the Operating System (Linux in my case)
- reinstall the application (Zimbra in my case)
- restore the backup form step 1

Probably you are meaning something different more "ProxMox oriented". If it is the case, it is unclear to me how to make such "backup from insisde the vm"?

Many thanks to you both for your kind help.

Best regards.
 
hi!

no it was really a "last resort", because any action you do from pve side, the qcow file is involved. Before that qcow gets even more damaged, i would try a (rsync?) backup from inside the vm to an external (to the vm) folder, just in case... and of course if nothing else works, you still have the chance to re-create the vm from scratch and restore from the old-style backup... :-D

Marco
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!