Christopher (Drashna)

Okay, then throttling the SMART queries should definitely fix the issue. The manual link includes the different options here.

Based on what you describe, it sounds like one or more disks are missing. Do you have any antivirus, backup, or disk tools installed? And could you do this: http://wiki.covecube.com/StableBit_DrivePool_Q2159701 Could you make sure that all the pooled drives are present and accessible? If not, then the drive in question is the cause of the problem. If they are attached, could you install this build: http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.625_x64_BETA.exe

There should be down arrow menu .... thing, at the top of the web page, next to "Windows Server 2012 R2". Click on that. It should list "Home", "Shared Folders", "Device", etc. Click on "Devices". This will list the computers, their status, and allow you to remote desktop into them.

We're definitely using the new API. However, in regards to throttling, but API's seem to be throttled. And i you want to see just how badly, check out the dev site: https://dev.onedrive.com/README.htm Check the bottom part out, where it says "Throttling". It delays you for 3600 seconds (one hour)! That's..... horrendous.

Glad to hear it. And yeah, we wanted to have the suite to be very, very well priced

Well, glad to hear about the drive! And the RDP Services was fine. Probably just a glitch from the setup process.

You are very welcome. And I'm very glad to hear that it is working! And let us know what your final settings are (that work the best for your connection).

The version should be listed in the UI at the bottom, or in the Control Panel (the uninstall section). And could you see if the latest internal beta build helps here? http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.625_x64_BETA.exe

I'm pretty sure we're using the newer (REST) API for this. However, I'll ask Alex to confirm (and update if needed) https://stablebit.com/Admin/IssueAnalysis/16675

Yes. And Alex has been actively going through the backlog, this week. And I've bump the feature request, to make sure that he sees it.

Sorry for the delay. As for the error you were seeing, it was related to the browser and the computer it was on. It was reporting that the certificate was expired/invalid. Which is very odd, and ... well, shouldn't be happening. If that continues, double check that the date and time are correct on both of the systems (and within a minute of each other). And you may want to consider switching to another browser.

Nothing. Specifically, any time that you have a missing disk, StableBit DrivePool puts the pool into a "read only" mode to ensure that NOTHING changes (at least not because of us or through the pool drive). This is specifically to prevent any sorts of issues that could be caused by the duplication or balancing engines (or from modifying existing files that are duplicated). So, no duplication or balancing has occurred or will occur until the external enclosure is reattached or the missing drives are removed from the pool. As for placement, by default we make sure that duplicate copies are not placed on the same physical disk (in the case of multiple partitions on the same disk). We don't do anything more complicated than that right now. (so we don't check the controller or type). However, we do want to introduce a "duplication grouping" feature that would accomplish that (albeit, manually). But, in the meanwhile, if you don't mind micromanaging the pool, you can use the file placement rules to do this. Select a folder, and then select two disks. It will make sure that the copies end up on only those two disks, if possible.

Yup, Alex let me know (there is a lot of communication that happens "behind the scenes"). And he did say that this was a very odd case. But I'm very glad to hear that. And he made a change to DrivePool specifically to help prevent this from happening in the future.

What OS is this, and what version of StableBit DrivePool? And were these brand new drives? Or did they have content on them already?

Talking with Alex some about this (since i'm not as familiar with all of the ins and outs yet), there are a couple of things to tweak). The threads are the number of parallel "IO" that happens on the CloudDrive. Try setting the write threads to 1, and the read to 2-5. And you're not having issues downloading (if you were, increase the size and time for the prefetcher). Also, for the errors, you'll want to increase the value for these: IoManager_HttpTimeoutMS IoManager_WriteRetries IoManager_WriteAbort Increasing these will ... well, just increase the amount of time before we error out. However, that should help prevent as many errors from showing up in the UI. But may affect shutdown time of the service (and the system).

Well Alex has tried to reproduce the conditions that caused the crash and has not been able to trigger it at all. If you haven't already, then the hotfix listed previously may help (as it does describe your situation). https://support.microsoft.com/en-us/kb/2789962 If you've installed it and it doesn't help, then the issue is more than likely hardware related. You've said you have already run memory test, have you tried CPU stress tests? If not, try that, as it may be CPU issue.

After that, it can become a lot more complicated. First, make sure the website itself is accessible and working properly (the correct certificate, eg no errors on connecting). If that is working fine, then the certificate import for the RDP Gateway may have failed. And that is more complicated to fix.

Google Drive itself plays fine with the Pool. OneDrive doesn't because of how the file are stored (some weird file system trick, and only in Windows 8.1). As for placing the file, the "Prevent Drive Overfill" should clear out the rive if it gets too full.

Well, thank you for the feedback! And I've already mentioned it to Alex. Though, I'm wrong. For most of the providers, it doesn't matter. But for Microsoft Azure, the name does matter (and possibly for other, future providers). In future builds, we'll see about clarifying. Also, when you log into the provider, it will list all the available CloudDrive's you've created. This way, you can access them easily, even if you've ended up reinstalling! As for "take the drive with you", only if it's using the local storage provider. Otherwise, as I've mentioned above, you'll see it listed on the other system. And thank you! We're glad to hear that you think it's great!

For which product? Could you try to disable both services (StableBit DrivePool Service and StableBit Scanner Service), in "services.msc". If it doesn't help, then the issue is that something is accessing the Pool drive and keeping the disks awake. If this fixes the issue, then one of the services is doing something to keep the drives awake. And in this case, try enabling the "StableBit DrivePool Service". If this causes the issue to come back, check to the UI to see if the Pool is balancing or duplicating. If it is, this is normal and should settle down after a while. Both of these tasks check the disks and move files around. This will obviously keep the disks awake. If this doesn't cause the issue to come back, then try starting the "StableBit Scanner Service". If this causes the issue to return, then check to see if it's scanning the disks (this is a sector by sector scan, so will definitely wake the disks. If it is not scanning, then it may be that the SMART data is being queried "too often" and keeping the disks awake. In this case, you can throttle the frequency of the queries: http://stablebit.com/Support/Scanner/2.X/Manual?Section=SMART If that doesn't help, then enable file system logging on the pool: http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Well, glad to hear that we could help put your Synology box back into use!

For the name, you can specify anything you want there. It's just to label the account, so you know which is which (in the case of having multiple accounts of the same provider). And yes, detaching and reattaching the drive is how to control how it appears. As for accessing multiple places, you'd need to detach it first, otherwise, multiple systems writing to it at the same time can cause corruption. That's why we have the limitation here. Creating a workaround to this issue would be very complicated. However, it should let you forcibly attach a drive, if you absolutely need to.

well, make sure the "Remote Desktop Gateway" service is running on the server. If it's not, then that's the problem. Otherwise, try using "proxy.org" or a smartphone (not on wifi) to make sure that the site is accessible remotely, and using the right certificate.

Sorry to hear that. And what errors are you getting on the server?

Ouch, I'm very sorry to hear that. And you could still use the Local Disk and Network share providers for local access (such as a dedicated NAS box like Drobo or Synology, one one hooked up to your router).