Christopher (Drashna)

Nope.  
The surface scan is a sector by sector scan. 
The file system scan is an api call for CHKDSK. 
So unless you're using the file recovery option, it should not be reading files. 

Mostly, this. 
You can use utilities like WinDirStat to view the drives.   But it's very possible/likely that you won't find anything specifically.   Most likely, the difference is due to the size vs size on disk differences (slack space), as well as the System Volume Information folder on each disk. 

It follows the normal balancing, rules.  
But you can use the Drive Usage Limiter if you wnt to clear out a specific disk or two. 

If you are using symlinks, information about these are stored in the metadata folder, and that is set to x3 duplication by default. 

You are very weclome!
Correct.  At least for that system.  Reconnecting it should automatically re-activate, though. 

Thanks for letting us know. 
I can confirm this behavior, as well, and have flagged it.
https://stablebit.com/Admin/IssueAnalysis/28645

You will need to manually update the location information. 
In StableBit DrivePool, disable the bitlocker detection.  That helps from that end. 
https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
For StableBit Scanner, throttle the SMART queries, as that usually helps. 
https://stablebit.com/Support/Scanner/2.X/Manual?Section=SMART
As for the work window, that's defined in the "general" tab.  So if you don't have a window set, then this setting doesn't do you much good. 
Meets or exceeds it.   Also, there is a threshold setting to.  It will warn you as it approaches that maximum.  (default is for a 15C window)
It's one disk per controller.  So if you have multiple controllers, such as onboard, and a controller card, it can scan multiple disks. 
It checks the disks, and see if there are any disks with sections that haven't been scanned in "x" days, with x being the settings for how frequently to scan. 
There are some other factors, such as disk activity, etc. 
It means that the scanning is done in such a way that any normal activity takes priority over the scans, and may stop the scanning from occurring.   This way, it minimizes the performance impact for the drives, ideally. 

Oh wow. 
It may be worth contacting PrimoCache's company to see if they have a recommendation here. 
That may work, but it would definitely be better to target the underlying disks, as the actual reads occur there.  You'll get better results that way, without a doubt. 

Ah, okay, I see what you mean about the UI saving, now.  I'll flag that as a bug, since I can definitely reproduce. 
https://stablebit.com/Admin/IssueAnalysis/28642

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

Because we've already have had a couple of questions about this, in their current forms, StableBit DrivePool works VERY well with StableBit Cloud Drive already.
 
The StableBit CloudDrive drive disks appear as normal, physical disks. This means that you can add them to a Pool without any issues or workarounds.
 
 
Why is this important and how does it affect your pool?
You can use the File Placement Rules to control what files end up on which drive. This means that you can place specific files on a specific CloudDrive.  You can use the "Disk Usage Limiter" to only allow duplicated data to be placed on specific drives, which means you can place only duplicated files on a specific CloudDrive disk.  
 
These are some very useful tricks to integrate the products, already. 
And if anyone else finds some neat tips or tricks, we'll add them here as well.
 

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

i would also like to see dark mode addedto all stablebit products

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

I mean, alex is alive and well.  but yeah, some issues that don't directly involve Covecube.  
If alex wants to answer what exacty so going on, he will.  But stuff is still happening. 

You posted on another thread too. 
 
But You may need to enable the "Unsafe" "Direct IO" option to get the SMART data off of these drives, due to the controller. 
https://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings
if that doesn't work, enable the "NoWmi" option for "Smart", as well. 

We have a number of people using Windows 11 already,  but we won't say that it's officially supported until Windows 11 is no longer a beta. This is because the OS is in too much flux until it's RTM'ed, and takes a lot of work to officially support it before then. 

Christopher (at support) came back on my ticket.  He reenabled my ID and all now good.  Can write to the DrivePool.
Just in case someone else encounters this problem use a fresh trial ID to get things going while waiting for support to reenable the paid ID. 

I mean, alex is alive and well.  but yeah, some issues that don't directly involve Covecube.  
If alex wants to answer what exacty so going on, he will.  But stuff is still happening. 

First, thank you for your interest in our product(s)! 
 
 
The default file placement strategy is to place files on the drive(s) with the most available free space (measured absolutely, rather than based on percentage). This happens regardless of the balancing status.   In fact, it's the balancers themselves that can (will) change the placement strategy of new files. 
 
