Christopher (Drashna)

And this is why we are not officially supporting Windows 10 until is has hit RTM (release) or is VERY close. Because the product is essentially a public ALPHA release... it is subject to drastic and total changes. And unfortunately, it does seem that you are being negatively impacted by that. Worst case here, if you need to get up and running, you can download the Windows 8.1 Enterprise Eval disk and generate a key for that: http://www.microsoft.com/en-us/evalcenter/evaluate-windows-8-1-enterprise It is a 90 day trial. Alternatively, Microsoft has a 180 day Eval of Windows Server 2012R2 Essentials, as well. http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2-essentials

Topic moved, so no worries there. As for the speeds, and Read Striping, I'm not exactly sure. I'll have to ask Alex (the developer) about this. However, for all intents, there shouldn't be a significant difference between SATA II and SATA III. The SATA II (3gbps) bus should be able to get very fast speeds (around 400MB/s) without any issues. Far faster that most "spinning" drives. However, if the bus speed is detected as much slower, then yes, the Read Striping feature should read from the faster drive instead.

I'm glad to hear that once you got the config file working right, that it seems to be working just fine!

The one that the friend had was the USB3 version of that, and it did work well. I haven't messed with this enclosure specifically, yet.

Exactly. iLO is HP's version of out of band management, which uses a dedicated card, IIRC. Intel vPro/AMT is Intel's version (and requires CPU and motherboard support). IPMI is "generic" and requires a special, "secondary" chipset on the motherboard.

