580guy

I also use Snapshot Raid with Drivepool.  If a drive failure, I physically remove the drive, THEN remove it on Drive pool.  Install a new drive, put it in the pool and restore. 

I know my post above is from a couple of years ago, but just wanted to confirm that it DOES INDEED work if there are any out there using this combination.  I had my first drive failure in my server of 21 drives.  I know I have been extremely lucky as I have drives that have over 6 1/2 years of 24/7 operation and are still going strong. Anyhow....
 
The drive that failed, didn't fail completely.  I had been receiving warnings from Stablebit Scanner about remapping sectors for the last several months.  I decided to wait and see how long the drive would go before it failed completely. This drive had about 4 1/2 years of service.  In the end there were 2 files which became unreadable and I decided to pull the drive and replace it.
 
Rather than remove it from the pool normally and allow Stablebit scanner to migrate files to other drives in the pool, I just physically removed the drive from the server.  I did this because so as not to disturb the array parity I had with Flexraid.
 
Then removed the "missing" drive with Stablebit Drivepool.
Put in a new drive, made sure same drive letter assigned by WHS 2011, and waited for duplication to finish restoring files.
I then took the Old Drive, renamed the poolpart.xxxx folder to prevent it from rejoining the pool, and copied my unduplicated ServerFolders back to the new drive, with the exception of the 2 unreadable files.
 
Then, deleted old symbolic link, and created a new one with the same name pointing to the new PoolPart.xxxx folder of the new drive.
Restored the 2 bad files from Flexraid.
Done! Parity is still unchanged for the new disk, avoiding a lengthy update to get the new disk files into the parity array.
 
Of course had the drive failed totally without being able to access any files at all, then I would just allow Flexraid to restore it completely.  But, since I was able, I think that copying the old drive's contents was slightly faster so I did it this way.
 
Just wanted to confirm this works great if there are any others that are using this combination of Stablebit Drivepool and Flexraid parity for data protection.

Do this:
http://wiki.covecube.com/StableBit_DrivePool_Q7200705B
 
Specifically, the info here is pulled from the Windows Search service.  This service sometimes has issues. Rebuilding the index should fix the issue in the dashboard.

Well, that would do it, as well.
And at least that link points you to where the settings are.

When you remove the drive, it sets the pool as "read only", so you can't write to it.  But you can still access the pool during this time.
However, because it is read only, any thing that relies on altering data will fail, such as client backups. But media streaming should work fine during this time. However, because one or more drives maybe written to during the removal process, it may make the system laggy.
 
 
If you want though, you could use the "File Placement Limiter" balancer to move the data off the drive in question, and once that's done, remove that drive from the pool immediately. And since there should be no pooled data after it's "balanced" the data, it should take minutes (if not seconds) to remove it from the pool.