Christopher (Drashna)

Yeah, unfortunately, this may be a very hard bug to reproduce. I've tried for about 20 minutes .... and the UAC prompt comes up every time. So it may be an issue with the Windows Installer service, as this is what these installers use. If you are able to reproduce the issue, get the logs (as listed above).

Indeed. It's a good question if these 8TB Seagate Archive drives are good for NAS/Pool storage.... We shall see soon.

Unfortunately, we haven't been able to get to this yet, as we have been very busy. However, I'll bring this up to Alex again. Regards

An "auditing" tool or option for the pool as been requested a few times. It is definitely on our "to do list". However, in the meanwhile, the "Folder Protection" option that brings up the folder tree actually calculates the duplication and size in real time. This can be used to audit the pool in the meanwhile. However, it seems like you are having issues with this. Could you see if the latest beta build fixes this issue? http://dl.covecube.com/DrivePoolWindows/beta/download/ If it doesn't, then enable file system logging and reproduce the issue. http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Tim, What OS are you using, and what version of StableBit DrivePool are you using? As for remeasuring, the driver automatically updates the information "on the fly" when adding/removing/modifying the data, so there shouldn't be a need to schedule this. However, if you are experiencing issues, then we want to FIX it rather that work around it.

Wow, you sure do have a lot of questions! In theory, yes. because we're dealing with some low level drivers and access... Also, BSOD's always risk data (by their very nature).However, there should be no issues. And we try to take care of any data corruption issues very quickly. Yes. The Pool is everything that is in these PoolPart folders. We don't do anything to the files, other than store them there. (we do store some metadata on the pooled disks, but that's the ".covefs" folder and the duplication "tags".Additionally, if you need to reinstall or migrate hardware (such as if it fails), then you just need to move the disks over and reinstall DrivePool. As soon as you do, it will see the pooled disks and automatically recreate the pool for you. It may end up with a different drive letter (most likely) but the duplication status and volume label and (*most importantly*) data will remain 100% intact. You should be able to upgrade over it. If not, then uninstall it and reinstall it. And the above point also covers this scenario also. Absolutely safe. It includes a number of extra steps specifically to prevent balancing while you're adding data, and to make sure that the pool gets properly measured.Normally, it updates "on the fly" if you use the pool disk, so seeding bypasses this and causes these stats to get out of sync. However, only the UI and balancing engine need this measured information. And I've done this on a dozen systems (some mine, some customers, and some friends). There is absolutely no problem with doing this, because we don't do anything special with the disks. But as you can see, there are some additional considerations when doing this (those extra steps), which is why we have this outlined. Also, you shouldn't access the "PoolPart" folders normally, except in extreme cases (we consider seeding an extreme case, because ... well 100TBs is a LOT of data!... that would take a couple of weeks!) There are two components of StableBit DrivePool. The Driver and the Service. The Driver is the actual pool. It handles combining the folders into one single disk. So as soon as you move files into the PoolPart folders, the Pool driver will see these files. It handles realtime duplication by writing the files or changes to all the disks required in parallel. It also handles the actual measuring of the pool (the service does kick this off, but the driver handles it). But the driver basically concatenates the disks into one "list". The Service does a number of things. It is the backend for the UI (the UI does very little... basically just communicates with the service). It handles the remote control aspect (in 2.X), the entire balancing engine, and part of the duplication (the driver handles real time duplication, the service maintains/copies/deletes duplication as needed). It also sets the duplication status of folders (which the driver reads). There are some more stuff that each does, but this is the core of the "bits". So the duplication and balancing parts are why we have you stop the service. We don't want it moving around files until we're done. And this is the simplest way to accomplish that. The reset is to force the service to kick off a remeasure and duplication pass, to ensure the integrity of the pool.You could just remeasure the pool, but we recommend resetting it, just in case. You can disable all of the balancers, if you want. There is absolutely no issue with doing so, and that definitely won't mess up your Pool at all.And you can set up things before or after seeding the pool, because the balancing code won't kick in until the pool is finished measuring. There are a couple ways to do this.The simplest is to use the Ordered File Placement balancer. This fills up one disk at a time, and tries to keep the content of folders on the same disk. The other way is very "micro management"-y. And that is to use the File Placement Rules. If you use the File placement rules, there are some caveats with the SSD Optimizer and the Ordered File Placement balancer, but that's about it. I'm not sure what you mean by this.But StableBit Scanner runs as a background service, so it's always active. Also, by default, we query SMART data every couple of minutes, so it's always up to date (this can be throttled though). Additionally, when you first start up StableBit Scanner, it should ask what sort of system it is. This configures the default work window for you. And by "work window", this refers to when StableBit Scanner can perform the surface and file system scans. The "server" option only does it at night (when you may not be using it), but the "Desktop" option can run it at any time. Also, the scans happen every 30 days, but can be configured to be more or less aggressive. Also, StableBit Scanner will throttle or stop scans based on disk and controller activity, as well as tempurature. But if you mean for the balancers, then yes, we always recommend leaving this on (and in the #1 slot). You may also want to enable the "move files off in case of SMART warnings" option in the balancer as well (but that's your choice). You can turn this one off, especially if you only have one partition per disk. If you're not using Duplication, then this isn't really useful for you... except in the case of preparing a disk for removal (uncheck the duplication and unduplication options for a disk and it will evacuate the contents of the disk automatically for you).So this balancer doesn't matter as much. Prevent Drive Overfill should always remain enabled. It does what it sounds like. Also, getting a disk completely full can cause serious issues with NTFS. A system disk will cause BSODs (or other instability in the system) while a "data disk" will because unstable.As for the settings, the "90%/100GBs" slider is for when it gets triggered (if it goes above this, it triggers). The "85%/200GB" slider is the target usage that it moves data to when the balancer gets triggered. Eg, if the disk gets more than 90% usage, the balancer will cause the disk to be emptied until it hits 85% usage. We would definitely recommend keeping this enabled in most situations. This should also remain enabled, as it helps ensure that ... well duplication is kept optimal.However, if you're not using duplication, this won't affect you either way, so you could turn it off. The SSD Optimizer balancer is optional and must be installed if you want it.If you don't plan on using it at all, then there is no reason to have it installed. But it definitely should be disabled if you're not using it. Nope, you definitely don't want the Disk Space Equalizer balancer installed. It's also optional, so must be installed if you do want it. If you plan on using the Ordered File Placement balancer (again, optional, so it must be installed), and file placement rules (which honestly, sounds like the best idea for what you want), then YES you need to do this, otherwise, it will cause issues with the file placement/balancing engine.(if you want, I can explain this in more detail, but it should be somewhat self explanatory). These rules affect how the File Placement rules are handled in regards to the main balancers.This one is trickier, because of the Ordered File Placement and StableBit Scanner balancers. In this case, I'm not 100% sure, but you'll want to make sure you cehck the "unless the drive is being emptied" option, but make sure the StableBit Scanner Balancer is in the #1 slot. None. That's the default strategy, specifically. When adding files to the pool, by default they are placed on the disk with the most free space. So while filling a disk, it may place the files on different physical disks.The SSD Optimizer and Ordered File Placement balancers change this strategy. As far as I'm aware, there aren't any. For the most part, the built in system handles most scenarios, even if it requires a bit of tweaking.However, we do have the API to create 3rd party plugins, in case anyone wants to build one. For the most part, the Ordered File Placement balancer should accomplish this. It fills up one disk at a time (instead of the "shotgun" effect of placing files on the disk with the most free space). As for more about developing a balancing, let me know if you do plan on doing this, and I'll forward you to Alex (the developer) so you can talk to him more about this. The settings in #16 affect the precedence.Otherwise, the balancers are listed in order of priority (#1 being the highest priority, and then downward). I offered to explain in further detail, and is sounds like that's what you want. So here goes: "File placement rules respect real-time file placement limits set by the balancing plug-ins." Enabling this means that files/folders follow the file placement rules ONLY if there is enough room on the disks allowed by the file placement rules. Eg, if you have the Ordered File Placement balancer installed and enabled... it sets one or two disks as "allowed" disk via the "Real Time file Placement limits". However, if you have a rule to place a file on a disk that isn't one of these... If this option is enabled, then the files WILL NOT be placed on the correct disk according to the rules. And this is why we recommend disabling this option in this scenario. "Balancing plug-ins respect file placement rules." Enabling this means that hte balancers must respect the file placement rules and will not move files off of a disk if there is a rule that says it should be on the disk still. Unless there is another disk that the rule allows the placement to be on. Eg, if this is enabled, then the StableBit Scanner or Drive Usage Limiter balancer couldn't force the data off of a disk unless the rule allows for placement on a different disk. "Balancing plug-ins respect file placement rules. Unless the drive is being emptied." (or just "Unless the drive is being emptied.") This modifies the above behavior. If both options are enabled, then when something like StableBit Scanner wants to empty a disk, it will allow it to happen EVEN if the file placement rules wouldn't allow it. As for the beta, yes, there is a bug with the balancing settings and multiple pools. As for stability, it should be fairly stable. Personally, I update to the newest beta builds once a week and run them. I've never had an issue doing so, but I do understand the hesitancy in doing so. Once StableBit CloudDrive is finished (it's getting close), then Alex plans on doing a major overhaul of StableBit DrivePool (we've added some new UI elements that should make troubleshooting a lot easier by providing much better feedback), as well as some tweaks and optimizations based on the CloudDrive code (as it's fairly similar). Once that's done, we should have a stable release pushed out. But the reason for the delay in a release here is that Alex has been focusing mostly on StableBit CloudDrive as it is VERY complicated/complex. Also, we are very active normally. When Alex doesn't have a huge project that he is trying to get out, the releases are fairly rapid. As as for the company, we're two guys. Alex is the owner and developer (sole developer), and I handle most of the customer service and tech support. And Alex hates letting stuff sit for too long. He really wants to get stuff out and updated quickly. Though sometimes, development takes a while (and we'd rather take our time and get a bug free version out, than provide rapid releases with tons of bugs). If you need any clarification here, or have any more questions, don't hesitate to ask! Also, some other info that you may want to know. In StableBit Scanner, in the Disk Settings for each disk, you can specify a "case" and "bay" for the disks. This allows you to sort the disks in StableBit Scanner, and the information shows up in StableBit DrivePool as well (both under the tooltips for the disk, as well as in any email notifications). So this may make sorting and organizing the disks a lot easier. And yes, I agree with panabodifed, it would be awesome to see some pictures of the hardware and/or the software config! In fact, we have a thread for that: http://community.covecube.com/index.php?/topic/5-my-rackmount-server/

Going from an AMD FX-8120 to the Intel Xeon E3-1245v3 was a big jump in performance and responsiveness, so a lower end CPU to a the Xeon will be great as well. Also, if the old system was using a HDD for the system disk and th if the new system is using a SSD for the system disk, that will make a HUGE difference as well. And yeah, the supermicro boards are very nice. One of the other advantages is that pretty much all of them support out of band management (OOBM) of some sort or another. Which means you don't need to hook up a monitor and keyboard to them EVER (well, initially to configure this stuff, but after that... OOBM allows for BIOS/firmware access remotely ) But either way, that gigabyte board looks like a very good choice as well.

Robbie, First, I'm sorry to hear about the apparent drive failure/dying, as that is never a pleasant experience. From what you describe, it definitely sounds like one of the drives may be dying. However, if possible, check it's connection (make sure it's not a loose connection). And swap out the cable if you have a spare (make sure it's not just a bad cable that's causing the issues). Well, that really does suck. However, getting some NAS drives is always good.

Yes, absolutely. If you have x3 duplication enabled, it means that you will have three copies of any given file (in that folder). Additionally, the duplication code ensures that we NEVER place duplicates on the same physical disk (in the case of a disk with multiple partitions on it). And we do this because we want to make sure that a failed disk NEVER risks your data. Additionally, this is part of why we don't support Dynamic disks currently. It's a LOT more complex to determine this with Dynamic Disks.

We have definitely considered adding something like this (and we may very well do so). However, implementing this is something that will need EXTENSIVE testing to make sure it works properly. Right now, that isn't feasible, as Alex (the developer) is focused on StableBit CloudDrive and getting that finished. Once that is done, we'll definitely look into this. But to re-emphasize here, this is something that we have talked about a lot. Also, for anyone running Windows 8 or Server 2012, or up... you can use the "/scan" option (and /perf with that), and this scans the disk online (perf runs it at a higher priority). So this may be useful for active systems.

Yeah, it doesn't appear to be disclosed at all. However, I do know a few people that use SpinRite a lot, and it is a known issue. IIRC, it's an issue with the version of DOS he's using ... but I could be wrong (meaning it could be a limitation in the code he's using).

That's odd. Normally, ti should prompt for Admin access after it starts running. That it was not doing that is very unusual.

Yes, when adding a disk to the pool, we don't add the contents automatically. We leave it there, so that you can continue to use the disk as you were before. That way, we don't interefere with your setup. However, you can "seed" the pool (move the contents into the Pool very quickly). To do so: http://wiki.covecube.com/StableBit_DrivePool_Q4142489 Additionally, we do have a number of users that have set up FlexRAID or SnapRAID with StableBit DrivePool. Using our software for the pool, but FlexRAID/SnapRAID to handle parity. If you're interested in doing this, we do have a number of links to threads talking about the best ways to set this up. http://community.covecube.com/index.php?/topic/52-faq-parity-and-duplication-and-drivepool/ Just check out the second post in that link.

I think this is a .... misprint, really. We've had one customer recently reporting that they used this chipset (the ASMedia ASM1061) with an 8 bay enclosure without issues (it was a "DataOPTIC" card specifically, IIRC). However, I absolutely understand not wanting to chance it. And if that is the case, then a HighPoint RocketRAID card (not Rocket, it has to be RocketRAID, even if you don't use the "RAID" part) will work for this.

