Over the weekend I blew away two Proxmox hosts (clustered) and reinstalled the hypervisors from scratch (two single nodes). Because I had backups of everything, I thought I'd be fine to just restore the backup files and continue working.
The hosts have multiple backups of most containers/VM's that were on these machines (stored on NFS via network). The containers restored normally, however not a single VM file was recoverable on the new hosts. In the past I have restored VM's and containers to the original hosts, just not the new ones.
I've tried everything and am at my wit's end. This is entirely unacceptable...what is the point of making backups if they are totally unusable? I have looked to this forum for advice, and most of the posts seem to be saying the files are just corrupted and totally useless. I have tried unzipping manually, it still gave me the same error:
** (process:7029): ERROR **: restore failed - wrong vma extent header chechsum
This error has been reported for at least a year, with still no fix in production, as far as I can see. Even with entire distribution upgrades!
Needless to say I am very frustrated and disappointed - I feel as though there was absolutely no purpose in even backing up my VM's in the first place!
If I am incorrect and these VM's are easily recoverable, someone please let me know. I do apologize if this comes off in a nasty way, but in this situation, all VM data appears lost because of the failed checksum, and this has been a known issue for years, which has not been fixed. I hope someone proves me wrong, because I love the platform, but this is kind of a dealbreaker if it can't be fixed....
[EDIT 1:]
As suggested, I attempted upgrading to a test version, rebooting the host, and restoring again. This did not make a difference.
https://forum.proxmox.com/threads/c...re-failed-wrong-vma-extent.33820/#post-166109
[UPDATE:]
I was now able to restore 2 of my ~10 machines. However the rest still give me the same "chechsum" error. I am not sure what certain users mean by "unreliable" storage; the NFS is on a FreeNAS server and I am not sure how these specific files (only for VM's on Proxmox) would have been the only files affected on the whole RAID drive for that server. I guess it's possible, but it really seems like there would be more than exclusively VM files being affected were that to be the case..
I have also used the backup/restore feature many times in the past without issue. My main concern is that somehow they were linked to the original host/cluster, as I was able to restore (even some of the same files) multiple times until I reinstalled Proxmox.
The hosts have multiple backups of most containers/VM's that were on these machines (stored on NFS via network). The containers restored normally, however not a single VM file was recoverable on the new hosts. In the past I have restored VM's and containers to the original hosts, just not the new ones.
I've tried everything and am at my wit's end. This is entirely unacceptable...what is the point of making backups if they are totally unusable? I have looked to this forum for advice, and most of the posts seem to be saying the files are just corrupted and totally useless. I have tried unzipping manually, it still gave me the same error:
** (process:7029): ERROR **: restore failed - wrong vma extent header chechsum
This error has been reported for at least a year, with still no fix in production, as far as I can see. Even with entire distribution upgrades!
Needless to say I am very frustrated and disappointed - I feel as though there was absolutely no purpose in even backing up my VM's in the first place!
If I am incorrect and these VM's are easily recoverable, someone please let me know. I do apologize if this comes off in a nasty way, but in this situation, all VM data appears lost because of the failed checksum, and this has been a known issue for years, which has not been fixed. I hope someone proves me wrong, because I love the platform, but this is kind of a dealbreaker if it can't be fixed....
[EDIT 1:]
As suggested, I attempted upgrading to a test version, rebooting the host, and restoring again. This did not make a difference.
https://forum.proxmox.com/threads/c...re-failed-wrong-vma-extent.33820/#post-166109
[UPDATE:]
I was now able to restore 2 of my ~10 machines. However the rest still give me the same "chechsum" error. I am not sure what certain users mean by "unreliable" storage; the NFS is on a FreeNAS server and I am not sure how these specific files (only for VM's on Proxmox) would have been the only files affected on the whole RAID drive for that server. I guess it's possible, but it really seems like there would be more than exclusively VM files being affected were that to be the case..
I have also used the backup/restore feature many times in the past without issue. My main concern is that somehow they were linked to the original host/cluster, as I was able to restore (even some of the same files) multiple times until I reinstalled Proxmox.
Last edited:
