Christopher (Drashna)

Honestly, we're not sure yet. We're pretty sure the Amazon Cloud Drive issues are server side, and not related to our usage (official API). However, if this is the case, it represents a SERIOUS issue with the service, that affects "normal users" of the service. At this point, I would recommend it for non-critical data. (also, you can always run a full chkdsk pass or manually initiate a surface scan in Scanner to ensure everything is already).

Very. As for encrypted pool, you can use the Local Storage provider to create a CloudDrive on the pool and encrypt it.

I believe this is by design. I've flagged Alex for verification. However, I believe this is what is going on here: To ensure data reliability, the files are cached locally, until we are able to upload them (and verify the upload, if the setting enabled). Since the internet/data connection may be be reliable or fast enough to fully handling the stream. Also, having a cache may be a good idea, even if it's relatively small. This allows us to "pin" certain data (namely file system data, and optionally, directory data), so that we're not constantly downloading from the Cloud Provider.

Well, Max, thank you for all the great feedback! Setting to one upload thread means that only one chunk is uploaded at a time. You should probably set that to a higher setting, and see if that works as well. As for the encryption, no, it's not encrypted by default. And there isn't a way to encrypt it afterwards, due to how the drives are created. You'd need to destroy the drive and create a new one. And I've passed on some of the feedback to Alex.

I believe that should work, actually. And no, there isn't a good way to do this at the moment. We do plan on implementing a "duplication grouping" feature in the future to better handle this sort of situation though.

I'm glad that you've found it, and I've passed the feedback on to Alex (the developer).

