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
Wake-on-LAN is probably what you want, if your specific hardware supports it which it probably does. This is a case of figuring out your exact hardware and a little RTFM-ing about how to enable and use WOL.
As for the drives it, in theory, would add more load/unload cycles to them and thus reduce their lifespan. But, in the real world, that almost certainly doesn’t matter, unless you’re turning the system on and off every 5 minutes: modern drives expect to go in and out of power saving modes and most controllers (especially usb enclosures!) do this pretty aggressively, so a couple more load cycles more-or-less are unlikely to actually cause your drive to fail any quicker than it would anyways.
Not quite. Wake on LAN requires a special packet be sent, the OS to boot, then you can attempt to connect to whatever’s running.
It’s fairly manual (though you COULD maybe automate it, if you have other infrastructure that’s watching for things: ex. using home assistant to send the packet when you come home), and has a delay since the system has to boot before it’ll respond to anything.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
Wake-on-LAN is probably what you want, if your specific hardware supports it which it probably does. This is a case of figuring out your exact hardware and a little RTFM-ing about how to enable and use WOL.
As for the drives it, in theory, would add more load/unload cycles to them and thus reduce their lifespan. But, in the real world, that almost certainly doesn’t matter, unless you’re turning the system on and off every 5 minutes: modern drives expect to go in and out of power saving modes and most controllers (especially usb enclosures!) do this pretty aggressively, so a couple more load cycles more-or-less are unlikely to actually cause your drive to fail any quicker than it would anyways.
Thank you
I think it has wake on Lan, so that means any connection attempt would wake it?
Not quite. Wake on LAN requires a special packet be sent, the OS to boot, then you can attempt to connect to whatever’s running.
It’s fairly manual (though you COULD maybe automate it, if you have other infrastructure that’s watching for things: ex. using home assistant to send the packet when you come home), and has a delay since the system has to boot before it’ll respond to anything.