How a 200TB Proxmox and TrueNAS Homelab Became a Career Portfolio
In the age of certifications, templates, and cloud dashboards that practically build themselves, there's something old-school, maybe even heroic, about one person spending their nights surrounded by SATA cables, Noctua fans, and the low hum of spinning rust.
That's what happened here. One engineer-in-the-making built a 200-terabyte Proxmox and TrueNAS system from the ground up, for no company and with no product in mind, purely as proof of what he could do. Think of it as a resume that glows softly in RGB and whirs like a small data center.
He built it in a living room, between family obligations, half-drunk coffee mugs, and the occasional cry from a one-year-old down the hall, and it's a beautiful piece of work.
The blueprint of a dream
The setup reads like a technophile's shopping list and a bank account's nightmare: a Silverstone CS383 case, a Ryzen 5900XT CPU, an ASRock X570 Taichi motherboard, one hundred and twenty-eight gigabytes of ECC memory, and a Corsair RM1000x PSU.
Then comes the main event. Twelve WD Red 16TB drives make up the main storage pool, which is 192TB raw before mirrors and ZFS parity chew it down. Two Intel Optane drives handle SLOG, a 2TB NVMe drive is the L2ARC, and there are several layers of caching, redundancy, and partitioning that most IT professionals would sketch diagrams for before daring to build.
What he ended up with is closer to a small enterprise lab than a home server, and every inch of it was designed for learning.
The builder didn't throw money at this to show off. He needed a canvas. He was tired of feeling stuck: his IT certifications had expired, job growth had slowed, and the field he loved felt like it was moving faster than he could chase.
So he did the only thing that made sense to him and built something no one could ignore.
Turning hardware into a career compass
Some people build gaming PCs, and others build tiny Kubernetes clusters to play with container orchestration. This setup went further, into real infrastructure. Proxmox handled the virtualization. TrueNAS ran nested inside it for storage duties. Docker and Portainer managed containerized services like Nextcloud, Immich, and custom web apps. On the network side, a full MikroTik configuration controlled VLANs, DHCP relays, and even PIM-SM routing for multicast traffic. Each of those layers doubled as a learning milestone.
The creator had been working in IT support, repairing PCs, cleaning up malware, and managing small surveillance networks. It was honest work, but hardly the kind that gets your foot in the door for a serious infrastructure or DevOps role. He knew he had the curiosity. What he needed was proof, something tangible that screamed "I know this stuff, and I built it from scratch."
Things started to change when a senior system administrator at his company caught wind of what he was working on. "Use it as your portfolio," the admin told him. "Document it. Show your logic, your mistakes, and your fixes. That'll say more than a certificate ever could."
That one comment flipped the switch.
Learning by breaking everything
Anyone who's ever tried to virtualize TrueNAS under Proxmox knows it's not exactly plug-and-play. Hardware passthroughs get messy, PCIe lanes max out quickly, and one misconfigured bridge leaves you staring at a black console with a blinking cursor that feels like judgment.
He hit those walls hard.
At one point, the system's network throughput dropped mysteriously. After hours of digging, he found the culprit in PCIe slot limitations. The Intel ARC GPU needed an x4 lane minimum for transcoding and machine learning tasks, and the dual Intel I226-T1 NICs were locked to x1. The fix was a compromise, and not an elegant one.
"Do I ditch transcoding or keep the NICs?" he remembered asking himself. The answer? "Neither. I'll make it work."
So he did. He balanced every PCIe lane, modded his HBA card with a Noctua fan, repasted the chips, and tuned the BIOS until the system stabilized.
It wasn't perfect, and it was never supposed to be. The point was to teach him, and it did exactly that.
The philosophy behind the build
Strip away the terabytes and tech jargon and what remains is a philosophy, the kind that defines modern IT culture.
In an era when certifications dominate resumes and automation threatens to abstract away the fundamentals, this project stood for doing things the hard way just to understand them. The build was optimized for learning under pressure, with convenience a distant second.
Every subsystem had a reason to exist. TrueNAS is reliable, but he chose it because it forces you to understand ZFS replication and vdev topology. Proxmox gave him a hypervisor and also a gateway into clustering, storage backends, and cross-platform management.
Even the networking side was deliberate. He learned VLAN provisioning, dual-stack IPv6/IPv4 routing, port-knocking, brute-force mitigation, and DDoS protection out of curiosity, since no job required any of it.
If IT is a language, this build was fluency through immersion.
When family meets firmware
It's easy to talk about projects like this as if they exist in a vacuum, just a guy, a rack, and a dream. But life doesn't stop for your lab.
When the builder's child was born, priorities shifted. Nights became shorter and patience thinner. Instead of giving up, he adapted. He would study during naps, install packages while feeding the baby, and label cables with one hand while scrolling through MikroTik forums with the other.
He chased progress instead of perfection, and that persistence built resilience along with the homelab.
The value beyond hardware
This system cost about six thousand dollars, most of it in drives. For many people that sounds insane. "Why spend that much on something that isn't even for production?" skeptics would ask.
You can't measure the return purely in hardware specs, though. What this setup gave back was confidence. It was tangible proof of growth, a visual and functional reminder that skill doesn't have to be certified to be real.
When interviewers ask "What have you built?", he can literally point to a machine running clusters, services, and backups that most small businesses would envy. More importantly, he can answer the questions that matter:
What challenges did you face, and how did you solve them?
What would you do differently next time?
How do you handle documentation, maintenance, and failover planning?
A lab that lets you answer those is a living resume.
What comes next
For now, the system runs a hybrid setup, with Proxmox managing virtualized services and TrueNAS hosting pools for Docker containers, VMs, and media. In the future, he plans to split them into separate physical hosts for a fully discrete setup: TrueNAS on bare metal, Proxmox cluster nodes running in high availability, and a dedicated backup server for ZFS replication.
It's not there yet, and that's okay, because the fun of this project lies in how it keeps evolving.
Every sysadmin, engineer, and DevOps hopeful knows that feeling. You never really "finish" a system. You iterate, tweak, and learn, and you build, break, and rebuild better.
The bigger picture
The story reaches past one homelab to a shift happening across the tech world.
For years, IT advancement was a gatekept process of degrees, certifications, and corporate experience. That has changed. Access to open-source tools, virtualization platforms, and community knowledge means anyone can learn at the same depth as enterprise engineers.
You don't need a data center, just curiosity, a few spare drives, and the willingness to fail in spectacular ways until it clicks.
This 200TB build is evidence that self-driven learning still matters and that curiosity can outpace credentials. Building something tangible that forces you to understand hardware, software, and systems teaches you more than any multiple-choice test ever could.
Final thoughts
In the end, this is a story about ownership: owning your growth and your mistakes, owning the nights you spent Googling kernel panic errors until 3 a.m., and owning the moment you realize the thing you built, the same one that used to crash every hour, has been running flawlessly for months.
The terabytes, the fans, and the RGB glow are the backdrop. What makes it powerful is the human behind it, the one who decided to stop waiting for a chance and build one instead.
Sometimes the best way to move your career forward is to build something so impressive that the jobs come to you, instead of applying for them.
Six grand and twelve drives went into one dream, and into a future that's finally, finally online.