Christopher (Drashna)

Well, it sounds like the write errors are due to that "missing" disk. That's normal when that happens, actually. This is to prevent the data from potentially from getting out of sync. As for what to do, is the disk missing? Or does it show up as "RAW"? (check "diskmgmt.msc"). If it's showing up as raw, there are "partition recovery" tools that may fix the issue, and make it rather simple. Otherwise, you'd want to "remove" the missing/damaged disk from the pool. This should be rather quick. Once that's done, the pool will go back to a working condition and it will run a duplication and balancing pass, as per your settings. Then you'd either replace the disk with a new one, or format the "damaged" disk.

Henry, If it's not creating the dumps, then use the link above. The system may not be configured to take the crash dumps properly. And you MUST have the page file enabled on the system disk, as well. There is also a folder of "minidumps" in "C:\Windows\Minidump". If there are any files in there, then upload them. Also which driver is specifically causing the issue? If it's CoveFS, then it is use, as that is the file system driver we use. If it's not... then it may not be. But post which it is. Alternatively, you can use a utility called "WhoCrashed" to view the basic information, if it is there.

Could you get a memory dump of the system when it's doing this? http://wiki.covecube.com/StableBit_DrivePool_System_Freeze And you may need to enter safe mode, and copy the "MEMORY.DMP" file off of the C:\ drive before restoring. Also, if you wouldn't mind testing it: set the "StableBit DrivePool Service"'s startup type to "manual". You may need to do this in safe mode. And once you've done that, please stay on 2.0.0.420 until we can isolate what's going on here. Also, are you using any antivirus software on the system?

I need to apologize, I misunderstood some things, or made some assumptions that were incorrect. So let me correct that here. When "Real-time duplication" is enabled, it doesn't make a periodic duplication pass. However, it does do one forcibly, when you change the duplication status, or level. If you change a folder's duplication status, it checks just that folder. If you change the "Pool File Duplication" status, it will check he entire pool. However, if real-time duplication is NOT enabled, then it will make a duplication pass, every day at 2AM (or whenever it is configured to). Additionally, the background duplication pass looks for any 3rd party app/user errors (access/modifications). It also compares each file part using the file size and times. If there is a mismatch, then it performs a hash check. If they're identical, then the file times are synchronized. In theory, between this, and StableBit Scanners surface scan, there should be no disk related corruption. Or at least, you should be notified of it. Specifically, the scan should "exercise" or "scrub" the disk to help identify disk errors before they affect your data. And should identify any issues with the disk itself. Though, talking with alex (in a large part because of this thread), it sounds like he is definitely seriously considering creating an integrity checking app. That would integrate with DrivePool.

Amanteka, What version of DrivePool were you using, and which were you upgrading to? And what OS are you using? And was this BSODing at the welcome screen? Or was this a normal reboot, or a sudden reboot? Also, would you mind doing this: http://wiki.covecube.com/StableBit_DrivePool_Q3017479

Ah, okay. And yeah, specifically the issue is that it will not let you add locations that cannot be indexed. And you cannot index network shares normally. I think the only way to do that would be to configure the folder to be available offline (using "Offline Files" feature). The downside is that this will cache the contents to the local disk. But it will be indexed. Unfortunately, HomeGroups cause all sorts of other issues, and don't work as well as it's advertised to. And since HomeGroups is basically "hacked" into WHS2011, it sounds like you've definitely broken something here. And unfortunately, I suspect that it's related more to the home groups stuff, than for the storage service or DrivePool. You can verify that by creating a custom shared folder on the pool. To do so, create a new share, add "Everyone" to the allowed users, and set it to "Everyone". It should show up in the dashboard (may require a restart). From there, you should be able to modify the permissions on the dashboard. I'm not 100% certain of this, but would be worth checking out. Alternatively, if you have a backup of the server, I'd recommend backing up to before you made the configuration changes and "be done with it". However, if you don't have a backup.... Also, if the issue is moving the folder to the Pool.... Running the "WSS Troubleshooter" utility, and selecting the "Rebuild DrivePool Shares (OS reinstall)" option may work to "force" the share to that folder. http://wiki.covecube.com/StableBit_DrivePool_Utilities

