triadcool
-
Posts
88 -
Joined
-
Last visited
-
Days Won
5
Posts posted by triadcool
-
-
i gave up on the speeds. went for rclone instead. much better than this shtty software and its free.
Rclone has a very different use case. It's only for backing up and encrypting data to the cloud. You can't stream encrypted content from the drive without downloading the whole file like you can with Stablebit. If storing encrypted data in the cloud without touching it for a while is what you are looking for, then Rclone would be a better program for you.
-
I have had this issue for a while. I pretty much have to restart my server every 5 days to free up system memory.
-
Hopefully a fix is being worked on right now. I'm on version .719 and my drive keeps dismounting because of this.
-
^ Same here. It it occurs no matter how many threads I have set.
-
I get the same thing on my newly created REFS drive on build 1.0.0.719.
-
Response times in .682 are improved.
200ms to 300ms while uploading
900ms to 1500ms while downloading
-
-
The newest stable build (.680) seems to be slightly improved in this area. Uploading still drops from 400+ Mb/s to about 20 or 30Mb/s when downloading something from the drive at the same time. Downloads drop to about 20 or 30Mb/s when uploading. This is on a 512GB Samsung 850 Pro cache drive.
EDIT: Once the files that I want uploaded are fully transferred to the cache, I have no problems getting great speeds with upload and download simultaneously.
-
I have noticed with build .680 that my response times are between 2,500ms and 6,500ms. I dont know how much of an effect this has on things but I do know that with some of the older builds i was getting response times around 100ms.
-
Check your device manager and make sure the chipset driver is loaded.
-
This would be a very useful feature for me as well. I could have the drive mounted as read/write on my dedicated server in the datacenter to do all of the uploading and another instance mounted as read only on my home computer. (You could sell a few extra licenses this way...
) -
I keep seeing people say that you need to set upload threads to 0 to stop any uploading. This information is incorrect. You can't actually set the upload threads to 0. You will need to uncheck the "Upload threads:" box.
-
This issue is fixed in .634. Amazon Cloud drive is working great.
-
Working great here! Thanks.
-
I am getting the same "Security error".
-
-
I have been told that this has to do with NTFS Metadata. Clearing the cache on my drives fixes the issue for a while, until it slowly uses all available memory again. I also have 32gb of ram in my server.
-
I'm not sure if its related but today and yesterday I have been having issues like this with a new drive created in BETA .621 where data will just sit in the "To Upload" section with no activity. When this is occurring, download stuff from the drive is very slow.
-
I sent the logs to you about a month ago. I can send them again if needed.
-
Version .621 fixed the issue I was having with mounting my old 100MB chunk Google Drive. I am still getting the "Error: The parameter is incorrect" on this drive though.
-
Here is what I am seeing with version .620 when I try to mount my older Google Drive 15TB 100MB chunk drive.
-
This is the same error that I still get while using my older 100MB chunk Google Drive. I sent in the logs a couple of weeks ago.
-
It looks like the performance is greatly improved with version .598. Good work.
-
It looks like there were some read thread optimizations along with a few other things that could of fixed the issues.
Upgrading to latest version = 2 corrupt drives. Detach resulted in "Deleted Drive"
in General
Posted
Steffenmand,
Can you give us an update on any progress you have made in getting these drives working again? I am holding off on any update until I hear back from you.