It's entirely caused by DrivePool, and the way we handle deleting folders IIRC. Specifically, this is the bug in question: [D] [issue #13443] When a folder delete fails because of files in one pool part folder, roll back the delete on any other pool parts. Just to forewarn you, I'm not going to explain this quite right, because this is a VERY low level file system issue. I talked with Alex directly about this, so I don't have the advantage of a nice issue tracker conversation to fall back onto to give a very detailed, accurate and correct explanation here. Specifically, we are marking them as deleted, failing to delete a folder and leaving them in "deleted" state. But this only happens when you have empty folders on other pool parts, IIRC. When deleting a file, it adds a "deleted" attribute to it before actually deleting it. We were setting that when deleting the files (which is normal), but we were not unsetting it when the delete failed (which is not normal). So when you try to access the folder afterwards, it would end up in an unusable state because the file system sees that the folder is in the process of being deleted. The patch corrects this by better handling the delete process, and if necessary, rolling back the changes (removing the attribute) if needed. If needed, I'll flag the thread for Alex, and he can see about giving a better explanation here.

I believe these are the values that the Manufacturer indicates are critical values. These percentages are based on the manufacturer's minimum and "threshold" values. These are also based on the manufacturer's minimum and threshold values. If you mouse over the bars, it will actually list the values so you can see what they are. You mean the RAW SMART data? If so, then no, there isn't a way to see this in StableBit Scanner. If you download the "DirectIO Test" utility, you can see this. However, for the most part, there isn't a need to see it, as we display the data in a much more meaningful (read: human readable) way.http://community.covecube.com/index.php?/topic/36-how-to-contribute-test-data/ The graphs that you see for the temparture are actually stored on disk, IIRC. As for a historical view of the other values, we actually do plan on implementing something like that soon.

