I’m new to selfhosting and I find myself rarely using the server, only when I need to retrieve a document or something.

I was thinking of implementing something to make it power on, on demand, but I’m not sure if this might be harmful for the HDDs, and I’m not sure how to implment it if so.

What’s your recommendation to do so? I’m running a dell optiplex 3050

  • Mir@programming.devOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    Right now I’m turning it over night but during the day I find that I might use it one day a few times and another day not at all. Wake up on demand would be great, I’m worried about the wear from doing it like 3-4 times a day

    • hendrik@palaver.p3x.de
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      I’m not sure if 3-4 times a day is a lot. I had computers (especially laptops) which were way more aggressive with spinning up and down the disks. Maybe you can look it up. A decent (enterprise(?)) hdd should have some datasheet available including info about how often you can powercycle or spin them up/down.

      And I wouldn’t wake up disks deliberately. If you don’t mind the 5-10s waiting, you can just spin them down at the end of the day and leave them that way. The next day they’ll either spin up on first access, or they won’t. And save that one cycle. I’m not sure though if you can change the spindown timeout during the day without also waking it up. I mean you could run a script that spins them down at 22:00 and sets the timeout to 1h, and at 07:30 you run a script to keep them awake for a 6h period. But you’d need to test if changing that setting wakes them up. Or I’d rather not run a script like that. Sometimes executing hdparm spins up a disk, even if unnecessary.