I have taken a look at this, it’s a complicated problem. 2 things I noticed:
- quite a lot of deleted blocks, so there is a lot of purging in this system
- the damaged block concerns a ‘block of block’, that is, a block containing hashes of other blocks - this happens for big files, and it concerns a particular file whose exact name I can’t tell you (obviously) but it is like this:
sqlite> select path, length from fixedfile join blockset on (blockset.id = fixedfile.blocksetid) where blocksetid in (1857582,1959476,2374472,2387775,2396715,2400383,2415547,2423463,2430949,2436523,2442908,2450029,2456499);
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
X:\106\506440.bin|1920401408
and the dates vary from 2023-08-20 04:51:35 to 2023-10-26 04:54:35.
I don’t know if you can identify the real file from the size, the dates and the apparent location.
If yes, maybe deleting it from the backup could fix it.