Christopher (Drashna)

You mean on the provider side? Not really. You may be able to use SDELETE to do so though (as this zero's out the data)

If you moved the data into the PoolPart folders, did you remeasure the pool after doing so? If not, then do so now (located in "Manage Pool"`)

Just a heads up: Those setting will cause issues. Try using 10 threads (upload and download). Unable upload throttling, for 75mbps. Set the upload threshold for 5MB or 5 minutes. Set the minimum download size to 20MB Set the prefetching to: * Trigger: 5MB * Forward: 100MB * Window: 20s That may help with your speeds. If not, try upping the upload threads to 15. If that doesn't help, and you live in the US, try a VPN, as your ISP may be throttling uploads to cloud providers (Thanks FCC)

@Gordon Currie Could you open a ticket at https://stablebit.com/Contact and then run the StableBit Troubleshooter? @HomeServerAdmin Could you do so, as well? http://wiki.covecube.com/StableBit_Troubleshooter

Well, hopefully, those should be good enough to get the job done That said, "alternativeto.net" is a great resource for finding software.

Where is the cache located? what drive, and how is it hooked up to the system?

"situations where data corruption" ... if you have any "to upload" data, then corruption can occur, if you try reading the data in the cloud. Eg, when you have two (or more) systems reading and writing data from the cloud, you'd have to ensure that ALL of the data is written to the cloud before any other system could read from it. Otherwise, you'll get incomplete data. And if that incomplete data was the file system, that could show up as a RAW partition. Or, only part of an image or video. Etc. Basically, what is on the cloud is NOT the completed data, if there is any "To Upload" data. So, that really means that any time the drive is written to, it means that the cloud copy is no longer the correct or viable copy of data.

Pictures are always helpful. And yeah, looks like the "PoolPart.xxxx" folder got corrupted/lost. It's probably on ef the "dir#####.chk" listed in the one screenshot. To clarify, StableBit DrivePool does not delete the PoolPart folder under ANY circumstances. At worst, we mark it as "not part of a pool", and then remove the hidden flag. That way, any data residing in it is still accessible. But because you have the "found" files, it looks like the directory structure was damaged and cause the PoolPart folder to be lost. You should be able to run data recovery to get your data back. However, we've had a number of users reporting VERY good results with Recuva. There is no affiliation with the company. It's what users have reported as working, so I wanted to pass that along to you, since it may make things much easier on you, because data loss is a shitty situation, no matter the cause.

Not currently, but it is something that we've talked about recently, actually. At least, maybe expose it in the disk settings (either the "unsafe" option, or the specific methods, like in the Direct IO Test tool), but only if the "advanced settings" option is enabled.

You opened a ticket about this already, and I've responded there. But for visiblility/ease:

Best way? Deactivate the license for StableBit DrivePool Uninstall StableBit DrivePool Move the drives to the new VM Install Windows and StableBit DrivePool Activate the software That's it. You may want to reset the permissions on the pool, if you used specific user accounts. Otherwise, it should "just work". As for the deactivation itself: StableBit DrivePool 2.X/StableBit CloudDrive: Open the UI on the system that the software is installed on, click on the "Gear" icon in the top, right corner and select the "manage license" option. StableBit Scanner: Open the UI on the system that Scanner is installed on. Click on "Settings" and select "Scanner Settings". Open the "Licensing" tab, and click on the "Manage license" link. This will open a window that shows you the Activation ID, as well as a big button to "Deactivate" the license. Once you've done this, you can activate the license on a new system.

This should be fixed in the 1052 build, now. Thanks for catching that and bringing it to our attention!

On some disks/controllers, it can cause it to "hiccup", crash the controller, or even BSOD. It's not very common, but it's enough of a possibility...

What OS were/are you using, and what version of StableBit DrivePool? As for the file, sorry, I it sounded like you may have been using something to access the file rather than directly. Sorry for that confusion. Do you know if the file shows up in the hidden PoolPart folders on any of the disks?

This is something that has been requested in the past. And is something that we'd like to implement. But while this is simple sounding, it's a lot more complicated to implement then it would seem.