Jump to content

Search the Community

Showing results for tags 'box'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Covecube Inc.
    • Announcements
  • StableBit Cloud
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic
  • BitFlock
    • General

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. I cannot even mount any drives with pending data at this point. This is in the service log and on this and other machines it just keeps getting longer (I think it was up to several hours at one point). Do you know if there have been any changes at Box? Please advise: 0:01:55.1: Information: 0 : [ServiceStoreSynchronization] Initial synchronization complete. 0:01:55.1: Information: 0 : Adding firewall rule 'StableBit Cloud - UDP (CloudDrive.Service.exe)'. 0:01:55.2: Information: 0 : [Main] Starting notifications... 0:01:55.3: Information: 0 : [Main] Starting BitLocker... 0:01:55.4: Information: 0 : [Main] Enumerating disks... 0:01:55.5: Information: 0 : [SignalClient.Controller] Connected to 0:01:55.5: Information: 0 : [ServiceStoreSynchronizationSignal] [signal] Connected to Signal server ( 0:01:56.0: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] Set CloudServiceInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:01:56.0: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] SetBatch on cloud (T=00:00:00.1781305) 0:01:56.1: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] Set UpdateInfo on cloud (Result=Saved, LocalCloudRevision=187, CloudRevision=188) 0:01:56.1: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] Set UpdateInfo on cloud (Result=Saved, LocalCloudRevision=277, CloudRevision=278) 0:01:56.1: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] Set UpdateInfo on cloud (Result=Saved, LocalCloudRevision=727, CloudRevision=728) 0:01:56.1: Information: 0 : [ServiceStoreSynchronization:27] [change-tracking] SetBatch on cloud (T=00:00:00.1627609) 0:01:56.1: Information: 0 : [ServiceStoreSynchronizationSignal:18] [signal] Cloud storable 0x3ab8b3c3d6c5fac1070e41136c9c21548f67b485 changed (CloudRevision=278). 0:01:56.2: Information: 0 : [ServiceStoreSynchronizationSignal:25] [signal] Cloud storable 0x6fcdb1ee9ababd38601c473df38c947206b7daab changed (CloudRevision=188). 0:01:56.2: Information: 0 : [ServiceStoreSynchronizationSignal:5] [signal] Cloud storable 0x60674b24d33d720f08a81e39f1eac17b56dd8b4a changed (CloudRevision=728). 0:02:02.6: Information: 0 : [Disks] Updating disks / volumes... 0:02:03.4: Information: 0 : [Main] Updating free space... 0:02:03.4: Information: 0 : [Main] Service started. 0:02:03.4: Information: 0 : [Main] Synchronizing cloud drives... 0:02:05.4: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:02:05.5: Information: 0 : [CloudDrives] Valid encryption key specified for cloud part 3b9fdbb9-b92f-43e2-a148-f6b32737475c. 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudProviderInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudDriveInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudDiskStatisticsInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudDriveStatusInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudMountingInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] Set CloudUnmountableInfo on cloud (Result=Saved, LocalCloudRevision=, CloudRevision=1) 0:02:07.0: Information: 0 : [ServiceStoreSynchronization:46] [change-tracking] SetBatch on cloud (T=00:00:00.3990282) 0:02:13.8: Warning: 0 : [ApiBox] Server is throttling us, waiting recommended 1,716,000ms and retrying.
  2. Hi all, Been experimenting and I think I found a bug, however, I did not want to do anything until I ran it by the community. I have signed up for a Free BOX.com drive. You get 10GB of space. What they did not tell you, is it seems you have less than that. I took a guess that they used hard drive manufacturers 10Gb (not 10gb) and it really was 9.7GB (there abouts). I found this by using this drive in a Drive Pool. The pool got saturated and that drive had over 9.7GB of data. That is, the drive was over 90% full. As Cloud Drive was trying to upload, it seemed to get stuck in a loop. After I noticed that this ONE drive was taking ALL my upload bandwidth, I hit PAUSE though the new PAUSE button. I validated that the settings changed (manage drive -> Performance -> Uploads UNTICKED). I also tried to use the "All drives PAUSE" under the pulldown (upper right Gear). Nothing I did could stop the upload from happening. I was sure this was happening as pulling the ethernet cable from the VM seemed to stop the upload (from the upload speed value being shown). After I plugged the ethernet back in, and a few hours later (I honestly do not know how long it was), I logged back into the machine and looked. I had a message in the message ticker that stated the drive was FULL and the upload attempt failed 260 times. EEEK! I also saw at least 1 other box drive listed in the log. I then tried to STOP and RESTART the Cloud Drive Process. This only seemed to anger other drives (now they had GB of data that was out of sync - this was being addressed in a Cloud Drive thread regarding rebooting and seemingly getting this error, which was brought to a conclusion with a TR/SR being submitted, so I did not bother...well bothering anyone about it). OK, all that aside, this drive was NOT going to stop trying to upload. I then tried a reboot. Still, no change. For a while, I just TURNED it's speed WAY down. That let other drives "catch back up" from the service stop and the reboot. At this point, I now think I discovered the issue. I changed a few settings on Drive Pool to fill to 80% as best it can, instead of 90% (just to be safe). I also mapped my box accounts to drive letters. Then MOVED an appropriate amount of data off to let me use the resize feature and set to 9.7GB. It seems just doing the move has made cloud drive happy and EACH drive that was STUCK like this has STOPPED trying to upload. I have only tested this with box (hence the post here). It might be with all - however there was a pretty long check when I SETUP the Google drives. If I put in a value that was too large, the original drive creation would fail. I would think this is the same with BOX? I am on the latest beta So, has anyone else seen this? Any tips? Is this just BOX? Thanks!
  3. Kraevin


    I have been testing several providers (Google Drive, Drop Box and Box.com). I am curious if anyone else here has been testing Box.com and their results with uploading files. I noticed with Google and Dropbox i can pretty much max out my upload connection (gigabit connection), 700-1100 mbps. and this is with just 5 upload threads. With box.com i see to get a different story with uploading only able to max about 50-70 mbps. Yes i have adjusted the upload threads and still no difference and upload bandwidth throttle isn't on. Box.com claims they do not throttle. So is anyone else here having slow uploads with them? If it helps i am uploading from the UK area. I have a feeling this is probably more of an issue with Box.com and their servers.
  4. Quick question: is upload verification required for box? I've seen on the forum here that it's not necessary for some providers, but haven ot found a specific comment for box.
  5. Hey CoveCube. I was looking into your neat software but recently ran into a really scary issue. Right now i have moved more than 1.8TB to BOX. The issue is that i can't detach the disk. It just says "Incorrect function". What the F* to do about that kind of error?
  • Create New...