Thank you to u/PackParking5786 for sharing a self-hosting journey that began with taking apart dead computers and grew into a multi-machine homelab. The current setup includes a ZimaOS host for applications and virtual machines, alongside other computers used for experiments, games and learning.
The Self-Hosting Day contribution connects those machines to a broader story. As the creator approaches the end of high school, they are already working as an IT technician and doing freelance repairs. A Raspberry Pi NAS in a LEGO enclosure was one early step along the way.
Dead Computers Became the First Learning Materials
The creator became interested in computers shortly before the pandemic. Their father noticed and began bringing home dead machines from work, giving them something to dismantle, understand and eventually try to repair.
That experience accumulated into a collection of equipment. Around two years before the contribution, the creator realized there were plenty of computers available but too little being done with them. An uncle was helping introduce Docker, Kubernetes and other infrastructure concepts, and a home lab offered somewhere to explore those ideas.
The motivation was partly practical and partly curiosity. The hardware was already present, and a dedicated place to run services could connect learning with something usable. This pattern remains visible throughout the later setup, which includes salvaged, donated and repaired equipment.
A LEGO Raspberry Pi NAS Was an Early Experiment
The first NAS project used an old Raspberry Pi 2 with an enclosure made from LEGO. It worked as an introduction, but the creator soon ran into limited storage and crashes while trying to run containers. Those limitations prompted several months of reading about homelabs and learning from other people’s installations.
The author links an original album of the early homelabs. The photograph reproduced here belongs to that earlier period: a white LEGO enclosure surrounds a Raspberry Pi, with its connections and cables visible.

The operating system of this photographed Pi is not identified. ZimaOS belongs to a later PC in the story. Keeping those stages separate preserves what the picture actually documents: the creator’s early attempt to make a small server from equipment already owned.
Several Computers Gave the First Lab Different Roles
Before settling on a more organized arrangement, the creator had Minecraft and Satisfactory running on an old laptop, Plex on a Dell Micro 9020, and NAS duties moved to a Dell XPS 8930. During a summer break, those separate uses began to take shape as a deliberate lab.
The first named arrangement, Aperture Science Labs, included the Dell XPS running Ubuntu with CasaOS, other Dell machines on Debian and Windows, a laptop running Void Linux, and a Raspberry Pi running OctoPrint. The mix reflected the equipment available and what the creator wanted to learn.
The installation kept changing over the following years. The author describes moving things, rebuilding and adapting to the budget and the needs of the moment. Some equipment came from a church, some was salvaged, and some was given by other people.
A useful comparison is the retired HP mini PC turned into a 3D-printed ZimaOS NAS. Both stories begin with reused hardware, but PackParking5786’s account develops into a collection of machines with separate learning and service roles.
The Current ZimaOS Machine Hosts Applications and ZVM
The newer arrangement is called Aperture Science Labs MKII. Its Black Mesa host is listed with a Core i9-12900K, 32 GB of RAM and graphics hardware. The author places ZimaOS here and reports three ZVM virtual machines, with one used continuously.
The application list spans media, development, synchronization and monitoring. Navidrome and Jellyfin serve personal collections. Gitea gives development work a home. Grafana, Prometheus and Uptime Kuma appear in the monitoring setup. Syncthing, Tailscale and other tools support access and file workflows.
| Machine or group | Role described by the author | Stage or important context |
|---|---|---|
| LEGO Raspberry Pi NAS | Early storage and container experiments | Historical project shown in the original photograph |
| Dell XPS 8930 | Ubuntu with CasaOS in the first named lab | Earlier arrangement; distinct from the current ZimaOS host |
| Black Mesa | ZimaOS, applications and three ZVM virtual machines | Current MKII host; one VM reported as continuously used |
| GLaDOS | A PC alternating between Windows and Proxmox | The author was still considering a more permanent Proxmox move |
| Other reused machines | k3s, printing, game streaming and experiments | Separate computers with their own operating systems and duties |
The official ZimaOS guides provide the appropriate starting point for system, storage and application questions. The source’s machine list explains one creator’s arrangement; it is not a measured minimum specification for reproducing every listed workload.
The author also mentions Ollama and a desire to explore local language models further, while being candid about the limits encountered. The contribution gives no model names, quantization settings or inference results from which to recommend this configuration for a particular AI workload.
Keeping Different Experiments on Different Machines
The rest of the lab shows why the creator kept adapting the collection. A machine named GLaDOS alternates between Windows for games and Proxmox experiments. An old ChromeBox provides somewhere to test how useful a very modest computer can be. Another system supports game streaming and emulation, while Raspberry Pis remain involved with 3D printing.
There are also laptops used for Docker and a small group of Dell and Lenovo machines running k3s. These are separate parts of the environment. The creator’s ZimaOS host has its own responsibilities within a larger collection of computers.
The list includes ambitions as well as completed uses. A new shelf, a UPS and further local-AI experiments were still being considered. The author explicitly lacked a current layout photo because the arrangement was being reorganized.
Readers planning their own layout can compare u/jc-21’s long-running small homelab, where the emphasis is on keeping the installation compact. The two accounts provide different answers to the same practical question: which machines continue to earn their place?
The Hobby Connected to Work Before High School Was Finished
The creator’s interest in repairs now extends beyond the lab. The account describes an IT technician role at a small company alongside freelance repair work, while school and ordinary life limit the time available for further tinkering.
That context helps explain the constant reuse. Each repair or service provides another opportunity to understand equipment already at hand. The lab changes as access to hardware, available time and learning goals change with it.
For someone considering a future compact host, the ZimaBoard 2 single-board server is a separate platform to evaluate against the intended role. It does not replace the factual distinction in this story: the current ZimaOS installation is on the creator’s Black Mesa PC, and the photographed LEGO machine is an earlier Pi project.
FAQ
Which machine actually runs ZimaOS?
The author lists ZimaOS on Black Mesa in the current Aperture Science Labs MKII arrangement. The first Dell XPS lab used Ubuntu with CasaOS.
Does the LEGO photograph show ZimaOS running on a Raspberry Pi?
No. It shows an early Pi NAS. The operating system on that photographed device is not specified, and the author places ZimaOS on a later PC.
How many ZVM virtual machines are reported?
The contribution lists three virtual machines, with one in continuous use. It does not identify all guest systems or their individual resource allocations.
Has the creator completed a permanent move to Proxmox?
The GLaDOS machine was alternating between Windows and Proxmox, and the author was considering a future move. That plan should remain separate from the reported ZimaOS host.
Does the article reproduce the current storage or AI configuration as a guide?
No. The source leaves storage-layout details and AI workloads insufficiently defined for that purpose. This is a story about the machines’ roles and the creator’s learning process.
Conclusion
PackParking5786’s journey connects a father’s supply of broken computers, an uncle’s help with infrastructure concepts and a long series of hands-on experiments. The LEGO NAS is a visible early chapter; the current ZimaOS host is part of a larger collection that grew around learning and actual use.
The result is also a path toward work. Repairing, hosting and reorganizing equipment created experience the author now uses in IT, while the lab continues to change with the next available machine and the next practical question.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.



