Christopher (Drashna)

Andry, I've added a request for Russian language translation for StableBit DrivePool and StableBit Scanner. We handle translations here: http://translate.covecube.com/collaboration/ As for localization, by default, we look at the system to select what language we should use. Also, any build after 2.1.0.450 includes a forced locatization option (CultureOverride) as detailed above: http://community.covecube.com/index.php?/topic/445-change-language-in-drivepool/&do=findComment&comment=2660 Once the Russian language section is added, please feel free to add the translations. We can add automatically translated entries, but we prefer that a native speaker verify the strings.

Since you've already tried the "remeasure" option.... Also, both drives show up as the exact same capacity, correct? As well as the free/used space on the disks?

Just to point out, the Ordered File placement balancer does try to keep the contents of a folder on the same disk. Which sounds like what you want. As for disabling the balancer, did you make sure that you unchecked the "Allow balancing plug-ins to force immediate balancing" option is unchecked as well?

You definitely could. Though I do beleive I'd had somebody with an issue with this card. I'm not 100% certain though. Personally I have the "RocketRAID" version of this card: http://www.newegg.com/Product/Product.aspx?Item=N82E16816115111 You'd need to get breakout cables as well... such as these: http://www.newegg.com/Product/Product.aspx?Item=9SIA00Z0TX9124 This is obviously a it more expensive, but it supports 8 drives instead. And may make cable management a bit cleaner.

done.

From all appearances, I don't see anything wrong here. The Pool Organization Indicator shows that the health is fine. As for the pie chart, that's not a "completion" chart, that's a representation of the the duplication status and size of the pool. However, do you mean that the entire pool should be duplicated, but it's not reporting as such? If so, then select that "Remeasure" option in Pool options, and that should forcibly updated that. Also, is there anything in the "root" directory of the pool?

Bill, Note that build 481 is a significant change. Ironically, because of an issue exposed by HyperV. But for creating files ON the pool, not in the VM. But it may work better. And you can edit the file at any time. But the changes won't take affect until you restart the system or the service.

Okay. If you're experiencing this issue, please open a ticket at Grab the Error reports and the service memory dumps as outlined above: http://community.covecube.com/index.php?/topic/516-bug-missing-drive-error-in-pool/#entry3139

Anything is patentable anymore. Depending on the country you live in. But that's another discussion. But yes, most sort "1, 10, 11, 2, 3, 4" Flagged for Alex. I can't say if it will be changed .... but it definitely won't, if it's not brought up. For reference, this is the "bug" I've created for this issue: https://stablebit.com/Admin/IssueAnalysis/1169 But the actual disk number sorts properly, just not the name. And that's the issue you have, correct?

I'd recommend using the Ordered File Placement Balancer. Why? Here is why: https://stablebit.com/DrivePool/Plugins I think this accomplishes what you want, without disabling balancing.

Okay, so you just want to swap them out. If they're already in the pool, and you have the connectors, just add them to the pool, and remove the old disks from the pool. That's the recommended way. If you don't have the connectors, that gets a bit more complicated. And we don't really recommend imaging/cloning the drives, because of how DrivePool works (you will cause issues if both disks are attached) And as long as the system recognizes the disks as hard drives, or USB hard drives, they can be added to the Pool. However, I recommend using USB drives for the pool for extended periods of time. Mostly because USB devices are prone to power supply failures. And they are not as stable as SATA connections.

You're welcome. if you have any other questions, don't hesitate to ask.

That really depends on the drive, and the manufacturer limits. The Pending and uncorrectable sectors should get mapped to "reallocated sectors" during normal usage (or forced by a chkdsk /r pass, or a full format). Generally, as long as these values are within specifications AND are not climbing quickly, the drive should be okay. Also, since it seems that you're using Windows 8... you don't need to take the disk offline to scan it. If you use "chkdsk /r /scan", it keeps the disk online and usable while it scans it.

