Christopher (Drashna)

Sorry for not getting back to you sooner. 
So, it's a SSD, then, and almost out of spare nand.   
For migrating to a new SSD, you should be able to just clone the system drive, no problem.  

No.  StableBit CloudDrive looks for these paths, specifically.  Changing them will corrupt your data. 
However, keep in mind, that these files are chunks of data, not the specific files, so they won't correspond directly with anything stored on the drive.
 

You can find the beta version here:
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3246_BETA.exe
 
Crashes definitely. But I'm sure there are other cases that the behavior could be triggered in, too.  Shutting down would definitely be one of them. 

You can find the beta version here:
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3246_BETA.exe

Yup, and we absolutely appreciate all the help finding this issue! 
Alex has pushed out a fix for this:
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3246_BETA.exe
Specifically, the issue was:

http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3246_BETA.exe
WIth the help of one user, we were able to pinpoint the issue, and this shouldn't happen in the future.
Specifically, the issue was:
 

You mean like adding a specific folder as a drive letter? 
If so, no, StableBit DrivePool doesn't support that specifically.

No, This is hard coded behavior.  But this should be pretty small in size, so shouldn't be an issue. 
When they're accessed, when duplication setting change, when the pool is measured.  So, yes. But we do so in a very lightweight way, that minimizes disk usage. 
As for the second part, if you're using Task Manager to look at this.  DON'T.  100% utilization could mean 1B/s, or 500MB/s. it's based on the last 60 seconds of activity. So, it is very likely that it will be 100% most of the time.
A better way to tell how pegged it is, is to look at the disk queue length.  Generally, you want it at or below 1 per platter in the drive. So, if it's a 2-3 for a long time, then the disk is being worked hard.

That sounds perfectly fine. 

Yup, it's an issue with the deployment on 32 bit systems. 
This should be fixed here: http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.3.939_x86_BETA.exe

Best way? 
Deactivate the license for StableBit DrivePool Uninstall StableBit DrivePool Move the drives to the new VM Install Windows and StableBit DrivePool Activate the software That's it.  You may want to reset the permissions on the pool, if you used specific user accounts.  Otherwise, it should "just work".
 
As for the deactivation itself: 
StableBit DrivePool 2.X/StableBit CloudDrive: Open the UI on the system that the software is installed on, click on the "Gear" icon in the top, right corner and select the "manage license" option.  StableBit Scanner: Open the UI on the system that Scanner is installed on. Click on "Settings" and select "Scanner Settings". Open the "Licensing" tab, and click on the "Manage license" link.  This will open a window that shows you the Activation ID, as well as a big button to "Deactivate" the license. Once you've done this, you can activate the license on a new system.
 

Though, thinking about this, you could do this by using hierarchical pooling for the first 2 disks (eg, add those to a pool).  Then add that and the "hot spare" to a top level pool, and then use the Ordered File Placement balancer to fill the sub-pool first.

No, not really. 
But ... hierarchical pools could let you effectively do that.  Add two pools to another pool and enable duplication on the top level pool. That way, one set of the files resides on each pool.   That ... may get what you want.  It's used primarily for reparse point, right now. 
And I think that this information is stored in memory once the system starts, but I'd have to double check with Alex (the Dev) 

Yes: http://wiki.covecube.com/StableBit_DrivePool_Q4142489
At least I believe that's what you're asking.

Mostly just backups, encryption, and deduplication.  Basically, if it's a disk tool, then yeah, probably. 
Just keep in mind that if you're writing to the pooled disks, in a pooled location, that it will cause the statistics to become inaccurate, and affect balancing and duplication. 

It means the pool drive.  And yeah... how Windows handles disk/partition/volume stuff is confusing... at best. 
For this ... take ownership of the folder, change it's permissions, and delete it (on the pool). 
Then resolve the issue.  It should fix the issue, and shouldn't come back. 

It's best to deactivate first.  
While, usually, you shouldn't need to deactivate in this circumstance, the reinstallation process can change some of the information that we use to identify the system.  So it's better to deactivate first, since that takes like 30 seconds.  Otherwise, if it doesn't activate on the new install, you'd need to activate the trial and then contact us. 

You posted a ticket asking the same thing, and I've already answered there. But basically: 
You want to do this: http://wiki.covecube.com/StableBit_DrivePool_Q4142489
 
And all of the data is stored in hidden "PoolPart" folders. 

Anyone still having this issue, grab the latest build, as that should definitely fix this issue: 
http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.1.0.1025_x64_BETA.exe

You could use the "balance immediately" and the "not more often than every" options.  Set it to about what you want. 
Then .... if needed, script the service to be restarted at the time you want balancing to occur.  
That .... should work, I think. But don't quote me on that. 
But here: https://stablebit.com/Admin/IssueAnalysis/27852
I've added a feature request for this
Yes, it would balance the recycle bin on the pool. 
 
However, depending on your pool..... balancing shouldn't happen too often.  All of the default balancers are more of "edge cases.  Sothey shouldn't cause balancing to happen, most of the time. 

That would do it.
And glad to hear that it was a simple issue. 
Enable "Pool File Duplication",  Then make sure that in "Folder Duplication" that no folder has a "+" next to it.
https://stablebit.com/Support/DrivePool/2.X/Manual?Section=File Protection
 
To clarify here, you'd want "duplicated" enabled on both pools, or you'll have issues. 
Duplicated refers to "any file that has a copy on another disk".  So any duplicated data on this pool will be on both disks, so both disks will have duplicated data.  Eg, we don't differentiate the copies. Both are "master" copies, and either can and will be used.
Unchecking the option means that it will "degrade" the pool condition and want to balance the data more aggressively.

There is a known memory leak. 
Install this version: http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.2.928_x64_RC.exe

No worry about being a noob! We all were once.
As long as the files are identical and are in identical paths... just add both disks to the pool, set the duplication to what you want, and "seed" it.  It should detect the duplicates, and "handle them". 
http://wiki.covecube.com/StableBit_DrivePool_Q4142489

For the people experiencing this issue:
Install the latest build:
http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.1.925_x64_RC.exe
You can find the newer builds here: http://dl.covecube.com/DrivePoolWindows/rc/download/?C=N;O=D Please open a ticket at https://stablebit.com/Contact  
We don't check the forums as often as we do the contact system.  So help here may be delayed.  Also, .... the other issue is that troubleshooting here leasds to a lot of "me too" type posts that actually MAY NOT BE RELATED.  (it's happened in the past, a number of times).  But we try to mention that yes others are having the same issue when it happens. 
 
That said, if you haven't already, enable verifier, grab the new crash dump and UPLOAD IT. 
If you don't do this, then we CANNOT help.  Not "won't" but "cannot".   We have not been able to reproduce the issue ourselves, even using some of the examples here.  And yes, on the correct version.   So ... without the verifier enable crash dumps, we cannot see what is going on, and CANNOT fix the issue.
 
 
 
Additionally, from the dumps that have already been submitted, we're not seeing anything DrivePool related.  The crashes appear to be SRV2 related. Meaning it's a network share issue, in this case.   And this is why we need the verifier enabled, so we can see more specifically why this is happening. And where it is happening at. 

Well, you'd be able to access the data still, but it will be all over the place.   
So, yes, you'd want/need both products installed.
As for assigning the drive letters, maybe.  If you'd removed them, then it "shouldn't" reassign drive letters on the new system, but Windows can be weird about it.  
Yes.  That's specifically how it automatically repools the data.
Yup, exactly.