Christopher (Drashna)

The licenses are good for any version of that product. However, you will want to deactivate the licenses prior to wiping the system. Or contact support directly to get your licenses deactivated. The licenses belong to you, not the hardware they're activated on, and are not locked to a specific version. Yup!

DiskCryptor should work for this, yes. Also, StableBit CloudDrive's local disk provider would also work for this.

Yup, it's fine!

Submitting a ticket would be best for issues like this. But that's very odd. But yeah, if one of the bays isn't on, then the files on that disk won't show up in the pool until the drive is reconnected.

Is this done through WSL? Also, is it using hardlinks?

Honestly, I've not run into this issue. However, when duplication issues occur, you would need to stop the database service, repair the duplication, and then start the backup service back up. DrivePool cannot correct in use file.

Just a heads up, some HBAs can mess with the partitioning information. It's rare, but not unheard of. if you haven't already, try remeasuring the pool. If that doesn't fix the issue, run a CHKDSK pass on the disks in question. Also, make sure that each of the disks has a hiddle "poolpart.xxxxx" folder in the root of the drive.

This is happening on the Google Drive provider, specifically?

It wouldn't. Period. It would error out, because when you have missing disks in the pool, the pool is put into a read only state. So you can access the files and folders that are still present on the connected disks, but you cannot write to the pool, nor change permissions on the pool.

Yup, the balancer settings will let you do that. As for the issue, reset the settings, if you can access X:\ normally.

if that's happenng, than the shutdown isn't happening correctly, and causing an unclean shutdown for StableBit CloudDrive, and triggering a recovery. If you could, open a ticket at https://stablebit.com/Contact

That's intential. It should use as much cache is set. Also, "to-upload" cache can exceed the set amount, if the type is set to expandable (default). You can set a fixed size if you want to make sure that it doesn't grow past a set size, no matter what.

Upgrades like that are tricky. They tend to nuke a lot of things (such as system services and drivers). It should work fine, but I would still recommend uninstalling StableBit CloudDrive first, upgrade to Windows 11, and then reinstall StableBit CloudDrive. This makes sure that the correct driver is installed, and that it's installed correctly. Especially as we've had a number of people that have had to reinstall or repair StableBit DrivePool and StableBit CloudDrive after upgrading.

No. Storage Spaces uses a block based method for storing the data, while StableBit DrivePool uses a file based method. So there is no direct way to convert. You'd have to remove the drives from the Storage Spaces array (which is destructive, eg, wipes the data), and then add the disks to a pool. However, you can add a Storage Spaces array to a pool, and use it directly that way, until you have enough storage to break the Storage Spaces array and re-add those disks.

you'd want to: * UNCHECK "File placement rules respect real-time file placement limits set by the balancing plug-ins." * CHECK "Balancing plug-ins respect file placement rules."

StableBit Scanner doesn't write to any disks without explicit permission, aside from it's settings store. So, that wouldn't have. StableBit DrivePool only writes to disks in a pool, and it's settings store. So, if a non-pooled disk was effected, then that's unusual. If you have had any unplanned power loss, eg BSOD's, hard resets, etc, then it can potentially cause file system corruption like this. Also, hot plugging drives can cause issues, too.

That's ... absolutely bizarre. Could you mind opening a ticket at https://stablebit.com/Contact/

Could you open a ticket at https://stablebit.com/Contact so we can help you with this issue directly?

I think you're looking for this: https://wiki.covecube.com/StableBit_DrivePool_Q4142489

If the disk was having issues, the permissions may have been reset. This can happen when running a file system scan. But yeah, it does try to keep the permissions in sync, usually. If you need, you can reset the permissions: https://wiki.covecube.com/StableBit_DrivePool_Q5510455

Connecting via USB 2.x? If so, then this can cause the scans to be super slow. You can check the disk details in StableBit Scanner to verify that. Also, double check the scanning section to see what exactly it's doing: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map

That's definitely not usual, especially if that's all in the same user account. However, try ending the task for all of the DrivePool.UI.exe processes, and then re-launch it. And if this continues to occur, open a ticket https://stablebit.com/Contact

I'd personally go with a supermicro based chassis, but I'm biased (I really like their design). but yeah, SAS is compatible with SATA (but SATA is not compatible with SAS drives).

You're very welcome!

Okay. Could you open a ticket at https://stablebit.com/Contact then?