A Silent ZimaBoard 2 Homelab: Dual NVMe and a Custom Printed Case

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/bluefish007007 for sharing a ZimaBoard 2 build shaped by one clear requirement: a home server should be quiet enough to live beside. A custom printed enclosure and solid-state storage bring the hardware together, while Proxmox divides the applications into manageable services. The result is a useful community example of designing around the room where a server will actually run.

In the original Self-Hosting Day comment, the creator explains the equipment choices and application layout. This account follows those reported choices. The operating considerations below explain their practical implications without assigning unpublished temperature readings, storage benchmarks or power measurements to the build.

Start with the Sound You Want to Remove

Noise is a concrete design requirement when equipment shares a living space. Processor cooling, storage and the enclosure all contribute to how a computer fits into that room. Thinking about those parts together makes the requirement more useful than simply choosing a small chassis.

For a similar project, decide when quiet matters: overnight, during work, or while watching a film nearby. Those situations can produce different workloads. Listening only while a machine is idle does not establish how it behaves during a backup or a sustained application task. The contributor describes a quiet result; the post does not supply a standardized acoustic test.

The creatorโ€™s ZimaBoard 2 and two solid-state drives in the custom printed enclosure.
The creatorโ€™s ZimaBoard 2 and two solid-state drives in the custom printed enclosure. Source: u/bluefish007007.

Solid-State Storage Changes the Physical Design

Removing rotating storage removes one source of mechanical sound, but it also changes how drives are mounted and connected. A drive attached through an expansion adapter and one reached through a USB enclosure occupy different physical paths. That matters when tracing a disconnected device or moving the server.

Keep the identity of each drive visible in the configuration record. A device name seen during installation is less helpful than knowing which physical enclosure contains a particular volume. That record becomes especially useful after adding another external disk or replacing a cable.

Component or service Role in the story
ZimaBoard 2 The compact host for this quiet build
Two NVMe SSDs One board-connected drive and one USB 3.0 enclosure
Custom 3D-printed case A deliberate home for the board and storage
Proxmox and LXC Separate environments for the reported services

For expansion planning, compare the PCIe to NVMe & NGFF SSD adapter interface and dimensions with the board and enclosure. This is a component reference for another build; the contributor does not identify the exact adapter model used in the photograph.

A Printed Case Should Preserve Access as Well as Fit

A custom enclosure can organize an installation without changing the need for access to connectors and cooling surfaces. The useful questions are practical: can a storage cable be checked without dismantling everything, and can the assembled machine remain in its intended position during maintenance?

The original image makes the arrangement understandable. It does not establish the printing material, dimensional tolerances or thermal performance of another copy. Anyone reproducing the idea should obtain the creatorโ€™s design details rather than infer a complete manufacturing specification from a photograph. IKEA cabinet mini-rack with ZimaBoard 2 offers a different example of starting with a physical constraint before organizing the services.

LXC Separation Makes Service Boundaries Easier to Follow

The reported workloads include Docker, Pi-hole, OpenCloud, Proxmox Backup Server, Time Machine backups and a small website. That range connects the quiet hardware to ordinary needs: filtering network requests, keeping files accessible, retaining copies and serving a page. The post does not provide a complete dependency map between those environments.

Containers can give different applications distinct configuration and maintenance boundaries. That helps when a change belongs to one service rather than to the whole installation. It does not make the underlying host, power supply or attached storage independent.

Before changing a container, identify its persistent data, mounted directories and network address. An application starting successfully is only one check; opening its normal interface and retrieving a representative file tests more of the path. These are checks for readers considering a similar layout, not additional results reported by the creator.

For the broader virtualization context, our Proxmox cluster guide for ZimaBoard explains a different, multi-host arrangement. The distinction matters: the containers in this story share one host. The two-node ZimaBoard homelab with local AI and Jellyfin provides a community example of distributing responsibilities across machines.

Backups Need an Outcome Beyond a Successful Job

A local backup service has a useful role, but its existence alone does not establish the durability of retained copies. Proxmox Backup Server documentation describes datastores, task history and verification, which help explain what an administrator can inspect. A completed backup job and a successful application recovery answer different questions.

For a small installation, start with one workload and identify exactly what needs to return: settings, application data and the files it serves. Recover a sample to a separate location before replacing the live copy. If the only retained backup depends on the same host and storage that failed, recovery still has a shared dependency to resolve.

A small recovery check can follow three concrete steps:

  1. Identify the application and the persistent data it needs.
  2. Locate a retained copy and the access needed to retrieve it.
  3. Restore a sample separately and check it through the normal client.
Official Proxmox Backup Server example; this is not the contributorโ€™s installation.
Official Proxmox Backup Server example; this is not the contributorโ€™s installation. Source: Proxmox.

Readers moving from backup planning to a concrete recovery exercise can consult the official Proxmox Backup restore instructions for repository access and restoring archived data. Use the instructions for the backup method actually deployed.

Keep a Quiet Server Easy to Maintain

A compact machine becomes easier to keep when routine work stays understandable. Maintain a short list of application addresses, storage locations and recovery steps. Update it when an enclosure or container moves, rather than relying on the original installation notes indefinitely.

The lesson from small-homelab service roles in u/jc-21โ€™s build is relevant here: the usefulness of a household server comes from the jobs it performs consistently. A quiet enclosure makes it easier to place; a clear service and recovery record makes it easier to keep using.

FAQ

Does this build use hard drives?

The contributor reports two NVMe SSDs rather than rotating disks. One is connected to the board and the other uses a USB 3.0 enclosure.

Is a temperature or noise benchmark available?

The comment describes the intended quiet experience, but it does not provide controlled measurements. This article makes no numerical acoustic or thermal claim.

Do separate containers provide hardware redundancy?

No. They can separate software responsibilities while continuing to share the host, its storage connections and power.

Is the second screenshot the creatorโ€™s dashboard?

No. It is an explicitly labelled official Proxmox Backup Server example. The enclosure photograph is the creatorโ€™s own image.

Conclusion

This project is strongest as an example of a clear household requirement guiding the hardware. The enclosure, storage and service layout all serve a server that is comfortable to keep nearby.

Readers can use that approach without assuming the photographed configuration is a universal recipe. Start with the room and the applications, preserve access for maintenance, and make recovery part of the design alongside quiet operation.

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.