Jump to content

  • Log in with Twitter Log in with Windows Live Log In with Google      Sign In   
  • Create Account

Photo

Files starting to go corrupt, Cloud Drive throws no errors


  • Please log in to reply
53 replies to this topic

#21 Akame

Akame

    Member

  • Members
  • PipPip
  • 20 posts

Posted 02 February 2017 - 09:59 AM

That sounds pretty painful! Let's hope they can give us a quick easy fix for this via an update!

It was all trial and error, but yeah they should be able to provide a easier fix. I just panicked a bit. 



#22 triadcool

triadcool

    Advanced Member

  • Members
  • PipPipPip
  • 87 posts

Posted 04 February 2017 - 03:15 AM

Version 1.0.0.826 has fixed all of the corruption issues that I was having.



#23 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 04 February 2017 - 08:18 AM

Fixed it for all drives which had not gone RAW.

 

The one the went RAW seemed to have multiple chunks on the main chunks. So i just tried deleting the new versions (took a backup) and started reindexing all over to see if that would fix the issues and let it mount properly. I guess one of those chunks hold the MFT data and if it uploaded a new empty file, it would ofc. not be able to mount, because the fix loads the newest version == empty file.

 

Will report back if that fixes the issue with the RAW drive :)



#24 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 04 February 2017 - 11:09 AM

Fixed it for all drives which had not gone RAW.

 

The one the went RAW seemed to have multiple chunks on the main chunks. So i just tried deleting the new versions (took a backup) and started reindexing all over to see if that would fix the issues and let it mount properly. I guess one of those chunks hold the MFT data and if it uploaded a new empty file, it would ofc. not be able to mount, because the fix loads the newest version == empty file.

 

Will report back if that fixes the issue with the RAW drive :)

 

Deleting all the newest chunks when we had multiple chunks with the same key worked. drive now mounts properly! Before trying this make sure to backup the chunks so you can fix it again!

 

if you already indexed just restart the indexing procedure by resetting the settings and the database under troubleshooting -> reset settings as your index currently will be pointing to the wrong chunk where we had multiple



#25 Akame

Akame

    Member

  • Members
  • PipPip
  • 20 posts

Posted 04 February 2017 - 11:24 AM

Deleting all the newest chunks when we had multiple chunks with the same key worked. drive now mounts properly! Before trying this make sure to backup the chunks so you can fix it again!

 

if you already indexed just restart the indexing procedure by resetting the settings and the database under troubleshooting -> reset settings as your index currently will be pointing to the wrong chunk where we had multiple

 

Just curious my drive mounted but is this any issue? As I've had no issues so bit worried if deleting them will destroy my drive. They must of came back from my restore process when I fixed the chunkIDs and raw drive. 

 

CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:36] Multiple files (2) found for chunk 577910. Choosing first one. 2017-02-04 01:52:20Z 9897885844
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:25] Multiple files (2) found for chunk 137. Choosing first one. 2017-02-04 01:53:09Z 10038302772
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:41] Multiple files (2) found for chunk 137. Choosing first one. 2017-02-04 01:53:30Z 10098630653
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:33] Multiple files (2) found for chunk 133. Choosing first one. 2017-02-04 01:54:14Z 10221480929
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:33] Multiple files (2) found for chunk 133. Choosing first one. 2017-02-04 01:54:18Z 10234209721
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:41] Multiple files (2) found for chunk 219021. Choosing first one. 2017-02-04 01:54:19Z 10237928233
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:33] Multiple files (2) found for chunk 6. Choosing first one. 2017-02-04 01:54:23Z 10247725571
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:48] Multiple files (2) found for chunk 137. Choosing first one. 2017-02-04 01:54:23Z 10247844483
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:46] Multiple files (2) found for chunk 160. Choosing first one. 2017-02-04 01:54:23Z 10247887275
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:27] Multiple files (2) found for chunk 577910. Choosing first one. 2017-02-04 01:54:23Z 10247909988
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:52] Multiple files (2) found for chunk 133. Choosing first one. 2017-02-04 01:54:23Z 10248987571
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:33] Multiple files (2) found for chunk 6. Choosing first one. 2017-02-04 01:54:25Z 10254499991
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:41] Multiple files (2) found for chunk 219021. Choosing first one. 2017-02-04 01:54:27Z 10259745493
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:48] Multiple files (2) found for chunk 137. Choosing first one. 2017-02-04 01:54:28Z 10261123716
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:46] Multiple files (2) found for chunk 160. Choosing first one. 2017-02-04 01:54:28Z 10262252306
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:27] Multiple files (2) found for chunk 577910. Choosing first one. 2017-02-04 01:54:29Z 10266083381
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:3] Multiple files (2) found for chunk 45398. Choosing first one. 2017-02-04 01:56:09Z 10549383981
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:24] Multiple files (2) found for chunk 45398. Choosing first one. 2017-02-04 01:56:30Z 10609982457
CloudDrive.Service.exe Warning 0 [ChunkIdSQLiteStorage:39] Multiple files (2) found for chunk 45398. Choosing first one. 2017-02-04 01:56:39Z 10633779392


#26 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 04 February 2017 - 11:33 AM

As long as you backup chunks it should be possible to revert back by uploading then again and reindexing :-)

 

I chose to go for the older ones, as i knew ihad not done any changes since the updates where they were made. so i trusted the old data more than the new, as the new potentially could have faulty data - this was also why my drive went RAW as i had multiple chunks on the chunk which contained the MFT data - the new one was corrupt, the old just fine


  • Akame likes this

#27 lazers

lazers

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 04 February 2017 - 01:54 PM

Deleting all the newest chunks when we had multiple chunks with the same key worked. drive now mounts properly! Before trying this make sure to backup the chunks so you can fix it again!

 

