[Checksum Mismatch....What do I do?]

Not currently. 

 

Ironically, running a CHKDSK pass or surface scan (via StableBit Scanner) would allow you identify the affected sectors.

 

The problem is that this isn't a specific "file" (well, a file on the provider, but not "on the disk"). It is a range, and it may be a part of a single file, or it could be multiple files.

 

Additionally, you can disable "checksum verification" on the drive to force StableBit CloudDrive to use the file, regardless of it's status (if you want to run CHKDSK, you'd want to do this first). 

 

Are there any plans to implement a feature to make it easier to identify which files or multiple files are effected by a corrupt chunk? Because running a complete surface scan needs a lot of time and bandwidth.

 

The log shows the chunk number of the corrupt chunk and cloud drive should know what is stored in this chunk. So a simple input box for the chunk number and a popup with the file-/foldernames stored inside the chunk is all I need.

[Checksum Mismatch....What do I do?]

Does this show up in the UI?

 

If not, then it was likely handled and isn't an issue.

 

however, if this is showing up in the UI, then that is different.

 

Yes, I saw it first in the UI and searched in the logfiles for more information about the error.

 

I hope to fix the checksum mismatch with a reupload of the file.

 

Is there a easy and fast way to identify the file?

[Checksum Mismatch....What do I do?]

Hi, I have a checksum mismatch error in my logfile, is it possible to tell what file is stored in this chunk? 

 

 

Log:

CloudDrive.Service.exe Warning 0 [ChecksumBlocksChunkIoImplementation:86] Checksum mismatch for chunk xxxxxx