Christopher (Drashna)

Unfortunately, no, there isn't a way to do this, that wouldn't potentially cause serious issues.

https://stablebit.com/DrivePool/Download Once you click the checkbox, there is a "what's new?" link that will take you to here: https://stablebit.com/DrivePool/ChangeLog?Platform=win Or you can see the beta changelog here: https://dl.covecube.com/DrivePoolWindows/beta/download/changes.txt

If you're using the latest release, you shouldn't need to install it, it should be pre-installed. Otherwise, you need to install it, and then open the balancing settings in StableBit DrivePool. You'd see them here: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing Plug-ins

I'm not exactly sure what you mean. Also, there are some command line utilites that deal with getting information about the pool, but would need some processing to be able to be displayed in a meaningful way. For instance: [HOWTO] File Location Catalog - General - Covecube Inc. check-pool-fileparts - Nuts & Bolts - Covecube Inc.

Have you seeded the top level pool? If not, then you may need to do that. https://wiki.covecube.com/StableBit_DrivePool_Q4142489 Also, don't use A:\ for the drive letter. Windows has some hard coded behavior that expects A:\ and B:\ to be floppy drives. This includes querying those drive letters frequently, which will keep the pool (and all the drives in it) awake.

This depends on a number of factors, but over time, it should do this, actually. Specifically, by default, StableBit Scanner should only be scanning one disk per controller. If you have multiple controllers, then that will increase the number of drives that scan at one time. Also, make sure that you have enable the throttling options that you want. You can see these here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Throttling Also, the heat tab in the settings have some additional settings that may help: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Heat But if you set a work window, that will reduce the amount of time that the drives can be scanned, and will help spread out when the drives get scanned, over the course of the month. And this is because, the 30 days isn't from the last time it was scanned, it was from the last time a specific region of each drive was scanned.

Have you tried manually running a CHKDSK pass on the disk in question? If not, try doing so and remeasure the pool. Also, the files are located in a hidden "PoolPart" folder on each drive, which should be accessible. See if you can reproduce the access issue on the drive in question. If you can, then it may be an issue with the drive that StableBit Scanner hasn't had a chance to pick up yet (the default is for 30 days, in most cases, so something may have happened within that window)". And if neither are successful, then open a ticket at https://stablebit.com/contact/

were you backing up the cache?

correct. Some of the drive "geometry" can't be changed after it's been created. You would have to destroy the drive and recreate it to change those settings. Also, some of it can be changed, but the process is dangerous or requires reformatting. So it may be simpler to just recreate, since you could have both running at the same time.

That's very unusual, and I haven't seen anyone else report it. If you could, open a ticket at https://stablebit.com/contact

that's rather odd. Could you open a ticket about this at https://stablebit.com/contact?

To clarify, StableBit DrivePool doesn't use the drive letters or mount points. It uses the volume ID for the disks. So you can change how the drive is mounted without any issues. Personally, I prefer mounting the drives to folder paths, as that hides them, but still allows them to be accessible.

There are some hidden by default, already, but that's because they're experimental. But I don't see a reason why this couldn't be added. StableBit Scanner uses Telerik controls, which we stopped supporting/using, since they come with a bunch of their own issues. StableBit DrivePool and StableBit CloudDrive use entirely custom implementations, and all native WPF controls, because of some of the issues we've had with telerik controls. So, pretty much the opposite. Eg, StableBit Scanner is the older product (the first, actually).

Yeah, this would be the best/simplest option, as you'd need to move the data off of the drive anyways, to change the cluster or sector size.

It's not currently supported, but may potentially be possible. The issue is that it then becomes harder to access the pooled data when this happens.

There isn't any documentation for it (other than snippets posted in the forums), because the dpcmd utility is not meant for normal usage and bypasses a number of normal checks and procedures. However, the utility itself will give a basic description. But in this case, "dpcmd unignore-poolpart poolpart.xxxxx x:" is what you want.

There isn't a publicly accessible API for Apple iCloud, so support is very unlikely. We avoid 3rd party implementations, as well as reverse engineering the API, because these are finicky solutions that may require a lot of updating due to hostile changes.

This should cover that in a bit of detail: https://stablebit.com/Support/CloudDrive/Manual?Section=Recovering from Errors But basically, it depends on how much data was left to upload. And which data. In essence, it's like power loss before the cache has been written to disk, which can result in data loss.

Try setting the balancing ratio to 100% and see if that helps. Otherwise, could you open a ticket at https://stablebit.com/contact ?

The 100gb has been there for a long while, TBH. And that's been the default for it since the start. And by a long while, I mean since the DrivePool v1 days> (so ~2011). Eg, back when drives rating in TBs were at the high end, for the most part. You and disable the option or set it to something more reasonable for your setup. But it sounds like unchecking it may be what you want here.

All of our installers are digitially signed, and I've verified that this is still the case (eg, the installers are clean). It's a false positive, because we're a small company. So it's software that isn't downloaded as much, so it's much more likely to get flagged due to heuristic/predictive protection. For instance: https://www.virustotal.com/gui/file/0e7f2f56af412d5ab5c2f185af0ea371ce20a68b901bba4dfafc2eb3f3812b1d

correct, internal operations (balancing, duplication, measuring) are not reported there. Only activity it reports is what happens through the pool drive.

For balancing and duplication operations, the files are copied to a temp folder, and then renamed when the operation completes. this ensures that even if an interruption occurs, that the files are intact, whole and not corrupted. And yeah, that's probably a good way to set things up.

It should be simpler, yes.

Nope. The surface scan is a sector by sector scan. The file system scan is an api call for CHKDSK. So unless you're using the file recovery option, it should not be reading files.