A ZimaBoard 2 Home Server for Media, Photos and Monitoring

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/Connect_7224 for sharing a ZimaBoard 2 that brings media, photos, monitoring and local files together without a large rack. An NVMe SSD supports applications and cache, a UPS provides backup power, and the creator reports running Jellyfin, Immich, Pi-hole, Uptime Kuma and SMB shares.

The original Reddit post describes a compact server that quickly became central to the home setup. Its strongest detail is the small, understandable collection of jobs. A 4 TB hard drive was still a future addition, so the documented installation should be read as a working starting point with room to grow.

A Small Server Started with a Defined Household Role

The creator wanted media, storage and several self-hosted services in a machine that would be comfortable to leave running. Quiet operation and avoiding desktop-level power consumption were explicit goals. The contribution describes the result as quiet and low-maintenance in personal use.

Those observations explain the choice without becoming a laboratory result. The post supplies no wall-power log, sound-pressure measurement or long-term failure record. Its practical value is showing which services the owner chose to keep together and how little equipment was needed to begin.

Part of the setup Reported role or status
ZimaBoard 2 Main home server
NVMe SSD Applications and cache
UPS Backup power; model and runtime not given
Jellyfin and Immich Media streaming and photo management
Pi-hole, Uptime Kuma and SMB DNS filtering, monitoring and local file sharing
4 TB HDD Planned secondary storage and media capacity

The exact RAM SKU, SSD capacity and UPS model are not identified. A reader can compare the ZimaBoard 2 hardware options, but should size a purchase around actual retained data and workloads rather than treating this partial inventory as a complete parts prescription.

The Original Dashboard Shows a Deliberately Short Application List

Connect_7224โ€™s ZimaOS dashboard on a ZimaBoard 2 with Jellyfin, Immich and Uptime Kuma
Connect_7224โ€™s original dashboard shows Jellyfin, Immich, Uptime Kuma and the ZimaOS interface. It documents the installation at one moment, rather than a simultaneous-load benchmark. Original screenshot: u/Connect_7224.

The screenshot makes the software environment concrete. Jellyfin and Immich occupy visible positions beside the file interface, while Uptime Kuma appears below. The written account also identifies Pi-hole and SMB shares. A service named in the post need not appear in the captured portion of the dashboard to be part of the reported setup.

What the image cannot tell us is equally specific. An application tile does not reveal its user count, recovery arrangement or workload history. The displayed component telemetry should not be converted into a whole-system electricity figure that includes the board, its attached storage and the UPS.

For a different approach to organizing applications, the ZimaCube 2 custom-dashboard story shows another owner building a management view around a growing service collection. Connect_7224โ€™s approach keeps the ordinary application interface and a smaller set of household jobs.

Media and Photos Give the Same Storage Different Responsibilities

Jellyfin supplies media streaming, while Immich handles the photo collection. They may both use local storage, but the information a household wants to recover is different. A media library has its files and application settings; a photo service also retains organization and database information that can matter just as much as the original pictures.

The Immich backup and restore documentation is a useful reference for that distinction. It covers the relationship between the database and stored assets. The source post does not publish a tested backup procedure, so the presence of Immich here should not be described as proof that every photograph already has an independent recoverable copy.

Media performance also depends on the playback client. The Jellyfin transcoding guide explains why some playback requires format conversion. Connect_7224 reports using the application but gives no controlled stream count or hardware-acceleration configuration. Those remain questions for a readerโ€™s own media and devices.

DNS Filtering and Monitoring Add Two Different Kinds of Visibility

Pi-hole gives the server a network role beyond storing files. Its DNS filtering can affect devices elsewhere in the home when they use it as their resolver. The official Pi-hole overview describes that DNS-level scope; it does not imply that every advertisement or page element can be removed.

Uptime Kuma addresses another question: whether a chosen service responds to the checks configured for it. The projectโ€™s official repository lists several monitoring methods. The contribution does not say which checks were enabled, so it would be premature to claim that this particular setup verifies every applicationโ€™s full health.

A useful planning distinction follows. A web endpoint answering successfully does not demonstrate that a photo can be restored, and a healthy disk indicator does not demonstrate that a DNS client can resolve a needed hostname. Each check should correspond to the household function it is intended to observe.

The Pi-hole-to-family-server story explores another installation that grew from a network service into broader family use. In this case, the creator began with several complementary services and kept the purpose of each easy to identify.

The UPS and the Planned Hard Drive Address Separate Needs

The board is connected to a UPS. That documents a power-protection choice, but the post supplies neither a tested battery runtime nor an automatic shutdown configuration. It should not be expanded into a claim that every prolonged outage is already handled without intervention.

The planned 4 TB HDD addresses capacity instead. It would add secondary storage and space for media according to the creatorโ€™s description. No completed installation, RAID layout or migration procedure accompanies that plan. Adding a disk and establishing a second recovery destination are also separate decisions.

For readers following this path, the useful order is to identify what currently consumes space, decide what the new disk should hold, and preserve a recoverable copy before moving important data. These are considerations for a similar project, rather than extra steps attributed to Connect_7224.

FAQ

Does this story actually use ZimaBoard 2?

Yes. The original post explicitly names ZimaBoard 2, with NVMe storage and a UPS. The screenshot shows its ZimaOS software environment, while the exact board SKU is not stated.

Was the 4 TB hard drive already installed?

No. The owner described it as future secondary storage for media. The article keeps that distinction instead of presenting a planned upgrade as completed hardware.

How long will the UPS keep the server running?

The source does not give its model, battery capacity or a runtime test. A runtime figure cannot be calculated reliably from the dashboard screenshot alone.

Does the post demonstrate a maximum application or stream count?

No. It documents the service collection and the ownerโ€™s experience. Comments about other peopleโ€™s larger setups are separate contributions and are not specifications for this machine.

Conclusion

Connect_7224โ€™s ZimaBoard 2 has a modest but useful assignment: media, photos, network filtering, monitoring and local shares in one compact home server. The original dashboard makes that working collection visible.

The next storage addition remains a plan, while UPS behavior and recovery details remain unspecified. Keeping those boundaries clear preserves the value of the case: a small set of everyday needs can give a server a defined place in the home before every future upgrade is settled.

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.