Thank you to u/trinnara for sharing how a movie collection became a reason to build a ZimaBoard home server. The creator keeps the library on a NAS and uses Jellyfin on the ZimaBoard to bring it to the household’s televisions, with Immich, Pi-hole and WireGuard adding other everyday uses.
The Self-Hosting Day contribution also includes an unexpected turning point: a computer that appeared unable to power on, a ZimaBoard 2 ordered while waiting for help, and a replacement power cable that brought the original machine back into use.
A Movie Collection Created the First Server Project
The story began while the creator was cataloguing movies. A Synology NAS was the first investment, and the author followed guides to install Jellyfin on it. The resulting playback experience did not meet their expectations, prompting more research.
The creator describes being a technical novice who can usually follow a guide. That background makes the next step understandable: the small size of ZimaBoard made a separate server feel like an appealing project, even without previous experience building one.
Through tutorials, trial and error, the author mounted the NAS library into the appropriate CasaOS directory on the ZimaBoard. Once the library was available there, the new machine became a usable home-streaming server.
This is one person’s experience with a particular NAS, media collection and client setup. Its useful lesson is the division of responsibilities that followed, rather than a general verdict on the capabilities of an entire NAS brand.
The NAS Holds the Library and ZimaBoard Hosts the Service
The storage and application roles are distinct. The existing NAS provides the media files, while the ZimaBoard runs the service that presents those files through Jellyfin. Keeping the original library available lets another computer take on the playback-server role.
The contribution identifies CasaOS in this arrangement. It does not describe installing ZimaOS on either machine. The Zima connection is the ZimaBoard hardware and, later, the author’s purchase of a ZimaBoard 2.
| Part of the setup | Reported role | Detail to preserve |
|---|---|---|
| Existing NAS | Home for the media library | The author mounts that library for use by the ZimaBoard server |
| Original ZimaBoard | Jellyfin and other household services | CasaOS is named in the source |
| Added graphics card | Part of the expanded media setup | No GPU model, codec test or stream-count benchmark is supplied |
| Televisions | Access to the home media collection | The reason for organizing the library and making playback convenient |
| ZimaBoard 2 | New host being prepared for Jellyfin | The rebuild was still in progress when the creator posted |
A different separation of duties appears in the dual-ZimaBoard family homelab story. Both accounts become easier to understand when each machine has an identifiable job, even though the hardware and storage choices differ.
Playback Needs Led to Graphics Hardware and a Mini Rack
As the creator learned more about subtitle playback and its processing needs, they added a graphics card and a mini rack. The original photograph documents the collection of equipment, cabling and storage surrounding that development.

Subtitle handling should remain specific to the reported experience. Client support, media formats and playback choices can change the work performed by a media server. The story does not establish that every subtitle requires an additional graphics card.
The official Jellyfin transcoding documentation explains the difference between direct playback and forms of conversion. It provides context for investigating another installation without turning this personal build into an untested GPU recommendation.
Convenient Access Made Older Favorites Worth Revisiting
The creator already owned some favorite shows on physical media, but reaching for a disc could be enough of a barrier to choosing something else. Some titles had also disappeared from streaming platforms or moved to another service.
A home Jellyfin library changed that experience. The author describes rediscovering older favorites and making them easy to reach from the televisions. The server’s value came from reducing the distance between an existing collection and the moment someone wanted to watch it.
The creator also values having local entertainment available during internet outages. That is their reported use, not a complete description of offline networking or authentication settings. The contribution does not provide those configuration details.
The same machine acquired more responsibilities through Immich, Pi-hole and WireGuard. The WireGuard project provides a reference for the VPN software named in the source; the author does not publish their keys, peer configuration or network rules.
A Power-Cable Problem Made the Services’ Value Obvious
The original ZimaBoard later stopped powering on. Replacing the CMOS battery did not solve the problem, and the creator contacted IceWhale support.
Before receiving a response, they ordered a ZimaBoard 2. The thought of losing access to the self-hosted services had become uncomfortable enough to prompt another purchase. That moment shows how far the project had moved beyond the original experiment with a movie library.
Support then supplied troubleshooting suggestions. The creator tried another power cable, and the original board worked again. The account reports that result without documenting an electrical diagnosis of the cable or a wider hardware fault.
The sequence matters: support did not direct the creator to buy a replacement machine. The ZimaBoard 2 had already been ordered, while the cable change resolved the original machine’s immediate problem.
The New Board Opens Another Chapter
The creator was taking time to rebuild Jellyfin on the ZimaBoard 2 single-board server when the story was submitted. Replacing the original board as the main host was a likely next step, rather than a completed migration reported in the source.
The old machine’s future was still open. It might go to a friend to introduce them to self-hosting, or stay as a place to experiment without disturbing the main services. Replacing cloud-connected security cameras with a self-hosted system was another longer-term goal.
For another example of learning through available equipment and real setbacks, see the college-laptop family and game-server story. Each creator’s hardware differs, but both accounts show useful services giving the next experiment a reason to happen.
FAQ
Does this setup run ZimaOS?
The contribution names CasaOS on the ZimaBoard. It should not be relabeled as a ZimaOS installation; the actual Zima hardware is what connects this build to the story.
Does the NAS still store the media?
Yes. The creator describes mounting the existing NAS library for the ZimaBoard’s Jellyfin setup. The account does not say the whole library was moved onto the board.
Which GPU and playback formats are tested?
The author mentions adding a video card but does not identify its model or provide subtitle-format, codec or concurrent-stream measurements.
What solved the original board’s power problem?
The creator reports that trying a different power cable solved it after replacing the CMOS battery had not helped. This is an incident report, not a diagnosis for every board that fails to start.
Was the ZimaBoard 2 migration finished?
No completed migration is reported. Jellyfin was being rebuilt, and the decision about whether to give away or keep the original board was still open.
Conclusion
trinnara’s server began as a way to enjoy a media collection more conveniently. The NAS kept its storage role while ZimaBoard supplied a place for Jellyfin and other useful services.
A power-cable scare later revealed how much those services had become part of the home. With the original board working again and a ZimaBoard 2 being prepared, the next chapter is about continuing a setup the creator already knows they value.
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.