Worst case, change the duplication, and then change it back. This will FORCE a duplication pass to occur.

I've seen some indication that the enterprise drives aren't significantly different, except in the warranty period (backblaze's blog) (5 year warranty as opposed to 1 or 3 year). However, the NAS drives definitely use a different firmware than the desktop drives, are supposed to run at a bit lower temperature, and consume less power. I do think they tend to have a larger cache size, but I'd have to double check that. That, and one of the major differences is that enterprise drives and "RAID Edition" drives use "TLER" to prevent the deep cycle error correction from occurring (or lasting long enough for the RAID controller to drop it out of the array). Here is some of the information about the NAS drives: http://www.wdc.com/en/products/products.aspx?id=810 http://www.seagate.com/internal-hard-drives/nas-drives/nas-hdd/ And a good comparison: http://www.storagereview.com/seagate_nas_hdd_review But basically, if you want good, consumer grade storage, the NAS drives are a good way to go. But if you are willing to spend almost twice as much money, the Enterprise grade drives are better.

To be honest, when I've tested this in the past, it's flagged it right away (within minutes) but that was on a very, very small pool (for testing). I've flagged Alex, to well, get verification for this, and more info. Though, I want to say that this happens at 2am, usually.

Kris, To make sure, are you on either 2.1.0.558, or 2.1.1.561? Either version should be fine. There was an issue with what you describe in older, internal beta versions, but that should be fixed now. However, if you are using one of those versions, and it's still having the issues, then that is definitely a problem. As for importing and exporting, no, there isn't yet. But most of these rules may be simple enough to not need one. But I can definitely see the appeal/necessity, if you have a large number of rules.

Uninstalling DrivePool shouldn't affect those bays/cards. If it was a RAID type solution, I could understand it... but as Windows will still see and access those disks even if StableBit DrivePool isn't installed, there shouldn't be an issue. However, the antivirus programs *could* be causing the issue though. However, I'm not able to replicate the issue on a VM. Though, if you were having memory issues before, maybe running another memory test now wouldn't be a bad idea.

NAS drives are designed to be more power efficient, and idle better, but without the hit to performance that the GREENs (or other lower power disks) suffer. And tend to not generate as much heat. But yeah, they definitely do have a different firmware. So I guess, it really depends on where your preference is.

Naturally, all these sales happen, after I've bought 2-3 of them.........

Speaking of which. Do you have any antivirus installed? Especially Avast? That, or uninstall DrivePool, and do this: http://wiki.covecube.com/StableBit_DrivePool_Q2159701

In theory, it should happen once a day, I believe. Specifically, it's part of the duplication pass, that should be happening once a day. Well, I'm glad I could help out there.

Since the drives are presented as normal disks, there shouldn't be any issue. In fact, RAID arrays are more sensitive, and that's why they may have disks "fall out" of the array. StableBit DrivePool doesn't have that problem. Same. However, I've got two disks that are a bit over a year old, with serious issues (500+ reallocated sectors, and 1200 uncorrectable sectors on the other) that I cannot RMA, because they're disks from external enclosures that I ripped apart. It's worth spending the bit more on drives that have a usable warranty... And in that case, I would recommend any disk designed for NAS or enterprise storage. WD Reds or Seagate NAS drives are fantastic for DrivePool. And they are what I would recommend.

You're the first case I've heard about any issues with the update... And the system definitely should not be doing that. Though it sounds like it may be related to DrivePool (updated device driver). If you wouldn't mind, could you do this: http://wiki.covecube.com/StableBit_DrivePool_System_Freeze If you do mind, then please, uninstall the old version, reboot, and install the new version (reboot if prompted). If you continue to experience the issue, please do the above. (and I've moved the post to the appropriate forum)

