Christopher (Drashna)

This. Reinstall or repair is the easiet option in this case. Though, to clarify, if yu haven't manually reset the settings or deleted the folder for DrivePool in the ProgramData folder, the settings should be retained.

Well, there have been improvements made to it in the meanwhile. But if you mean feature requests, that's usually what we do. We're a small company so constantly developing on all of our products at the time is tough. We try to get to bug fixes fast, but new features tend to come in batches/waves

Mostly right, yes. Though, if you have drives on your account these will show up, but as "in use" drives. You can force mount them on the new system. You'll want to run a CHKDSK pass on the drives, in this case. And once the drives are mounted on the new system, and StableBit DrivEpool is installed, it shold see these drives as pooled drives (if they were pooled) and recreate the pools. From there, add disks to the pool, and it should "just work" for you. Or copy files from the CloudDrive pool to a new local pool. In this case, contact us at https://stablebit.com/contact and we'll take care of it.

Yup. Specifically, it uses the Volume ID for the drives, which shouldn't change ever, normally (cloning the drive *may* change it, though). So DrivePool is very resilient about moving drive around, even to other controllers (as long as they show up correctly).

Unfortunately, we see this from time to time. I think it's something to do with Invision's security stuff

Depends on what you're trying to do. Personally, I prefer to keep all drives internal, as USB and eSATA are finicky. There are some computer cases that have a lot of drive bays that can be used. But server chassises may be the best option. You can find 24-36 bay enclosures, and host all of those drives with a single controller or two. (HBA controllers, specifically)

Good catch, and yeah, that could definitely cause issues. And yeah, the Pool doesn't support hardlinks, either. unfortunately, plex's database/cache likes to use them heavily. If you want to use them, then you'd need to change the folder location for that stuff to be outside of the pool.

In that case, a CHKDSK pass of the pooled disks (not the pool) may help.

Welcome!

If you use StableBit Cloud, it should actually do that. Also, if you copy the contents of "C:\programData\StableBit DrivePool\Service\Store\JSON" to the new system, that should copy most (if not all) of the settings. Some UI settings may be lost, but balancing settings and the like should be retained, this way.

The simplest way to do this may be: Add the 7x HDDs to a pool, then add that pool, and the OneDrive cloudDrive disk to another. Seed the data from the local disk pool to the "hybrid" pool. Use the "Drive Usage Limiter" to not allow unduplicated data on the cloud drive disk, but allow duplicated data on both. Enable duplication for the folders that you want on the OneDrive disk. That depends on what you mean. StableBit CloudDrive creates and uses a folder on the account that was authorized. And it doesn't read the existing data on the provider, at all. it stays there and isn't touched by our software. if you want to add it to the drive, you'd have to download and copy it. Conversely, you can't access files placed on the drive on the provider, directly, as the files themselves are not stored there.

StableBit DrivePool doesn't touch any files outside of the hidden "PoolPart.xxxxx" folder on each pooled drive. So, using a folder that isn't on the pool, and is outside of that folder , you should be absolutely fine, and the files shouldn't be touched, at all. And this is absolutely supported. If the files are getting corrupted, then likely, it's something between the data on the drive, and OneDrive's web service. If you have any antivirus software or disk utilities installed, it is possible that they're intercepting them and causing issues. Additionally, if you're using a proxy or VPN service, it could be those that are modifying the data in transit.

Thanks!

Yeah, it's ... manufacturer fun. SMART really isn't a standard, it's more of a guideline, that a lot of manufacturers take a LOT of liberty with. NVMe health is a *lot* better, in this regards (it an actual standard).

Listed? it doesn't really matter. Ideally, it should be the only balancer enabled (or at least, it and the StableBit Scanner balancer). But the order of the balancers is the priority (with the top/#1 being the most important).

Ah, okay, I missed that part! Also, "fun" fact, the repair mechanism in Storage Spaces requires ReFS, and I believe that the integrity checking for Storage Spaces is only enabled on critical file system data (not the whole drive). So ... yay.... Also, we definitely recommend having StableBit Scanner (or something similar) on the system, as that will detect and let you know if there are issues on the drives, including read errors. It's not quite "repair", but it will use the balancing system of StableBit DrivePool to evacuate the data off of problem drives.

That would be normal, actually. As for "unauthorized" changes, the issue is how that would be tracked. It basically leads into the same issue. And it's not just that it's checking the one disk, but it needs to compare the duplicated contents to make sure they match, too.

IIRC, we do store the times in GMT-0, and the times *should* be localized. But I cold be wrong about that. If that's not the case, could you open a ticket at https://stablebit.com/Contact and let us know there.

Also, should be noted that it's a good idea to disconnect the pooled disks. The reason is two fold: To prevent the accidental installation of windows on that drive To prevent Windows from installing the bootloader on that drive (the number of times I've experienced this ...) And yeah, once the system is reinstalled, the software reinstalled and the pooled drives reconnected, it will automatically rebuild the pool from the available disks. Duplication settings are stored in the pool's folder structure, so that will be maintained. However, balancing settings won't be retained and will require that you reconfigure them on the new installation, if you need them setup.

Heads up, if you're using the Ordered File Placement balancer with the File Placement rules. then you need to make the following changes on the "Einstellungen" tab. UNCHECK "File placement rules respect real-time file placement limits set by the balancing plug-ins." CHECK "Balancing plug-ins respect file placement rules." UNCHECK "Unless the drive is being emptied."

Yup. This is an issue we see from time to time, and it's a known issue with Windows (not our software). Specifically, the issue is that ... sometimes, windows will not mount a volume if it doesn't have a letter (or path) assigned to it. Fortunately, this is a dead simple fix: https://wiki.covecube.com/StableBit_DrivePool_F3540

You might be able to use the file placemeent rules to do this. Eg. "/*/*/*" However, I'm not sure that this will work.

You mean the Load Cycle Count, specifically?

Yeah, wdf_violation is likely wdf related, and generally a removable device issue. Eg, the USB controller is probably freaking out. And as for cases, used server chassis' may be the way to go.

I think that file placement rules could do this, but ... it's not really meant for what you want, I think.