Page 1 of 1

OneDrive Chunk Errors

Posted: Sun Jan 09, 2022 2:36 pm
by pscanuck
Dealing with OneDrive Chunk Errors, preventing sync of large Files.
Small files syncing OK.
Re-Sync attempts result in a different Chunk Error number for the same large file.

Syncovery (Windows) purchased DEC2021.
Dataset being synced approx 900GB, (approx 46,500 files, 10,300 folders).
Current Syncovery version 9.44c, (since purchase Syncovery version has been upgraded two times).
Windows 10 (21H2) X64, Dataset on ReFS filesystem.
Internet provider bandwidth 50Mbits/s up, 10Mbits/s down.
Windows Task Manager, Network for Syncovery during sync, approx 8 Mbits/s.

Did some Testing/Troubleshooting as per attached file, (“Testing.zip”).

OneDrive Chunk errors available from provided Syncovery Log, [“LOG.zip”]

Any thoughts for solution to OneDrive Chunk Errors would be appreciated.

Re: OneDrive Chunk Errors

Posted: Sun Jan 09, 2022 3:49 pm
by tobias
Hello,
thanks, I am looking into it now.

Re: OneDrive Chunk Errors

Posted: Mon Jan 10, 2022 12:36 pm
by tobias
Hello,
I have made extensive tests and could not produce the problem.

It could be an intermittent server error, or a bug related to the combination of various settings.

In general for OneDrive you don't need to split files in small files of 250 MB each. Feel free to remove this splitting option on the Internet Protocol Settings dialog. It just adds an unnecessary additional complexity to the task.

If the error continues to happen, could you turn on Internet Protocol Logging on the Logs tab sheet of the Program Settings dialog and post these log files or send them to support@syncovery.com?

Re: OneDrive Chunk Errors

Posted: Mon Jan 10, 2022 1:36 pm
by pscanuck
Tobias:

As per your post feedback;
“It could be an intermittent server error, or a bug related to the combination of various settings.”
“turn on Internet Protocol Logging”.

Will pursue further Testing on my end, based on feedback.

Thanks for checking into this OneDrive Chunk Error issue.

Re: OneDrive Chunk Errors

Posted: Sat Jan 15, 2022 12:31 am
by tobias
Hello,
thanks for the logs, this has now been fixed in Syncovery 9.45a.