Christopher (Drashna)

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. 

Okay, a couple of things...
Clearing the health warnings should come in the near future (these are very new features, and NVMe is VERY different than SMART, even if we do make it look similar).  So... they should be added in the next week or two.
 
For the drive itself, Alex (The Developer) agrees that RMAing the drive would be a good idea here.  Both him an myself would do so, in your situation, honestly. 
Specifically, this is 12 errors that it couldn't correct that have occurred on the drive.  More could cause the drive to fail to boot, or the like.  So, I wouldn't trust the drive.  But that's your call. 
 
 

If this is an upload (looks like it), these are automatically retried, so it isn't a critical issue.
 

It's probably a timing issue, where pinning is attempting to "do it's thing", but the volume isn't quite mounted yet. 

Yup, that's it. 
You can use the "disk usage limiter", but with the revamped removal code, this shouldn't be necessary. 

IIRC, you need to "double escape" the strings here. 
So you need:
    "Override": "C:\\Snapraid\\Balancing.txt"   

You're very welcome for it! 
 
And yeah, the larger chunk size means potentially lower overhead, so it's not a bad idea, if this is for multimedia storage. 

Yes, if you disable Pool file Duplication, it will unduplicate the entire pool, assuming you don't have custom duplication settings.
and when you set it, it will run a duplication pass and delete the extra copy.  
and you should be able to remove the J:\ drive at any time, though. 
Also, assuming that SnapRAID uses a single, large file, you may want to reformat the J:\ drive to use larger allocation units. 

Could you install the RC and retry? 
http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.0.904_x64_RC.exe
There are a bunch of changes, including to the drive removal code, that should make it more robust and less prone to issues.
 
If that version still has issues, then let me know.

That depends on how the encryption works for the container.  Best case, it would corrupt a chunk of the data. Worst case, it would corrupt the entire thing, rendering it unusable. 
But this is why we do generally recommend enabling duplication.  It's when, not if a drives fails or exhibits issues.  Many refer to hard drives as "spinning rust" for this reason, actually. 
Ah, yeah, I can understand that being a but confusing.  Specifically, it deletes the the older part, and then reduplicates the data.  But that should be made clearer. 
(https://stablebit.com/Admin/IssueAnalysis/27743)

Nothing.  It's the default behavior unless another balancer overrides that behavior. 
 
Also, for the most part, there is no need to disable the balancers.  For the most part, they're designed to NOT move data around much, unless there is a very specific reason that could impact your pool. 
To be blunt, the recommendation or idea that they should be disabled for SnapRAID is a misunderstanding of what they do. 
http://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing Plug-ins
StableBit Scanner: This should only move data off of the drive, it serious issues are detected.  At most, this is the only one you'd want to disable. And even that's arguable. Volume Equalization: This only does things if you have multiple partitions/volumes on the same physical disk. This is pretty rare, so most likely, it won't actually do anything.  Drive Usage LImiter (previously File Placement Limiter):  This allows you to limit if duplicated or unduplicated data can be placed on a drive.  If left at the defaults, this doesn't actually do anything.  It would only move data around if you uncheck options for drives, and even then....  Prevent Drive Overfill: aka the balancer most likely to move files.  This triggers if any drive is more than 90% full. In that case, it will attempt to move enough data so that it's 80% full.  If the drives get too full, you may end up with "not enough free space" errors on the pool.  Duplication Space Optimizer: This balancer's sole purpose is to rebalance data to eliminate the dreaded "Unusable for Duplication" space in a pool.  
As you may see, most of these can (and probably should) be left on. 
 
 
That said, if you install the SSD Optimizer or Ordered File Placement balancer, these balancers will change this behavior.  

You need to take ownership of the folder, reset the permissions on it, and then delete it.
Most likely, this is due to the aggravating "System Volume information" folder. 
 
To do this: 
http://wiki.covecube.com/StableBit_DrivePool_Q5510455
This is meant for the whole drive, but the method is actually the same. 
Once you've done this, you should be able to delete the folder. 

If you double click on the drive, and open the "File system health" section, you can reset the status. Click on the button with the green circle to do this.
 
But this will cause it to rescan the drive, sooner or later (depending on the option you chose).

We're glad to hear that you like it!
There is a limit though (8 licenses per product, per activation ID, but that should be plenty for most)
And all of the software includes the ability to deactivate the license on that system, so you can activate it on a new system. 

Posting in a ticket. 
but upgrading to the latest public beta should fix this issue. 

Yup, we highly recommend the "quick and dirty" method.  It works well, and is still valid.  
Nothing has changed in regards to how we store the files, so by all means, do this and buy a license (I may be biased though )
 
My recommendation is to enable duplication though. This does take up twice the amount of space for the data (as each file is stored on two different disks), but it means that if one fails, you don't lose a bunch of files.  And I know you can just re-get them, in many cases... but not always, or not quickly. 

Should be fine, as far as I'm aware.  Unless it's doing something really weird... and even then, the latest beta should handle "weird" better. 
But I would recommend enabling duplication for this data. You DEFINITELY wouldn't want to lose it! 

Well, glad you found us! 
 
I do a full format (which writes 0s to the entire volume), and then let StableBit Scanner run a surface scan. That's it. 
Also, all of my data is duplicated
 
Caveat: I may be biased on the tools.
 

That's not surprising.  It's a common issue, ad likely due to Amazon relying on VSS support, which isn't supported on the pool.

Yes, this is normal.   When connecting or reconnecting a pool that has been offline, it will remeasure the pool, since we don't know if the contents have changed in any way. 

Uninstall the software, reboot, reinstall the software.
 
This should fix the issue.

For StableBit Scanner, this only applies to the v1 product.  The v2 includes the ability to deactive the license. 
 
To do so, open the settings (on the system it's installed, not over remote), and open the "licensing" tab.  From there, you can deactivate the license. 

I'm not sure why the SSDs got filled, but probably because the other drives were too full at the time.  Pretty much the only reason why that would happen.
 
 
That said, I would highly recommend installing the latest beta version: 
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.866_x64_BETA.exe
 
There are a bunch of bug fixes in it, both for the measuring code, but also for the balancing code.  And installing this version will likely outright fix the issues that you're seeing.