Christopher (Drashna)

Try doing the same on the underlying drives. Also, if you have antivirus software installed, it may be worth disabling/uninstalling that temporarily, as that can cause issues.

That's definitely not typical. Is StableBit Cloud connected? And could you open a ticket at https://stablebit.com/contact ?

Tinkering with the I/O performance settings may help here, namely the download threads. And the enumeration is dependant on the pinning and connection speed.

Is this over Remote Desktop, by chance? If so, make sure you're on the latest versions.

Are you using MSI Afterburner, by chance? If so, that can cause this to happen. Otherwise, there is a "C:\Program Files\StableBit\DrivePool\DrivePool.UI.exe.default.confg" file, copy this and remove the ".default" from the file name. Edit the file (I recommend Notepad++ for this), and there should be a "Wpf_SoftwareOnlyRendering" setting. Set this to "True" and it should fix the issue.

I wouldn't say dead. It's far from mature enough to be used with anything other than Storage Spaces, and a mirrored or parity array.

It's an automount issue. We have a guide on how to fix this, actually: https://wiki.covecube.com/StableBit_DrivePool_F3540 This will let you remove the drive letters and still keep the drives mounted properly.

Remeasuring the pool is a good idea. Also, running a CHKDSK pass on the disk in question may help (and remeasuring).

Try stopping the StableBit Scanner service, and see if that helps?

DrivePool does read and enumerate the directory listing directly from the underlying disks. If one of them is taking forever, it can adversely effect the pool.

Yes, it should be able to identify those drives, as long as the Orico enclosure wasn't modifying the partitining/file system.

More than likely, it's a section of the disk that hasn't been scanned. StableBit Scanner uses a sector map to keep track of which parts of the disk have been scanned, and when. So you may see it finish one day, and then scanning "again" the next. Also, by default, StableBit Scanner only scans one disk per controller, at a time. This is to prevent saturating the controller's bus.

My guess is that there are locked files on the disk in question, and it's stuck on that. Alternatively, antivirus or disk tools could be causing this. either way, could you open a ticket at https://stablebit.com/Contact

"Arm64"? that should be x64, not ARM. If that's the problem you're having here.

if it's stored, it's stored internally for the drive.

No, not itself. A number of drives do actually store historical temperature data within their firmware, and StableBit Scanner will display that information, if it's present. StableBit Cloud will track that sort of information but only for as long as it's been installed and enabled.

It's run with the normal priorities. And the order of the balancers in the settings dictates which balancers have priority.

It's on the do-do/evaluate list.

Yeah, it's to make sure that the system doesn't create hot spots while scanning. And no, I don't think there is a way to exclude a specific drive from this.

First, I'm sorry to hear about your drive failures, as that is never a pleasant experience! For the settings, I personally like having the StableBit Scanner balancer move out unduplicated data for SMART warnings too. I also have the rescan option to 14 days instead of 30. Otherwise, that ll looks good.

Could you open a ticket about this at https://stablebit.com/Contact

Are you accessing the pool over the network, or directly? And does this happen with any of the disks in that pool, as well?

You should have no issues running all of our software on Windows Server 2022

Also, keep in mind that you add pools to pools. So you can use CloudDrive still, but add that drive, *and* the pool into another pool. That may be a bit easier to manage.

StableBit DrivePool doesn't remove empty folders, for a number of reasons. If you want, you can manually clean up the empty folders. As for prevent rclone, if it can, have it check if the pool is writable first. If there is a missing disk, the pool goes read only until the missing disk is resolved.