this post was submitted on 29 Dec 2023
9 points (100.0% liked)

Selfhosted

40183 readers
557 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
 

Hi everyone. I’m on the verge of building a new NAS/Media server, and wanted to check here to see if any of you could provide some recommendations based on my goals (below) or your current builds. I currently have a Raspberry Pi 4 running some basic services (Portainer, Home Assistant, Plex, sonarr/radarr/prowlarr, sabnzbd, etc.), but would like to expand my options and capabilities as my interests in the hobby grow.

My goals:

  • Ability to have 4+ 1080p streams on Plex. Right now my Pi works surprisingly well at home with one 1080 stream, but basically shits its pants doing much more. Would like to give my parents and a friend or two access.

  • Document storage/backup. Interested in Nextcloud, but it seems people have mixed experiences here.

  • Photo storage/backup.

  • Hosting the services mentioned above, plus some extra headroom for others. I’ll probably move back to Home Assistant OS on my Pi, unless you think I should utilize it for something else.

  • OS - unRaid. Not opposed to others, but this does seem to be a great option with a lot of how-guides and videos available.

  • Storage/Drives - I honestly don’t know how much I want or need. As it stands, my partner and I probably have less than 1TB of files and photos between the two of us (being very generous with that figure). Would like to expand the media server capabilities as mentioned above.

  • Budget - $1000 max including drives.

While the details above are what I would like to achieve with this, you can also consider me an empty canvas. Open to all ideas and suggestions. Let me know if there are other details I can provide that would be helpful. Lastly, thank you all for creating such a great community here.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 10 months ago (3 children)

To play off what others are saying i think a mini pc and a stand alone nas may be the better route for you. It may seem counter intuitive to break it out into two devices but doing so will allow room for growth. If you buy a creeper bare bones mini pc and put more of your budget towards a nas and storage you could expand the mini pc without messing with your nas. You could keep the pi in the mix for a backup if your main pc is down or offload some services to it to balance performance.

[–] [email protected] 3 points 10 months ago (2 children)

Just want to second this - I use an Intel nuc10i7 that has quicksync for Plex/jellyfin, can transcode at least 8 streams simultaneously without breaking a sweat, probably more if you don't have 4K, and a separate synology nas that mainly handles storage. I run docker containers on both and the nuc has my media mounted using a network share via a dedicated direct gigabit Ethernet connecting the two so I can keep all the filesystem access traffic off of my switch /LAN.

This strategy was to be able to pick the best nas based on my redundancy needs (raidz2 / btrfs with double redundancy for my irreplaceable personal family memories) while being able to get a cost effective low power quicksync device for transcoding my media collection, which is the strategy I chose over pre-transcoding or keeping multiple qualities in order to save HDD space and be flexible to the low bandwidth requirements of whoever I share with who has a slow connection.

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

What synology model did you go with? Do you host any other services with that type of setup?

[–] [email protected] 0 points 10 months ago* (last edited 10 months ago)

I went with the DS1621xs+, the main driving factors being:

  • that I already had a 6 drive raidz2 array in truenas and wanted to keep the same configuration
  • I also wanted to have ECC, which while maybe not necessary, the most valuable thing I store is family photos which I want to do everything within my budget to protect.

If I remember correctly only the 1621xs+ met those requirements, though if I was willing to go without ECC (which requires going with xeon) then the DS620slim would have given me 6 bays and integrated graphics which includes quicksync and would have allowed me to do power efficient transcoding and thus running Plex/jf right on the nas. So there's tradeoffs, but I tend to lean towards overkill.

If you know what level of redundancy you want and how many drives you want to be running considering how much the drives will cost, whether you want an extra level of redundancy while rebuilds are happening after 1 failure, how much space is sacrificed to parity, then that's a good way to narrow down off the shelf nases if you go that way. Newegg's NAS builder comes in handy if you just select "All" capacities and then use the nas filters by number of drive bays, then you can compare whats left.

And since the 1621xs+ has a pretty powerful xeon, I run most things on the nas itself. Synology supports docker and docker compose out of the box (once the container app is installed), so I just ssh into the box and keep my compose folders somewhere in the btrfs volume. Docker nicely allows anything to be run without worrying about dependencies being available on the host OS, the only gotcha is kernel stuff since docker containers share the host kernel - for example wire guard which relies on kernel support I could only get to work using a user space wire guard docker container (using boringtun) and after the VPN/tail scale app is installed (presumably because that adds tap/tun interfaces that's needed for vpn containers to work.

Only jellyfin/Plex is on my NUC. On the nas I run:

  • Adguard

  • Sonarr/radarr/lidarr/prowlarr/transmission/overseerr

  • Castblock

  • Grocy

  • Nextcloud

  • A few nginx instances for websites

  • Uptime-kuma

  • Vaultwarden

  • Traefik and wire guard which connects to a vps as a reverse proxy for anything that needs to be accessible from the public internet