Christopher (Drashna)

Sync.com cannot be added, as there is no publicly documented API. Without that API, and a way to officially read and write files/data on the provider, there is no way to support it.

No, no changes have been made, in this regards.

That's positiviely bizarre. Though, I can't really say that it's surprising, unfortunately.

YOu can use the "Quick settings" to reset these values. And the different profiles do have slightly different profiles. As for the settings, and what they do, there is some basic information about that here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Scanner

Setting the balancing ratio to 100% may help. But to be blunt, the SSD Optimizer and the Disk Space Equalizer balancer are at odds. The Disk Space Equalizer wants to fill every drive, equally, but the SSD Optimizer wants to clear out several of the drives.

There isn't a set amount of time, because tasks like balancing, duplication, etc run as a background priority. This means that normal usage will trump these tasks. Additionally, it has the normal file move/copy issue, estimates can jump radically. A bunch of small files take a lot more time than a few large files, because it's updating the file system much more frequently. And for hard drives, this means that the read/write heads are jumping back and forth, frequently. But 6-12 hours per TB is a decent estimate for removal.

could you open a ticket at https://stablebit.com/contact about it?

Glad to hear it!

That's definitely not normal, but I think you've already opened a ticket for this, as well.

StableBit Scanner won't repair the drives. Eg, it never writes to the drive (the exceptions being the settings store, and if you run file recovery) That said, it will rescan the drives, and update the results. The important bit here is the long format, though. This writes to the ENTIRE drive, and can/will cause the drive to reallocate or correct bad sections of the disk. As for not correcting right away, it has to run the scan again, and unless you manually cleared the status, it won't do this right away, but will wait for the 30 days (or whatever it is configured to)

No. Hardlinking doesn't work on the pool drive, at all, and never will. The hard links are an object/feature of the volume, not the disk, and require that all instances of the file be on the same *physical* volume. They work on StableBit CloudDrive, because it doesn't emulate the filesystem the way that StableBit DrivePool does. It handles things on a block level (below the file system, basically), and never directly deals with the file system. Because of this, just about anything you can do on a normal disk, you can do on the StableBit CloudDrive disks. But if they're pooled, then the pool's limitations still apply (at least to the pool drive).

Could you open a ticket at https://stablebit.com/contact for this issue?

Correct. Duplication is inheritted unless explicity set. Enabling pool file duplication enables it for the root, and everything else gets inherrited. And when you change it, it checks to see which files need to be duplicated or unduplicated (the "checking duplication" part that you may have seen). So, it shouldn't mess with the existing data.

As shane said, please contact us. Also, even with the trial expired, the software will continue to work, but the upload is incredibly throttled , so you can get data off but makes it impracticle to use.

Yes. This has the effect of telling the virtual drive that it is read only, and that files cannot be written to it. Otherwise, it may start filling up the cache with new data.

In general, the Microsoft store apps have some additional/unusual storage requirements, and may not work on the pool. This includes the xbox applications.

Just a heads up, the bitlocker detection can cause the drives to be awakened by WMI. You can disable this functionality: https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings And it is the example too. Also, make sure that you're not using A:\ or B:\ as the drive letter, as windows has hard coded behavior to ping these drive letters, under the assumption that they are floppy drives. And if you have StableBit Scanner installed, enable the throttling option for SMART.

The poolpart.xxxx file ... shouldn't be a file. It should be a folder, with all of the content. That it is showing up as a file shows that there has been file system corruption, which means recovery will be needed, and shane has covered all of that already

Yeah, we're looking at a few providers. No details yet, though.

Deleting files from the drive doesn't delete the data on the drive. Shis is because the drive acts like a normal, physical disk, and the file system just unallocates the data (eg, the file is a pointer to that data, deliting the file just deletes the pointer, but leaves the data). This is part of how and why data recovery works, and this also applies to the CloudDrive disks. You'd need to use a utility like "sdelete" that zeros out the data, too.

Still the same issue with the CLI tool. It's not an API, and while the API could be reverse engineered, we have no interest in doing so.

Internet is hard. Stuff like your ISP, distance from nodes, etc can all effect the speeds. That said, try 10 download threads, 10MB for the minimum download size, and enable prefetching (with 1MB/70MB/120s), and see if that works better for you.

First, I'm sorry to hear about your drive, as that is never a pleasant experience. You may be able to use "dpcmd ignore-poolpart" to eject the drive from the pool. This marks the drive as removed, but doesn't move any of the files off of it, and causes the drive to show up as "missing" in the UI. This does require writing to the drive, to write the tag that marks it as removed. Once the drive is ejected, you can manually move the files over. The poolID for the drive is the name of the hidden "PoolPart.xxxx" folder on the disk (with or without the PoolPart part).

For reference, the beta versions have some changes to help address these: .1648 * Fixed an issue where a read-only force attach would fail to mount successfully if the storage provider did not have write access and the drive was marked as mounted. .1647 * Fixed an issue where read-only mounts would fail to mount drives when write access to the storage provider was not available. .1646 * [Issue #28770] Added the ability to convert Google Drive cloud drives stored locally into a format compatible with the Local Disk provider. - Use the "CloudDrive.Convert GoogleDriveToLocalDisk" command.

If you're using automatic unlocking (weth the system disk encrypted too), then you shouldn't. Otherwise, you may run into issues, yeah. (restarting the service after unlocking the drives may work, though).