• Content count

  • Joined

  • Last visited

  • Days Won


garycase last won the day on March 8

garycase had the most liked content!

Community Reputation

32 Good

About garycase

  • Rank
    Advanced Member
  • Birthday 12/22/47


  • Gender
  1. Yes, the HGST NAS drives are excellent.
  2. Longest server uptime for unRAID

    Basically the only time my servers are ever shut down or rebooted are (a) extended power outages that last longer than the 10 minutes I have the UPS control software set for (rare); (b) software updates that require a reboot (the most common reason); or (c) hardware changes (adding/replacing a disk drive -- also fairly rare). It would be easy to get a year or longer of runtime (been there/done that) ... but it's not something I focus on. Basically I reboot whenever there's a new stable release (I have a test server for the pre-releases).
  3. Longest server uptime for unRAID

    I had a v5 server with over a year of uptime ... the only reason that streak ended was a power failure that exceeded the UPS timer I had set, so the system shut down. I agree, however, that with the much more frequent updates (and much simpler update process) with v6, you really don't want to go over a year without updating, as many of the updates are designed to improve security.
  4. Agree with johnnie => the disk are VERY different. The most perplexing thing about the performance of the DM004 is that it's so much slower than the previous version even though they're significantly improved the areal density of the platters. This almost certainly means they're simply running them at a much lower rpm ... which is also supported by the very low power consumption figures.
  5. Agree -- I was just noting that the performance is not consistent with the specs noted on Amazon & Newegg's listings for that model. I suspect the model # for the drives in the external cases is, for some reason, not correct (or perhaps there's both a "Pro" and a non-Pro version with the same #)
  6. Very interesting. The specs also show a max sustained transfer rate of 190MB/s -- the same as the archive drives. Doesn't make sense with the higher density platters unless they are indeed spinning appreciably slower to achieve the higher platter density. But the drive is shown as a 7200rpm drive (at least in Amazon's listing for it):
  7. It is disturbing that Seagate dropped the Workload Rate Limit so much on the latest drives. Not sure that's a "real" change as much as simply a lower spec for drives slated for the consumer market. Seagate rates their Enterprise class drives with a WRL of 550TB/yr, and their "near line" drives at 180TB/yr ... I suspect the 55TB figure is simply because this is a consumer oriented drive -- perhaps more of a marketing difference than a real technical concern. Although they don't differentiate reads from writes in the computation of the WRL, I also suspect that writes are FAR more important in terms of actual degradation of the performance. (That's certainly true for SSDs) And of course a parity check is virtually all reads. Bottom line: I doubt the WRL figure is really anything to be concerned about. It is, however, very interesting that the speeds aren't better on the v4 drives, especially since that model # is supposedly a 7200rpm drive. I can't find a link that confirms it's using 2TB platters, however ... Johnnie: Are you certain about the platter count? I wasn't aware anyone was shipping anything larger than 1.5TB platters on PMR drives. (WD ships 1.5TB platters on their 12TB helium units, which are PMR; and manages to stretch that to 1.75TB/platter on the 14TB shingled version of that drive)
  8. Glad you were able to recover most of your files. Now is a good time to setup a backup strategy
  9. 20TB sounds like a lot to back up, but not when you consider the size of modern drives AND the impact of losing that much data. There are a variety of ways to do it -- a 2nd UnRAID server (a good idea); a bunch of offline drives that you update periodically; or even a cloud backup if you have high enough internet bandwidth. I have both a backup server (that my other 2 servers back up to) AND a set of offline disks (most of which are simply smaller disks (1-3TB) that I've repurposed to backups as I upgraded to larger disks) that I keep in a waterproof, fireproof, data-rated safe.
  10. Reiserfsck can do some amazing recoveries -- hopefully it will help here. It should as long as you didn't do ANYTHING on the disks except format them ... but as Johnnie noted it can take a LONG time. Just have patience and hopefully you'll recover a significant amount of your data. However, as CHBMB noted above ... Once you recover your data, you should keep this in mind and be sure you have backup copies of anything you would be upset about losing. I always tell folks they should always assume their system is going to suffer a catastrophic crash at midnight; and if there's anything they're going to be upset about losing be sure it's backed up before then
  11. Sounds like there's enough space on each of the machines for all of the data -- apparently her husband had a good backup strategy So ... I'd suggest that after you create an UnRAID machine and copy all of the data from the other server to it (with verification to be sure they're all good copies), that you then turn the 2nd machine into another UnRAID system for backups ... and copy all of the data back to it. You could set it up to run the backups automatically; or it could simply be kept OFF most of the time; and just turned on periodically to sync the backups [It sounds like there's not a lot of changes likely on the systems]. I'd use dual parity on the main machine, and probably just single parity on the backup.
  12. It would be easier to assess this situation with a detailed description of the specific hardware in the two systems -- motherboard, CPU, any add-in controller cards, and the exact complement of disk drives in the machines. Clearly this take a bit of disassembly - be VERY cautious that you don't change or disconnect anything, as you don't want to mess up the currently running server, and you don't want to make things worse in the 2nd (non-functioning) server. This info might suggest a method of recovery for the old server. One thing you might want to consider -- 24TB can be backed up on just 3 modern 8TB drives ... e.g. Best Buy currently has WD external 8TB units for $169. Before doing ANYTHING -- especially on the running server -- you might want to copy all of its data to a backup drive. You could also, instead of using the backup drives in their cases, simply build a small UnRAID server with 4 8TB drives with single parity and then you'd have 24TB of protected space to back up all the data to.
  13. I presume you tried another power supply ... "just in case" "No video" makes this unlikely -- but are you sure it's not just hanging due to a switch in the boot device (if it's attempting to boot from a hard drive instead of the USB flash drive it will generally hang with a blank screen. This can happen after a power failure ... especially if the motherboard battery has failed. But you should still be able to boot to the BIOS, so assuming you have a keyboard and display connected, the "no video" comment likely excludes this. Just wanted to be sure you'd considered it.
  14. Basic Question re Dual Parity

    Actually to add 4TB you don't need to buy 3 drives. If you buy 2 of the 8TB drives and replace your parity drives with them, then you'll have 2 4TB drives available for other uses (the old parity drives). If you only have one free slot you can only add one of them to the array -- but that will give you 4TB of additional space. If you have 2 free slots you could add both of the old parity drives and gain 8TB. Another thing you could do with the old drives is replace any smaller drives you might have -- which would also gain a bit more space.
  15. Basically agree, but as I noted earlier it's more complex if you consider the non-NAS functions that are now common in UnRAID. Dockers and/or VM's that use the disk to-be-removed would have to be either shut down during the process or somehow notified to not use that disk. Excluding those, it is indeed a fairly simple function => step (1) is already available in UnBalance, which could perhaps be invoked to empty the disk (and STOP the process with a "NOT ENOUGH SPACE" if there isn't sufficient space to do it); step (2) is indeed very simple (albeit LONG) -- but would also require the system be set to NOT do any further writes to the disk (this would perhaps mitigate the Dockers/VM issue as far as the removal goes ... but could generate questions as to "why my Docker isn't working anymore); and step (3) should be virtually instantaneous (just modifying the config) ... although as bjp999 noted it may be tricky with the array online.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.