Christopher (Drashna)

Install the latest beta version, there are a number of fixes for this stuff, and it may fix the issue you're seeing.
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.798_x64_BETA.exe
 
If not, then let me know

Yeah, definitely simple.  And it works very well.
 
Though, if you really do want an encrypted container (a la truecrypt), then StableBit CloudDrive does still work for that, and well.

No NFS support at the moment.   
 
And yes, the WIndows File Share provider is Samba/SMB/CIFS.

(post moved to the appropriate section).
 
Well, to address the initial question,  just remove the bad drive.  StableBit DrivePool will handle things from there.  If there aren't enough disks to get back to the proper level of duplication, it will warn you.  But reducing the duplication level isn't necessary. 
 
 
As for a "hot spare", this really isn't needed. Once the missing/failed drive is removed, StableBit DrivePool will take care of reduplicating the data.  Additionally, the StableBit Scanner balancer will "effectively" do this, by evacuating the contents of the drive, if it detects unreadable sectors. 
 
Between these two things, there really shouldn't be a need for hot spares, as .... it should treat the entire rest of the pool as "hot spares". 
 
If you want it to work more aggressively, enable evacuation for SMART warnings, as well. 
 
 
 
 
Yeah, this happens so that if the issue is just a bumped USB cable or the like, the data won't get out of sync.  

You're using multiple pools, correct?

If so, then yes, that should absolutely work.
 
 
And since you're not using duplication, no complications from that.  So, full speed ahead then.

This is normal, as the sub folder is NOT inheriting the permissions.
 
You need the check the "Replace all child object permission entries [...]" option when setting the permissions.  
Once you'e done this (it will take a while to complete, depending on the contents of your pool), you should see the "proper" permissions then.
 
 
Also, make sure you add "SYSTEM" here, and give it full control.  This is for a number of reasons, but primarily to ensure that StableBit DrivePool has no problems with duplication or balancing (as the service runs in the system account)

First, thank you for your interest in our product(s)! 
 
 
The default file placement strategy is to place files on the drive(s) with the most available free space (measured absolutely, rather than based on percentage). This happens regardless of the balancing status.   In fact, it's the balancers themselves that can (will) change the placement strategy of new files. 
 
For what you want, that isn't ideal.... and before I get to the solution: 
 
 
 
The first issue here is that there is a misconception about how the balancing engine works (or more specifically, with how frequently or aggressive it is).
 
For the most part, the balancing engine DOES NOT move files around.   For a new, empty pool, balancing will rarely, if ever move files around.  Partly because, it will proactively control where files are placed in the first place. 
 
That said, each balancer does have exceptions here.  But just so you understand how and why each balancer works and when it would actually move files, let me enumerate each one and give a brief description of them. 
 
StableBit Scanner (the balancer). 
This balancer only works if you have StableBit Scanner installed on the same system.  By default, it is only configured to move contents off of a disk if "damaged sectors" (aka "Unreadable sectors") are detected during the surface scan.  This is done in an attempt to prevent data loss from file corruption.  
Optionally, you can do this for SMART warnings as well. And to avoid usage if the drive has "overheated". If you're using SnapRAID, then it may be worth turning this balancer off, as it isn't really needed Volume Equalization.
This only affects drives that are using multiple volumes/partitions on the same physical disk.  It will equalize the usage, and help prevent duplicates from residing on the same physical disk. Chances are that this balancer will never do anything on your system.  Drive Usage Limiter
This balancer controls what type of data (duplicated or unduplicated) can reside on a disk.  For the most part, most people won't need this.  
We recommend using it for drive removal or "special configurations" (eg, my gaming system uses it to store only duplicated data, aka games, on the SSD, and store all unduplicated data on the hard drive)Unless configured manually, this balancer will not move data around.  Prevent Drive Overfill
This balancer specifically will move files around, and will do so only if the drive is 90+% full by default. This can be configured, based on your needs. However, this will only move files out of the drive until the drive is 85% filled. This is one of the balancers that is likely to move data.  But this will only happen on very full pool.
This can be disabled, but may lead to situations where the drives are too full. Duplication Space Optimizer.
This balancer's sole job is to rebalance the data in such a way that removes the "Unusable for duplication" space on the pool.   If you're not using duplication at all, you can absolutely disable this balancer  
 
 
So, for the most part, there is no real reason to disable balancing.  Yes, I understand that it can cause issues for SnapRAID. But depending on the system, it is very unlikely to.  And the benefits you gain by disabling it may be outweighed by the what the balancers do.  
 
