Christopher (Drashna)

In some cases, resetting/Rebuilding WMI can fix weird issues. "Winmgmt /resetrepository" from an elevated command prompt and rebooting the system can help.

To be blunt, this doesn't sound like it's an issue with duplication, at all, but rather is an issue with NTFS permissions. Worst case, you can reset the permissions on the whole pool by reapplying them: https://wiki.covecube.com/StableBit_DrivePool_Q5510455

2.3.11.1663 should be safe for people with existing pools. However, if you're an older version ow Windows, then you may need to use 2.3.8.1600 due to signing issues. As for folder enumeration issues, there isn't a specific fix for this, and ChatGPT is *not* a reliable source of information, ever. LLMs are incredibly prone to "halluciating" (a nice way to say "making shit up with no basis in reality"). And the absolute latest release is: https://dl.covecube.com/DrivePoolWindows/release/download/StableBit.DrivePool_2.3.12.1680_x64_Release.exe If you're having issues on the newer versions, please open a ticket at https://stablebit.com/Contact

Depends on what you mean by local notifications. Email, SMS, and mobile notifications should be available. As well as Speech powered by TTS in Windows. As for system to system notification, no, that is not supported.

StableBit DrivePool expects all of the pooled disks to be kept togethor. You can't just grab one drive from the pool (well you can, but the system will complain about the now missing disk). That said, you can "seed" the pool, eg move the files into the pool structure without having to copy the files over and without losing the folder structure: https://wiki.covecube.com/StableBit_DrivePool_Q4142489 And the poolpart folders you mention are hidden by default. We don't recommend accessing or manipulating files from these folders normally, as it can cause issues long term. But for initial conversion/adoption, the seeding process is fine (since it's a one time thing, and is done).

No, the system in question needs to be connected to the internet, as the statistics and communication happens between the software and the service directly. It does not relay through other devices on the network. The "other systems on your lan" is meant for the local remote access. While the page is for StableBit DrivePool, the "remote control" function is the same: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Remote Control Details

Welcome!

Then the "balancing immediately" and checking the "but not more than once ever X hours" option may be better, as this should balance the data periodically and be a bit more aggressive than the "balance daily" option. However, you may still end up with other drives being active, depending on how much data needs to be moved, and how long that takes. Eg, there may not be a good solution that will prevent the hard drives from being used. It may be simply a matter of finding a balancing that works while making compromises.

If this is an inplace upgrade: Uninstall, upgrade, reinstall. If this a clean install of windows: deactivate, wipe+reinstall, install StableBit DrivePool, reactivate.

Yes and no. The scan themselves are limited by the drive's speed, other activity on the drive, other activity on the same controller, etc. But, in general, should be a consistent speed. That said, the automatic scans (or really any scan after the initial scan) won't be scanning the entire disk. StableBit Scanner keeps track of what sectors have been scanned, and when they were last scan. Manually triggering a scan will still abide by the scan history and scan settings (eg, it won't scan sectors that were scanned less than 30 days ago, assuming the interval for scanning is set to 30 days). You can see this sector map, as well as the "condition" of the drive here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map Also, on the left side of the sector map, there are 4 buttons (the 4th may be hidden due to sizing). But you can reset the scan history for the entire disk (using said 4th button), and rescan the entire disk. However, because of how the sector map works, over time it should scan when the drives aren't in use as much, and should break it up over the month. Resetting the sector map will reset this "learning" too.

Absolutely: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing Settings Change it to not balance immediately, or increase the "not more often[...]" value.

Unfortunately, StableBit Scanner doesn't support SAS drives, so doesn't manage them. That said, the StableBit Scanner plugin is reading the disk status from WMI, so if you "jerry-rigged" up something that read from the SAS health information and created the proper structures in WMI, you could fake it. (however, the information is very basic, but at least that's simpler to manipulate)

As above, by default, StableBit Scanner should only be scanning 1 disk per controller. This can only be changed by getting into the advanced settings. You can see how StableBit scanner sees the controllers by right clicking the column header in the UI and selecting "By Controller". If you do this, do you see all of these disks on different controllers, or on one controller?

It would also be worth double checking the sector map, as that may be updating. So the percentage may be based on the current scan, not the whole disk's status. https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Scanning Panel#Sector Map

Can confirm that there is no issue with mounting the drives to a folder path. StableBit DrivePool doesn't use the drive letter or path, but uses the volume ID via the UNC path (eg, what you see when you run "mountvol" in a command prompt, the "\\?\Volume{GUID]\" path).