Christopher (Drashna)

Thanks for the response. Turns out, I was clicking on the down arrow and that did not give the option of enable auto scanning. So after reading your response, I clicked on the "button" itself and it toggled to enabled. Problem solved. Auto scanning immediately started so I know that it is working. Thanks.

It is. 
However, you should be able to set the "override" value for "CloudFsDisk_IsDriveRemovable" to "false", and it may fixe the issue. But the drive will no longer be treated as a removable drive. 
https://wiki.covecube.com/StableBit_CloudDrive_Advanced_Settings

Nope, definitely not dead! 
But if it's urgent, or basically, it's the best way, direct any support queries to https://stablebit.com/Contact

StableBit DrivePool doesn't have a master and subordinate/duplicate copy. Both are equally viable, and treated as such.  This is very different from how Drive Bender handles things.5
As for being documented, not really, but sort of. Eg: https://wiki.covecube.com/StableBit_DrivePool_Knowledge_base#How_To.27s
 
That said, if the data is in the same relative path under the PoolPart folders, they're considered duplicates.  Changing the duplication settings, or even remeasuring can kick off a duplication pass that will automatically prune the duplicates, as needed. 
Also, the "dpcmd" utility has an option to disable duplication for the entire pool, recursively. However, that kicks off a duplication pass that actually manages the files. 
Just have both products installed. That's it.  You can fine tune settings in StableBit DrivePool, in the balancing settings, as the "StableBit Scanner" balancer is one of the 5 preinstalled balancer plugins. 

