Guys, I’m using this HDD (ST8000NM000A-2KE101) as a parity drive in a snapraid configuration, most of the time it is in spin down mode. A couple of days ago scrutiny shown a failed status with ‘command timeout’. Do you think it could be a real problem or is it because of the recovery time from the spin down status?

    • @catloaf@lemm.ee
      link
      fedilink
      English
      03 months ago

      That is the SMART data.

      Usually parity drives are spun up. Hard to read or write the parity data if it’s not. I would make sure that otherwise it performs properly, and be ready to order a replacement if it doesn’t.

      • @schizo@forum.uncomfortable.business
        link
        fedilink
        English
        03 months ago

        Snapraid parity is offline, so that’s not strictly accurate.

        You build the parity, and then until you do a sync/scrub/rebuild they don’t do shit, so there’s no reason to keep them spun up.

        If the drive are slow spinning up, then this is probably not a fatal concern, but there’s zero details here.