Especially because of the balancer plugins. 
 
 
Specifically, you may want to look at the "Ordered File Placement" balancer plugin.  This specifically fills up one drive at a time.  Once the pool fills up the disk to the preset threshold, it will move onto the next disk. 
 
This may help keep the contents of a specific folders together.  Meaning that it may help keep the SRT file in the same folder as the AVI file. Or at least, better about it than the default placement strategy.  This won't guarantee the folder placement, but significantly increases the odds.
 
That said, you can use file placement rules to help with this.  Either to micromanage placement, or ... you can set up a SSD dedicated for metadata like this, so that all of the SRT and other files end up on the SSD.  That way, the access is fast and the power consumption is minimal. 

Well, StableBit DrivePool won't rebalance the pooled data onto the drive automatically.  This would only happen if one or more of the drives are more than 90% full, if the duplication was not optimal (eg, if you have "unusable for duplication" space), or there is another problem disk. 
 
 If you want to force the software to rebalance to use the drive, then you can install the "Disk Space Equalizer" balancer plugin. This will rebalance the data to equalize disk usage. 
 
 
That said, you may want to try remeasuring the pool. Any "grey" data is generally "other" data and not considered pooled. 

Duplication and balancing activity are not shown in the StableBit DrivePool UI, only access "through" the pool are shown.  
 
This is a common request though, and may be added in the future. 
 
 
 
As for the speed itself, this is entirely normal.  We use a background priority to duplicate and balance data, so this won't be as fast a a straight file copy.  Additionally, because there may be a lot of small files, this can (will) reduce the speeds of any transfer in general. 
 
There are some advanced setting that can increase the priority (and thereforce may increase the speed), but this may impact overall performance. 
 
