Jump to content
Covecube Inc.

otravers

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by otravers

  1. It turns out this had nothing to do with the Windows updates. I had input - apparently incorrectly - Google API settings in ProviderSettings.json, which prevented the service from restarting. The way I found this was the source of the issue was by executing CloudDrive.Service.exe from the command line. Phew!

  2. I just installed the 2021-05 and 2021-06 cumulative updates for Windows 10 Version 20H2 and now have CloudDrive stuck "Connecting to service" even though the service is still set to Automatic startup type. When I try to start the StableBit CloudDrive Service from services.msc, I get:

    Quote

    The StableBitCloud Drive Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

    This still happens after a cold reboot. Anyone else running into this, hopefully with a fix? I'm running the latest beta which had been working reliably for a good while for me.

     

  3. On 4/10/2021 at 4:05 PM, Christopher (Drashna) said:

    However, a daily limit or schedular is something that has been requested and is on our "to do"/feature request list.  I just don't have an ETA for when it would be considered or implemented.

    This would be great, currently I feel I have to micromanage uploads manually to make the most of my upload bandwidth and use the 750GB/day quota.

  4. Get ready to lose the "unlimited" GDrive storage. The new Workspace TOS spell out that beyond 5TB per Enterprise user it will remain within Google's discretion to grant you extra storage.

    I just got the email introducing the new plans, I'm guessing that we have a few months left before they force the transition, a year at best for those people who just signed up to an annual GSuite plan before they were retired. I just checked and it doesn't look like you can convert a flexible (i.e. monthly) plan to an annual Gsuite plan, now it's all about migrating us to Workspace.

  5. I also had one of my cloud drives showing checksum errors starting about two weeks ago, without any apparent reason, i.e. no Windows crashes or problems on the physical hard drive where CloudDrive stores its cached data. I tried chkdsk but this didn't solve the issue and the "to upload" quantity reported by the CloudDrive UI keeps creeping upwards (gained a few GB since the problems started occuring).

    I'm using CloudDrive + infinite GDrive for Plex too, it's great when it works but just doesn't seem reliable over the long run.

  6. As I came back to my desktop this morning, I found my two cloud drives unmounted. It turned out that one of my SSDs was no longer seen by Windows 10 for some reason, and that's where the CloudPart folders were located. So I remounted the drives and set up their local cache to another of my local hard drives. The two cloud drives remounted without a hitch, so far so good.

    I then turned off my PC, checked that the SATA cables were still properly in place, restarted the PC and checked that the missing SSD was seen in the BIOS (it was), and booted back into Windows. The missing SSD is now showing again, which is good news. Stablebit CloudDrive managed to remount one of the two drives pretty quickly, but it's been stuck for the past couple of hours on a loop telling me that the other cloud drive cannot be mounted because it's attached to a different computer. Another computer was never involved in this, just two local hard drives on the same PC.

    I see that I have CloudPart folders for the two cloud drives on both local drives. What should I do from there without risking losing any data?

    Here's what support sent me (lightly edited for readability), which I followed and solved my issue. Phew!

    Quote

    "That's a tricky issue as the cache for the drives are available in two locations, which is a serious problem for StableBit CloudDrive. The best bet would be to disable the StableBit CloudDrive Service (run "services.msc", find the service, right click on it and select properties, and set the startup type to "manual"), and reboot the system. Once you've done that, remove the CloudDrive folders from the SSD.  Once they're gone, start the service (and set it back to "automatic". From there, run a CHKDSK pass on the CloudDrive disks to make sure there is no corruption.   And if you want, detach the drives and reattach them on the SSD again."

     

     

  7. 8 hours ago, srcrist said:

    You're just moving data at the file system level to the poolpart folder on that volume.

     

    Thanks! Sounds like this is handled without needing a reupload of these files, right?

    I'm still on the fence because I don't know that I like the idea of losing control of the volume on which specific files/folders end up being stored.

  8. On 1/22/2019 at 6:35 PM, srcrist said:

    "You'll want to MOVE (not copy) all of the data that exists on your CloudDrive to the hidden directory that DrivePool creates ON THE SAME DRIVE, and that will make the content immediately available within the pool. [...] So let's say you have an existing CloudDrive volume at E [...] Now you'll want to navigate to E:, find the hidden directory that DrivePool has created for the pool (ex: PoolPart.4a5d6340-XXXX-XXXX-XXXX-cf8aa3944dd6), and move ALL of the existing data on E: to that directory. This will place all of your existing data in the pool."

     

    @srcrist Thanks for your very detailed post, I'm reaching the limit of my first 16TB (Google Drive) volume and your setup looks more streamlined than mounting more and more separate CloudDrive volumes. I'm uncertain about the part I quoted above and am very frightened to make a mistake that might nuke my existing CloudDrive volume. I have slow upload speed, it took me months to upload 16TB.

    How do you accomplish the above? Can I move the Cloudpart directory of my initial CloudDrive volume to the Drivepool folder?

  9. I'm currently testing CloudDrive and I like how I can see encrypted files right in the Windows explorer (well, Directory Opus in my case). I mounted two drives pointing to ACD, and I see that moving data from one to the other goes through my internet connection. Obviously very inefficient.

     

    Is there a way to move data where the actual physical transfer happens directly in the cloud, which presumably should be "just" moving logical pointers within the same cloud? Is the answer maybe different depending on the cloud provider (ACD vs. GDrive and others)?

×
×
  • Create New...