

Two requirements stand out: Media streaming (jellyfin) and multiple hard drives.
In the video front, Jellyfin has documented what you want to look for if you’re building “new” (that is, not just using what you have lying about). Discrete video card is very much recommended for tranacoding (which will invariably happen). Check their docs here. They also cover which processor to use and why.
Let’s consider drives now: what’s the reasoning for multiple drives? I had this requirement too, then had a Dell OptiPlex SFF (Small Form Factor) fall in my lap. Because it can only handle 2 drives (in addition to the M2 OS drive), it made me rethink things. At first I added a 4 port SATA card and four 2.5" drives I had lying around. It worked, but what I realized was my media server needed enough storage to hold my library, but it didn’t need internal redundancy. So currently it has an 8TB drive for my library, and an M2 drive for the OS (which is how this machine comes anyway). That drive is duplicated to a NAS and two other drives on different machines (to protect against drive failure).
I run a monthly host OS backup to my NAS, just in case (but it’s a simple rebuild as my services/tools run in VM’s).
I had a cooling issue at first, then realized it was an old machine (2017), and the cooler paste was likely hard. Cleaned it off and put on new and the fan now runs quietly, even when converting. At idle it hardly makes any noise at all.
One nice thing is it has a relatively small power supply, so it peaks at 80w while converting, and idles about 15w.
It lacks a discrete video card, so when it does transcoding the quality suffers a little. I’ll need to upgrade the power supply to add a video card.
I’m really impressed with this little box - I’d buy another in a heartbeat.
My experience after 35 years in IT: I’ve had 10x more outages caused by automatic updates than everything else combined.
Also after 35 years of running my own stuff at home, and practically never updating anything, I’ve never had an outage caused by a lack of updates.
Let’s not act like auto updates is without risk. Just look at how often Microsoft has to roll out a fix for something an update broke. Inexperienced users are going to be clueless when an update breaks something.
We should be teaching new people how to manage systems, this includes proper update checks on a cycle, with appropriate validation that everything works afterwards, and the ability to roll back if there’s an issue.
This isn’t an Enterprise where you simply can’t manually manage updates across hundreds or thousands of servers, and tens of thousands of workstations - this is a single admin, small environment.
I do monthly update checks, update where I feel it’s warranted, and verify systems afterwards.