Christopher (Drashna)

Yup, had another user with this bug. Specifically, this is an issue with how Windows is identify the drive and sector size. It's being misreported to us... so we are misreporting the drive size. I doubt it is a coincidence, but the other drive was a WD drive (Red, I believe). Please download the latest beta build, as that should fix the issue: http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.2.3079_BETA.exe

The CPU is a very good one. IIRC, it is still the best "bang for your buck" (eg cost vs features). As for the motherboard, it needs to be a 10th gen board. Otherwise, yeah, you run into the wrong socket. However, here is a list of the X10 (10th gen) series boards, all Micro ATX form factor: http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&IsNodeId=1&N=100006519%2050001655%2040000302%20600452057%20600009017&Manufactory=1655 And here's the one you linked from microcenter: http://www.newegg.com/Product/Product.aspx?Item=N82E16813182819&cm_re=X10SLL-F-_-13-182-819-_-Product As for the server prices, yeah, they're definitely intimidating. But a point that has come up before... if you're using the backup features... that literally pays for the entire OS. I've looked for similar solutions, and either they require hours to get working at all.... or they cost $1000 or more for the backup server functionality... and are licensed per client as well.... But if you're not using the backup, then it may not be worth the cost. (though Microsoft does have a 180 day trial version of all the server OS's). That, and if you're going to run VMWare ESXi (over HyperV), then before you buy the hardware, PLEASE check the hardware compatibility list for ESXi, otherwise you may end up very unhappy. Though, the SuperMicro board should be supported, there is a large gap between "should" and "is".

