this post was submitted on 24 Aug 2023
89 points (95.9% liked)

Selfhosted

40006 readers
786 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
89
Best current hardware solution for selfhosting? (lemm.ee)
submitted 1 year ago by tehnomad@lemm.ee to c/selfhosted@lemmy.world
65 comments fedilink hide all child comments
 

I use my desktop PC for Jellyfin and torrenting, but I'm looking for something that I can keep on 24/7 that draws less power and run other self-hosted services on Linux. I would like to have at least 2x 14 TB 3.5" hard drives in or attached to it with the possibility of expanding in the future.

From my research, these seem to be some good options:

  1. Mini PC like this Beelink S12 Pro + USB hard drive enclosure. The price seems reasonable for the specs and low power consumption. Not sure if USB will limit transfer speeds.
  2. ODROID HC-4 or similar SBCs. I feel like these have much lower performance for not much price savings, and it's harder to get software running up because of ARM. But it seems like they don't use too much power.
  3. Used enterprise PCs/servers. I know they can be found cheap used, but I'm a little lost at comparing the performance and power draw to other options.
  4. DIY build. I'm interested in getting a Mini-ITX case like this Jonsbo N2 and getting parts for it, but it seems like it will be the most expensive option. It does seem like the most modular and upgradable.
  5. Classic NAS products like Synology. It seems like these are falling out of favor because they are pretty under powered for the price.

What does selfhosted think about these options, and what would you recommend?

you are viewing a single comment's thread
view the rest of the comments
[–] knobbysideup@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (2 children)

I run proxmox on a System76 Thelio. ZFS mirror, 16 cores, 64GB. Synology NAS for data storage and backup. Dual NICs bonded with ovs for the VMs. The onboard NIC for connecting to proxmox itself. One of the VMs then rclones the backup share to rsync.net

One of the VMs is Plex/Sonarr/Radarr/Transmission. Media is stored via NFS to the NAS.

[–] tehnomad@lemm.ee 2 points 1 year ago

The Thelio looks awesome, but it seems overkill for what to do and spend. I would probably do DIY if I wanted something with the specs of the Thelio.

[–] uis@lemmy.world 2 points 1 year ago (1 children)

Why VMs?

[–] knobbysideup@lemm.ee 1 points 1 year ago (1 children)

I don't like lxc containers, and my build automation works well at the full system level vs containers.

Running your services bare metal these days is insane. If I have a problem, I just restore or rebuild that purpose-built vm from configuration management. This is also a lot more flexible and cost effective vs having separate hardware for each thing.

Redundancy is also easier, should I decide it is worth the hardware investment.

[–] uis@lemmy.world 0 points 1 year ago

While you are correct with insanity of running bare-metal, this argument is manipulative. Indeed, no sane person will ditch existing kernel(e.g. Linux of FreeBSD) and write one themselve, running program in common OS is not bare-metal.

Another manipulation is VM vs per-dervice dedicated hardware.

Redundancy is also easier, should I decide it is worth the hardware investment.

Same thing valid for regular userland.