Thank you to u/Ok_Charge5080 for sharing a first mini-lab built around three practical goals: compact size, quiet operation and power efficiency. Its ZimaBoard handles NAS storage while two Dell Micro computers handle most of the computing work, giving a small rack a clear division of responsibilities.
The original build post includes front, angled and rear photographs alongside an equipment list. Together they explain both what the lab runs and how the owner fitted its networking, storage, management and cooling into one enclosure.
A Small Rack Starts with a Clear Division of Work
Putting several devices in a rack can make a collection of equipment look organized. The more useful question is whether its jobs are organized too. In this installation, the storage host and the machines doing most of the compute work have separate roles.
The arrangement gives the owner room to change an application host while keeping the storage role identifiable. It also makes the network part of the server design: applications on another computer must still reach the data they need.

| Equipment | Reported role |
|---|---|
| ZimaBoard with OpenMediaVault | Dedicated NAS storage |
| Four 4TB Samsung SSDs | The listed storage devices |
| Two Dell Micro PCs with Proxmox | Primary and backup compute roles |
| Netgate router with pfSense | Routing |
| TP-Link managed switch | Network connectivity |
| Two JetKVM devices | Remote console equipment |
| Fan controller and Philips Hue controller | Cooling control and a separate home-control device |
The Zima hardware in this story is the original ZimaBoard. The source does not identify it as ZimaBoard 2, and the reported NAS software is OpenMediaVault.
ZimaBoard Gives Shared Storage a Dedicated Home
A dedicated storage host gives the owner a specific place to administer disks, shared directories and access. The OpenMediaVault documentation describes a Debian-based NAS platform with a web administration interface and file-sharing services such as SMB and NFS.
That background explains the software’s role here without assuming which sharing protocol the owner selected. For someone planning a similar layout, the important record is the relationship between an application’s data path, its network share and the account permitted to access it.
OpenMediaVault’s shared-folder documentation also separates the logical share name from its filesystem and relative path. That distinction is helpful during maintenance. A familiar share name can hide a changed mount point or permissions problem; writing down the underlying location makes diagnosis easier.
The listed SSDs total 16TB of nominal capacity before any redundancy, formatting or reserved space. The post does not specify their array layout or explain how all four drives connect. Readers should therefore avoid treating the equipment list as a complete storage wiring guide.
The Dell Nodes Keep Compute Separate from the NAS
With the data role assigned, the other hosts can be considered in terms of the services they need to run. The official Proxmox VE feature overview describes management of both virtual machines and Linux containers, along with backup and restore capabilities.
The owner labels the two Dell systems primary and backup. That description establishes their intended division, but it does not document automatic failover, clustering settings or a successful restore. Those are separate implementation details.
For another builder, this distinction prevents a common planning shortcut. A second machine only becomes useful for recovery when the required data and configuration can reach it and the service can be brought back. A spare host, a scheduled backup and a tested recovery procedure each answer different questions.
Our u/jc-21 small homelab story is a useful comparison: its interest also comes from the responsibilities assigned to a few machines, rather than from combining everything into a single server.
Management Access Belongs in the Layout

The inclusion of JetKVM equipment makes maintenance part of the physical design. Remote console access is useful when a host’s normal administration page is unavailable or when installation requires interaction before the operating system is ready.
The JetKVM documentation covers console use, mounting installation media and optional power-control extensions. The rack’s equipment list does not establish which extensions or remote-access integrations the owner configured, so those capabilities should be checked against the chosen installation.
There is also a dependency to plan around. If access to a management device relies on the same network equipment being maintained, changing that equipment can interrupt the maintenance session. Keeping local access and device addresses recorded gives an owner another way back in.
The Rear View Explains More Than the Front Panels

The finished front provides a clear set of places for equipment. Behind it, cables and power adapters occupy real space. That rear view is valuable because it shows the practical work required to make a compact rack serviceable.
For readers adapting the idea, access deserves attention alongside appearance. A drive drawer needs clearance to open. A connector needs enough room to unplug without pulling another cable. Fans need a path through the enclosure, and labels need to remain visible after everything is assembled.
The author describes the lab as virtually silent. That is their experience of this build; the post provides no measured decibel level or wall-power figure. SSDs and a compact layout alone cannot establish how another installation will sound under its own workload.
Future Upgrades Have a Defined Place
The owner’s next ideas were a move to UniFi networking and an additional fan controller. These were plans at the time of the post, rather than completed changes.
For another owner, a useful upgrade sequence would be to save the current network configuration, change one component, then check storage access and management connectivity before continuing. That makes it easier to connect any new problem to a specific change.
The Proxbox story about a separate backup role offers a related lesson: adding a machine becomes more meaningful when its purpose is clear before the hardware joins the lab.
FAQ
Does this rack use ZimaOS?
The reported storage system is OpenMediaVault on ZimaBoard. The Dell systems run Proxmox. The article follows that combination.
Are the four SSDs a 16TB usable array?
Their nominal capacities add to 16TB. Usable space depends on the actual storage arrangement, which the creator did not document in the post.
Do the two Dell hosts provide automatic failover?
The source describes primary and backup roles but does not supply the configuration needed to verify automatic failover.
Can I reproduce the rack from the photographs?
The images are useful layout references. They do not provide a complete parts list for every mount, storage adapter, cable and power connection.
Conclusion
This first mini-lab has a strong organizing idea: shared storage, compute, networking and management each have somewhere to belong. The photographs make that idea tangible, including the cabling and cooling that the clean front panels would otherwise conceal.
For a reader planning a compact lab, start with the services and their dependencies. Then leave enough physical access to maintain the devices that provide them. The result can remain understandable as individual components change.
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.