Well, I definitely understand not wanting to duplicate everything, especially if it's a lot of fairly easily replaceable files. Though, even if Plex does list the missing files, IIRC, it doesn't do so in an easy to view list. And I'm sorry to hear about the errors on one of those drives, but glad to hear that StableBit Scanner is already showing it's worth! And yes, you can set the duplication per folder, as you want (even higher than just 2x, if you're especially concerned).

I wasn't sure, since you didn't specify (or mention anything that would have been "telling" to what version). And yeah, that method is rather simple (just make sure you have the install disk somewhere). And the only caveat, is that the destination drive needs to be the same size or larger than the original disk.

Glad to hear it!

Ah, okay. yeah, I'd replace the drive. I'm not 100% sure here, but I'd guess that the drive is out of "slack space" for remapping sectors (or never had any), and the nand cells are degrading (becoming uncorrectable/unreadable). RMA the drive if it's still under warranty, or stop using it for anything critical. If you are using this for the system disk in WHSv1 (then I'm not surprised, as it doesn't support TRIM commands, IIRC), then yeah, cloning is a bad idea. However, you can do this: https://web.archive.org/web/20090411184621/http://wiki.wegotserved.com/index.php?title=Migrate_Shares_and_Backups_to_New_System If you are using this for the system disk in WHS2011, then you can use the Windows Server Backup function to backup the system disk to a dedicated drive (not the pool), and then restore to a new system disk.

Personally, I feel that the full format is unnecessary, and more detrimental to the drive's health than it is helpful. (but all evidence for and against this is purely anecdotal). In theory, if a full surface scan doesn't detect any issues, it's probably fine. And yeah, there are a good number of options in the built in balancers. Worth taking a look at.

Sorry for not explaining. It may be a SMART error that is generating the warning, as opposed to strictly the temperature. And speaking of which, have you unchecked the "Notify on SMART Warnings" as well? If not, try that, and see if that helps, as well. Also, could you enable verbose logging for the notifications? To do so, click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option. Click on Settings, and select the new Advanced Settings and information option. This should open up to the "Logging" tab. Find "Notifications" in the list, click on it, and then select the "Verbose" option. Click "Ok" Once it's generated more notifications, send the logs to us: Open up " C:\ProgramData\StableBitScanner\", right click on "Service", select "Send To" > Compressed folder. THen open a ticket at https://stablebit.com/Contactand upload the Compressed folder there.

Welcome! If you're using Windows Server 2012 R2 Essentials, then the only version that works for that system is StableBit DrivePool 2.X (2.1.1.561 is the latest stable version). Just download it, and then run it on the server directly. As for StableBit CloudDrive, we do store everything in a proprietary format (well, it's raw disk data, unless you've encrypted it). So it wouldn't necessarily integrate in a way that's accessible on your other devices. As for SMART info, there are a couple of utilities that can grab the SMART data from the Storage Spaces disk, as long as the drive controller allows it. However, most utilities don't, because of a drastic API change in Windows 8/Server 2012 and up (it hides the disk from the normal API used before these OS's). As for the controller itself, StableBit Scanner may be able to get the SMART data, but it may require advanced options to do so. Once you have the disks removed from Storage Spaces, let us know if you're not able to access the SMART data. As for a missing disk, no, we dont' keep a list of what was on the drive (this would be fairly resource intensive, and we wanted to avoid heavy resource usage). There are several methods on how to do this (command line, "fv++", or any integrity/inventory software). Alternatively, this is part of why we heavily recommend using duplication. While it is 1:1 file based mirror, and uses up a lot more disk space..... If a drive fails, it is literally as simple as removing the disk from the pool. The software will then recheck all of the files and reduplicate the files as needed. In the meanwhile, you can still access the entire pool, without any issues.

Lee, We apologize for the issue, as this is definitely not intentional. If you could grab the error reports from your system? http://wiki.covecube.com/StableBit_Scanner_for_Windows_Error_Reports

What model of disk is this? What temperature is it hitting when this happens? Also, what is the "warning" threshold set to, a la this: http://stablebit.com/Support/Scanner/2.X/Manual?Section=Heat

Yup, this has been requested. Specifically "duplication groups" so you can specify that one set of disks gets a copy of the files, and another set gets the other. However, one option here is to open the Balancer settings, and the "Balancers" tab. From there, you can set the "StableBit Scanner" balancer to evacuate unduplicated (and optionally, duplicated) data from a disk with SMART errors (this is turned off by default, because things like the temperature can trigger this). Optionally, you can use the "Disk Usage Limiter" balancer to only place duplicated files on the drive, by unchecking the "Unduplicated" data option for the disk in question.

Easiest way, run "mstsc". Open the "Options", and that should allow you to specify the system name, and save the credentials. If this is for remotely, then open the Advanced tab, and click on the "gateway" settings. Set your external Anywhere Access url (.remotewebaccess.com) as the gateway server, and check the "use same credentials" (paraphrasing). This should allow you to save the credentials properly. As for why this is happening.... You're downloading the file from your Anywhere Access site, right? If so, it's a file, and saved locally.

Yeah, they're supposed to suffer from "infant mortality". And for me, if they pass a full surface scan, they get put into the pool right away. And since I duplicate everything, if the drive fails, it's not going to be a huge loss for me. However, you could configure the "Disk Usage Limiter" to only place duplicated data on the new drive, if you're worried.

Definitely. It's clearly not me though: However, my entire pool is duplicated. I've lost drives before and it caused me to lose a bunch of files. Even though most would be easy to grab again, I'd rather just avoid it. I'm also using a Norco RPC-4220. Though, I suspect you have the later revision (do you have 2x 2.5" drive mounts? Because I don't :'( ) Also, I still do have 6 bays empty on my server (something I need to correct ) I've already detailed my hardware here: http://community.covecube.com/index.php?/topic/5-my-rackmount-server/&do=findComment&comment=13 Also, what controller card are you using?

This actually appears to have been two issues. http://dl.covecube.com/CloudDriveWindows/beta/download/changes.txt It's issue #17677, for the fixes listed here. Could you download the latest version, and verify that it resolves the issues for you: 32-bit: http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.288_x86_BETA.exe 64-bit: http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.288_x64_BETA.exe

That is definitely a tight situation. I think the best bet here may be to use the "Disk Usage Limiter" balancer, to evacuate the unduplicated contents of one of the smaller drives. This will cause StableBit DrivePool to handle all the juggling of data around. This may take a while, depending on your situation. Once it's completed, there is a "duplicate data later" option when removing a drive. Use this. Then once that disk is removed, add the 4TB drive. This should get you the results you want. Otherwise, you could just pull one of the 1TB drives, remove the missing disk from the pool, connect the 4TB drive, and then copy the data over the network, back onto the pool (it should be located in a hidden "PoolPart" folder).

I'm very sorry to hear about that. However, there is a technical reason for this. In part, because we do use some of the file system features that are not universally available in ReFS (File IDs and Alternate Data Streams). Specifically, we store some information on the pool as Alternate Data Streams (including the duplication status of a folder), which isn't supported in the Server 2012 version of ReFS. Additionally, there is a performance hit for using ReFS over NTFS. Regardless, please open a ticket at https://stablebit.com/Contactand we can see about issuing you a full refund of your purchase.

Yes, if your CPU supports the AES-NI instructions (or the AMD equivalent), then this will definitely benefit the API that we use, and help boost performance. As for combining with StableBit DrivePool, you can use the "Local Disk" provider. Either: Create a single large CloudDrive on the pool and encrypt it (since it uses "chunks", there is no issues with size), or Create a CloudDrive on different disks and pool the CloudDrive's together.

Yup. Though it does suck to see that you have bad drives, regardless. But that does happen. They wear down over time, unfortunately.

What version of StableBit DrivePool are you using, and what operating system? ANd did you do one of the following? http://wiki.covecube.com/StableBit_DrivePool_Q8964978 http://wiki.covecube.com/StableBit_DrivePool_Q3017479 If so, could you grab the "setup" logs from "C:\Windows\Inf\"?