Selfhosted

39435 readers

4 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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Low usage power saving recommendations request? (self.selfhosted)

submitted 4 months ago by Mir to c/[email protected]

25 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

[–] [email protected] 3 points 4 months ago (1 children)

Something like an old laptop will make a power-saving homeserver. But that won't work if you want to attach lots of storage.

I don't think an Optiplex is the most energy-efficient choice. They seem somewhat okay, but you'd need to put some effort in and read some tests and reviews to find a really efficient mainboard and PSU. That's not easy

You can spin down your harddisks. I have some udev rule that executes hdparm -S60 /dev/sdb after boot. That'll spin down the hdd after 5 minutes of inactivity. It's alright for low usage scenarios. And it doesn't spin up that often because the hdd contains my photos, backups and a few movies. And my operating system and files that are accessed often, are on a SSD. Starting and stopping disks like once a day should work for many years. But don't cycle it every few minutes.

And obviously, you can also shut off your server over night or just wake it on demand, if that fits your use-case.

[–] Mir 2 points 3 months ago (1 children)

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

[–] [email protected] 1 points 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.