Christopher (Drashna)

Well,I think I may know what is causing this. If this is a brand new release stable, we recently found a bug with the licensing that would make it appear to be working fine, while in fact it was on an expired trial license. Upating could produce this sort of issue. Reactivating should fix the issue. If this isn't the caes, or if you can't activate your license, head to https://stablebit.com/contact and we'll get you sorted out.

Welcome! The util itself should have a good deal of documentation. So if you're not sure about it, run "dpcmd ignore-poolpart" with nothing else in the command.

It should be in the system path, so you should be able to just run `dpcmd`, But keep in mind that you should be running it from an elevated command prompt or powershell. Specifically, it's dumped to "C:\Windows\System32\dpcmd.exe"

@Tartifless Basically, go to add a new pool (the "+" at the top. You can add pools to that pool. So you could have a pool with the disk from one controller in a pool, the disks from the other controller in another pool, and then pool together those two pools. If you're using duplication, enable it on the top level pool, and you have a copy on each controller, basically. This isn't required, but it's not a bad idea, in case a controller fails.

Honestly, it shouldn't matter too much. The drives aren't going to saturate the bus, so this wont make a different. For instance, each PCI-e card, assuming it's PCI-e 2.0 8-lane, that can support ~20 hard drives being saturated. And that you have 2, and even if the onboard sata ports were using just a single lane... You should have no problems here. (I'm using 24 drives on a single LSI SAS controller, and have had zero issues)

Ignore Task Manager. 100% means 100% compared to the activity over the last 30-60 seconds. This could be 1GB/s, or 1B/s, because of this. So it's a VERY bad measure of activity. Using something that reports both speed *and* disk queue length. The Windows Resource monitor (run "resmon"), or even StableBit Scanner will show you a MUCH more reliable status of the drives. From there, if it's grinding to a halt, then open a ticket at https://stablebit.com/Contact so we can help you more directly, which may require private information.

Ah, the dynamic disk array is the culprit for you, then. In general, we don't support dynamic disks, because they're a mess.

Sorry, I did skim, and didn't fully read. However, I've learned more about how the file system works (alex is the expert here though), but with that expanded knowledge is learning that hard links on the pool is not possible. Not a "maybe possible in the future", but a hard no. However, with StableBit CloudDrive, you could create a drive with the local disk provider, use the pool drive, and then use hardlinks to your hearts desire on the CloudDrive disk, since CloudDrive doesn't deal with the file system at all. It deals with the raw disk data. Also, features like data

It's a command line tool, yes. And no, there really isn't a manual for it, but the tool should be pretty self explanatory (as each command has a good deal of info).

@SteveK Same for you. Especially as it's the same category and type. Do you know what version this is for specifically?

This is a false positive, and happens from time to time. And the specific "match" is the predictive engine, which is more prone to false positives. You can safely ignore this.

That's the "old school" method. And yeah, that definitely works. If you still have issues, then the "dpcmd ignore-poolpart" command will be the go to.

Valid point. I think there is a powershell command for this stuff, as well. And that should handle things much better than the older commands. I'll do some digging on that.

Awesome, glad to hear that! And yeah, AV can be annoying sometimes, but that it's been that long since you have had an issue is a good thing (or a horrible, horrible thing )

Also, if the system is actively measuring, .... file access is a very resource intensive process. Also, any antivirus or disk tools can contribute to this, as they intercept every file access.

If it's installed, it should show up in "C:\Program Files\StableBit\DrivePool\Plugins\Balancing". There should be folders here, and a dll in the folder. That should be a "CovecubeInc.SSDOptimizerPlugin.dll" file there. If that's there, then it's installed. Re-open the UI and see if that helps.

Also, Google Drive has a 750GB per day, per account upload limit. So a limit of 70mbps will actually come in slightly under that limit. So ... they may be throttling on their end to ensure that, now.

Just a heads up, for any beta builds, if you're getting the internal builds, check the change log file. Get only NUMBERED builds in the log, as these are stable, whereas builds not numbered in the log may not work, at all.

This is a topic that comes up from time to time. Yes, it is possible to display the SMART data from the underlying drives in Storage Spaces. However, displaying those drives in a meaningful way in the UI, and maintaining the surface and file system scans at the same time is NOT simple. At best, it will require a drastic change, if not outright rewrite of the UI. And that's not a small undertaking. So, can we? Yes. But do we have the resources to do so? not as much (we are a very small company)

I agree with you all. SAS information would be amazing. Especially as I have a 36 bay server chassis with an LSI SAS controller. However, our focus is on consumer technologies. So that is where our time and effort is spent. That said, once StableBit Cloud is finalized, I do plan on pushing for SAS support. Especially as NAS and enterprise drives are getting fairly close in price, anymore.

I've also been bad about checking the forums. It can get overwhelming, and more difficult to do. But that's my resolution this year: to make a big effort to keep up with the forum.

You could also do this with StableBit CloudDrive, actually. And while that may be a bit of self-promotion, it has the advantage of breaking the storage files into chunks, so that the drive doesn't have to fit on a single disk, as it will for a VHD(x) file.

Sounds like this is a file system corruption issue, which may not be a surprise for you. Running CHKDSK may fix the issue, but it may not. Worst case is the "dpcmd ignore-poolpart", this will immediately eject the drive from the pool and mark it as removed. The disk will show up as "missing" in the UI, and will need to be removed from there, as well. But this should be instant. Also, none of the data on the drive will be moved, so you'll need to manually recover the data from the "poolpart" folder.

(also: https://wiki.covecube.com/StableBit_DrivePool_Q5510455 )

Also, there is this: https://wiki.covecube.com/StableBit_DrivePool_Q5510455