For what you want, that isn't ideal.... and before I get to the solution: 
 
 
 
The first issue here is that there is a misconception about how the balancing engine works (or more specifically, with how frequently or aggressive it is).
 
For the most part, the balancing engine DOES NOT move files around.   For a new, empty pool, balancing will rarely, if ever move files around.  Partly because, it will proactively control where files are placed in the first place. 
 
That said, each balancer does have exceptions here.  But just so you understand how and why each balancer works and when it would actually move files, let me enumerate each one and give a brief description of them. 
 
StableBit Scanner (the balancer). 
This balancer only works if you have StableBit Scanner installed on the same system.  By default, it is only configured to move contents off of a disk if "damaged sectors" (aka "Unreadable sectors") are detected during the surface scan.  This is done in an attempt to prevent data loss from file corruption.  
Optionally, you can do this for SMART warnings as well. And to avoid usage if the drive has "overheated". If you're using SnapRAID, then it may be worth turning this balancer off, as it isn't really needed Volume Equalization.
This only affects drives that are using multiple volumes/partitions on the same physical disk.  It will equalize the usage, and help prevent duplicates from residing on the same physical disk. Chances are that this balancer will never do anything on your system.  Drive Usage Limiter
This balancer controls what type of data (duplicated or unduplicated) can reside on a disk.  For the most part, most people won't need this.  
We recommend using it for drive removal or "special configurations" (eg, my gaming system uses it to store only duplicated data, aka games, on the SSD, and store all unduplicated data on the hard drive)Unless configured manually, this balancer will not move data around.  Prevent Drive Overfill
This balancer specifically will move files around, and will do so only if the drive is 90+% full by default. This can be configured, based on your needs. However, this will only move files out of the drive until the drive is 85% filled. This is one of the balancers that is likely to move data.  But this will only happen on very full pool.
This can be disabled, but may lead to situations where the drives are too full. Duplication Space Optimizer.
This balancer's sole job is to rebalance the data in such a way that removes the "Unusable for duplication" space on the pool.   If you're not using duplication at all, you can absolutely disable this balancer  
 
 
So, for the most part, there is no real reason to disable balancing.  Yes, I understand that it can cause issues for SnapRAID. But depending on the system, it is very unlikely to.  And the benefits you gain by disabling it may be outweighed by the what the balancers do.  
 
Especially because of the balancer plugins. 
 
 
Specifically, you may want to look at the "Ordered File Placement" balancer plugin.  This specifically fills up one drive at a time.  Once the pool fills up the disk to the preset threshold, it will move onto the next disk. 
 
This may help keep the contents of a specific folders together.  Meaning that it may help keep the SRT file in the same folder as the AVI file. Or at least, better about it than the default placement strategy.  This won't guarantee the folder placement, but significantly increases the odds.
 
That said, you can use file placement rules to help with this.  Either to micromanage placement, or ... you can set up a SSD dedicated for metadata like this, so that all of the SRT and other files end up on the SSD.  That way, the access is fast and the power consumption is minimal. 

Well, it may be worth testing on the latest beta versions, as there are some changes that may effect this, due to driver changes. 
If you're already on the beta or the beta doesn't help, please open a ticket at https://stablebit.com/Contact so we can see if we can help fix this issue. 

Yeah, it's ... manufacturer fun.   SMART really isn't a standard, it's more of a guideline, that a lot of manufacturers take a LOT of liberty with.  NVMe health is a *lot* better, in this regards (it an actual standard). 

Yes, you can do that, too.  
 
However, I generally prefer and recommend mounting to a folder, for ease of access.
 
It's much easier to run "chkdsk c:\drives\pool1\disk5", than "chkdsk \\?\Volume{GUID}"... and easier to identify.
 
 
 
Yes. The actually pool is handled by a kernel mode driver, meaning that the activity is passed on directly to the disks, basically. 
 
Meaning, you don't see it listed in task manager, like a normal program. 

StableBit DrivePool doesn't care about drive letters.  It uses the Volume ID (which Windows mounts to a drive letter or folder path). 
 
So you can remove the drive letters, if you want, or mount to a folder path. 
 
http://wiki.covecube.com/StableBit_DrivePool_Q6811286

Just a heads up, yes, it does continue to attempt to upload, but we use an exponential backoff when the software gets throttling requests like this. 
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.