← Lab notesaanjacotar.com
home server26.10.20264 min read

I finally built my own home server (and I love it!)

Our old PC died and left me with a pile of drives I couldn't access. Now it runs my photos, documents, films and backups.

The short version
Problem
Our old PC died, and with it my only way to access a pile of drives full of photos and files. Also, as a personal rule, I don't do subscriptions.
Built
A home server for photos, documents, films, file storage and automatic backups. Reachable from my phone and laptop, anywhere.
My part
Putting the hardware together, picking the operating system, organising my files and deciding how it all should work. Learning arrays and the terminal along the way.
New to me
Linux, Docker, disk arrays and parity, remote access, backups that run on their own.
The home server with its side panel off and a white desk fan pointed at it
One drive kept running warm, and I got a bit paranoid. Desk fan first, a real case fan later.

The PC that died

Our old PC had been retired for a while. We kept it running as a Windows machine with all my hard drives inside. There was always some issue getting to them from my Mac, which was annoying. Then it stopped booting, and all those disks full of data were just sitting there with no way to get to them.

After some time grieving, I opened it up and tested it piece by piece: power supply, RAM, graphics card, front panel cables. Everything checked out except the motherboard and the processor.

I already knew what I wanted instead. My films on Jellyfin, my photos in Immich, my documents in Paperless, and somewhere for the files that don't fit on my laptop. And as a personal rule, I don't do subscriptions. The only one we have is a shared Netflix.

you can download more RAM. sadly not a motherboard.

Used parts for the win

My rules:

I spent about €100 on eBay for a used motherboard, processor and RAM. The old gaming graphics card stayed out. Too power hungry for something that’s on all the time.

Picking the system

As a Linux noob, I asked a developer coworker who I knew was into homelabbing. He mentioned a few options: OpenMediaVault, TrueNAS, Proxmox. I looked into them briefly, but when he mentioned Unraid, it checked all the boxes.

I wanted to use the disks I already had, all different sizes, and Unraid is built for exactly that. The others mostly want matching drives, or need extra add-ons to handle mixed ones. I tried the 30-day trial, then bought a licence.

The Unraid dashboard: server info, the list of Docker apps and the shared folders
The Unraid dashboard: the server, the apps running on it and my folders.

Cleaning up first

Before sorting anything, I cleaned up. I went through folders inside folders in the terminal, renamed the oddly named ones and removed duplicate files with Czkawka.

Sorting my life by how much I’d cry if I lost it

I’ve lived on a computer since I was 14, and as a former photographer and videographer I have a lot of raw photos and footage I like to keep. That’s a lot of data, and not all of it is equally important. Storage is crazy expensive right now, and I wasn’t going to spend close to €1,000 on bigger disks just to protect everything the same way.

So I didn’t sort my folders by topic. I sorted them by how bad it would be to lose them.

essentialsarchiveactivemediabacked upkept, rarely openedon the fast SSDno backupwould crywould download againphotos, documents, contractsraw photos, old video projectswhatever I'm working on nowfilms and shows
Sorted by what it would cost to lose, not by topic.

Once the structure was right, the backup plan was obvious.

information architecture, but for hard drives

Proven right, almost immediately. Halfway through, my external backup drive died. I lost some of the archive, and I wasn't even upset, because I had already decided that part was replaceable. Everything important was safe.

the backup needed a backup

What runs on it now

Immich photo library showing a grid of concert photos and a timeline of years
Immich, my own Google Photos.

How I used Claude

Without Claude I would have spent countless hours reading documentation and watching tutorials. I asked it to explain everything in plain language, so I actually understood what I was doing.

At first I didn’t connect it to the server at all. I asked how things should be set up and why, and did every step myself. Once I was comfortable with the setup, I gave it access so it could make changes too.

I also set Claude up to keep its own notes about the server, updated automatically after every change, so we always know what the latest setup is.

What’s next

After the initial setup, it's much simpler than figuring out file sharing permissions between two operating systems ever was. And 100% worth it.

Windows file sharing permissions. not even once.

I wish I'd done this years ago. Turns out a dead motherboard was the best thing that ever happened to my files.

More notes

I missed the konbini door chime, so I soldered my own

Making · 3 min

I deployed my first real app

Apps · 4 min