Storage Spaces is a block based solution, much like (if not almost identical to) RAID. Like RAID, the data is stored in a "raw" format, and read and written to in that style. What does this mean? That the data is in a proprietary format, and may not be readable outside of the system (you should be able to migrate storage spaces to another system, but I've not tested this....). Another issues, is that since is a software implementation, it relies much more on your hardware. You will want a good CPU (it does a lot of number crunching with a PARITY array), and that you will want to have good quality RAM (ideally ECC). DrivePool is a file based solution. Meaning that the data is stored on the disks as normal files. Accessible any time. Also, you should see native disk speeds when accessing the files (or potentially faster with duplication enabled, and Read Striping). The biggest difference here is when it comes to disaster recovery and/or migrating away from the pool. With Storage Spaces... there are a couple of companies (and only a couple) that boast the ability to restore data from Storage Spaces. And their software is $$$$. With DrivePool, ANY recovery software that is capable of accessing NTFS can be used to restore the data. As for migrating away from the pools... with DrivePool, you can just uninstall it and then move around your files as needed. With Storage Spaces... it's a CF. THat's the nicest way I can describe it. But basically, you need to have enough space to empty the Storage Spaces volume.... You may be able to remove some of the disks, so you can play "musical chairs" with the disks... but chances are that you may not be able to.... Another important point here, if you're on a Server OS, using Storage Spaces, and using parity, you should ABSOLUTELY be using ReFS. It supports automatic correction of damage data, by using the parity information.

The OneDrive client uses a new/unique form of file system links that are not supported on DrivePool currently. This means that you will definitely see issues if you try to store it on the pool, unfortunately. For now, it's best to not put the OneDrive folder on the pool.

Well, I hope it's a larger SSD.... I have ~16TBs of various media... and my plex database is ~100GBs. (though I have it configured to download all the metadata it can). So just a warning. And I completely understand the time copying the files.... I just did this a linux VM for Plex... that I may end up removing because it's not working well.

Well, I'm glad that the upgrade/reinstall went fine! As for OneDrive, don't store it on the Pool. The Windows 8 version uses a special sort of file system link (new, it looks like) that isn't currently supported by DrivePool. As for Recycle Bin files, make sure that the Recycle Bin on the desktop is empty. If it already, then try deleting the recycle bin folder on the pool. You may need to enable "Show Hidden Files", as well as the option to show system files, to be able to see it. From there , you should either a "Recycle Bin" folder, or a "$RECYCLE.BIN" folder. Delete that. If you have issues deleting it, then you may need to take ownership of the folder and change the permissions. If you need help doing that, then could you open up a ticket at "https://stablebit.com/Contact" and we will help you there (and likely set up a remote support session).

Not a problem. And sometimes, if you don't know what you're looking for, it can be very easy to overlook.

I'm not entirely sure what you mean by that. Though, depending on what you want, a server OS isn't necessary. Stuff such as a website can be done with the Pro versions of Windows. Same with media servers (though any version of windows should work for that). However, the nice "WHS" type package is nice, but the newer versions are expensive (Server 2012R2 Essentials is ~$400). And it does have some more advanced options. As for managing Drivepool in a VMWare environment, there shouldn't be any issues with that. Just keep in mind, that it's a Windows only OS, and if you want to use the remote management feature, you need to do that from a Windows OS.

The hyperV link does cover that. But to clarify, talk? Not really. They don't pass on information between the two instances. However, you absolutely can do a surface scan of the passed through disks. This will detect issues reading the disk, just as well if it was running on the host. But as you've indicated, you won't be able to SMART data. You can run StableBit Scanner on the host as well, and you can get SMART data there. But currently, there is no way to pass this SMART data onto the guest VM.

Glad I could show you that. It's also the go to place for diagnosing problems. As for the speeds, that ... unfortunately seems about right. There is a lot of reading here, because the backups ARE incremental. And IIRC, they're actually differentiated VHDx files. So it may not be an efficient storage solution for the SMR tech. As for benchmarks, synthetic ones like ATTO and the like are common. But they're synthetic. Copying files and actually using it are the best benchmarks, IMO. And again, yeah the SMR is going to bite for any sort of random access, which will happen for frequent access.

Could you open a ticket at https://stablebit.com/Contact then? Specifically, so you can grab the files from DrivePool: http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection Just do steps #6-8 and upload the files. Also, do this: http://wiki.covecube.com/StableBit_DrivePool_Service_Memory_Dump After doing that, try this: http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

Blue Iris is definitely a processor hog. Either go high end, or a separate machine for it. Otherwise, you'll be hurting. THough a dedicated machine could get away with a Core i5, depending on your settings (direct to disk is best, whenever possible). This works great with DrivePool (is what I have set up, actually, or close to it). Again, definitely a good CPU here. If you're going to be streaming a lot, then a Core i7 or a Xeon E3 is a good choice. And if you compare the specs, they're not that different. Either would work, but if you're going to go server hardware for this, then the Xeon would be better. SabNZBd may require some CPU usage periodically, but nothing like the previous two. And CouchPotato and Sickbeard are relatively light weight. If you're going to be virtualizing, and running the server all the time (or a LOT of it), then a Server motherboard (such as from SuperMicro or ASRock RACK) may be better. It won't sleep, though. But that may not be a concern for you... if it is, a desktop board with a Core i7 may be better. But I would still recommend the server board, as it will have better support for ECC RAM, which would be better for virtualization. As for recommendations, it really depends on what exactly you want. I have a SuperMicro S10XAT motherboard, and am VERY happy with it. As for Server Essentials, yes, it does have the hyperV role... however, it's licensed only for a single VM, and of Essentials. You can use it beyond that, but you will be doing so in violation of the license agreement. Also, if you enable Remote Access in Essentials... make sure that you ONLY use dedicated NICs for HyperV. No sharing NICs, or you'll see hour shutdown/reboot times..... As for disks.... A smallish SSD is a good idea, regardless of the system configuration. As for VMs, I would recommend a RAID array or a very large SSD (and maybe data deduplication enabled on that volume).

Absolutely! Open up the balancer settings, find the "File Placement Limiter" or the "Disk Usage Limiter" (same thing, but we renamed it to avoid confusion with the File Placement Rules). Select the balancer, and you should see a list of ALL the disks in the pool. And each disk should have a checkbox next to it, one for "Duplicated" and one for "unduplicated". Uncheck the "Unduplicated" and ONLY duplicated data will be placed on the disk. Also, you may want to enable the option to "move un-duplicated data off of a disk with SMART Warnings" option in the StableBit Scanner balancer, as well.

Unfortunately, the simple answer is no. Though, this does depend on the virtualization software you're using, and if you're passing the disks through. HyperV: http://community.covecube.com/index.php?/topic/29-how-to-getting-smart-data-from-hyper-v/ VMWare ESXi: http://community.covecube.com/index.php?/topic/131-how-to-get-smart-data-passed-on-from-esxi-51-host/ However, regardless of the software, the surface scan will still work, and should absolutely pick up read issues (which will trigger the evacuation, if it's on the same VM).

Yes, exactly. As for what you need to resetup... well, the pool, the license, and the duplication information will remain intact. That's it. Balancing options will be reset, performance options will be reset, file placement rules will be reset. Any information about existing/old pools will be wiped. Duplication will be checked though (we store the settings on the pool itself, so it's always present). As for the other settings, no, we don't have an export option yet.