We plan on implementing something like this, with a new product (StableBit FileSafe), and potentially more features. As for means to do this now, you could export a "dir" command. That, or something like "File Verify ++" which will check the files. (http://sourceforge.net/projects/fileverifier/)

No there isn't yet. We've been busy working on StableBit CloudDrive, so we haven't been able to focus on getting out any major code changes to DrivePool. As for implementing... it's a lot more complicated than you'd think. While allowing dynamic disks would be very simple.... ALL of the code for Duplication would have to be tweaked, and the balancing engine would have to be overhaul. The big thing is that we prevent duplicate files from being placed on the same physical disk. This ALONE makes a huge problem with the duplication and balancing code.

That is very unusual that it doesn't get good speed. While I only have 12 drives in my pool, I do usually saturate my gigabit network (~100MB/s). Read Striping can definitely help, but that should be enabled by default, and only works with duplicated data. However, Network IO Boost may definitely help out with network performance, but it may use a bit more CPU and memory. And by a "bit" it depends on the hardware in usage. If the performance issues continue, please open a ticket at "https://stablebit.com/Contact" so we can help you more directly.

Generally, because the danger has passed. The issue has already occurred. CHKDSK (what we use for the file system scan) will identify and fix existing errors. It's not really for detecting new issues. The reason we added it to StableBit Scanner is because WHSv1 did run chkdsk passes automatically. But WHS2011 and other OS's don't. So we added it, to add additional health checks, basically. So evacuating the disks due to a file system issue wouldn't help protect your data at all. That is ... if the disk errors would even ALLOW you to move the data off of the disk. As for running the scans, they are handled separately. IIRC, the file system scan happens after the surface scan is completed. Do you mean that it crashes the Dashboard? If so, could you grab the logs from "C:\ProgramData\Microsoft\Windows Server\Logs".

It definitely does. And you can "export" to different formats if needed. IIRC.

Ah, okay, I wasn't sure about the HP controller. And I'm sorry to hear that it does seem to be a major issue getting everything to work properly. As for the BIOS, HSS does have a nice section about modded BIOS' for the MicroServers. Is there not a modded bios for your system?

Not a problem. I completely understand.

Could you open a ticket at https://stablebit.com/Contact ? Also could you do this: http://wiki.covecube.com/StableBit_Scanner_for_Windows_Error_Reports And this: http://wiki.covecube.com/StableBit_Scanner_Freeze And after doing that, try resetting the settings: http://wiki.covecube.com/StableBit_Scanner_Q4200749

You are very welcome. If you need anything else or have any more questions, don't hesitate to ask.