Christopher (Drashna)

Honestly, not enough information. Missing stuff like the balancing ratio reported on the pool, etc. That said, setting the balancing ratio to 100% should make it balance very aggressively (when/where it needs to). But the default balancing settings shouldn't move the data around except for in specific edge cases. Such as the disks being over 90% full, there being "unsuable for duplication" space reported on the pool, etc. That said, could you open a ticket at https://stablebit.com/contact and after doing so, run the StableBit Troubleshooter, using the contact ID number from the ticket?

I mean, by default, it kind of tries to do this. New files are placed on the disk with the most available free space. If you have multiple disks with the same amount of free space, it should kind of round robin the placement (though this heavily depends on the file sizes).

Depending on the exact chain of events, this may be normal. When balancing or changing duplication, empty folders are not pruned. So if the files were on that disk but moved off, you will likely see empty folders. As for the recovery tools seeing the files, that may be normal. Files deleted from a disk, even when done by the balancing/duplication engine will still leave the data on the drive until those sections are needed. This is actually how recovery software is able to get that data. So if duplication was enabled, it soulds like you should be fine. However, you can recover the data, and remeasure the pool. It will check the duplication level against the number of copies, and adjust things accordingly (eg reduplicate data, remove extra copies, etc).

That is very odd, especially since it appears that the empty file is about the correct size, but filled with empty characters. If you continue to see this behavior, there may be other issues on the system.

Just a note, Microsoft removed all support for ReFS on removable drives. Also, I would recommend against using ReFS except for with a properly configured Storage Spaces array (as recovery only works in that setup).

To add to this, yes, the progress is saved. The "scanning" percentage is based on what needs to be scanned currently, not on the whole disk. Which can be misleading. That said, you can see how the drive is tracked here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map And you may note that each sector has a date when it was last scanned. Each region is tracked, and different regions on the same disk can and will have different dates and times. Over time, this should actually help the software to "learn" when to scan the drives, by picking times when they are much less likely to be throttled.

There is also the "archive removal" option. And in a pinch, the "dpcmd" command line tool has a "ignore-poolpart" command that marks the disk as removed.

It should be noted that when adding a new disk, StableBit DrivePool does NOT rebalance the data in the pool to use the new disk, immediately. This is ... unnecessary and over time leads to a lot of unneeded/unnecessary writes/moves. Over time, it will use the drive, as new files are placed on the drives with the most available free space (and the new drive is likely to be the primary candidate for that). However, if you are insistent on rebalancing the data to the new drive, you can use the "disk space equalizer" balancer. It is disabled by default, but enabling will rebalance the data on the pool so that it's similar usage between all of the drives.

Also, things like the balancing ratio, and when to balance will influence how often it balances the data too.

You absolutely can use StableBit DrivePool in a VM. There shouldn't be any issues with doing so, if you're passing the whole disk through. The only caveat is that you may not get SMART support for the drives inside of the VM, but this depends on hypervisor and how things are configured.

Has also been flagged in a ticket, and we're looking into handling.

If it helps, iDrive E2 uses an S3 compatible endpoint, which should be the best option. I'm not sure about the pricing though (I haven't really looked close at it).

As I've been using linux more and more, the main/only thing keeping me on Windows is our software (and well, gaming, but even then ... valve has made that so much easier)... so I feel you. However, it's a complex issue. And that's not even counting distribution of the software... But at this time, no. Sorry.

For the mount points, at any time that the drives are connected to the new system. Personally, I would recommend changing the volume labels for the drives to match their locations/IDs, so that it's easier to identify the drives. Also, if you're using StableBit Cloud, it should sync the settings for the pool in StableBit DrivePool, and should sync the scan history and settings for StableBit Scanner, on the new system.

If this was the case, then it may be that the "SYSTEM" account permissions were changed or corrupted. This accound should have full control on the pool. This is the account that the service runs in, and uses for accessing the pool for balancing, duplication and drive removal. The "forced damage drive removal" option should skip problem files and continue with the removal, though.

For reference, you can manually merge pools, if needed. https://wiki.covecube.com/StableBit_DrivePool_F1655

It might be worth running this on both systems: https://wiki.covecube.com/StableBit_DrivePool_Q7420208

the pool does support adding multiple drive letters to a single disk (well, really, it's windows thing, and is supported). As for the delete/undo, the pool does support the recycle bin, but that depends on the specific settings you have configured.

Also, the system Event Viewer can give you an indication for why it failed. In fact, with support tickets, it's one of my first go-tos for troubleshooting weird issues. If you're seeing a lot of disk errors or the like in the event viewer, it can indicate an issue. Also, the burst test in StableBit Scanner can help identify communication issues with the drive.

welcome!

That is the pool drive. The 2048GB size exactly, that is the giveaway, and the "COVECUBECoveFsDisk_____" is just confirmation of that. (that's the driver name). I'm not sure why that happened, but uninstalling and reinstalling StableBit DrivePool can also fix this. And the drive is always reported as that size, in that section of Disk Management. But elsewhere it shows the correct size.

That's a hard question to answer. SSDs tend to be fast, including in how they fail. But given this, I suspect that you might have some time. However, back up the drive, for sure! Even if you can't restore/clone the drive, you'd be able to recover settings and such from it. But ideally, you could restore from it. And cloning the drive should be fine. Most everything is SSD aware anymore, so shouldn't be an issue. But also, sometimes a clean install is nice.

Would you mind opening a ticket about this? https://stablebit.com/contact/ This is definitely diving into the more technical aspects of the software, and I'm not as comfortable with how well I understand it, and would prefer to point Alex, the developer, to this discussion directly. However, I think that some of the "twice" is part of the upload verification process, which can be changed/disabled. Also, the file system has duplicate blocks enabled for the storage, for extra redundancy in case of provider issues (*cough* google drive *cough*). But it also sounds like this may not be related to that.

Make sure that you're on the latest release version. There are some changes to better handle when the provider is read only (should be at least version 1.2.5.1670). As for the empty chunks, there isn't really a way to discern that, unfortunately. If you have the space, the best bet is to download the entire directory from Google Drive, and convert the data/drive, and then move the data out.

In general, this shouldn't happen, but certain scenarios seem to trigger this more. Namely the large semi-annual updates for Windows 10/11. But if you do seee this happening, open a ticket, and then run the StableBit Troubleshooter, and let us know when it's complete.