Delta apply fail with "xdelta3: target window checksum mismatch: XD3_INVALID_INPUT"

General Discussions
6

Hi and thank you,

I’m using the branch zeus-next I’ve already verified that the partition n.5 and n.6 from the table below of the uefiimg, and they have the same SHA256 hash.

The hash of both partition is the same of the .mender artifact.

GUID Partition Table (EFI)
Offset Sector: 0
Units are in 512-byte sectors

      Slot      Start        End          Length       Description
000:  Meta      0000000000   0000000000   0000000001   Safety Table
001:  -------   0000000000   0000016383   0000016384   Unallocated
002:  Meta      0000000001   0000000001   0000000001   GPT Header
003:  Meta      0000000002   0000000033   0000000032   Partition Table
004:  000       0000016384   0000049151   0000032768   boot
005:  001       0000049152   0002113535   0002064384   primary
006:  002       0002113536   0004177919   0002064384   primary
007:  003       0004177920   0008388574   0004210655   primary
008:  -------   0008388575   0008388607   0000000033   Unallocated

➜  qemux86-64 git:(develop) dd if=image-qemux86-64.uefiimg  of=1 skip=49152 count=2064384
➜  qemux86-64 git:(develop) dd if=image-qemux86-64.uefiimg  of=2 skip=2113536 count=2064384

➜  qemux86-64 git:(develop) sha256sum 1 2
fcbcf3c9465b11e103067f954f502b981d4fd15566240d00d18277fead8f404f  1
fcbcf3c9465b11e103067f954f502b981d4fd15566240d00d18277fead8f404f  2

so, it’s not an issue with the building process of the image, but something is written at runtime before mounting in ro, i suspect someting systemd related.

Best,
Mauro