if you already indexed just restart the indexing procedure by resetting the settings and the database under troubleshooting -> reset settings as your index currently will be pointing to the wrong chunk where we had multiple

 

I'm sorry I think I'm being slow.. What chunks are you deleting?

 

My drive is still RAW, the CONTENT folder is full of chunks, the ChunkIdStorage is empty. I'm not an admin on my google drive, so I can't restore anything deleted but looks like I can roll back individual files a day or two. Is there any hope?



#28 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 04 February 2017 - 04:45 PM

go to technical overview and look at the service log.

 

you will get a warning about multiple chunks with the same id and the number it has: search for this on the drive and you should find two chunks. Download the newest (for backup) and then delete it afterwards. do this for all the chunks which have duplicates.

 

after you finish go to troubleshooting - > reset settings and include the databases.

 

reboot and start :-) should mount fine now! if not then reupæoad all the chunks you dowbloaded and make a ticket with stablebit



#29 lazers

lazers

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 04 February 2017 - 06:17 PM

Thanks Steffen!

 

Found one chunk that had 3 versions, deleted the two newest ones, reset settings and db and rebooted. Still RAW :\

 

I'll make a ticket and keep my fingers crossed ;)



#30 CalvinNL

CalvinNL

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 04 February 2017 - 07:32 PM

Thanks Steffen!

 

Found one chunk that had 3 versions, deleted the two newest ones, reset settings and db and rebooted. Still RAW :\

 

I'll make a ticket and keep my fingers crossed ;)

 

Same issue here, I responded to my original ticket.



#31 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 04 February 2017 - 08:23 PM

Sorry my fix didn't work for you :-(

#32 Akame

Akame

    Member

  • Members
  • PipPip
  • 20 posts

Posted 04 February 2017 - 09:52 PM

I think using the original ChunkIDs can fix the drive, but i would suspect waiting for developer to help you as modifying files could potentially start a chain reaction wiping everything, I am probably gonna remake my drive as I am not sure how corrupt this one is and would be better as I know it's clean. 



#33 KiLLeRRaT

KiLLeRRaT

    Member

  • Members
  • PipPip
  • 23 posts

Posted 07 February 2017 - 12:43 AM

Any update on this yet? I'm still stuck without my files :(



#34 lazers

lazers

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 07 February 2017 - 06:16 PM

Tried running chkdsk, it found errors, and chkdsk /f exited with "insufficient disk space to insert the index entry."

 

I've made a new cloud drive and am uploading stuff again, thankfully only had about 5 TB on the drive that went RAW..



#35 KiLLeRRaT

KiLLeRRaT

    Member

  • Members
  • PipPip
  • 23 posts

Posted 08 February 2017 - 08:37 AM

Is there a way to have the application automatically discard the duplicate chunks that were made after a certain date? Or automatically keep/use the oldest file if it finds duplicates? That may fix my problem, then I can just restore my Google drive to say the 28th of Jan or something, and voila?



#36 Akame

Akame

    Member

  • Members
  • PipPip
  • 20 posts

Posted 09 February 2017 - 09:19 PM

Is there a way to have the application automatically discard the duplicate chunks that were made after a certain date? Or automatically keep/use the oldest file if it finds duplicates? That may fix my problem, then I can just restore my Google drive to say the 28th of Jan or something, and voila?

Apparently the new beta has the ability to combine chunks into one, did that one fix it for you?



#37 KiLLeRRaT

KiLLeRRaT

    Member

  • Members
  • PipPip
  • 23 posts

Posted 09 February 2017 - 09:56 PM

Apparently the new beta has the ability to combine chunks into one, did that one fix it for you?

 

I think my drive is too far poked. I tried it but it remained RAW.

 

I was part way through a backup to another cloud drive.  That one recovered fine, but I'm now missing a load of stuff that wasn't backed up.

 

I wonder if it's a good idea to create a full backup of your drives, and detaching them, then maybe once a while, connect it, and sync it.  Like a backup, although it will be on the same provider... But it'd mitigate these issues. 



#38 Akame

Akame

    Member

  • Members
  • PipPip
  • 20 posts

Posted 09 February 2017 - 10:43 PM

I think my drive is too far poked. I tried it but it remained RAW.

 

I was part way through a backup to another cloud drive.  That one recovered fine, but I'm now missing a load of stuff that wasn't backed up.

 

I wonder if it's a good idea to create a full backup of your drives, and detaching them, then maybe once a while, connect it, and sync it.  Like a backup, although it will be on the same provider... But it'd mitigate these issues. 

I guess you could use another utility to copy the chunks to a backup folder once a month. It will not take any client side bandwidth as google drive supports server side moving. One utility that can be used together with drivepool is rclone as it supports server-side moving. 



#39 KiLLeRRaT

KiLLeRRaT

    Member

  • Members
  • PipPip
  • 23 posts

Posted 09 February 2017 - 10:44 PM

I guess you could use another utility to copy the chunks to a backup folder once a month. It will not take any client side bandwidth as google drive supports server side moving. One utility that can be used together with drivepool is rclone as it supports server-side moving. 

 

Ah that's a good idea, I will check that out :D



#40 Christopher (Drashna)

Christopher (Drashna)

    Customer and Technical Support

  • Administrators
  • 8,208 posts
  • LocationSan Diego, CA, USA

Posted 11 February 2017 - 01:00 AM

For anyone still having issues, please upgrade to the latest version.  

 

There is some code there that may recover the data, and return your drive to a usable state. 

 

http://dl.covecube.c...34_x64_BETA.exe


Christopher Courtney

aka "Drashna"

Microsoft MVP for Windows Home Server 2009-2012

Lead Moderator for We Got Served

Moderator for Home Server Show

 

This is my server

 

Lots of "Other" data on your pool? Read about what it is here.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users