Christopher (Drashna)

I live in the San Deigo area, so yeah, lots of dust. That, and lots of animals. I'd be more inclined to believe it is the box it's in or maybe the controller card. That's where I'd put my money. But swapping out the cable should be trivial, and very easy/quick to test.

Okay, I wasn't sure. On the DrivePool UI, when it's measuring, it has a small "pac man" type icon in the bottom left corner of the Pie Chart area to indicate that it's still indexing. And from the sounds of it, it wasn't still indexing. If that is the case, it is possible that it got interrupted. Such as if it got rebooted, or needed to do a balancing/duplication pass.

Dust and stuff... I live in an area that everything gets dusty, so I have to clean out my server and other computers every six months. As for burning out cables... There isn't a cable type that I haven't burned out at least once. that includes SATA cables, cat5(e), and even Coax.

Scanner is definitely compatible. The underlying API that it uses has not changed. You can use either the "Windows 7" or the "Windows Home Server 2011" version. The difference is that the WHS2011 version will deploy over the network and will have a dashboard tab. As for DrivePool, that should be compatible. I know it's been extensively tested with the Preview version, and has no issues with it. And it should work fine with the RTM version.

It's possible that it's blocking that. You could check by running the stand alone app for it as well: https://bitflock.com/

I can't say that I'm completely surprised by that. The next time that happens, would you mind getting a memory dump of the system? http://wiki.covecube.com/StableBit_DrivePool_System_Freeze This will cause BSOD (it's intentional), but just make sure that you run the "bugcheck off" entry after doing this.

ACtually, the other is okay. It's supposed to be there. There is a nice post about that, as well as a blog post: http://community.covecube.com/index.php?/topic/37-faq-unduplicated-vs-duplicated-vs-other-vs-unusable/ But basically, it's any files outside of the pool (such as data on it already when you added it, or shadow copies, or the recycle bin on the hard drive). As well as "misc used space", as in that 1kb file still takes up the 4k sector. And the discrepancy gets reported by NTFS, when is what we read, and calculate the usage.

Kihimcarr, Okay, then something weird is definitely happening here. I suspect that it may be the "Virtual disk server" not updating properly, but I'm not sure. Would you mind grabbing the Error Reports and opening a ticket? http://wiki.covecube.com/StableBit_DrivePool_2.x_Error_Reports

Blake, DrivePool does and can move files around, but that should be completely invisible to you. I also run utorrent on my server, and I have not had an issue download or seeding from the pool. However, if you wouldn't mind enabling the "trace logging", so we can help track down this issue: http://wiki.covecube.com/StableBit_DrivePool_Log_Collection http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Glad to hear. If you have any other issues, don't hesitate to ask us.

No, neither version supports VSS at the moment. Microsoft has pretty much *no* documentation about implementing the feature, so getting it to work relies solely on trial and error to get it working.

Yeah, that will definitely wear the disk out rather fast. But that 97% is after ~220 days of running it as the system drive. On my desktop, I have the same SSD (Newegg screwed up), running for ~160 days as well, with the wear at 99%. Both of these are system disks. But I try to not install anything to the SSDs. Also, if you're using duplication, you'll want two feeder disks.

It's very likely. Unfortunately, it does happen. Also, Scanner's surface scan will cause the reallocated sectors to show up more often (well "appear" more often, but it just triggers the internal error correction mechanisms, and report it via SMART). I've also... done the not as great thing, and shelled a bunch of Seagate Backup Plus drives for my 3TBs.

I have already replied to your ticket, but : It sounds like the WIndows Search database got corrupted. Just try rebuilding that, and it should fix the issues with DrivePool: http://wiki.covecube.com/StableBit_DrivePool_Q7200705B Regards

Just want to make sure, all the clients are using build 400 as well, right? And you've double checked that the peer list is still properly configured.

Things you lose by upgrading: The "Stable" label, for now. It's an RC, but ... still. There are bugs possible. But that's only for now. Major dashboard integration. There is a tab, but you lose the tab under storage per folder/type information, Pie chart of folder distribution Things you gain Remote control, without using the Dashboard updated drive for drivePool (most changes are backported, but there is more active development on 2.x) larger list of supported OS's Per folder duplication Greater than 2x duplication This list isn't comprehensive. It's basically off of the top of my head. However, balancing shouldn't be affected, nor duplication. At least not significantly. Nor is disk usage (however, it is displayed a bit different)

I believe this is information from the Drive's SMART data, so definitely drive dependant. But i'm not 100% certain about that.

Well, for Scanner, you can change the disk activity sensitivity. And do you have the "Read Striping" and "Network IO Boost" options enabled for DrivePool (should be under Pool Options->Performance) If you already have those enabled, if you wouldn't mind, could you enable "Tracing Logs" on the "server" and try duplicating the "issue" and then submit the logs? http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Try resetting the settings for Scanner and DrivePool (you'll have to reactivate): http://wiki.covecube.com/StableBit_DrivePool_Q2299585B http://wiki.covecube.com/StableBit_Scanner_Q4200749 If the problem persists, then please let us know.

I have seven of the ST3000DM001 drives, and none have any reallocated sectors. All of them are the -9YN166 model, but still. And they are the CC9E or CC9F firmware. This could make a difference. It is possible that the drives are from the same batch, and that batch has a defect (this unfortunately does happen, with *all* manufacturers). If you are very concerned, check with Seagate support and you should be able to RMA the drives. May be a good idea if the reallocated sector count keeps climbing (as this would indicate a serious defect)

It sounds like it is reindexing/remeasuring the pool. This is normal. If this takes an excessive amount of time... then it may be stuck, and resetting the DrivePool settings may correct the issue (but will force it to reindex it again). http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

That doesn't quite cover the 1.x to 2.x upgrade though. Basically, uninstall 1.x, reboot, and then install 2.x. Your pool will remain intact, though you may need to change the letter (via disk management).

I only do the "file placement limiter" for removing the drives. And.. for drives that I know may be in less than perfect health, I leave the "duplicated" option checked, and uncheck the unduplicated option, that way if the drive *does* fail, I only lose duplicates, and not any "unique" content. But I do leave the "balance immediate" options enabled. Though, I do have the "not more often than" enabled, as everything has "settled" properly and this helps prevent unnecessary activity.

You'd have to do it for each drive individually. If there is an issue with the controller, it should show up on any drive attached to that controller as well.

Set the "Automatic" balancing (in the first picture) to "Balance Immediately". (and ideally uncheck the "Not more often" option as well). That should automatically move the files off. (both of those settings are in the first picture you attached.