Jump to content
Covecube Inc.
  • 0
Harri

Google Clouddrive producing lots of checksum mismatches

Question

Hi all,

since yesterday I have trouble using Clouddrive on one maschine

19:22:00.4: Warning: 0 : [ChecksumBlocksChunkIoImplementation:15] Expected checksum mismatch for chunk 439804651256, ChunkOffset=0x00600000, ExpectedChecksum=0xb25990f640cc5ab1, ComputedChecksum=0x44aa4b13478d1aa6.
19:22:07.7: Warning: 0 : [IoManager:64] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:07.9: Warning: 0 : [IoManager:54] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:08.1: Warning: 0 : [IoManager:64] [W] Error writing range: Offset=2.127.888.384. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted.
19:22:08.1: Warning: 0 : [IoManager:60] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:08.2: Warning: 0 : [IoManager:54] [W] Error writing range: Offset=2.121.793.536. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted.
19:22:08.3: Warning: 0 : [IoManager:60] [W] Error writing range: Offset=2.126.774.272. Length=4.096. Checksum mismatch. Data read from the provider has been corrupted.
19:22:09.4: Warning: 0 : [IoManager:58] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:09.6: Warning: 0 : [IoManager:58] [W] Error writing range: Offset=2.125.398.016. Length=212.992. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.2: Warning: 0 : [IoManager:57] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.4: Warning: 0 : [IoManager:57] [W] Error writing range: Offset=2.122.776.576. Length=327.680. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.4: Warning: 0 : [IoManager:66] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.6: Warning: 0 : [IoManager:66] [W] Error writing range: Offset=2.131.165.184. Length=110.592. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.8: Warning: 0 : [IoManager:71] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.8: Warning: 0 : [IoManager:65] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:10.9: Warning: 0 : [IoManager:65] [W] Error writing range: Offset=2.129.920.000. Length=69.632. Checksum mismatch. Data read from the provider has been corrupted.
19:22:11.1: Warning: 0 : [IoManager:71] [W] Error writing range: Offset=2.132.672.512. Length=655.360. Checksum mismatch. Data read from the provider has been corrupted.
19:22:11.1: Warning: 0 : [IoManager:15] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:11.3: Warning: 0 : [IoManager:15] [W] Error writing range: Offset=3.069.116.416. Length=69.632. Checksum mismatch. Data read from the provider has been corrupted.
19:22:11.3: Warning: 0 : [IoManager:42] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.
19:22:11.4: Warning: 0 : [IoManager:9] Error performing Write I/O operation on provider. Failed. Checksum mismatch. Data read from the provider has been corrupted.

 

Used version is 1.1.1.1131. Duplication is activated since the last update.

What can I do to repair the volume?

 

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Could you open a ticket at https://stablebit.com/Contact

Also, unfortunately, it may not be something that is fixable.  It looks like the data is corrupted.  But if you could run the StableBit Troubleshooter after opening the ticket, we'll see what we can do.

http://wiki.covecube.com/StableBit_Troubleshooter

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...