Christopher (Drashna)

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?

In this case, yes. Or create a rule that bypasses it. But you can also just turn it off temporarily.

That's ... very odd. But for reference, you can manually add "peers": https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#RemoteControl.xml

Have you tried the beta version of StableBit Scanner. IIRC, there are some improvements that should help with false positives in the file system scanning.

Yup, they run on Windows 11 just fine (Also Server 2022 looks to be Windows 10 based, 21H2, specifically). And yes, you can use 2x SSDs for cache, just download and install the SSD Optimizer balancer plugin. StableBit DrivePool Balancer Plugins

we've run into a few people that have had issues with the HFS driver for windows causing BSODs, and a good number of people using primocache with StableBit DrivePool without issues.

I think you opened a ticket for this as well, and that one of the poolpart folders is showing up a file. If so, then data recovery, or wiping the drive and letting it reduplicate the data is the best option here.

Yup. But I would recommend deactivating all of the StableBit products before moving over to the new hardware, that way you don't run into any activation issues.

Use powershell, and "remove-item". It should be able to do this. Otherwise, this should work. And if it's not, could you open a ticket at https://stablebit.com/contact

Not currently, but I definitely do keep on bringing it up.

The simplest option would be to use the file placement rules to exclude the SSD drive from being used.