Yeah, that can make a difference. But I've always done that, as I'm a bit OCD... (you should see how my music is organized....)

Actually, this happens naturally during the life of the disk. Normally, it will reallocate the sector eventually or recover it. But it usually is invisible to the end user. A chkdsk /r pass on the disk may "clear" up the setting (but likely increase the Reallocated sector count). And here is the definition from wikipedia:

Bill, So it sounds like when the Client Backup Service is "moving data around" is when the issues are occuring here. Are you still using the 2.1.0.432 build of DrivePool? If so, would you be willing to upgrade to a more recently internal beta build and see if that helps? http://dl.covecube.com/DrivePoolWindows/beta/download/ (newest at bottom). If you are not willing, I completely understand. As for the background IO setting, the one I believe Alex is referring to is "FileBalance_BackgroundIO". Set this to "False". There is also "FileDuplication_BackgroundIO". This does the same thing for duplication (but is less likely to benefit you. The "DrivePool_BackgroundTasksVeryLowPriority" setting sets the DrivePool service to use a higher CPU priority. This doesn't affect the IO priority, and wouldn't affect this issue. The "CoveFs_BoostNetworkIoPriorityWrite" boosts the priority for network writes. But the Client Backup Service isn't using a network path, and shouldn't affect this issue either. Regards

That form doesn't support larger than 10MB files. The upload form on the above links uses Box.com and stores it there. That's what we recommend. However, if you want, upload it to DropBox or OneDrive, or similar cloud services, and then use the https://stablebit.com/Contact form to send us the link to the files (and this thread). Also, for those experiencing this issue, what version of DrivePool are you using?

Find the disk in question, click on the "+" button on the left hand side, Now find the button with the green circle, with a circular arrow. Click on that, and mark all as good or unchecked. That should fix the issue (and is the normal way to do this).

Well, I would recommend checking the contents of the old Poolpart folders, and delete them once empty/unneeded. At least to keep it clean. If you're still having issues... let us know.

umfriend is pretty much spot on. Or you could use "Ctrl00Disk00" for the name. (Ctrl short of Controller)

In theory, the balancing module uses a background IO priority, which means that it should not interfere with normal usage. In fact, if you enable "network IO boost", it priorities network traffic over local disk activity. This uses a bit more CPU overhead, but should do what you want. And two SSDs should get you great read speeds. But as for performance, I download directly to the pool, while access MKV files. Without any buffering issues. As for performance issues, if you are experiencing any, then check out this link: http://forum.wegotserved.com/index.php/topic/8335-before-you-post-media-stuttering-playback-issues-performance-irregularities/ It's for WHSv1, but most of the stuff applies to .... well, any version of Windows. I'd recommend checking it out.

Do you mean this? http://wiki.covecube.com/StableBit_DrivePool_Q5463715

The Pool will mark ~2TB of that space as "Unusable for duplication, so you will only have 2TBs of space available for duplciation (1TB on each drive, so 1TB of data). If it's not increasing, then it should be fine. Emphasis on "should". If it increases, then you may want to consider it. As for the bad sectors, as soon as they are written to, the disk should "fix" them. That means a full format, a chkdsk /r pass, or ... just normal usage. We don't do it automatically, because we never want to risk your data's integrity. And to be blunt here: if the disk reallocates the sector, you CANNOT recover the data that was there. Period. And we don't want to cause that, just in case. And yeah, I post a lot at Home Server Show forums. as well.

Safer is always better! And yeah, Dynamic disks are tricker to move from... But again, just copy the data out first, then break the mirror, delete the dynamic volumes (they'll be a different color than the other disks) and that should "convert" them to basic. (It should say "Basic" under the disk number).

RJGNOW, That's.... bizarre. Are all of these PoolPart folders hidden? If they are... then something odd is happening here. If they are not hidden, then that's normal, usually. When you remove a disk from the pool, it leaves the PoolPart folder there (in case it missed anything) and "un-hides" it.