This post is Part 2A of my Homelab Journey. In this series, I’m sharing the lessons I’ve learned and the process I’ve gone through as I figure out homelabbing, self-hosting, digital sovereignty, and learning by building.
Introduction
Before the Metal Box, before Proxmox, before I knew what a hypervisor was, there was a dark grey Sony Vaio desktop humming in the corner of my basement. The first computer I ever really made my own.
It wasn’t built for power. It was built for freedom.
This is the story of how a hand-me-down college computer became my first server, and how that experiment shaped everything that came after.
The Subsonic Era
Around 2010, I started building what I thought of as “my own Spotify.” MP3 players were all the rage, and streaming was ubiquitous, when most people still bought individual songs on iTunes or burned CDs from Napster.
I had thousands of CDs that I purchased from used music shops while in college. I was fortunate to have access to two or three stores in Amherst and Northampton, Massachusetts, that featured a large collection of used CDs and allowed you to resell the discs as well. I would regularly stop off with twenty or thirty dollars in my pocket and spend hours digging through the crates, listening to music I might like, and buying it if it sparked interest.
As mobile devices started replacing MP3 players, I wanted to have the ability to pull music over from my CDs to my devices to stream anywhere. I also wanted the opportunity to share my listening experience with others. This included having a small set of friends and family who could listen to music and build community playlists.
The goal was simple but radical: stream my entire music collection, thousands of ripped CDs, anywhere, on any device, with no ads, no algorithms, and no subscriptions.
That’s how I discovered Subsonic , an open-source media server for personal streaming. A Lifehacker post introduced me to it, and suddenly the possibility clicked. I didn’t need to depend on anyone else’s platform. I could build my own.
I spent years ripping my entire CD library. Album by album, genre by genre, until I had thousands of tracks cataloged and ready to stream. (I wish I hadn’t gotten rid of those physical discs when we moved years later; that collection was an archive of entire chapters of my life.)
The Hardware: A Frankensteined Vaio
The server itself started as a Sony Vaio desktop that my uncle gave me for college. It was a machine that he used for business, and I used for writing papers. As I was graduating from college, it was collecting dust, and he indicated that I could take it with me.
Over time, I Frankensteined it together with scavenged parts from eBay, Craigslist, and swap meets:
- New hard drives when the originals failed
- Extra RAM picked up on Craigslist
- Fans and power supplies salvaged from dead towers
- Whatever worked and was cheap
I was inspired by classic Lifehacker posts about building your own media center PC and early YouTube videos about Plex setups. The guides showed me that you didn’t need expensive hardware. You just needed patience and a curious mind.
The Vaio was loud, messy, and barely held together. But it worked.
DIY Sonos Before Sonos
I even built a DIY whole-home audio system around it, years before smart speakers were common. It was not uncommon when you visited my house to have an old laptop strapped to the baker’s rack in the kitchen, belting out tunes. Using cheap speakers scattered around the house, I could push music from Subsonic to any room. My house literally sang.
A few friends joined the server, and we had our own little proto-Spotify. Long before streaming was the default. There was something deeply satisfying about building this together: not just the technical challenge, but the shared ownership of something we’d made ourselves.
Early Lessons
Looking back, that first server taught me foundational lessons that still guide how I think about systems today:
1. Backups Matter More Than Performance
Early drive failures taught me the hard way: if it’s not backed up, it doesn’t exist. I almost lost entire music libraries to failed drives before I understood the importance of redundancy. I had two or three external hard drives that I would use as a local backup. This system was not helpful when something broke and you needed to rebuild.
2. You Don’t Need New Gear to Learn Deeply
That aging Vaio lasted through multiple rebuilds and reuses. The limitations forced me to understand how systems actually work. Memory management, network protocols, filesystem choices. Constraints breed understanding.
3. Self-Hosting Builds Confidence
Managing users, firewalls, dynamic DNS, and port forwarding all became hands-on learning opportunities. Every problem I solved made the next one less intimidating. I still have a lot to learn, but I’m still learning.
4. Community Makes It Better
Sharing that Subsonic server with friends transformed it from a technical project into something meaningful. We were building infrastructure together, claiming a small corner of the internet as ours.
Moving to Plex and Family Life
As my family grew, so did our media needs. This time with DVDs and Blu-rays instead of CDs.
We had a mountain of kids’ movies, and after the first few discs got scratched beyond saving (as they always do with toddlers), I realized I needed a better system.
At the same time, I needed a way for us to quickly transfer a movie file to an iPad, cell phone, or stream it while away from the house. A toddler wasn’t going to wait patiently for the movie Cars to start playing.
I rebuilt the server again, using the same hardware, but with a new purpose: Plex. I ripped our entire DVD collection, set up Plex clients around the house, and learned about codecs, transcoding, and metadata management.
The old Vaio continued to evolve. It received new drives, fans, a new case, and a new lease on life. All of these parts were still cobbled together using old, used parts.
Plex turned it into a family media hub long before “streaming” was a household word. It wasn’t elegant. But it was ours.
And that sense of ownership, of our data, our media, our infrastructure, stayed with me.
Passing It On: Decommissioning the Vaio
When we moved about a decade ago, the old Vaio had served its time. It had been rebuilt so many times that almost nothing original remained. Just the case and the motherboard, both of which showed their age.
Before we said goodbye, I wanted to give my kids a chance to see what had been humming in the corner all those years.
We spent an afternoon taking apart the Vaio and a laptop together. I showed them:
- How the hard drives spun and stored data
- Where the RAM lived and what it did
- How the CPU cooler worked (and why it had gotten so loud)
- The tangled mess of cables that somehow made everything talk to each other
They were fascinated by the physicality of it. The weight of the drives, the shine of the circuit boards, and the way the power supply fan still spun when we tested it one last time.
We carefully sorted the components:
- Drives went into a static bag for potential data recovery
- Metal parts into the recycling bin
- Circuit boards to an e-waste collection center
It felt important to show them that technology isn’t magic, it’s material. It can be opened, understood, repaired, and when its time is done, responsibly recycled.
That afternoon became an unexpected lesson in both systems thinking and sustainability. Nothing lasts forever, but everything we build teaches us something we carry forward.
The Spark That Never Died
The Vaio was gone, but what it had taught me remained.
I’d learned that I could build my own systems. I could reclaim agency over my digital life instead of renting it from platforms that could change the rules at any moment.
I wanted to go beyond media servers. I wanted:
- Redundancy — so I’d never lose data to a single drive failure again
- Control — over what data I kept, where it lived, and who could access it
- Independence — from cloud services that could shut down, raise prices, or disappear overnight
- Understanding — not just what worked, but why and how
That desire lay dormant for a few years as life moved forward. But it never really left.
That desire eventually became what I now call The Metal Box , the subject of the next post in this series.
What’s Next
In Part 2b , I’ll trace how that early curiosity evolved into a modern homelab: the hunt for hardware, the scavenging and learning process, and the technical choices that shaped my current Proxmox + TrueNAS setup.
But the foundation was always this: a beige desktop from my uncle, a pile of CDs, an afternoon with my kids pulling it apart to see how it worked, and the realization that technology we understand is technology we can control.