Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11531
  • Joined

  • Last visited

  • Days Won

    365

Everything posted by Christopher (Drashna)

  1. I'll have to ask to double check, but most likely, this would be us deactivating our app API key. You'd need to set up your own API key to continue using the software, or download all of the data from Google Drive, and use the converter tool to convert it to the local disk provider format.
  2. Absolutely understand that! That data (can) be precious!
  3. No. There is some very hidden data that doesn't copy over, really. But if the new drive is added to the pool, you could copy the contents of the PoolPart folder on the old drive to the PoolPart folder on the new drive. Just make sure you remeasure after it's done.
  4. Using CIFS/smb/whatever-which-OS-wants-to-call-it should be enough to circumvent most/all of the issues that WSL has with the pool. As for docker volumes, I'm genuinely surprised that you've having issues with that. Personally, I have the WSL VHDX files for docker stored on my pool, and I have a couple of containers using file paths on the pool. Eg `-v S:/docker-data/(name):/data` (with S:\ being the pool). No issues, other than my system is running short on CPU power.... Also, IIRC, you can use cifs as a provider for volumes in docker, IIRC.
  5. To make sure/clarify, this only shows activity that occurs through the pool driver. Eg, balancing and duplication information does NOT show up here. But anything accessing files through the pool should show up here. In both the open files and the speeds.
  6. 80643 error? If so, reboot the system and try again. If that doesn't help, grab the "Microsoft installer fixit" tool, and run that. Between these two, that usually fixes the 80643 error, usually. Otherwise, what error specifically are you seeing? (and feel free to open a ticket at https://stablebit.com/contact/ if you're concerned about personal information, as that is private)
  7. Included with StableBit CloudDrive is a conversion tool. You can download the entirety of the data on Google Drive and then convert it to the local disk provider format, which should allow you to mount it there. It should still need the unlock code for the drive.
  8. Welcome! And if it helps, I'm using an old... old Haswell based system (Xeon E3-1245v3), and an LSI SAS 2008 based card (9240-8i). Ran HWiNFO64, loaded without issues, showed verything, and no drive crashes. Which is why I suspect that it's a system config related issue.
  9. The main reason there is no VSS support for the pool, is that there is zero documentation on just how to implement it on the file system side (plenty on the API side, though). So, at best, we'd have to completely reverse engineer it, do a bunch of testing (stress testing, compatibility testing, consistenty/integtrity testing) of that code, and hope it works right. While it's something I'd love to see, the main issue is resources. We're a very, very small company and simply don't have the resources to do this. As shane mentions, there are other approaches that you could take to accomplish this. Though, one that isn't mentioned, is that you could use the Local Disk provider from StableBit CloudDrive and create a drive on the pool. This drive would be VSS compatible, since StableBit CloudDrive isn't emulating the file system, it's emulating the raw data, and Windows handles the file system and VSS implementation. However, backing up the individual pool drives, or using a file based solution are going to be much simpler, and less fragile (less complexity generally means less fragile).
  10. Just to be clear, StableBit Scanner actively avoids writing to the drives, except for in very specific cases. As mentioned, there are some other utilities that can be used to accomplish this. However, personally, I use a full (non-quick) format of the drives, persionally. Also, diskpart's "clean all" command will clear the entire drive, and write over every sector on the drive. (same as a full format, but also writes over the partition info).
  11. The red and orange arrows are Realtime Placement limiters. And yeah, there was a recent change that makes them show up when they wouldn't have before. Eg, this should be fine. Especially as it more accurately reflects the status of the pool and balancers.
  12. That's very odd. And I can't reproduce locally. Most likely, this is an issue with the drivers for the drives/enclosure, and hwinfo causing it to crash the driver/controller. I'm guessing that this happens regardless if StableBit DrivePool is installed or not? If so, then you may want to check for updated drivers and/or firmware for the system, and see if that helps.
  13. Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads), the writing has been on the wall for a while.
  14. Is there a reason the "not more often than every X hours" option doesn't work for you?
  15. Also, make sure that you're up to date. There was a recent release, and there was some updating to the Cloud integration code, that may affect this.
  16. I'll post it here too. There is a fix in the latest betas involving memory corruptions of file IDs. However, ... the issue may also be the wrong API being used:
  17. If you want to use the SSD Optimizer and use the rest of the pool, the "simplest" option may be to use hierarchical pools. Eg, add the SSD/NVMe drives to a pool, add the hard drives to another pool, and then add both of these pools to a pool. Enable the SSD optimizer on the "pool of pools", and then enable the balancers you want on the sub-pools.
  18. Unfortunately, some enclosures do this. Fortunately, it's not very common, but it sucks when you find one that does.
  19. I believe that you've opened a ticket for this already, and I've replied there.
  20. Make sure that you're changing the "override" value, and not the default. The default may get overwritten, but the override value shouldn't.
  21. Well, the biggest issue is that the folders are likely not actually empty. There are some hidden files that are in use by StableBit DrivePool. For instance, we use Alternate Data Streams to set the duplication settings. These don't show up normally, even with enabling the "show protected system files" option.
  22. Sync.com cannot be added, as there is no publicly documented API. Without that API, and a way to officially read and write files/data on the provider, there is no way to support it.
  23. No, no changes have been made, in this regards.
  24. That's positiviely bizarre. Though, I can't really say that it's surprising, unfortunately.
×
×
  • Create New...