Christopher (Drashna)

No additional hardware is required here (eg, you don't need a TPM module). As for the encryption: StableBit CloudDrive uses low level kernel-based encryption for maximum performance and for full round trip encryption support. Industry standard AES-256 CBC is used to encrypt every bit of your data. The Operating System's core services (Cryptography API: Next Generation) are used for all hashing and encryption functions in the kernel (FIPS 140-2 compliant). This, and a number of other features are mentioned here: https://stablebit.com/CloudDrive/Features As for accessing the CloudDrive, you can only access it from one system at a time. If you try to "attach" it to another system, it will give you a warning that it's already in use. You can go ahead and forcible attach it on the new system, and it should detach it on the other system. However, it will be encrypted, and require you to put in the passphrase or hash key for the CloudDrive before you can access the data.

Well, free for most people. We're waiting on the new version of Visual Studio to be released, that properly support Windows 10, so that we can compile and test a Windows 10 specific driver for StableBit DrivePool. Since we're waiting on Microsoft for this, we don't have an ETA. But we do hope that we will have it out before the July 29th GA (release) date. As for recommended upgrade procedure, that depends on the system. However, we would recommend uninstalling the current version before updating, then update the OS, and then reinstall StableBit DrivePool, to ensure that you get the correct drivers installed.

I'm assuming this is part of the Quota feature? If not, could you clarify where this is located (a screen capture, just in case)?

You're very welcome! And just in case it's important, one of the balancers (the "Prevent Drive Overfill" balancer, specifically), will try to keep the drives at least 10% free (or 100GBs) to prevent any issues from overfilled drives. Just having a good product isn't good enough. You need to have good support for the product too. At least, that's how we feel! And treating people rudely just because they're newer to the product or don't have a lot of experience with it is a very good way to alienate people that would otherwise become huge fans of your product. Besides, you never know if somebody may know more than us, but are just unfamiliar with the product or just overwhelmed (I've been on the other end, so I definitely know that it makes a world of difference on how people respond). If you have any more questions, don't hesitate to ask.

Sorry, I meant how did you resolve the issue? Or did it go away on it's own?

Honestly, I'm not sure how the read striping feature works with CloudDrive. I'll have to confirm, specifically. And request different handling for it, if needed. However, by default, Read Striping does check the bus speed of the drives, and will use one disk over another if it's significantly faster. So depending on how exactly CloudDrive is handled, it may already do this. (hence why I need to confirm the behavior). Well, it shouldn't go down if the internet connection does. The local cache should handle that, up to a point. And we do appreciate the feedback!

Glad to hear it, what was the issue?

I know we changed some of the handling for SMART commands in the beta version, so it's very possible.

It's worth at least trying the hotfix. And hopefully it does fix the issue. Though, once a while is definitely hard to diagnose. As for the Clock Interrupts, that's usually referring to the CPU specifically. However, if the LCD panel is having issues, it may be a good idea to disable it, just in case (if the BSOD occurs again).

Thank you. And I've responded to the ticket already.

Actually, if everything is duplicated, if one drive fails, you'll still have a copy of the files on that drive. And once you remove the missing disk, StableBit DrivePool will automatically start re-duplicating the data as needed (create new copies). This is handled automatically and without your intervention. As for how the files are distributed, ... new files are placed on the disk with the most available free space. This ends up creating a kind of "shotgun effect", where the files end up all over the place. We do have a "Ordered File Placement" balancer that fills up one (or two or more, with duplication enabled). Also, by default, real-time duplication is enabled, so it means that any new files are written to both destination disks at the same time. I think I've covered everything here. If not, or if you need clarification, don't hesitate to ask.

Ross.dargan, Well, thank you for the feedback. We definitely appreciate it, as it definitely helps us. For the multiple provider/CloudDrive UI, I've flagged that Alex (the developer), to see if we can improve upon that (maybe a wizard to start off with, to make it easier to understand). https://stablebit.com/Admin/IssueAnalysis/16681 As for the Provider setup, we definitely do plan on improving that in the future. Though, again the feedback is appareciated as it helps us with what exactly should be changed. https://stablebit.com/Admin/IssueAnalysis/16682 As for the local disk, there are two use cases for this: Creating a CloudDrive on StableBit DrivePool (this would allow you to get VSS/backup support), Or as an alternative to TrueCrypt or the like, as you can encrypt the CloudDrives. As for the service stuff, it shouldn't restart the service or need you to restart the computer. It's failing at some point here, then. In this case, could you grab the error reports from the system? http://wiki.covecube.com/StableBit_CloudDrive_Error_Reports However, this crashing is probably the cause of some of the other issues you're seeing. By default, StableBit CloudDrive should automatically partition, format and then assign a drive letter to newly created drives. Because the service appears to be crashing at some point, it is not completing this process for you. This is why you're not seeing the drives listed in the "This PC" properly, and why you're seeing the "COVECUBECloudFSDisk___" (the disk's hardware ID name) in StableBit DrivePool. You should be able to use Disk Management (run "diskmgmt.msc") to manually assign these drives letters (again, this should be happening automatically, but because of the above issue... it's not). As for the Pinning, this "pins" files to the local cache. Specifically, we "pin" the file system data to the cache, so that it's always available (eg, so you don't have to access the cloud provider each time you query the file system). And you can optionally pin the directory entries, as well. As for the network share provider, you should force attach in this case. This is happening most likely because of the service crashing. Specifically, we only allow a drive to be attached to one system at a time. However, due to the service crashing (most likely), it's lost the association, and is prompting you about attaching it to this "new" system. This is a precautionary warning to prevent data corruption (eg, uploading the same chunks from different systems). As for clearing the feedback, I'm guessing it mentioned the "named pipe service" specifically. If that's the case.... You may have an issue with your installation, as this is a core .NET Framework feature. This ... may also be the cause of the Service failing as well. In this case, run "chkdsk c: /r", and after that, "sfc /scannow", to ensure the integrity of your installation.

Sorry, that was for "right now" at least. If/when we implement WebDAV, you could set that up on your server, and use that as a provider. WebDAV supports HTTP and HTTPS, but you should always use HTTPS when you can. And I think that would accomplish what you want.

You're using Amazon Cloud Drive, correct? If so, it does get a lot of errors. Additionally, we enable verification on the drive as well, which may use a lot more traffic. And could you do this: http://wiki.covecube.com/StableBit_CloudDrive_Log_Collection Also, what OS is this for specifically?

eSATA isn't necessary. I wanted to make sure how it was connected. However, if this is always on, I would recommend switching to eSATA (as it's much more stable than USB). Could you download the "DirectIo Test" utility? http://community.covecube.com/index.php?/topic/36-how-to-contribute-test-data/ Run it on the system in question, and select one of the drives in question. You're looking for it to "light up" the "SMART Attributes" in either the WMI or DirectIo section, with a green check/tick mark. If it does, click on the ellipse button ("...") and make sure that there is text there (not blank). If the SMART attributes is not lit up in either section, click on the "Unsafe Direct IO" option. This will reload the information. Either way, let us know which works and the "hardware ID" that it displays at the bottom, as well as the methods that it lists. If it does require the "Unsafe DirectIO" setting, then you'll want to do this: http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings Find the "DirectIo" section, check the 'Unsafe' option, click OK, and reboot the system.

