Full backup restore error: Stream_vdi.Invalid_checksum
- 
 @RS Few years ago I faced the same errors on all xva backups and after that switch to vdi backups. 
 I did not find the root of problem, but I know how to "repair" broken backup.Check xva backup with command vhd-util check -n name_of_backup.xva.
 If you got something like Checksum : 0x0|0xffffffff (Bad!), the solution is:- Create VM or get server with modern Ubuntu. You will need x3 space of your backup size.
- Copy broken backup
- Install xva-img https://github.com/eriklax/xva-img
 apt-get install libssl-dev g++ cmake add-apt-repository ppa:ubuntu-toolchain-r/test && apt-get update && apt-get install -y gcc-7 #To compile execute following commands in xva-img folder cmake ./ make install- Unpack backup
 mkdir my-virtual-machine tar -xf name_of_backup.xva.xva -C my-virtual-machine chmod -R 755 my-virtual-machine- Create RAW disk. Replace Ref\:1 with your digits
 xva-img -p disk-export my-virtual-machine/Ref\:1/ disk.raw- Install qemu-utils from standard repos apt install qemu-utils
- Convert RAW to VHD qemu-img convert -f raw -O vpc disk.raw resotred.vhd
- Copy VHD to xcp-ng SR cp resotred.vhd /run/sr-mount/{sr-uuid}/
- Get UUID of your restored VHD. This command should be executed on xcp-ng server. vhd-util read -p -n resotred.vhd
- Rename vhd
- Rescan SR, rename VHD with empty name
 
- 
 @splastunov said in Full backup restore error: Stream_vdi.Invalid_checksum: vhd-util check -n I try all backups, and all backups looks corrupted. I dont have problem re-create all backups again, but now is main problem I cannot use XO for backup because every next backup is bad. About some month ago, all works. 
- 
 @RS sorry, I have no idea how to fix it 
- 
 @Danp I try diferent SMB repository, but with same result. 
- 
 @RS Are you able to replicate this problem using XOA? 
- 
 @Danp said in Full backup restore error: Stream_vdi.Invalid_checksum: Are you able to replicate this problem using XOA I dont use XOA, I only try re-create new installation on new VM but with same result too. 
- 
 @RS Deploy an instance of XOA and start a trial. Then use this to test if you can replicate this issue. This will help determine if it is an issue with your build environment or a larger issue affecting XOA. 
- 
 @Danp I try XOA in trial mode and backup/restore works, so problem is probably in our build 
- 
 @RS There's no source "versions", just latest commit must be used. Please see https://xen-orchestra.com/docs/community.html#report-a-bug If you want to test, deploy an XOA and see if it works better, that might help to rule out a build issue or the fact you are not on the last commit. 
- 
 @olivierlambert I test XOA - works. I try build from source - Ubuntu 22.04.4 - not work, Ubuntu 24.04 - not work, Rocky linux v9.4 - works. 
 So problem is only on Ubuntu, I can re-install Xo server to new server and stay on Rocky Linux v9
- 
 Yes, you can always export/import the config on a working install. So it's a problem on your build, it's really hard to tell where's the culprit (because you built it, you see why we distribute it via XOA for production/professional usage  ) )