yeah, backup database corruption is/was fairly common. There have been updates to fix the issue. But if the database got corrupted by the failing disk (which is very likely), or the database wasn't duplicated... then this will definitely happen. And I highly recommend checking the duplication status on the backup database folder. Make sure it's set to AT LEAST 2x. 2x (or just 'duplication enabled") means that there will be a copy of any given file on two different disks. Setting it higher means it will be on more disks (and take up more space in the pool). Setting it to 3x may be a good idea if you suspect issues. Alternatively, you could create a script to stop the backup service, copy the files and start it back up. You could then setup the Task Scheduler to run the script once a month/week/etc. That way, you would always have a good copy somewhere else.

Sounds about right, given their use case. I'm wondering how well they'd fair in the pool honestly. I'll be finding out soon.

You mean other than an SAS expander case. Right? Those can hold a lot of disks. As for an enclosure, I'd recommend IcyDock or something else. Like, really anything else. I've had a friend use this brand: http://www.newegg.com/Product/Product.aspx?Item=0VN-0003-00065 It seems to be very stable, from that I could tell.

To be clear, you're using Data Deduplication on the disks that are IN the pool, correct? If so, then there is an advanced setting that you HAVE to enable to (hopefully) get this to work, otherwise, you will definitely see the issues that you are reporting. http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings Find "CoveFs_BypassNtfsFilters" and set this to "False". However, even with this setting configured, it may not work. The reason for this is how the Deduplication process works. Specifically, it uses a file system filter (you can view these with "fltmc"). Normally, when you access the file, the filter intercepts the request and can modify it (this is also how antivirus programs work). Deduplication requires this, as only part of the file is stored in the normal location. The deduplicated part is stored elsewhere on the disk (in the "System Volume Information" folder, actually, I think). So when you access the file normally, the DeDup filter re-joins the deduped data with the rest of the file, to present the whole file. However, the driver for the pool bypasses the NTFS filters (for performance and compatibility reasons). This means that the Pool is only picking up the non-deduplicated data, and present "corrupted" files to you. Disabling the "BypassNtfsFilters" option will cause the pool to respect the filters, and should "fix" the data.

I'm not entirely sure that the "\*" rule will work, but I am absolutely certain that "\Foldername\*" will work. So if you are using WHS2011 or Server Essentials (as it appears that you are), then you could use "\ServerFolders\*" for the rule and that should work exactly how you want. Additionally, we do have a section in the manual that goes over the File Placement rules: http://stablebit.com/Support/DrivePool/2.X/Manual?Section=File%20Placement

Unfortunately, it sounds like the Client Computer Backup database lost one or more files. You may want to delete the entire contents of the folder and start from scratch. This may be the only way to proceed. (you could just move the contents to a different directory, it produces the same result). Also, if you grab the logs from "C:\ProgramData\Microsoft\Windows Server\Logs", and check the Event Viewer ("eventvwr.msc") and check for errors related to the services. These may give you a better idea of what is going on. However, they can be a PITA to read. If you want, email them to me at christopher@covecube.com and I'll take a look at them. As for the chkdsk, you cannot run that on the DrivePool drive, as it's an emulated disk. However, you can run it on all of the disks in the pool. Just note that it will unmount the disks, and produce a "missing disk" error until the scan completes.

I'm sorry to hear that you did lose a few files. But I'm glad to hear that everything went smoothly otherwise. As for StableBit Scanner: If you own a copy of StableBit DrivePool, you can get StableBit Scanner at a discounted price. To do so, grab your StableBit DrivePool Activation ID, and head to "https://stablebit.com/Buy/Scanner/" and scroll down until you see the "Already own one of our products?" section. Input your Activation ID into the box and hit "Apply Activation ID". Once you've done that, it will will refresh the page with the discounted pricing ($15, instead of $24.95). Depends on how you mean. If you mean to view the pooled disk (eg, to be able to access the files), then you'd need to share the folders and use an app to access the files (or us a media server such as Plex). If you have shared folders on the pool, then this maybe useful: https://itunes.apple.com/us/app/fileexplorer-free/id510282524 If you mean to manage the pool, then no, there isn't a way to do this on a mobile device directly. However, you could use Remote Desktop, VNC, or TeamViewer to access the system and control it that way.

..... I have a few of those laying around... And a few WD drives too. Well, varying from 2GB to 6GBs. But none are in use. I don't have a PC capable of IDE, and haven't for a while.

Personally, I would recommend against the MediaSonic boxes.... Both Alex and I have had issues with these boxes, as have a few customers. Also, Newegg indicates that it only supports up to 4TB drives. Though, you are right, it's website indicates that it supports up to 6TB drives.

Well, since the default strategy is to fill up disks all at the same time (specifically to place files on the disks with the most available free space), I don't think this would be too difficult. So specifically, you want a balancer that would allow you to create groups of disks to be filled, one group at a time. Are you using StableBit DrivePool 2.X? If so, then you may be able to do this already, by using the "File Placement rules", in theory. Create a rule for "\*" and select the disks you want. Then make sure that you use the option (at the bottom) to "Allow files to be placed on other disks if all the selected disks are this full", and set the slider to something reasonable, like 90% (this prevents the disk from becoming too full, just in case). This should

What mode is the enclosure in? And once the Unsafe option is enabled in DirectIO, it should work with the HighPoint card just fine. However, could you download the "DirectIoTest" tool from here: http://community.covecube.com/index.php?/topic/36-how-to-contribute-test-data/ Run it on the system and select the disk that is having issues. It should (hopefully) light up the "SMART Attributes" option for either the WMI or DirectIO (or both) section. If it does, click on the ellipse ("....") button and make sure it's listing information. If it is, then let us know.

In that case, you don't need the WHS style OS then... and ESX may be a better idea. As for the HCL, I'm genuinely surprised that the SuperMicro boards are not on it. So I dug... their hardware does appear on it, but not as motherboards. They only list the pre-built systems. In fact, this was one of the supported systems: http://www.newegg.com/Product/Product.aspx?Item=N82E16816101791 But it's better to be certain here, I think. As for the BIOS issue, .... yay. that's fun. And speaking of which, for a headless system, I highly recommend a board that supports Intel vPro/AMT or IPMI, as these allow for "out of band management". Meaning you can view the "console" over the network. The intel board you linked has IPMI, so you're set, just remember to enable it.

Depends on the issues, really. In a lot of cases, the full "Zero pass" may fix a lot of issues because it's causing the disk to write to every sector, and triggering the drives' error correction routines. After this, a format isn't really needed (a full format does a zero pass of the partition). And as for a chkdsk, it may not be a bad idea, but again, may not be necessary. But letting Scanner do a full pass of a Surface scan would be telling. As would looking at the SMART data afterwards. And just FYI, I've done this on disks before (specifically that had uncorrectable sector count SMART warnings and damaged sectors). It converted all of the uncorrectabler sectors into reallocated sectors (which is fine). However, after a while, the uncorrectable sector count continued to increase. The moral is... if issues continue, then RMA or toss the disk. Or use it for non-critical data. I've has the opposite experience. Most of the disks I've had go bad on me generally did give SMART warnings prior to failing. The batch of bad ST3000DM001's that I had all showed uncorrectable sector counts in SMART. I pulled them immediately.. Two of them completely failed shortly after pulling them (I was using them for testing). However, given how the disks work, there are plenty of ways for them to fail, including suddenly. Though, I've found the most important metric on drives to be their warranty period. Not only is that a good indication of longevity, but it usually lines up with the component lifespan info. As for that old 20GB, that's pretty amazing. Though, I'm sure it's slow as dirt compared to the newer drives. That's the trade off, the newer drives pack a lot more tech in them, which means there are more points of failure.

Absolutely. There should be no problem with that, at all. Other than getting it mounted when you reboot (but you could use a script to do that, if needed. To clarify, you're having issues with StableBit DrivePool on the newest Windows 10 build? Or with OneDrive? Or? I'm not entirely sure here. And yea, the "Tech Preview", it's an Alpha product.

Yeah, taking ownership of the files may be a good idea when rebuilding the pool. It's pretty much the "end all" for permissions. However, just make sure you a) replace the child entries when you do this, and change the permissions as well (Admins, system and owner with full control, and Users with read and execute). This will ensure that everything is accessible and usable. And should definitely clear up the issues you were seeing.

Glad to hear it!

Investigating the issue and fixing it (if possible) is definitely on our "To-Do" list. However, I can't really give you an ETA. Alex has been focusing on getting "StableBit CloudDrive" out as soon as he can. Once that's done, there is a bunch of code to backport to DrivePool (such as a much better issue feedback UI), and then onto hitting the to-do list. While I know that's not really a great answer, we are a small company, and we are doing what we can, as fast as we can.

Well, I'm glad that you were able to identify the problem, but I'm very sorry to hear about the server crash! And if that was the case, then it sounds like maybe a disk issue with the system disk... Or the drivers for the USB3 controller or externals got corrupted, maybe. But either way, if you need anything else, let us know.

Yeah, it is. Microsoft does a fantastic job of hiding a lot of these types of files form the user (which is a good thing in 99% of cases).

Thanks for submitting. I've flagged alex, and we'll see about adding a proper interpretation for these drives. And I meant to use "VHD(x)". But either way, I'm glad to hear that it is working well. And yea, the write performance is most likely due to the SMR technology (shingled magnetic recording). Ironically, the best analogy is ... shingling a roof. It's easy when you do it layer by layer. But if you have to replace a single tile/shingle, it's a PITA to do so.