Self Hosted (part 1) : Server Hardware

Intro

I wanted to run a server to host some of my data and applications. I have gigabit internet at home with ethernet cables running in all rooms, so I decided to put it to use and have a setup at home.
Initially I thought about using a few Raspberry Pi with a pre-built NAS like Synology. I bought a Raspberry Pi to test it and it worked fine for some low power applications like Home Assistant, but it struggled with some heavier applications like FileRun. So, instead of using Raspberry Pis, I decided to buy components and build one high performance server.
The obvious drawback of having only one server is that there is no redundancy and a part failure will make all the applications inaccessible. This is a risk I am winning to take because the replacement parts are usually available on most major retailers (like Amazon and Newegg) with fast shipping, which should keep the downtime between one to two days.

Essentail Hardware

Motherboad (ASRock Rack X570D4U-2L2T)

Features

Reasons for picking

Memory (Kingston Fury Beast (2x32GB))

Features

Challenges

I am using ZFS on the server, and ECC memory is highly recommended to avoid zpool and data corruption. When I was building the server, the ECC memory availability in my region was terrible and the prices of the few available were very inflated. So, I decided to temporarily go with non-ECC memory and upgrade later to ECC memory when it becomes a bit more available

Reasons for picking

CPU (AMD Ryzen 5 5600G)

Features

Reasons for picking

Storage (6x Seagate Ironwolf 4TB)

Features

Reasons for picking

Miscellaneous Hardware

Thank you for reading. Check out the other parts in the series below.