Failed to download the chunk

I have read through similar issues on the forum, but I can’t figure out how to resolve the issue. I started getting the “failed to download the chunk” messages a few days ago when running the prune command. Below is what I get when running the check -a command. Just about every command I run returns the “failed to download…” message. Any ideas where I should go from here?


Storage set to b2://***

Listing all chunks

All chunks referenced by snapshot Mitchells-MBP-mitchellspille-mitchellspille at revision 1 exist

All chunks referenced by snapshot Mitchells-MBP-mitchellspille-mitchellspille at revision 2 exist

All chunks referenced by snapshot dennis-external at revision 3 exist

All chunks referenced by snapshot dennis-external at revision 4 exist

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

URL request 'https://f001.backblazeb2.com/file/DGS-Computers/chunks/63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff.fsl' returned status code 404

Failed to download the chunk 63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff: Maximum backoff reached```

Do you see the missing chunk in any of the prune logs located in .duplicacy/logs/ on the computer that ran the prune command? For example, using

grep "63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff" /path/to/.duplicacy/logs/*
1 Like

Another basic check: is this file in B2 (inside the chunks folder)?

1 Like

Shouldn’t the chunk 63071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff actually be
...\chunks\63\071f20a157430f143f0bbabbd5d9a4c4007754b2eef3f948c368aa422a60ff ?

so basically the chunk is in the folder named 63 and it starts with 071f.....?

I think this was the standard for all storages after 2.1.0.

1 Like

@Dennis are you running the latest version 2.1.2?

1 Like

Looks like I’m running v2.1.0.

I confirmed that the file exists in B2 in the chunks folder, and my B2 file structure is not the ...\chunks\63\##### format. It’s the flat format, i.e. I have 250 pages of chunk files on the B2 site.

In that case just update to latest version from http://duplicacy.com/ and you should be good to go.

1 Like

The update helped, but I still had a missing chunk. I went ahead and deleted from B2 the revision that contained it, did a prune -exhaustive -exclusive, and things seem to be working well once again. Thanks all for the assistance.

2 Likes

For anyone: Feel free to use the :heart: button on the posts that you found useful.

For the OP of any support topic: you can mark the post that solved your issue by ticking the image box under the post. That of course may include your own post :slight_smile:

1 Like