Christopher (Drashna)

Well, StableBit DrivePool and StableBit Scanner has remote management built into them. You can install the software on another computer and remotely connect to another system. http://stablebit.com/Support/DrivePool/2.X/Manual?Section=Remote%20Control As for iSCSI... it may not be as simple... but Server 2012R2 does include the feature, and you could set it up. As well...

You mean want to check this out: http://wiki.covecube.com/StableBit_DrivePool_Q4822624 And no, the it won't affect the DLNA players at all. If they're pointing to the pool, then it doens't matter how the disks in the pool are mounted. As for adding the disks to the pool. You can add them, it doesn't format the disks. However, the contents will remain on the disks, outside of the pool. We do have a guide on how to quickly seed the pool, if needed: http://wiki.covecube.com/StableBit_DrivePool_Q2299585B If you have any other questions, don't hesitate to ask. Oh, and if you format the 8TB Seagate Archive drives yourself, I'd recommend using the "64K" allocation unit size, as you may get better performance out of them (especially with large files)

Thank you, and I've responded to the ticket.

Well, the logs that you posted don't indicate any sort of issue. Just normal stuff. If you want, please do upload the entire log. and do so here: https://stablebit.com/Contact (as there may be "sensitive" files names listed, and the contact form is private). If possible, could you enable file system logging for the next full back? If you know when it's going to happen. http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection Otherwise, the issue is likely that the full backup is kicking off a VSS snapshot of ALL of the disks in question. This obviously fails on the pool drive, and produces the above error.

Unfortunately, no we don't support Dynamic Disks. in a large part because of the added complexity to the balancing engine (which takes phsyical disks into account for duplication), and because of way that Windows handles them (weirdly...) That said, you cannot just swtich the controller mode on your system in place. Doing so will likely cause BSOD's as you've seen. You would either need to reinstall ..... or maybe use a hack to switch the controller's mode in Windows: http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation This may allow you to switch the mode without BSODING or reinstalling.

Sorry, no ETA. Alex wanted to take a small break after CloudDrive because it's been a very intensive project (trust me, he deserves it!). After that, well, he really wants it too, so he'll probably work on it very hard. Between the fact that it shouldn't be anywhere near as complex as CloudDrive (famous last works....), and other things Alex has said, hopefully the wait isn't too long at all. But that really depends on how complex everything for StableBit FileSafe turns out to be. And what exactly we want/need to include with it (such as file system filters....) As for replacing damaged files, that's part of what we (and by that I mean myself, and I will be pushing for it) want FileSafe to do. To help facilitate this sort of behavior. And not just with damaged files, but potentially corrupted files as well. As for fixing damaged sectors/files, deleting the file directly and remeasuring the pool (or even just accessing the files) should prompt DrivePool to reduplicate the files. Additionally, running a chkdsk /r pass on the disk (add "/scan" if you're using WIndows 8 or server 2012 or up) should identify and fix these damaged sectors as well. And this repair behavior is something that I know we want to fix as well. *sigh*. I'll ask. I'd love to, but Alex gets final say on those. That said, it's pretty awesome. It really compliments and fixes some of the issues with DrivePool. (enough teasers for you? )

Unfortunately, the Disk Control settings are controlled by your disks firmware. It may be that power cycling them is resetting the settings, or just not displaying the active settings. This is dependant on the drive and the controller you're using. What drive(s) and controller(s) are you using specifically?

Peter, Thank you for letting us know. What versions of StableBit Scanner (and StableBit DrivePool) are you using specifically? This way we can check the files, and send them to TrendMicro for review, if needed. Regards

Correction, Alex is saying "hopefully within 30 days" for a beta release for StableBit CloudDrive

We don't have an ETA. "Soon". And Alex really wants to get it out very soon. And don't forget, we need to change a bunch of stuff on teh website to add support for a third product, as well as licensing stuff, discount stuff, etc. But you'll definitely see changes to the forum, the main site, and a blog post about it when we're ready to release it.

It's not a cosmetic bug, but we should explain it better.... See the "Try not to fill a drive above X" slider? Set that to 95%. That should fix what you're seeing. As for hte arrows, the blue is the "Target for balancing" and the red arrow is the real time placement limiter (files can only be placed on the drive up to that limit).

It doesn't matter. You can add arrays to DrivePool, if you want, actually. However, passing the disks through to the OS is the best option. I don't think it's "JBOD" that you want, but i could be wrong. I've never used the RAID option on these cards.

