Christopher (Drashna)

Honestly, I wouldn'r really recommend disabling balancing. The default balancers cover edge cases, mostly... so if it's balancing data, there is probably a good reason for it, and disabling it may cause problems, down the line.

before anything else, upgrade the version. There was an issue that caused the user rate limit exceeded warnings, and has been fixed since. Just to make sure that this isn't the same issue .... Also, if you have 2+ drives backed by Google Drive, you want to split the resources between them. Eg, 40mbps each (if there are 2), and 4-5 threads, each.

That's good information to know! Though, would you be willing to post the process of how you did all this, specifically?

Also, there are PCI-e riser cards that have NVMe slots. Though, they may be expensive.

It's already on the list.

The best question here is: how to determine it's actually enabled and in use? by .... checking for bitlocker'ed drives. It's really a catch 22. It also effects other encrytion types, for the drives. Not just bitlocaker. So, "it's complixated", for sure.

You need to contact support to get this resolved. https://stablebit.com/Contact

Specifically, Dynamic Disks add a significant level of complexity, just because of the many different ways that they can be configured. This causes issues because DrivePool actively avoids putting files on the same, physical disk when a drive has multiple partitions. This detection is done in the kernel, so it has to be fast. But because of how complex dynamic disks are, this would drastically slow down the driver. Motherboard based RAID would absolutely work for this.

A better question may be, check the toolbar, make sure that it says "Automatic Scanning Enabled". If it does not, then click on it to enable it. Additionally, check the license status for the software. We recently found a bug that prevents the UI from properly displaying the "trial expired" UI. This has been fixed, but you may be running a version that hasn't.

It should only delete files that are duplicated and shouldn't be. Or if you've changed it. However, it only delets the files if they have identical file paths (and therefore would be treated as the same file, by the pool). You can have the same name for every file, but unless they're at the same file path, they're considered different files.

Absolutely! That's how we do a majority of our testing, in fact! And yes, it would. Best solution for that? Create a second drive for the VM, use that exclusively for the cache, and don't back that drive up.

So the automounting didn't help? That's .... odd. And nice, on the RED utility!

^ This. The level of duplication is the number of instances of files you have. x1 means just one of the file, unduplicated. x2 meaning 2 of the files, and so on. And any time you change the levels, it will run a duplcation pass, and ensure that whichever files are at the correct number of instances that they should be at. That means copying or deleting files, depending on what you changed.

Well, a lot of that is that Stablebit Scanner and StableBit DrivePool have been out for a long while now. A majority of any bugs have been found, so not as much fixes out. Most of the issues we get now are extreme edge cases (eg very weird), or due to hardware/software interactions. We haven't really added any new features to them, as the last set of features were in prep for StableBit CloudDrive, in fact. However, we are working on StableBit Cloud right now, and that has a majority of our focus. Once that's "completed", we'll be able to shift focus more (eg add new features, or

You can always manually add a list of peers to each system. https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#RemoteControl.xml But this can be complicated, and not due to upgrading. Also make sure that all of the systems are using the same version.