Christopher (Drashna)

That's very odd, and you should definitely be seeing faster speeds. If you could, open a ticket at https://stablebit.com/Contact Also, doing this: https://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection And then running the StableBit Troubleshooter, using the contact ID request number from the contact form: StableBit Troubleshooter - Covecube - Wiki

Awesome, glad to hear it! And thank you for pushing back/insisting on a better fix.

Just a heads up, Alex did take a look into this, and did find a solution that is actually lower level, shouldn't keep the drives awake and allow them to sleep. You can find the installer for this version here: https://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.3.14.1744_x64_BETA.exe

Welcome! If you do run into any issues, let us know, though.

I did/do have a Mac (intel based) that I did use parallels on. And did use the software in, and it worked with no issues. Though, it wasn't a heavy load, at all.

It's "just" a VM platform. You should be able to, yes. And a quick look, you should be able to pass through the whole disk to the VM, too. https://docs.parallels.com/landing/pdfm-ug/parallels-desktop-for-mac-26-users-guide/parallels-desktop-preferences-and-virtual-machine-settings/adding-and-removing-devices/connecting-a-physical-disk-to-a-virtual-machine-as-internal

You are very welcome.

Could you open a ticket at https://stablebit.com/contact then?

If you're using file placement rules and the ordered file placement balancer, you need to configure things specifically to support this. There is a note for this in the balancer's readme, but is obscured by the fact that the balancer is built in now, rather than having to download and install. Specifically: https://dl.covecube.com/DrivePoolBalancingPlugins/OrderedFilePlacement/Notes.txt

Well, part of the issue is that we do try to minimize disk queries. StableBit Scanner (and the other products) look for disk change notifications. Eg, when a disk is connected, disconnected, etc. However, the bitlocker stuff it a special case. Our official stance on this is "no, it's not a good idea, it's actually a really bad idea". Official methods are official for a reason, and using shortcuts, hacks, and other non-official methods means that those behaviors are not documented and not supported. And in fact, are likely to be patched out of existence. Using them leads to an unstable or even unusable product. And we're actively opposed to that, because we have no desire to build, to be very blunt, a shitty product. However, I've passed on the request to Alex, the developer, to see if there is a way that we can improve things here. Because there is always room for improvement, but sometimes it can take an outside perspective. https://stablebit.com/Admin/IssueAnalysis/29129 This won't show any info unless it's posted publicly. Generally, the posts are public, but if there are code changes based on this, those are always public. So I'm posting here so if there is a change or public explantation, it's accessible here.

You shouldn't need to mess with the native service. Mostly, it makes sure that the system shutdown doesn't happen until the service has shut down/ended gracefully. But yes, restarting the "StableBit DrivePool Service" should refresh the drive list. As for why... most of this should happen invisibly, and the goal is to make sure it does. Unfortunately, the bitlocker detection causes issues on some systems. As for "full restart", do you mean of the service? If so, it's because it's loading setting from disk, checking hardware config, and running startup routines (such as checking if the pool needs mounting, etc). Depending on the system and number of disks, this can take a bit to complete. There are some advanced settings that may help, but depend on having more cores in your CPU, basically (eg, by using more threads to run background tasks). That's the thing, we are using the officially support API to check. It's that API that is what causes the drives to wake up on some systems, because Windows considers that activity, and wakes the drive. As for listening to the event viewer, I'm sure that's possible, but as you may have seen, that is a LOT of data to parse, and may cause other issues.

I apologize for missing this. In some cases, restarting the StableBit DrivePool service should forcibly refresh things. If that doesn't help, or you're still seeing issues, please do open a ticket at https://stablebit.com/Contact

By chance, do you have two hidden "PoolPart.xxxx" folders? If so, then this guide should cover how to fix things: https://wiki.covecube.com/StableBit_DrivePool_F1655 Otherwise, you have a "poolPart.xxxx" file? If so, the directory got corrupted, unfortunately. CHKDSK may fix things (but may dump things into a "found.###" folder), or you may need to run data recovery (testdisk+photorec, recuva, etc).

No need to cross post in a bunch of threads. It's counter productive. Also, there is no SMART data for SAS. It's an entirely different thing, using a different protocol (and software that is lazy and calls is SMART do a disservice to everyone). That said, historically, we have opted to not implement SAS because it's not a consumer facing technology. It's meant for businesses/commercial usage. However, that may change due to some of the planned development path for StableBit Cloud. However, there is no ETA on such changes, if they appear, at all. and yes, I too would love to see SAS support. However, it wouldn't be supporting RAID configurations, just HBA/passed through disks, if it does happen.

Make sure you're using the latest beta version. There are some fixes: https://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.6.14.4133_BETA.exe That said, the advanced settings, there are a couple of other options that may help (but try the beta first). Namely, in the SMART section, check the "ignoreChecksum" option and restart the service. If that doesn't help, try the "NoWMI" option, as well. If those don't work, head to https://stablebit.com/Contact and open a ticket there. And then run the StableBit Troubleshooter, and use the ID number for that ticket. StableBit Troubleshooter - Covecube - Wiki