From Raspberry Pi to Two ZimaBlades: Mateo’s Printed Homelab

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/mateorzan for sharing a Self-Hosting Day story that grew one experiment at a time. A Raspberry Pi 5 running CasaOS became the starting point for two ZimaBlades, Proxmox, a move to ZimaOS and a collection of household services. An orange printed rack gives the installation its distinctive shape; the maintenance notes explain how it keeps evolving.

In the original Reddit contribution, Mateo describes learning system administration while building something useful at home. His public homelab repository adds an important companion to the photograph: a record of the machines, their roles and problems encountered along the way.

A Raspberry Pi Made the First Weekend Possible

The first step was modest. Mateo had basic terminal knowledge but had not operated a self-hosted server. After seeing CasaOS and ZimaBlade on YouTube, he installed CasaOS on a Raspberry Pi 5, attached a USB drive and began using applications including Nextcloud and Jellyfin.

That weekend established something more useful than a final hardware specification: he could put a service on a machine under his own control and use it. The interest in a larger lab followed from that experience. It was not necessary to decide on every later application before the first one became useful.

As his interests moved toward snapshots and virtualization, the software and architecture became part of the next decision. The account describes difficulties with the ARM-based environment and Docker Swarm in his particular setup. Those experiences led him toward an x86 platform rather than proving that every Raspberry Pi installation needs the same upgrade.

Two ZimaBlades Gave the Lab Separate Roles

Mateo bought a ZimaBlade, discovered Proxmox VE, added another ZimaBlade and introduced Proxmox Backup Server. His software journey also included migrating from CasaOS to ZimaOS and writing bilingual guides. ZimaBlade has since been renamed ZimaBoard SE; the original name is retained here for the hardware he describes.

Part of the installation Role documented by the creator
First ZimaBlade A Proxmox node running services
Second ZimaBlade A second Proxmox node with backup, replication and service responsibilities
Raspberry Pi 5 An independent machine; Jellyfin remains part of its reported use
ZimaOS Part of the software migration and service-management journey
Proxmox Backup Server The backup platform included in the lab
Printed rack The physical home for the compact installation

The repository distinguishes the current two-node cluster from the separate Raspberry Pi. Three physical computers therefore do not automatically mean three Proxmox voting nodes. That distinction matters when explaining the architecture or comparing it with a larger cluster.

The current software inventory is also broader than one operating-system dashboard. It would be inaccurate to describe every service as a native ZimaOS application or to suggest that the same operating system runs directly on all three machines.

The Orange Rack Makes a Growing Project Tangible

Mateo printed the orange rack on a Bambu Lab A1 Mini. The original photograph shows the assembled structure with a display, a network switch and the compact computers. It documents how the equipment is arranged without supplying a complete set of enclosure drawings or a thermal test.

Mateorzan’s orange 3D-printed homelab rack with a display, network switch and two ZimaBlade systems
The completed printed rack brings the display, switch and small servers into one visible installation. Photo: u/mateorzan.

There is a useful parallel with the IKEA-cabinet mini rack. Both creators used printing to organize equipment they wanted to keep using. Mateo’s project has its own form and software history; the photograph should not be treated as a parts-for-parts version of the cabinet build.

A Household Reminder Gives Automation a Clear Purpose

Among roughly twenty services, one n8n workflow stands out because its purpose is easy to understand. Mateo built a WhatsApp reminder for his partner, recorded replies locally and used a Telegram notification to complete the loop. The automation became part of a household routine.

The useful idea is the connection between a message and an acknowledged action. Sending a reminder, receiving a response and keeping a local record are separate steps. The original account explains why the workflow mattered to its users, without presenting a reusable workflow export or a tested delivery guarantee.

The wider service collection includes Nextcloud and Vaultwarden, media tools, monitoring through Beszel and Uptime Kuma, and access tools such as Nginx Proxy Manager and Tailscale. These applications support different tasks; the number alone is not the accomplishment. The household routine gives one of those tasks a concrete outcome.

For a different use of similar automation tools, Bender-426’s ZimaBlade office server connects storage with messaging and business workflows. Mateo’s example stays at home, where the benefit is a small recurring task that no longer depends on somebody remembering to send a manual message.

Failures Became Part of the Documentation

The maintenance history gives this build depth. Power interruptions, storage trouble and software changes each created work beyond installing another application. Mateo collected the incidents in a public troubleshooting notebook so that a solved problem would not have to be reconstructed from memory.

Those notes cover several different failure layers. A logical-volume startup problem can prevent a VM from reaching its disk. A Docker-related networking error can stop a container even when its host is running. After a storage move, a VM definition may still refer to a disk location that has not been transferred to the new destination.

The last example appears in the notebook’s PBS troubleshooting section: the backup-server VM could not locate its disk after an SSD change. Documenting the missing location and the recovery process makes the migration understandable as a data-placement problem, rather than a vague statement that the backup application had broken.

The notebook also records changing an n8n timezone setting to match the creator’s region. That is a smaller issue, but it belongs in the same maintenance story. A scheduled reminder needs the intended local time as well as a running container. Configuration details become visible when an application is used as part of an everyday routine.

These are the creator’s installation notes, not universal repair commands. Readers developing their own recovery process should use the appropriate platform documentation, including the Proxmox Backup restore reference, and verify recovery separately from the working service. A backup platform and a successful restore are related but distinct parts of the plan.

The Current Lab and the Next Goal Remain Distinct

The repository describes two active Proxmox nodes and a separate Raspberry Pi. It also shows a target architecture with a future third node for quorum and further experiments on the Pi. Keeping the target diagram separate from the current installation preserves the project’s actual progress.

High availability is an ambition in the documentation. The material does not establish a completed failover test or a measured uptime result for this setup. The interesting achievement is already visible without that claim: multiple machines have defined roles, useful services are running, and operational knowledge is being retained as the system changes.

For another approach to compact virtualization hardware, see the silent dual-NVMe ZimaBoard 2 build. Mateo’s story adds a different emphasis: learning how to maintain a small collection of machines and document the incidents that shape it.

FAQ

Does this installation include both Zima hardware and ZimaOS?

Yes. The account describes two ZimaBlades and a CasaOS-to-ZimaOS migration within the broader homelab. Proxmox and the independent Raspberry Pi also have their own roles.

Is the Raspberry Pi the third Proxmox cluster node?

The repository lists it as an independent machine. A future third node appears in the target architecture, so the existing Pi should not be counted as that completed expansion.

Can I download a complete copy of the reminder workflow?

The Reddit contribution explains the messaging sequence and its household purpose. It does not provide a complete workflow export with every credential, service connection and error-handling step needed to reproduce it.

Does running PBS prove every service can be restored?

No. The platform is part of the installation, while the recovery result depends on the data included and the procedure tested. Keep the application’s files, configuration and dependencies in view when planning a restore.

Where can I follow the creator’s ongoing work?

The HOMELAB repository contains the architecture overview, migration material and troubleshooting notes. Its current-state descriptions and future goals should be read as different parts of an evolving project.

Conclusion

Mateo’s orange rack began with the appeal of running something on a shelf. It grew into a set of machines with different responsibilities and services that fit into daily life. The reminder workflow explains the household value; the maintenance notebook explains the effort behind keeping that value available.

The strongest part of this story is the habit of turning an incident into something documented. The printed structure holds the hardware together, while the notes preserve what the creator has learned each time the installation changes.

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

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.