Given how hard links work (only between files on the same volume).... And for reference sake (in case somebody wants to know why, or more details): http://blog.covecube.com/2013/11/stablebit-drivepool-2-1-0-432-beta-reparse-points/

I've not heard of the issue with sharing that you have mentioned. However, it is much easier to set up with HomeGroups. However, as you've basically learned, HomeGroups are horrible, and it's implementation is atrocious at best. To be honest, I would recommend removing/disabling the homegroups and go back to a "work group" layout. In that scenario, you'd need to have matching user name and passwords... or store the correct ones in the "Credential Manager" (Control Panel->Users). As for the shares... make sure you reconfigure them in the dashboard, and that will "restore" their permission settings, and may fix the issue.

... Neither was I actuall. I just have a passion. But as I said above, for files that are very important, or irreplaceable, you should definitely use that "3-2-1" strategy. Because what happens if you accidentally delete the files? Sure, there is data recovery, but that may not get it back 100% intact. And I do think that I really did get Alex to seriously considering creating some sort of integrity checker. Hopefully. No. Normally, when it checks the duplication, it checks that the there are the expected/correct number of copies, and compares the file hash of both. I'm not sure if you've seen it, but the "file mismatch" error? That's what it's complaining about. The contents don't match. If you want, test this out with a simple text file. The notification may not be immediate, but it WILL happen. I don't consider it hijacking, actually. This is all very related information. And if AMCross didn't ask, I'm sure it was probably on his mind. As for the silent data corruption, or "bitrot".... well... that's a funny term. Because there is no real good definition for it. And better yet, for what is happening, theoretically, between NTFS and the disks' Error correction routines in it's firmware..... it shouldn't happen. Also, it's very possible that the corruption is much less esoteric. Windows Search tries accessing the files periodically, and other tools may as well. If they open the file as writable, or updates it's metadata... or any other program does the same.... it could cause the issue as well.

I do believe that StableBit DrivePool does do a hash check of files when it runs a duplication pass. Also, there are a couple of reasons I mentioned accessing the file via the PoolPart path directly. If it's duplicated, it's possible that only one version is corrupted, and the service hasn't run a pass on it yet. This way, you can verify and resolve the issue yourself. Also, it could be an interaction with the pool causing the issue, and the actual files are fine. And by "interaction", I mean with something like Avast or other antivirus software. They install file system filters and could cause complications if they don't handle the Pool drive properly.

you are very welcome. If you have any other questions or need any clarification, don't hesitate to ask.

I don't believe there is currently. However, I've flagged this for alex to review and fix: https://stablebit.com/Admin/IssueAnalysis/5246

Given that your HDD can only access data about 120MB/s (average).... and that 4TB is ... well, 4 million MBs... that's roughly 9 hours and 15 minutes to scan a 4TB disk. So that seems right. And as Umfriend has said, StableBit Scanner is good about throttling the scans based on usage, to prevent bottle-necking or impacting the performance. As for the "timeout".... it does that. If you open up the volume map, (click on the "+" next to the disk), it marks each range with when it was last scanned. It then uses THAT information to determine when to scan each SECTION of the disk. Not the whole disk, but section. That means if the scan got stopped part way because of activity and didn't start till the next day... those two sections will have different deadlines. And that also applies to disks, as well. Also, StableBit Scanner can and usually does scan multiple disks at the same time. By default, it scans one disk per controller, but you can disable that functionality in the Scanner settings. That *may* speed up the scan though, or it may bottleneck the controller...

Well, I've flagged the request for alex (if it's again, that's fine) https://stablebit.com/Admin/IssueAnalysis/5243 And I was talking with Alex about it again. I do try to keep pushing for it, because it is a great idea. Hopefully, Alex will decide to whip something up.