Christopher (Drashna)

Awesome, glad to hear it!

It's a linear process, but it may not be predictable, since it's pinging the files on the provider.

By default, duplication and balancing are ran as background I/O tasks, meaning that they will slow or stop, if there is other activity on the pool. This is so that normal usage isn't slowed down by these tasks. Increasing the priority means that these ***will*** interfere with normal usage, which sounds like what is going on here. However, once duplication is finished, it should be better. It may not. Because StableBit DrivePool is a file based solution, rather than a block based one, the performance gains are going to be only so much. Additionally, just because the file

Try resetting the settings for DrivePool, as that may resolve the disks not showing up, but will force a remeasure of the pool, as well.

Most likely, it's rebuilding the Chunk ID database, since that would have been on the system drive. And yeah, it can take a long time to complete, depending on the size of the drive and the chunks.

It may be worth trying that, yeah. And if that works, it may also be worth trying to set the StableBit Scanner Service's startup to "Automagic (Delayed)" and see if that helps. You'll see drives show up as missing, if they're in a pool, but will be detected if they're re-added.

Honestly, I'm not entirely sure about that. It should be fine, as I don't think it should move the users data,

Support ticket was opened, and replied to. Thanks!

That's very, very unusual. If you could, open a ticket at https://stablebit.com/Contact Also, information about what controller card you're using would be very helpful, too. And are the drives that are disappearing just in the eSATA enclosure having issue? Or is it ALL of the drives? But given what is happening, my guess is the load that StableBit Scanner is producing by attempting to scan the drives is causing the USB controllers to crash. This isn't typical, but it's not unheard of, unfortunately.

If the drives were in a pool, and removed, it is possible to have multiple poolpart folders on a disk. The "removed" folders will not be hidden, while the active ones will be, usually.

I don't think that there is a way to do this, right now. However, I think you've opened a ticket for this, as well. And I have submitted a feature request for this.

Double check the provider. But if the "content" folder is missing on the provider, you're SOL. Also, make sure that you're on the latest release (you're not), especially if this is a Google Drive based drive. http://dl.covecube.com/CloudDriveWindows/release/download/StableBit.CloudDrive_1.1.7.1391_x64_Release.exe There have been some changes to how the contents are stored for Google Drive, so the older version will not work, if you've used it.

Well, if it's an emergency, and you're okay with not keeping the files on the drive... there is a command line tool that can IMMEDIATELY eject the drive from the pool. The caveat here is that it does not move any of the data over, so if it's not duplicated, it will no longer be in the pool. But you can copy it from the drive, at your leisure, at least. It's "dpcmd ignore-poolpart". You'll need to specify the "pool ID", which is just the name of the hidden "poolpart.xxxx" folder on the drive in question. Once you've done this, it will show up as "missing" in the UI, and you

Moving around files can be ... tricky. If you didn't move *all* of the files out of all of the pool parts, the it may want to reduplicate them, because they're missing now and not properly duplicated. What shane recommends is pretty much what I'd recommend, though: https://wiki.covecube.com/StableBit_DrivePool_F1655

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.