this post was submitted on 26 Jul 2023
5 points (85.7% liked)

Selfhosted

40113 readers
974 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
 

I’m looking to re-purpose an old desktop into a multi-purpose home server. I’m looking for some advise on how to set things up in a way that won’t bite me in the ass later. I’m a confident Linux user, but have limited docker experience. I’m looking at using TrueNAS scale for: straight cloud storage, syncthings, home assistant, and tailscale to access it. If things go swimmingly, I might add jellyfin or *arr apps.

Here’s the hardware I already have:

  • i7 6700
  • 32 GB DDR4 (non-ECC)
  • GTX 1060
  • Storage:
    • 1 TB NVME SSD
    • 250 GB SATA SSD
    • 4x 4 TB WD Black HDD

So, here are my noob questions:

  • Is this system capable enough to handle the things I want to do?
  • My first pass at research says I should use TrueCharts for Tailscale. For Home Assistant, should I also install through TrueCharts? I was reading that you can’t install community docker plugins for home assistant, but I’m not sure if that’s something I’ll need. I also don’t know if I that’s something I need. The alternative is a separate VM, but that seems a lot more complicated.
  • How should I set up my drives? Should the 1 TB NVME drive be the boot drive, is that better used for something else. I’ve done some basic reading on vdevs/pools, but I’m not sure how syncthings/home assistant/other apps fit into the picture. Any good resources you could point me to for understanding this better?
top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago
  • My first TrueNAS homelab was based on an Athlon 3000G and 16GB of RAM. And I ran Nextcloud, Home Assistant, and multiple other services with globaly no ptoblem. Your configuration should be OK.
  • It'd be easier to stick to Truecharts. But I can't tell for community plugins, never tried them.
  • Do not use that 1To SSD as boot drive, it won't improve anything over the 250GB SSD. Use the later, maybe buy a second one to make it redundant. Then use the 1 TB SSD for an Apps pool, and the HDD as a single RaidZ2 array for all your important datas.
[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Have you thought of trying UNRAID. It will introduce you to world of docker. Lots of videos out there to get you started.

Your hardware is fine for truenas.

[–] [email protected] 0 points 1 year ago

That system is plenty capable, in fact you could drop out the GPU if you don't have anything that will specifically be using it. It's just going to draw power when all you need is a video-out port. The qty of RAM is particularly good, will provide plenty of cache for the array and the CPU is strong enough you could enable full-drive encryption and not have it be a bottleneck (assuming that is something you want).

TrueNAS' boot drive doesn't need much space or speed, might as well boot from the 250GB SSD and save the NVME SSD for w/e else you want.

For array-type, a RAID 5 (or ZFS equivalent) is going to be your best setup. Will use one drive as parity and the other three for storage. A single drive failure is allowed with no data loss.

load more comments
view more: next ›