Those are all normal filters. (WdFilter is MSE, luafv is the UAC filter, npsvctrig is for .NET I believe, FileInfo .... is what it sounds like, and WoF is a microsoft filter as well (for WIM file mounting, IIRC)). So you should be good there. If this continues to happen, could you enable file system logging and reproduce the issue? http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection This is kernel level tracing, and should be able to cature what exactly is going on. Also, could you open a ticket (https://stablebit.com/Contact) and export the "System" section of the Event Viewer (run "eventvwr.msc") logs? Just in case there is a disk or controller that is crashing/rebooting on you?

First, I'm sorry to hear about your drive dying. As for moving the files, yes, you can move the files directly into the "PoolPart" folder. The caveat is that you MUST remeasure the pool after doing so (open the UI, click on "Pool Options" and select "Remeasure"). If you don't do this, it can cause issues with the balancing engine, the duplication code, and the pool in general (where to place files, etc).

I'm very glad to hear it! And I'm not surprised that this fixed it. Specifically, we changed how some of the code works to measure the pool, as well as re-ordered some of the priorities of different sections. Between these changes, it most likely fixed the issue, where ever it was getting hung up on. If you need anything else or have any questions, don't hesitate to ask!

Okay, that's what I thought. If the issue continues, then try to remeasure the pool. If it still happens, enable logging, and remeasure: http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Could you grab the error reports? http://wiki.covecube.com/StableBit_DrivePool_2.x_Error_Reports Other open a ticket, and we'll take a look at the issue that was causing this.

Well, we do have a "Local Storage" and "Network Share" provider for StableBit CloudDrive. This would allow you to use local disks (or the pool), or a network share for the CloudDrive. As for over the internet, a VPN may be a better choice here, as it would treat the system as a local device on the network.

That's a ... much more technical question. I've flagged the inquiry for Alex (the developer), so that we can get you an accurate answer here. However, I do know we use the officially published APIs for our providers. So it's whatever the API supports, that's what we do. As for HubiC, I've added it to the "to add" list: http://community.covecube.com/index.php?/topic/1225-why-isnt-xxxxx-provider-available/

How are you connecting the drives? Are you using the USB3 or eSATA connector? (We recommend eSATA usually). If you are using eSATA, what controller card is the enclosure connected to?

No, you don't need the drive letter, just "\movies" works. And if you want this folder on JUST the specific drives, then the File Placement Rules are designed SPECIFICALLY for that. Just create the rule, and uncheck all but the disks you want for the rule. http://stablebit.com/Support/DrivePool/2.X/Manual?Section=File%20Placement There is no need to configure the Disk Usage Limiter, here. If you have two or more "disks" that you want the files on, then the File Placement Rules are perfect for that. However, if you only want duplicates on the CloudDrive, then you'll want to use the previous linked thread. Don't mess with the Disk Usage Limiter balancer, as that will cause issues (when it says "duplicated data", we mean both the original and the copy, so if you limit the duplicated data to one drive, .... it will cause issues).

You are very welcome. And we do try to do everything we can to ensure that your data is safe. So the read only mode only made sense for this sort of situation. And thanks! We hope that people like it (we realize that not everyone will, but hopefully a majority will!).