Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11549
  • Joined

  • Last visited

  • Days Won

    365

Everything posted by Christopher (Drashna)

  1. If you're having issues with the drives, then that may be a good idea. As for the wiki, it's definitely a tried and true method. You shouldn't have any issues with it. However, if you do, then please let us know and we'll try to help you however we can.
  2. How are you adding the contents to the pool? If you copying everything to the pool using a command line utility or the like, it could definitely cause the recursive folder structure like this. Specifically, when moving existing data into the pool, using our "Seeding" guide is the best method: http://wiki.covecube.com/StableBit_DrivePool_Q4142489
  3. It absolutely will. Not too dissimilar to my setup, and mine runs fantastically.
  4. Could you do this: http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection And reproduce the error? Once you've done that and submitted the files, could you reset the settings and see if that helps? http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
  5. Well, the StableBit Scanner software can submit info to BitFlock. But yes, we are hoping to integrate all this together into a much more cohesive package, in the future.
  6. This depends on the Synology box. I'm assuming that you're referring to the consumer grade boxes, that are using the Synology DSM operating system. If so, then this is actually using a distro of Linux. This would require porting over all of the code. Additionally, because the DSM OS uses a form of RAID, we may not be able to get the disk information anyways.
  7. First, I'm guessing that the D:\ drive is the DrivePool disk. It's not clear from what you have said. So, unless corrected, I'm going to assume it is here. This depends on what exactly you plan on doing. But to completely remove a pool, you need to remove all the disks from the pool. This means that you need to empty it, and based on what you've said, that may be problematic for you. However, if you remove most of the disks, or at least some, you can then add those disks to a new pool. This would at least partially simplify things for you. Depending on which OS and version of DrivePool you are using, you can absolutely set per folder duplication. It's one of the core features. If you're using StableBit DrivePool 2.X, open the UI, click on "Pool Options" and open the "File Protection" section. The "Folder duplication" option lets you specify which folders are duplicated and which are not. So you could duplicate one folder, but not another. Or even enable duplication for a folder, and disable it for a sub-folder. Depends on what you're trying to accomplish, but there shouldn't be too much of an issue. However, why do you want do this? Specifically, what are you trying to accomplish here?
  8. Well, thank you for the kind words! As for which version of StableBit DrivePool, it doesn't really matter. Both the license and pool are compatible with both versions. However, the v1.X product does feature better integration with the WHS code (it uses the indexing to display the amount of data in the folders, as well as has a "Pool" tab where you can add and remove disks and change the duplication status). However, the v2.X product is newer, and has more features (such as stand alone remote control, reparse point support and File Placement rules). And there should be no issue with installing v2.X and popping in your existing disks. It will see them as pooled disks just fine. There is no conversion needed. And if you decide that you like 1.X better, you can uninstall the current version, reboot and then install the 1.X version. You'll probably need to reactivate, but otherwise, there isn't anything else you'd need to do. So yes, it's purely a structure constructed on the disk. Specifically, the pool is located in the hidden "PoolPart" folders, and we don't change the formatting of the folder between versions.
  9. First, we absolutely do not mind. This is migrating your data, and it's a very sensitive subject. Nobody wants to risk their data, so we absolutely do not mind the questions. And very nice. Sounds like a very fun upgrade. Yup, pretty much just that. Once the disks are moved over, StableBit DrivePool will recognize the pooled disks, and recreate the pool. However, you do need to move ALL the disks over, or they won't be included (the new system won't know about the rest of the disks yet). Well, first, make sure that the disks migrate properly to the new controller. If not, it may be best to move that controller over. What I mean, is that some RAID cards are very picky about how they pass disks through, and can cause issues migrating to different controllers. In most cases, this is not an issue, but it's always worth checking out FIRST. As for organizing the disks, we actually have a guide for that. But specifically, it's mounting the drives to a folder path, instead of as disk letters. This also has the advantage of cleaning up the drive list in "Computer"/"This PC". http://wiki.covecube.com/StableBit_DrivePool_Q4822624 Additionally, if you want, you can use that guide to completely remove the drive letters and not mount them again. Though I recommend mounting the drives, so that you can still access the contents, if needed (or easier to run a chkdsk pass). Also, if you have StableBit Scanner installed on the system, you can "mark" the locations of the disks in the "Disk Settings" on each disk. It may be worth taking a couple of minutes to configure all of this (especially as Scanner can "group by case". And this information appears in the tool tip and email notifications for DrivePool. And if you need help figuring out which disk is which, the "Ping" and "Burst" tests in Scanner will help (the "Ping" option continually "pings" the disks, while the Burst option saturates the disks' bus). If I missed anything, you need any clarifications, or have any more questions, don't hesitate to ask.
  10. True, and would be great for using with the SSD Optimizer balancer. But even still, assuming ~500MB/s read speeds, with a PCI Express 3.0 8x (8 lane) card, you could max out 16 SSD on the controller. At this point, I'm not sure about the cables though. This starts to get to where I'm not as sure about. Theoretically, the cables have 4 lanes, which means it could saturate 6 SSDs (again at about 500MB/s) and have a little more room to spare. However, chances are, that you're not going to be continually using disks like this. You'll use them in spurts, and idle most of the time. That means that to really hit these bottlenecks, you'd need to be recording to the disks constantly, and with high HD content. While, yes, you could do this with a PVR or NVR (IP camera server), potentially, chances are, that you're not going to come close to these limits. Also, $199 gets you a 6TB NAS drive anymore. That's 12 times the capacity.
  11. Ouch, I'm sorry to hear about the drives! Since I wasn't sure, if you actually are migrating from WHSv1, then you'll want to check this out: http://wiki.covecube.com/StableBit_DrivePool_Q5463715 This is based on Shane's post, but improvements have been made, and the guide has been streamlined. As for #5, pretty much: http://wiki.covecube.com/StableBit_DrivePool_Q4142489 This is a "seeding" guide, and very similar to the other guide, but for content that isn't in a Drive Extender Pool.
  12. No, you don't want to sysprep the system at all. This may (most likely) break the system and leave it in an unusable state. As for moving the system disk, WHS2011 should be pretty good about it, but it may not work. If you're using very similar hardware, then it should work. Otherwise, you may run into issues. You can try, and if it fails, moving back should be fine. Otherwise, deactivate the licenses, reinstall WHS2011 and reactivate both. Once you've done that, move the pooled disks over, and reshared the pooled locations. If you're just moving the pooled disks around, StableBit DrivePool is very flexible and very resilient. It has no issue with moving disks to a new system and recognizing the pool (the only caveat is that you need to move all the disks in the pool over, or it won't know about the "other" disks). Once you've moved the disks over, it will recognized the pooled disks and recreate the pool automatically. You may need to run the "WSS Troubleshooter" utility to reshare the pooled folders, though. http://wiki.covecube.com/StableBit_DrivePool_Utilities And just to clarify, I've moved the pool around like this a few times. Also, I use a single pool between multiple VMs, and just swap the "disks" between the VMs. So, it's well tested.
  13. As it has been pointed out here already, no, we don't have any sort of auditing tool. This has been highly requested, and we will see about doing this soon. In fact, we plan some significant overhauls to both StableBit Scanner and StableBit DrivePool soon, once StableBit CloudDrive has been finished and released. As Umfriend has indicated, it should be "trivial" to write a script to identify and compare the disk contents. Specifically, we store everything in hidden PoolPart.xxxxx folders (where the "xxxxx" is a GUID), and we don't store the files in any unusual formats. So you can read from these directories without any problems. Also, DrivePool makes sure that the duplicates are not on the same physical drive. So even if you have multiple partitions on the same disk, it will not place the duplicates on the same physical disk (this is also why we don't support Dynamic disks, as this makes it significantly more complex). As for the documentation..... you'd be spot on.
  14. As for the temperature thing, you can override the temperature max, by right clicking on the disk and selecting the "Disk Settings" option. From there, you can set the max temp for the drive. This may be better for this disk. Alternatively, if you open the Scanner Settings (click on "Settings" in the toolbar), on the "Heat" tab, you can set the "Warning Threshold" for the disks. By default, this is 15C, but you could set it to something lower. Or set the global max temp here (for "unknown disks", as we use the manufacturer values for disks we know). As for the unreadable/damaged sectors, ... well, we won't apologize for being very good at tracking the disks (as that's usually a very good thing). However, this could be handled better (or more specifically, we should give better feedback about this). To clear this, find the disk in question, and click on the "+" next to the disk. This should open up a big section, with a lot of info about the surface scan. On the left side of the sector map, should be four buttons. Click on the bottom most one (the one with a green circle and a yellow arrow in it). Select the "Mark all unreadable sectors as unchecked". This will clear that status and cause StableBit Scanner to start a surface scan as soon as it can. Additionally, in the Scanner Settings window, on the "Scanner" tab, you can instruct StableBit Scanner to re-scan unreadable sectors more often. By default, everything is checked every 30 days. However, you can set the "re-check unreadable sectors" to a lower value (such as 3), so that it will rescan these damaged sectors every 3 days.
  15. I'm very interested in the same. Though I have a head start. I have 12 disks in my Norco RPC-4220 case. I need to sell off two of my controller cards, and buy an expander card to replace it... because as I said, one SAS controller card can connect MANY disks (mine's only PCI Express 2.x 8x, so only half the amount of bandwidth as the one I linked). Using the cheaper controller card, and the expander should give you plenty of speed and plenty of bandwidth. Unless HDDs get significantly faster (which they really having for a long while now), or we start seeing dirt cheap SSDs (not likely)... then that hardware will still serve you VERY well for years to come.
  16. Ah, okay. So you mean some sort of parity (or more specifically), file integrity verification of the pool's content.
  17. Unfortunately, we don't support using Windows Server Backup to backup the pool directly. Specifically, it relies on Volume Shadow copy Service (VSS) working in the drive. However, there is absolutely no documentation on how to support VSS on the file system, so to add support would require extensive reverse engineering, to get it working. However, you can back up the disks that make up the pool without any issues. http://stablebit.com/Support/DrivePool/1.X/Manual?Section=Using%20Server%20Backup%20to%20Backup%20the%20Pool Though, ignore the references to the 2TB limit as this doesn't apply to Server 2012R2 or up. Alternatively, any file based solution does work here, such as robocopy/AllWays Sync/Free File Sync/etc.
  18. It could be something like that. Though, my norco has issues with reverse breakout cables (it has 5 SAS backplanes). If I use the onboard and connect a reverse breakout cable to any of the backplanes, the 3rd port will produce a bunch of errors. Tried swapping out cables, etc... but the issue persisted. If I connected to a SAS card, no issues.... So sometimes, weird things like this do happen. And I do hope that the issue doesn't come back.
  19. Ryo, I absolutely understand that, and it's a big consideration. However, unless you're using a LOT of SSDs... or a very large RAID array, then it's not really worth the money to get the higher end card. Higher end performance drives (include NAS drives) will get between 80-120MB/s speed, which doesn't come close to saturating the SATA II bus. And the PCI Express 3.0 x8 (8 lane) card is capable of supporting ~70 drives running at 120MB/s sustained. That's more than plenty of bandwidth for your drives. You should be completely fine with the "lower end" card for a long while (unless TB SSDs suddenly become super common and drop in price significantly).
  20. Well, if you were moving the disk around physically, it could have been a loose connection, as cable issues can cause the damaged sectors (which are any sectors we have issues reading from, so that could be a cause). Very weird though. If it does come back, then definitely let us know.
  21. Try running a burst test on the disk overnight (or longer) and see if it comes back with issues. Also, this sector comes back in the same place? Or different sections on the disk?
  22. Thanks for posting that! That looks like some pretty decent pricing for the rackmount cases. At least from what I've seen of the UK pricing.
  23. Again, sorry that I can't give you any more information than that, but CloudDrive is definitely getting there. Alex is also very anxious to get it released, as he's very happy about how it's turning out.
  24. That's .... complete overkill. Unless you're getting high RPM SAS disks... you're not going to even need that much. Get this instead: http://www.newegg.com/Product/Product.aspx?Item=N82E16816118182 Just for reference... that card should support 69 standard HDDs running at max throughput, just by itself. Well, with an SAS Expander card or two as well. Such as this: http://www.newegg.com/Product/Product.aspx?Item=N82E16816117207 And just to clarify, most HDDs don't even come close to saturating the 6gbps speeds of SATA III (which would be approx 768MB/s). So you definitely don't need 12gbps speed connection.... So, spend the same amount of money and support 24 drives for the same price.
  25. Depending on what is going on ... you should be able to take ownership and change the permissions at the root of the drive, and "replace" the sub-items/child objects. Baring that, use the older version: http://dl.covecube.com/WssTroubleshoot/Release/download/Wss.Troubleshoot_1.0.0.165.exe (not supported on other OS's, but it doesn't block them)
×
×
  • Create New...