Christopher (Drashna)

Are you sure that this was with StableBit DrivePool, and not Drive Bender?  
The reason I ask, is that we don't disable duplication, and we don't use the term "mirror" for file protection (it's always duplication).  
And because of the section in the licensing FAQ, and experience: 
https://stablebit.com/Support/DrivePool/Licensing
 
This is a topic that has come up from time to time, and we do have plans on if this were to happen.  Obviously, we don't want it to ever happen, but the future is uncertain. 
I believe the plan in that case was basically, disable the licensing altogether, and stop support completely for the software.  

To clarify, Windows 7 (and 8,) are no longer supported by Microsoft, and no longer receiving updates.
We follow suite with the Microsoft support lifecycles, since we can't ensure stability of the OS outside of the support lifecycle. Additionally, key components (such as .NET Framework and Visual C++ runtimes) may not be supported, anymore.  Especially in the case where we need/want to update this components. 
However, we haven't done anything to explicitly disable support for these OSes, so they may still work just fine.  However, the longer it's been since they've exited the support lifecycle, the more likely you are to have issues.
 
Additionally, Windows 10 leaves extended support Oct 2025. Yay....

Due to an unexpected glitch while updating the site, the Contact site is broken.
 
We're working on fixing this issue as quickly as possible.
 
 
We have fixed the issue with the Contact site. 
However, if you experience any issues with it, please let us know know right away.
You can do so, by contacting me directly at "christopher@covecube.com".
Just let us know what the issue with the site is, and what the issue that brought you to the site was.
 
 
We apologize for any trouble that this may have caused.

There should be absolutely no issue with doing so.  
 
Neither product does anything that takes exclusive control over anything, so it should be safe to run both products concurrently. 
 
 
 
 
What are you trying to monitor specifically, here? If you don't mind me asking.

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. 

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. 

I'll post it here too.  
There is a fix in the latest betas involving memory corruptions of file IDs.  
However, ... the issue may also be the wrong API being used: 
 
 

To clarify (and make it simple to find), here is Alex's official definition of that "Other" space:
 
 

Folks, thank all for the ideas. I am not neglecting them but I have some health issues that make it very hard for me to do much of anything for a while. I will try the more promising ones as my health permits but it will take some time. From operation and the lack of errors during writing/reading it seems that I am in no danger except duplication won't work. I can live with that for a while.
Keep the ideas coming and, maybe, I can get this mess fixed and report back which tools worked for me.
I am making one pass through my pool where I remove a drive from the pool, run full diagnosis and file system diagnosis on that drive then I re-add it back to the pool. When completed that will assure that there are no underlying drive problems and I can proceed from there.
Thanks to all who tried to help this old man.  

You and your fibre broadband bubble
Fair enough, thank you for your response. We'll wait for a message from Alex.

Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. 
That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads),  the writing has been on the wall for a while.  

No.  There is some very hidden data that doesn't copy over, really.  But if the new drive is added to the pool, you could copy the contents of the PoolPart folder on the old drive to the PoolPart folder on the new drive.   Just make sure you remeasure after it's done. 

Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that. 
That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads),  the writing has been on the wall for a while.  

Agree.  I use Link Shell Extension, as well.  It is super useful! 
 

Is there a reason the "not more often than every X hours" option doesn't work for you? 

You may need to do this: 
https://wiki.covecube.com/StableBit_DrivePool_Q2150495

If you want to use the SSD Optimizer and use the rest of the pool,  the "simplest" option may be to use hierarchical pools.  Eg, add the SSD/NVMe drives to a pool, add the hard drives to another pool,   and then add both of these pools to a pool.  Enable the SSD optimizer on the "pool of pools", and then enable the balancers you want on the sub-pools.  

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. 

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).

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).   
 

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. 

Perhaps you could ask Stablebit for an extension of the trial, to test clouddrive with idrive again, via the contact form?

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.  

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.  

beta version: 
* [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.