TimoJ, Could you open up a ticket here: https://stablebit.com/Contact And could you upload the entire contents of your "C:\ProgramData\StableBit Scanner" folder? And no, the specific issue you mentioned should affect you. It was because a user was seeing StableBit Scanner reporting a LOT less capacity that the disk actually had. We just changed how we process the data is given us, to make sure it's correct. Regards

Yeah, you could definitely do that. Also, it may not bie exact. Remember that it's not just the raw data that's being written. It's the file system entries as well. And VSS snapshots, etc. But regardless, please do, and see how far off it is. That way, we have a good idea of where the math is wrong at.

If I had to guess at why, probably file system damage. You should definitely run a chkdsk pass of the disks affected this way, just in case.

These are the specific changes since the 3079 build. However, it sounds like the installer corrupted files, as there should be nothing that significantly changed in regards to the scanning engine. In fact, this was all UI changes. If you wouldn't mind upgrading to the newest version again, and see if the issue reappears? If ti does, could you do this: http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings Go to the "Logging" tab. Find the "Scanner" entry and click on it. Select "Verbose". Repeat this for ControllerInfo and DiskInfo. ANd hit "OK". Let this scan the system, and then grab the logs from "C:\ProgramData\StableBit Scanner\Service\Logs\Service" and attach them here, or at: https://stablebit.com/Contact/

Sorry for that.... we are working on ... well, finishing the manual, to cover this and pretty much every aspect of the UI (hidden or otherwise). And it shouldn't come back, unless there IS an issue.

.... without logs, I couldn't really tell you. Maybe a disk error, or a permissions issue. Or issues with elevating the installer properly? If you rebooted, prior to running the command, there may have been a pending reboot that was blocking the installation.

If you're seeing an unknown user for the owner (probably starts with "SID-", or just "S-"), then the account that owned it got deleted, or ... possibly a file system issue. To emphasize, StableBit DrivePool does not use any custom accounts. The driver runs as a kernel level driver, so it requires and is not affected by user permissions. The service runs in the system account, so it should always have access the disks (you can change this, but because so many things run in the system account, we HIGHLY recommend against this) Check the event viewer, the "system" section for disk related errors. If you're seeing a lot for one or more disks, then you may have a problem here. I would highly recommend running a chkdsk pass on all of the disks in the "O:\" Pool, to make sure there are no issues ("chkdsk x: /r" would be best, where "x:" is the drive letter of the disks in question). After doing that, it may help. Worst case, reset the permissions for the entire pool, by doing so on the constituent disks. Do this on the root of each disk in the "problem" pool. http://www.techfleece.com/2011/05/15/how-to-take-ownership-of-files-or-folders-or-an-entire-hard-drive/ Also, change the permissions to ... well, match what you see here, as well (administrators and system with full control, and users and authenticated users with read+list+execute priviledges). In both options use the "replace" option, to force inheritance to ALL files and folders. Once you've done this, hopefully, the pool should return to working properly.

I'm glad that the link helped you out! And I'm sorry to hear about the issues with Avast... but we've been having issues with them more and more often lately. And Norton isn't that bad. Personally, I prefer ESET or Sophos.

Please run the command, then. It will produce a log regardless of the outcome. In fact, it may indicate why it's not installing, which is why I directed you to run it. Worst case, try rebooting, and see if it will install then.

You'll want to check out this then: https://en.wikipedia.org/wiki/SUBST#Custom_label It looks like the drives don't support the volume label in the same way. ALso... it appears that on server 2012R2 and WIndows 8.1, these drives don't show up in explorer at all. And aside from keeping stuff the same, why not just use "X:\Videos", "X:\Music", etc? It

Are you using the correct version of the SSD Optimizer? If you are, try running this: msiexec /i DrivePool.SSDOptimizerPlugin.Setup_1.0.2.3_x64.msi /Lime c:\SSDOptimizer.log If this errors out still, then grab the c:\SSDOptimizer.log file and upload it here or at https://stablebit.com/Contact

Have you cleared the status in StableBit Scanner to see if the issue comes back? To do so: double click on the disk, click on the arrow next to "file system scan" and click on the button with the green circle on it, and select the "mark all damaged file systems as unchecked" option. This will clear the status and cause it to rescan the disk at the next opportunity. Also, a surface scan may not detect file system errors. The surface scan detects areas of the disk that are unreadable. Not that are corrupted. The file system scan uses chkdsk actually, to find corrected file system entries (and to fix them).

What command are you using specifically, so I can test this out. Also, why do you need to mount the folders to disk letters? Why not use the pool drive directly? If there is an app that is having issues with the pool, then let us know. Also, why not map "\\localhost\x$\folder" to a drive letter? (where "x" is the drive letter of your pool, and "folder" is the full folder path)