Christopher (Drashna)

https://stablebit.com/DrivePool/Download
Once you click the checkbox, there is a "what's new?" link that will take you to here:
https://stablebit.com/DrivePool/ChangeLog?Platform=win
Or you can see the beta changelog here:
https://dl.covecube.com/DrivePoolWindows/beta/download/changes.txt

There are some hidden by default, already, but that's because they're experimental. 
But I don't see a reason why this couldn't be added. 
StableBit Scanner uses Telerik controls, which we stopped supporting/using, since they come with a bunch of their own issues.  
StableBit DrivePool and StableBit CloudDrive use entirely custom implementations, and all native WPF controls, because of some of the issues we've had with telerik controls. 
So, pretty much the opposite.  Eg, StableBit Scanner is the older product (the first, actually). 

To clarify, StableBit DrivePool doesn't use the drive letters or mount points.  It uses the volume ID for the disks.  So you can change how the drive is mounted without any issues. 
Personally, I prefer mounting the drives to folder paths, as that hides them, but still allows them to be accessible. 

For balancing and duplication operations, the files are copied to a temp folder, and then renamed when the operation completes.  this ensures that even if an interruption occurs, that the files are intact, whole and not corrupted.   
And yeah, that's probably a good way to set things up. 

correct, internal operations (balancing, duplication, measuring) are not reported there. Only activity it reports is what happens through the pool drive. 

The 100gb has been there for a long while, TBH.  And that's been the default for it since the start.  And by a long while, I mean since the DrivePool v1 days> (so ~2011).   Eg, back when drives rating in TBs were at the high end, for the most part. 
You and disable the option or set it to something more reasonable for your setup.   But it sounds like unchecking it may be what you want here. 

It should be simpler, yes. 

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.