Duplicacy check reports missing chunk

running
duplicacy_win_x64_2.7.2.exe -log check -chunks -threads 32 -a -fossils -resurrect -persist

reports a missing chunk, but all snapshots and all their revisions are reported OK.
Now I wonder where this chunk belongs to and what might be broken?

Is there any way to dig in deeper ?
Ideas are welcome :slight_smile:
juergen

duplicacy_win_x64_2.7.2.exe -log check -chunks -threads 32 -a -fossils -resurrect
2022-05-22 13:44:57.768 INFO STORAGE_SET Storage set to D:/backup-storage/local_02
2022-05-22 13:44:57.770 INFO SNAPSHOT_CHECK Listing all chunks
2022-05-22 13:45:04.023 INFO SNAPSHOT_CHECK 11 snapshots and 1494 revisions
2022-05-22 13:45:04.029 INFO SNAPSHOT_CHECK Total chunk size is 1619G in 351394 chunks

> 2022-05-22 13:51:16.951 INFO SNAPSHOT_VERIFY Verifying 351394 chunks
> 2022-05-22 13:51:17.304 ERROR DOWNLOAD_CHUNK Chunk fa4e94b95a28df9a762ccf2dd9d5c5667f39fcda65f64226c691b9f57abf1689 can't be found


Run Duplicacy with the -v flag - perhaps even the -d flag - although it may already indicate in the log what revision it was having trouble with, in the preceding log entry, particularly if it was a metadata chunk.

Also, you’re running all the flags under the sun - start without -chunks, -fossils, -resurrect, and -persist and deal with each error as they come. It’ll also be quicker.

Maybe add -fossils in later and only when there’s missing chunks, add in -resurrect. When everything looks good at that point, do a final -chunks check. Just do the basic check first with -v would be my initial recommendation.

You may want to delete your local cache directory (under .duplicacy) beforehand.