steffenmand

You can always follow the changes in the beta here: http://dl.covecube.com/CloudDriveWindows/beta/download/changes.txt I always use it to see if an update was needed from my side Beta's can ofc. be found at http://dl.covecube.com/CloudDriveWindows/beta/download/

Try the newest version: http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.1.2.1174_x64_BETA.exe It should fix the issues

Depending on the sector size when creating, you should be able to expand with no issues. Try going into the hard drive partitions settings in windows and expand the drive there - maybe its just sitting as an unpartitioned part of the drive which just needs to be extended to the current You will never be able to go above your sector size limit though Recommend never going above 50 TB, so chkdsk will always work. Above that it will fail. Then its better to do two different drives

Maybe this could be a slow process taking maybe maximum of 100 GB per day or something (maybe a limit you set yourself, where you showcase it would take ~X amount days to finish), with a progress overview. Having maybe 50 TB would be a huge pain to migrate manually, while i would be OK with just waiting months for it to finish properly - ofc. knowing the risk that data could be lost meanwhile as its not duplicated yet Would also make it possible to decide to change to duplication later on instead of having to choose early on with Google Drive it does limit the upload per day, so could be nicer to upload first and then duplicate later when you are not uploading anymore Another good feature could also just be an overview of how much you uploaded/downloaded from a drive in a single day - could be great to monitor how close you are to the upload limit on google drive drives

Save as PDF and just cancel

I got a dedicated SSD for my cache, maybe that is why i never encountered it. Maybe your SSD's hit their max IOPS due to the OS and more stuff also running there?

you could try testdrive

usually it would continue or throw an actual error. I always see that one you see in the middle

Does it throw an error when it ends ? Insufficient space is expected.

try chkdsk e: /f instead /r is recover and search for bad sectors

I got 19 drives on 5 accounts and no issues at all - im at 10 download threads and 12 upload threads and 20 MB chunks with limited throttling My guess is something in your system is causing it

No, but using multiple accounts you could in theory increase speeds, while also ensure stability by using multiple providers

It's not because it is marked as Offline? Did CloudDrive give a notice that it couldn't assign the drive letter?

Did you create your drive with 20 MB chunks ? If not you should do that and also increase the minimal download size to 20 MB. If its currently at 1 MB you get limited by the thread count and response times for retrieving 1 MB / Thread

My disc only lost reference to the files - recovery programs could find them all. So i think your first fix shouldve solved it as im certain its because an old chunk with data indexing was retrieved! Nice with the data duplication though. Quick question - does drivepool make it possible to "raid" different google drive accounts into 1 for less throttling and better speeds ? - If not this could be a nice request for either stablebit or drivepool as it could help in many ways also regarding data safety. So pretty much building a raid based on drive accounts