triadcool

Has anybody tested version .597 yet? It looks like there were quite a few changes made. If you have, is the concurrent stream issue any better?

In your Google Drive do a search for the words CONTENT, ATTACHMENT, METADATA and delete the folders that appear. This will delete the files from your drive. You will most likely need to remove them from the trash afterwords. EDIT: Only do this if you have no other Stablebit Clouddrives created. If you do, you will need to match up the names of the folders with what is shown in the Hidden Stablebit Cache folder on your windows computer.

The multiple concurrent stream issue is one of the issues that I was experiencing before, that I was hoping this update would resolve.

I haven't tested it yet, but I am glad to see that the minimum download size issue has been resolved in version .593. (* When minimum read size is enabled, avoid downloading the same range of data multiple times.)

Upload scheduling would be a pretty useful feature. Good idea modplan.

Yes, any update (good or bad) would be greatly appreciated.

Kraevin, Do you have more than one Stablebit Clouddrive on Google running at a time? I believe there is a 20 thread limit for Google as a provider and if you have more than one clouddrive running and have each drive set to use more then 10 threads, than you would get the userRateLimitExceeded error. I would also like to hear from Christopher to address some of these issues.

Christopher, is this issue being looked into?

There does seem to be an issue with the minimum chunk size. 1. I started a file transfer from stablebit clouddrive to a local disk on my server with 20MB chunks and no minimum chunk size. Stablebit was using all 15 threads that I assigned and said that the file was downloading at roughly 60Mb/s. I monitored the actual speed of the file transfer and it was downloading at an average of 6 MB/s which is about right. 2. I then started this same exact test, but this time I used 20MB minimum chunks with the 20MB chunks. Stablebit was using all 15 threads and was reporting that it was downloading the file at 400Mb/s. I monitored the actual speed of the file transfer and it was downloading at the same 6 MB/s speed as before I enabled the minimum chunk size even though stablebit thought that it was downloading faster. You can easily test this yourself by doing the same steps that I took above. Note: I monitored the transfer speed with both Ultracopier and Windows built in file copy. The transfers were to a very fast ssd.

There is a definite issue with this latest release. I am getting great speeds with it but it seems that it can't handle doing more than one thing at a time.

Do you have any sync services setup on your cloud drive such as cloudhq.net that could be deleting these chunks? I have 40TB + uploaded to Google Drive using Stablebit and haven't had any chunks randomly deleted like this.

Would a cloud backup service like Backupify work with Stablebit Cloud Drives way of storing the data? If I knew a date in which cloud drive data was corrupted or lost and went in to Backupify and restored the files to how they were on that date do you know if Stablebit would be able to work with this recovered data? I'm just looking at possible options to backing up data that is contained in Stablebit.

I created a new drive using the latest verison 1.0.0.463 and got about 500GB uploaded to it and now i'm getting the same mime error. Back to square one. This scares the crap out of me to even use stablebit cloud drive even when it does come out of beta. One thing goes wrong and you lose all data that is in a proprietary format. I may need to stick with my old process of using netdrive and boxcryptor. Unfortunately I already paid for the program. EDIT: The data is sitting there in chunks on my google drive. It would be really nice if there was something implemented where if a major failure happened, we could somehow import the chunked data in to a new drive. It doesn't make a whole lot of since that you lose all of your data just because an error in the software when all of the data is still there.

I am running Windows Server 2012 R2 64bit. The issue came up when I was on Cloud Drive version 1.0.0.454 and is still occurring after updating to version 1.0.0.463. I get the option to unlock the drive and after I type in my encryption key the drive tries to mount then fails. I have uploaded the logs as requested on your support upload page. Here is what it looks like after I Unlock it with my Encryption Key. Here is what it looks like after about 30 seconds

I started getting the mime error so I restarted my server and now stablebit asks for my encryption key then says recovering then goes to the normal stablebit screen where you can create a new drive. Can you please assist me in trying to get this drive to mount again? I have over 10TB on this drive and would really like to be able to recover it. Thanks.

I reauthorized the drive with Google and it took the quota limit off!!!! If you guys run in to the issue this may be a quick workaround.

Unfortunately I just received my first ever Quota error and can no longer use the drive. Error: The download quota for this file has been exceeded. This error has occurred 46 times. Make sure that you are connected to the Internet and have sufficient bandwidth available. How long does this error last?

The newest update version: 1.0.0.454 is fantastic. I am now getting great download speeds with it. Thank You.

Is there a way to have the cache automatically clear itself nightly or something? I use this with Plex and have a 80GB ssd that I use for my cache drive and it fills up after a day or two. After it fills up plex starts buffering on the videos really bad until I manually clear the cache. This issue happens much faster when transferring files to the cloud drive. It would be nice if I could set it so files that are being copied to the cloud drive are not cached. I have experimented with running the drive without a cache and it seems to work alright but I just don't know what prefetch time window settings I should use so prefetched data isn't removed before plex has a chance to read it. P.S. I'm really looking forward to the larger chunk download sizes. That will really help out the plex streams.

I have been experiencing the same thing. When copying a large amount of data to the Google CloudDrive the "To Upload" field lags behind what is being copied to the cache and almost nothing will upload or download from the clouddrive until the "To Upload" field catches up after all of the files are copied to the cache. If I pause a file transfer half way through, I can see the "To Upload" working on catching up to where it should be for a few minutes then the upload starts up again. If I resume the transfer again, almost all upload and download activity stops until the "To Upload" catches up. I am running Windows Server 2012 with Stablebit CloudDrive version 1.0.0.422 100MB Chunks 1Gbit Connection

When I transfer large amounts of data (50GB+) to my Google Stablebit CloudDrive I am not able to read any data on the cloud drive until the transfer is fully complete. Is this normal? I have plenty of space on my cache drive and plenty of bandwidth to spare. The data stored on the clouddrive is accessed frequently and makes it so that I have to plan to do file transfers late at night when not being used.

I get the same error when trying to do a bare metal backup of my windows server 2012 system.

I am experiencing the slow 20 second startups using Stablebit Clouddrive with Google Drive so it doesn't seem to be a Amazon issue.

I am wondering if the 20 second delay to start playing a file in plex is something that can possibly be reduced with future developments to Stablebit Clouddrive? I know Netdrive works completely different but it can usually start a stream via plex in about 5 seconds for me.

My current settings are as follows: Download Threads: 30 Upload Threads: 5 Prefetch trigger: 1MB Prefetch forward: 15MB Prefetch time window: 20 seconds Local Cache Size: 80GB (SSD) Chunk Size: 100MB When I start media from the cloud drive it takes Stablebit about 6 or 7 seconds before the download speed reaches 1Mb/s (Megabit) and it refuses to use more than 3 or 4 download threads even though I have it set to use 30. After about 7 seconds the speeds jump up to 15 to 20Mb/s while still only using 3 or 4 threads and never going higher. I assume the initial download speed delay is what is causing the media to take so long to start playing. I tested the same thing with Netdrive and the download speeds immediately jump to 15MB/s (Megabyte) and the media plays almost instantly. EDIT: Upload speeds are great!