You can do this temporarily, in the UI, by clicking on the ">>" button at the bottom (when it's balancing/duplicating). 
Or you can set this permanently, by editing the advanced config file.
http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
Set "FileBalance_BackgroundIO" and/or "FileDuplication_BackgroundIO" to "false" and reboot the system. 

This is most likely a "bug".  Specifically, some drives ... have some weird issues with how the data is reported.  It causes issues for the surface scan in released versions, unfortunately.
 
Please try this version and rescan: 
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.2.3126_BETA.exe
 
To rescan, double click on the drive in question, click on the fourth button on the left side (with a green circle), and select "mark all as unchecked" (or something like that). 
 
This should complete "properly". 

I ... thought I'd posted here!  I'm sorry to for not doing so. 
 
 
That said, Alex (the Lead Developer) has added the ability to "mount disconnected" drives, so that you should be able to access the data now. 
 
that said, data *may* be missing here, if it wasn't all downloaded.  So this is explicitly for troubleshooting and data recovery purposes ONLY. 
 
http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.1.877_x64_BETA.exe

Correct, it's one license per PC.  Additional licenses are only $15 each though.  So you can get them for "dirt cheap"
 
That said, you DO NOT need a license if you are solely using the software for remote control functionality. 

For now, that beta should be fine. 
 
THough, hopefully, we should have another public beta for StableBit Drivepool out soon (and then a release build sometime after that). 

Sorry for the long delay,
 
This should be fixed with the latest beta versions. 
 
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.754_x64_BETA.exe
 
Alex (the dev) beleives that the issue was fixed here: 
https://stablebit.com/Admin/IssueAnalysis/27103

Well, the "quick" solution would be to uninstall the release version, install an older version and then create the drive. Then upgrade.
 
that said, this may not fix the issue, as chunks showing up as photos may still occur in the newer version.  Encrypting the drive may further help with this, but it may not, as well.
 
To be blunt, there is a reason we discontinued support for ACD, and we don't recommend using it for any important data. PERIOD.
 
As for re-adding support, this depends ENTIRELY on Amazon, as we've tried repeatedly to make the provider to work, and work within their undisclosed limits.   At this point, all we can do is keep on asking them to approve us for production use ... which we've been doing, to no avail. 
And no, we don't plan on completely dropping it, as there are people still using drives (like yourself).  We don't want to leave them in a situation where they cannot access their data. 

The simplest way to do this is to create a new drive and sync them.  DrivePool isn't necessary, but if you want to keep the contents up to date and synced, then pooling the drives and enabling duplication is going to be incredibly simple.
 
And yes, you can use multiple accounts here, if you want. (ideally). 

Okay, then this may not be directly related to StableBit DrivePool. then. 
 
Either way, are you able to reliably reproduce the issue, or does it happen seemingly randomly? 
 
Also, does this happen when deleting folders? Or otherwise cleaning up stuff on the disk? 
 
Also, does this only happen on the drives in on the Syba controller? 
 
Also, it may be a good idea to test the internal beta build, as there are a number of fixes that may address this (such as the folder deletion). 
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.742_x64_BETA.exe

Do not run "/scan".   This actually skips the bitmap errors, for the sake of keeping the disk online.
 
You need to run "chkdsk d: /f", in this case, rather than "/scan". This will identify and fix the issues.

The 429 response code is a throttling response.  
 
This means that there isn't anything we can really do.   We do automatically retry when we get these sort of errors, and we back off exponentially (eg, wait longer and longer to retry).  
 
But basically, Amazon's servers are actively refusing to return the data that we're requesting.  There is no fix or work around here, because this is ENTIRELY a server side issue.  It's not an issue with our software (especially as we're not the only ones experiencing this issue. RCLONE and other cloud utilites are seeing this with Amazon Cloud Drive.  
 
THis is likely due to Amazon's servers getting "hammered" and them not able to keep up with the requests.  Which means this is an infrastructure issue.... or "a consequence of using a consumer grade cloud provider" (which is a shitty response....). 
 
 
This has happened a couple of times in the last couple months, and usually this clears up in a couple of days.  It's a shitty situation, as "waiting" is a horrible response.  But we're completely at Amazon's mercy here.  
 
 
It's issues like this, is why the Amazon Cloud Drive provider is considered an experimental provider.   
 
Hopefully, if they re-approve us for production status, this will stop occurring, but I seriously doubt that (RCLONE and the like *are* approved, IIRC).  

Yes. 
 
When you change the settings, StableBit DrivePool will run a duplication pass, and unduplicate data, as necessary.  This basically means that it will delete the unneeded copies. 

Reboot the system.  See if that helps. 

This. 
 
It's not harmful or anything. It's just letting you know that the drive was created with a pre-release (beta) version of the software. 
 
You can safely ignore it, as it won't impact the drive. 
 
That said, if the drive was created with a much older version, you MAY want to consider recreating the drive and migrating the data over, because there have been a bunch of changes and improvements since some of the older builds. 
But this is not mandatory, nor necessary.  It is completely optional, on your part. 
 
http://blog.covecube.com/2017/03/stablebit-clouddrive-1-0-0-854-rc/
 

Well, you found a race condition (eg, a very rare set of circumstances). 
 
This issue should be fixed in the latest build:
http://dl.covecube.com/CloudDriveWindows/release/download/StableBit.CloudDrive_1.0.0.858_x64_Release.exe

If you've set the settings on the main page, then you should be file. The other stuff shouldn't need to be messed with.  But you can uncheck all of the balancers, if you want. 

Yes.
 
however, the drive has to be non-removable, and cannot be a "dynamic disk".