Christopher (Drashna)

For the encryption key used here, there should be what you used and a hex variant that starts with a H. And it won't be the same as your Activation ID. If you do not have this, the drive cannot be unlocked. There is no way for us to help unlock the drive. You have to have the unlock key here.

It's a good idea to update, yeah. As for why it's not updating, if it's an old enough version, there was a switch between http and https that may be causing issues. The newer versions shouldn't run into the issue.

I'm sorry to hear about the drive failure! And yeah, any drives that were only on the drive that failed would no longer show up in the pool.

If read striping is enabled, it should automatically handle that. https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Performance Options

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!