Akame

If the SSD is getting filled up a way would be to calculate depending how much space is left and how much it take to fill and lower it by that amount so it adjusts your speed so it doesn't get lower. As of now it just dismounts.

Have you tried going on amazon cloud drive online and seeing if you are banned? And also have you tried pressing reauthorize? The issue is probably the new query chunks method is being heavily throttled by Amazon. @drashna

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.

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

You will not be able to go on Google Drive to open an encrypted file but need to use the software, it will be like a regular file you can copy to your system or open directly in the drive depending how big your cache is. Cache is used to keep a copy of stuff you regularly access locally. 10 TB can be extended more depending how much you need, for example I set mine to 100 TB. And you can create new drives if you want for each type of data.

The size of the drive does not matter as you can just resize. I believe the reason for the size is that Windows would have issues if the space was unlimited and there is a max limit in Windows. When you create a drive it will mount itself as NTFS and you can read it just like a normal drive and the driver will handle the rest so it will be seamless.

For me streaming works if I do 20 download and upload threads, prefetching start 1 and prefetching stop 200 and keep it for 100 seconds. But it is smooth to stream but to go back and forward there is noticable delay.

I pressed y to dismount but chkdsk did not solve my issue, it made it worse infact and made the whole drive RAW so I wouldn't recommend it but it may work for you.

My stuff was RAW so the new update did not help me. This was my issue and resolution, http://community.covecube.com/index.php?/topic/2567-files-starting-to-go-corrupt-cloud-drive-throws-no-errors/?p=17786

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.

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

Hello does the latest beta fix it for you guys? http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.827_x64_BETA.exe Apparently you have to reset database in settings and reauthorize for api v3 to work. .827 * [issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [issue #27331] Rewrote volume name query code to not use VDS. .824 * [issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [issue #27342] Updated the Google Drive provider to use the v3 API. * [issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one..827 * [issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [issue #27331] Rewrote volume name query code to not use VDS. .824 * [issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [issue #27342] Updated the Google Drive provider to use the v3 API. * [issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one.

Hello does the latest beta fix it for you guys? http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.827_x64_BETA.exe Apparently you have to reset database in settings and reauthorize for api v3 to work. .827 * [issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [issue #27331] Rewrote volume name query code to not use VDS. .824 * [issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [issue #27342] Updated the Google Drive provider to use the v3 API. * [issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one..827 * [issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [issue #27331] Rewrote volume name query code to not use VDS. .824 * [issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [issue #27342] Updated the Google Drive provider to use the v3 API. * [issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one.

Hello does the latest beta fix it for you guys? http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.827_x64_BETA.exe Apparently you have to reset database in settings and reauthorize for api v3 to work. .827 * [Issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [Issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [Issue #27331] Rewrote volume name query code to not use VDS. .824 * [Issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [Issue #27342] Updated the Google Drive provider to use the v3 API. * [Issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [Issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one. .827 * [Issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [Issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [Issue #27331] Rewrote volume name query code to not use VDS. .824 * [Issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [Issue #27342] Updated the Google Drive provider to use the v3 API. * [Issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [Issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one.

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

I can say I've managed to restore my stuff, so apparently the new update or maybe two updates backwards added something called authorative chunk ids so there is only a metadata folder and nothing in chunkid folder. So I used the google business restore which allows you to restore permanently deleted items, data-chunkIdStorage is where the chunks where saved before it migrated over, luckily I had one from 31 the day the migration and the corruption started. Cache is at 0 B but afraid of a reboot at this point as moving pc made it unallocated. Moving files works and opening. Adding as well I think but I put it to read-only. 1: Updating to 819 made some folders corrupt as I could not access them. 2. I ran chkdsk and it detected errors 3. I ran chkdsk /r and it deleted index and fixed errors so cloud usage showed 6 GB at this point. 4. After several troubleshooting steps involving contacting google support they notified me if you go to google suite admin center and go to user you can press at three dot menu and press store, but you can only specify date and not what files to restore so you may end up with multiple chunks. As probably most know API deletes on CloudDrive deletes a file permanently which rendered our files unable to restore without going to google suite admin center, I think most has unlimited plan. 5. After restoring my fourth chunkid storage file from 31st it migrated into Metadata and as we know API does not manage versions when stablebit is editing them which proved to be a problem if I wanted whole drive restored, but when I was on my fifth file it managed to mount but still corruption errors. And the random file I tried CloudDrive deleted the chunkid file for the migration process and my clouddrive was 12.1 TB, even though some chunkid messed with my CONTENT folder and I may have multiple chunks that are different and I believe I may have corruption due to the steps involved I took the risk. At this point was my drive no longer unallocated and I was able to access any file and folder, calculated i may have around 80 MB corruption, so I transferred over the most important stuff and transferring less important now and it seems stable, remind me not to update versions as soon as it releases. I have been up all night and pretty tired writing this, admin can edit this to make it more readable if they want. But with that said StableBit CloudDrive is a good product which is in beta, I've had no issues with DrivePool. Also you may wanna wait on @Drashna before you do what I did due to the consequences involved.

If you enter some folders does it say corrupt? As the 819 update may not be related

I ran chkdsk /r and it changed my cloud usage to 6 GB from 11 TB but the chunks are still there, so I think Covecube needs to find a way how to search or readd them manually.

I think our data is lost due to the way MFT works if it is MFT it should be fairly hard to restore.

Same here, updated to 819, got some corrupt folders that wouldn't open so ran chkdsk /r and then it went RAW. My cloud usage went from 11.2 TB to 375 GB at the UI of the program. I can confirm the chunks are still at Google Drive provider but it seems it lost track of them. I ran testdisk http://www.cgsecurity.org/wiki/TestDiskwhich allows you to see files even though it's RAW. When you start testdisk.exe press Create for log file Pick the physicaldrive which has your clouddrive size. Pick EFI GPT, then go to advanced and press down button to press on the other bigger size and do LIST, when I do list I only see 375 GB of information which is worrying.