If this was the server backup, then run "wbadmin.msc". Open an entry, and it will tell you how much data it transferred. As for client backups... check the modified date?

Unfortunately, we do not support hard links on the Pool. This is important because instead of using a database and storing each file that is needed once.... Plex creates the files in a folder structure for each item in the database, and then hard links the files together. So, no, we do not support the plex database on the pool. As for WHY we don't support it, let me quote Alex (the developer): Specifically, because we are a virtual file system, implementing hard links would be incredibly complex (much more so than reparse points, symbolic links and the like). For a detailed dive into reparse points and how the various types work, there is an arrow in the top, right corner of the quoted text area.

Upload the dump to us. Anytime you have a BSOD that you even suspect is related to the pool, please do so. The reasons is that only "we" have the driver symbol files for the CoveFS.sys driver. Which means that only we know what is EXACTLY happening at the time of the crash. While others can guess, it's nowhere near as good. And that's what all the "Covefs internal function" references are. It's specific actions that our driver is taking. So, please do upload the dump to us. If needed, using the following link: http://wiki.covecube.com/StableBit_DrivePool_System_Freeze There is a Box upload widget at the bottom of the page (you may need to disable the ad or script blockers to see it). ALso, if you want, utilities such as "WhoCrashed" or Blue Screen View will also tell you what it thinks caused the crashes, as well. They're great "quick check" utilities. As for the check, an extended check is always a better option. It takes much longer, but it's much more thorough. Also, what version of StableBit DrivePool are you using specifically?

As lee has stated, DrivePool will handle that for you. However, this won't be instantaneous, it make take a while depending on how much data this is. But once you've done this, the DrivePool Service will go through and check the duplication status on all of the files in the pool. It will delete files as needed, or copy them if needed. Either way, it will denote the progress in the UI, and you should notice the reclaimed free space slowing increase.

What was the ticket/contact number for this issue? Basic or extended check? And how many passes? Also, do you have any antivirus installed on the system? And if so, which? Also, it may be a good idea to physically inspect the motherboard. Look for bulged capacitors, burn marks, warping, etc.

Sophos UTM. It scans everything for me. Otherwise, I don't run any antivirus on my server. If you do run any antivirus, we recommend that you exclude the program files folders for our products, as a lot of antivirus products will occasionally have issues with them and flag our files as malicious.

For Scanner, I'm not 100% sure. Besides ... disks haven't used CHS for addressing in forever, so it's harder to tell. We start from LBA sector 0 and go up from there, IIRC. So yes, it should be in the "center" of the platter, theoretically. As for scanning speed, it should all be sequential. But if the disk is doing something else, it will affect the scan speed. And it could be the disk doing something internally, as well. And i'm not surprised that it runs warmer.... makes sense. As for the seek error rate, wikipedia says it best: (Vendor specific raw value.) Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. The raw value has different structure for different vendors and is often not meaningful as a decimal number Basically, the drive isn't in our database yet, so we display raw values. Submit it to bitflock, and let me know the ID number. Then we can see about adding the correct SMART interpretation. As for the backups, if this is server backup, especially, the inital one, this doesn't surprise me at all. The Server Backup feature uses VHDs and writes block by block, meaning that you should get at least decent performance out of it. The real question is how fast it runs in a week, or month.

This issue should be fixed in the latest beta builds. Specifically, it is an issue with the metadata and it not getting cleaned up properly. http://dl.covecube.com/ScannerWhs2/beta/download/StableBit.Scanner_2.6.0.3055_BETA.wssx http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.596_x64_BETA.exe If you don't wish to install the beta versions, then you can reset the settings on them, and this will also fix the issue (though you'll have to re-setup everything). Regards

Are the disks showing up in "Disk Management"? (run "diskmgmt.msc") If they are not, then something is going on ... and preventing windows from listing them correctly. If they are showing up, then make sure they are "Basic" disks (listed in the left hand column under the disk number). If they are dynamic disks, then that is the problem (as we don't support them for a number of reasons). Otherwise, let us know. Regards

You're very welcome. It definitely makes managing the server that much easier!