Glad to hear you resolved your hash mismatch error, I went ahead and flagged your post about running repair as the solutoin.
Note that @ts678 is correct that a test restore of some files the use the duplicati-ba144e47ab35b40beab74611f9130d454.dblock.zip.aes file would be a good confirmation.
The database Repair command MOSTLY resyncs local database information with the destination, which might (as in your case) be storing the new hash from the destination into the database or it could go the opposite way of using the database to recreate a missing dlist or dindex file.
Unfortunately, dblock files themselves can’t be recreated which is why the expert (actually, primary developer) post he linked to two message ago suggested purging the bad file.
If you don’t feel like running affected to see what files / versions could be restored to test that dblock you could also try running a full test (see link below) or just wait until Duplicati (eventually) randomly tests that particular file.
No matter what you choose, just note that Duplicati will restore what it can, even from mangled destination files.