That should be fixed now.  Though, the file system scan won't trigger the drive evacuation.  And yeah, that fix was shipping in the 2.5.5 version, and the latest stable release is 2.5.6, so this definitely shouldn't be an issue anymore.  (we haven't seen it in a while). 
 

Now I have an image of you having some sort of steampunk mechanical networking setup...

Honestly, I'm not sure.    I suspect that the processing is per drive, rather than duplicated/unduplicated, first.   
Since I'm not sure, I've opened a request, to ask Alex (the Developer).
https://stablebit.com/Admin/IssueAnalysis/28301
 
  
Not currently.   It would require a change to both StableBit DrivePool and StableBit Scanner to facilitate this.  
My recommendation would be to just evacuate unduplicated data on SMART warnings. 

So when you add a 6TB HDD to that setup, and assuming you have not tinkered with the balancing settings, any _new_ files would be stored on that 6TB HDD indeed. A rebalancing pass, which you can start manually, will fill it up as well. With default settings, DP will try to ensure that each disk has the same amount of free space. It would therefore write to the 6TB first until 4TB is fee. Then equally to the 6TB and 4TB until both have 3TB free etc. The 500GB HDD will see action only when the others have 500GB or less available.
This is at default settings and without duplication.

I believe you need to seed the pool. See Pool Seeding

To clarify (and make it simple to find), here is Alex's official definition of that "Other" space:
 
 

Yeah, as long as the drives show up correctly, then it will maintain the pool. 
 
As for the power savings, that entirely depends on the power consumption, both at peak and idle.  
And to be honest, you probably won't see a lot of power savings.  The best way to get that savings is to use large capacity SSDs, which is what data centers do.  However, they can be a LOT more expensive. 

I'm always impressed with the extent you go to help people with their questions, no matter how easy it complex.   Thanks Chris.  

Yes, that's definitely a false positive. 
 
It's just some of the troubleshooting stuff for the UI.  It's nothing harmful.  
 
And if you check, the file should be digitally signed.  A good indicator that it's legit. 

Sure. I purchased and installed PartedMagic onto a USB. I then booted using this USB to run a Secure Erase, but it was not able to complete successfully. So I ran DD (through PartedMagic as well) on the drive around 5 times. I then converted the disk to GPT using diskpart and installed a fresh copy of Windows. I used CHKDSK, StableBit Scanner, and Intel SSD Toolbox (Full Diagnostic) to confirm that read/writes were functioning as intended. 
Based on what I could understand from Intel, it seems like the Optane drives are fairly unique due to their usage of 3D XPoint technology which caused the specific/strange behavior I was facing. 

I definitely suggest configuring snapraid so it points to the drivepool folder with the GUID inside the config file so that it's much easier to restore. Snapraid doesn't have to be the root of the drive, it can be anywhere you like (as long as they are on different psychical drives).
So instead of doing:
data d1 z:\ data d2 y:\ data d3 x:\ You do:
data d1 z:\drivepool.{guid}\ data d2 y:\drivepool.{guid}\ data d3 x:\drivepool.{guid}\ That way after a failure e.g d2 dies, you drop your new drive in, add it to the pool, get the new GUID from the new drive, and edit your snapraid conf to comment out the old drive and add the new one by changing d2 y:\drivepool.{guid}\ to d2 y:\drivepool.{newguid}\ like so:
data d1 z:\drivepool.{guid}\ #data d2 y:\drivepool.{guid}\ data d2 y:\drivepool.{newguid}\ data d3 x:\drivepool.{guid}\ Then run your fix and it all just works - and you don't have to move your files around. 

It's not a bad idea, at all.  
 
Add a request for "all drives" in the reporting, as well, as more robust reporting, in general. 
 
https://stablebit.com/Admin/IssueAnalysis/27368
 
That said, this won't make it into the 1.0 release, most likely. Alex doesn't want to add any more features right now, as we want to get the software "out the door".  But after that, we will be adding a bunch of providers, and addressing feature requests like this. 

Unfortunately, no, there isn't.  
It's been asked before, but we don't have any plans on adding an option, since it introduces too many potential issues. 

Get a Norco box for the drives, and a LSI Host Bus Adapter with External SAS connectors.  Then plug the internal SAS connector into the backplane of the Norco box, and the external connector to the external connector of the HBA.

Sorry for the delay!
Seed it, just like a normal pool:
http://wiki.covecube.com/StableBit_DrivePool_Q4142489
 
And the rest looks good

Well, normally, I'd agree with you.  But StableBit Scanner isn't tracking the scan as one whole thing.   It actually uses a sector map of the drive. So it tracks sections of the drive, independently.   Each section is checked based on that status, and it over time, spreads out when the scanning happens. And should actually make it more intelligently scan (by ideally scanning at times and days when the drives are less likely to be active). 
 
You can check out this by double clicking on the disk, and looking at the sector map.  It will show different colors for different regions.

OK, I came up with a solution to my own problem which will likely be the best of both worlds.
Setup my Cloud Pool to Pool Duplicate, also setup my HDD Pool to Pool Duplicate.
Then use both the pools in the storage pool with no duplication as normal.

Found it, thank you! It was the serial number i was looking for.

The problem is that you were still on an affected version 3216. By upgrading to the newest version the Stablebit Scanner Service is forcefully shut down, thus the DiskId files can get corrupted in the upgrade process. Now that you are on version 3246 which fixed the problem it shouldn't happen anymore on your next upgrade/reboot/crash.
I agree wholeheartedly though that we should get a way to backup the scan status of drives just in case. A scheduled automatic backup would be great. The files are extremely small and don't take a lot of space so don't see a reason not to implement it feature wise.

Unfortunately, it may be. 
There is a setting that we have enabled by default that may be causing this behavior.  Specifically, the BitLocker setting. 
This setting queries the system for data, which creates a WMI query, which causes disk activity.  
That said, you can disable this:
http://wiki.covecube.com/StableBit_CloudDrive_Advanced_Settings
And the setting is "BitLocker_CloudPartUnlockDetect", which is actually used in the example.  Set the "override" value to "false", save the file and reboot the system.  That should fix the issue, hopefully. 

Well, a number of others were having this as well, and I've posted this info in a number of those threads, so hopefully, confirmation will come soon.  

This information is pulled from Windows' Performance counters. 
So it may not have been working properly temporarily. 
Worst case, you can reset them: http://wiki.covecube.com/StableBit_DrivePool_Q2150495