• @grue@lemmy.world
    link
    fedilink
    English
    86 days ago

    The main issue I see is that the gulf between capacity and transfer speed is now so vast with mechanical drives that restoring the array after drive failure and replacement is unreasonably long. I feel like you’d need at least two parity drives, not just one, because letting the array be in a degraded state for multiple days while waiting for the data to finish copying back over would be an unacceptable risk.

    • @Cenzorrll@lemmy.world
      link
      fedilink
      English
      46 days ago

      I upgraded my 7 year old 4tb drives with 14tb drives (both setups raid1). A week later, one of the 14tb drives failed. It was a tense time waiting for a new drive and the 24 hours or so for resilvering. No issues since, but boy was that an experience. I’ve since added some automated backup processes.

    • @BakedCatboy@lemmy.ml
      link
      fedilink
      English
      26 days ago

      Yes this and also scrubs and smart tests. I have 6 14TB spinning drives and a long smart test takes roughly a week, so running 2 at a time takes close to a month to do all 6 and then it all starts over again, so for half to 75% of the time, 2 of my drives are doing smart tests. Then there’s scrubs which I do monthly. I would consider larger drives if it didn’t mean that my smart/scrub schedule would take more than a month. Rebuilds aren’t too bad, and I have double redundancy for extra peace of mind but I also wouldn’t want that taking much longer either