Selfhosted

59939 readers

274 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Low usage power saving recommendations request? (programming.dev)

submitted 2 years ago by Mir@programming.dev to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] hendrik@palaver.p3x.de 1 points 2 years 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.