“check” command with the “-chunks” option fails

Support
, ,
#21

Agreed there are network timeouts but the occasional timeout is to be expected and there’s not much I can do about them anyway.

We’re getting a little off-topic here - my problem is still that I’m getting “missing chunks” errors, even after the token renewal is fixed and even in the absence of network problems.

2022-07-22 02:32:48.830 INFO VERIFY_PROGRESS Verified chunk 33f3fabf806a498ddb52e434328d061a40f770f6a9bc7f918521c0a4b1218d66 (1270/17329), 2.56MB/s 08:31:14 7.3%
2022-07-22 02:33:51.322 ERROR DOWNLOAD_CHUNK Chunk aa4ea15197db7efe6df402b24bc4a25d7157aed46b1c12183cc6af6a84511ce5 can't be found
2022-07-22 02:33:51.354 INFO SNAPSHOT_VERIFY Added 1270 chunks to the list of verified chunks
Chunk aa4ea15197db7efe6df402b24bc4a25d7157aed46b1c12183cc6af6a84511ce5 can't be found
#22

After more trials, I am cautiously concluding that the remaining problems may be caused by the (Windows 11) PC sleeping, or restarting after an update. That and restarting Duplicacy too quickly or running too many parallel tasks.

I have not found any firm evidence yet of network problems or problems at OneDrive or Wasabi (despite misleading error messages).

#23

I finally got a clean report! This means there were never any missing chunks in my case, and it’s probably possible to restore a large backup, which is very good news (not yet confirmed though).

Basically, moving the one-token.json file and preventing the computer from sleeping did the trick. It’s pretty fragile and there are lots of things that can cause problems and need to be avoided, such as using “parallel” mode, reordering checks, restarting the scan and lots of weird error messages, but it can be made to work.