Christopher (Drashna)

There are no plans on adding support for this, at this time.

Unfortunately, no.

It's a good question. It depends on if the enclosure does anything weird with the drives. It's not too common, but it happens. Assuming that it doesn't do anything weird, you should be able to power off the system, pull the drives, and then move them over to the new enclosure. No issues, no fuss.

There isn't a simple way to handle this, I don't think. If you only have three drives, then this would be pretty simple. You could enable file placement rules and only select one drive for the folder. This should work, but isn't ideal.

Was about to ask, the amount of storae on the provider matters, as it will be checked against before creating the drive. If the account is unlimited, you may need to create a smaller drive and expand it out, IIRC.

Most likely, no. But I'll flag a request, just in case. https://stablebit.com/Admin/IssueAnalysis/28742

Well, file system errors can be caused by a whole bunch of reasons. But if DrivePool is also evacuating a drive, then it's likely because Scanner also marked that drive as bad. So, if this is all the same drive, it could be that the drive in question is actively trying to fail. And sometimes, new hardware isn't a bad idea. If you do, I recommend something that supports ECC memory.

I think you posted a ticket about this, as well? If not, could you open one at https://stablebit.com/contact Though, a quick guess is that the SMART data itself is the issue here, and it may be rolling over.

Hold hostage, no. But if there was a file system error, the repair process may take the volume offline to fix it. This is normal, and part of how CHKDSK (and related API) works. The disk scan from windows, CHKDSK and the file system check in StableBit Scanner all use the same API/method, and can do this.

I don't see a record of a ticket from you. Could you email me directly at christopher@covecube.com then?

You are very welcome!

hmm. Could you open a ticket at https://stablebit.com/contact about this?

please open a ticket at https://stablebit.com/contact if you have not already. All licensing issues are handled there.

You also opened a ticket for this. But to repeat what I said there, and echo what vapechiK said, This is perfectly normal, and expected. In all cases, here. the pool drive itself is fully virtual, but doesn't have any blocks/data on the drive. All of the data is "reverse proxied" to the underlying disks, and handled invisible. So CHKDSK won't work on the drive, and it does not appear in StableBit Scanner. And the size is normal, as Windows needs a size before that can be properly read, so the 2TB size is a placeholder.

Yeah, we try to not do anything too tricky/weird, as it mostly just causes more issues down the road. So "not exciting" sounds about right. And yeah, migrating could cause permission issues, in some cases, so I'm glad that this has fixed the issues!

Also, could you open a ticket at https://stablebit.com/Contact Also, as shane mentioned, if this is a USB drive, they can ... behave oddly sometimes. Especially if you have them in the pool. Also, if you have duplication enabled on the pool, and one of the drives is having issues, it can cause this sort of behavior, too.

You could set the volume or drive as read only, but you may run into write errors when doing that. What has been outlined above is probably best.

If you're using an older version of StableBit DrivePool, it may not properly download the updates due to some hosting config (https vs http). You can always find the latest release version here: Index of /DrivePoolWindows/release/download

Mostly, because this is a complicated issue, and there isn't a "one size fits all" type solution. There are a number of things to try: Run "netsh interface tcp set global autotuninglevel=highlyrestricted" on both systems, from an elevated command prompt, and reboot the system. On the Network Adapter properties, disable any setting with "offload", or "checksum". Disable "green" features, and Interrupt Moderation, if present. Enable flow control, and disable jumbo packets (or toggle them, as they can help in some cases) Update the drivers for the network adapters Check for any antivirus software, and (temporarily) remove them Disable Windows Search on both systems.

Yup.

The Performance panel only shows activity that happens through the pool driver. Balancing and duplication activity is not reflected here. The reason for this is how Windows handles the performance counters, and that we don't want to use any hacks to try to make it reflect duplication/balancing, since those can lead to a lot more issues, than what it solves.

Okay, thank you for confirming that, at least. If this happens again, please open a ticket before doing anything else.

Just a heads up, the Set-Disk command is effectively doing the same thing that the diskpart commands are doing. Both are interfacing with the "Virtual disk service", which manages the drives/volumes/etc. Also, it should be noted that Windows Defender also has a number of ransomware prevention options that can be configured. And it may be worth looking into those.

Reparse point information is stored in the .covefs folder in the root of the pool. Worst case, delete the link, remove the contents of the .covefs folder, and then reboot.

Remeasuring the pool may have fixed this, as well. As may have resetting the settings.