Thank you to u/Tuteloo for sharing an older mini PC that has become useful to the whole household. Running ZimaOS, the small machine brings together media playback, family photo storage, network ad filtering and a camera made from an old phone.
The original Reddit showcase identifies an Intel i3-6100, 8GB of RAM and two external hard drives. The photographs and dashboard give this budget server a concrete shape: existing hardware has been given a collection of everyday jobs.
An Older Mini PC Finds a Household Role
A home server does not need to start with a rack or a long list of new parts. It needs something useful to do when it is left running. Here, the connection to daily life is clear: people want to watch their media, keep photos in a shared place and make use of a spare phone.
The hardware is a third-party mini PC. Its Zima element is the operating system. That matters when reading the story: it illustrates ZimaOS on an existing computer, rather than a specific Zima hardware kit.

| Part of the setup | Reported use |
|---|---|
| Intel i3-6100 mini PC, 8GB RAM | Shared host running ZimaOS |
| 500GB and 1TB external HDDs | Storage for the household server |
| Jellyfin and a request workflow with Radarr | Family media access |
| Photo storage | A central destination for family backups |
| AdGuard Home | Network-wide DNS filtering |
| MotionEye and an old smartphone | Camera use with motion detection |
The author planned a move to 16GB of RAM. At the time of the showcase, that upgrade was still ahead. The reported system should therefore be understood as an 8GB installation.
Media Playback Turns the Server into a Shared Service
Jellyfin gives the media collection a way to reach household screens. A request workflow adds another kind of convenience: family members can express what they want through an application, instead of asking the administrator to handle every item manually.
There is a small naming difference in the source worth preserving. The author’s text calls the request tool Overseerr, while the dashboard screenshot labels it Seerr. The post does not explain the transition or exact integration settings, so it is better read as a working household arrangement than a version-specific installation guide.

The Jellyfin transcoding documentation explains why the playback device matters. Direct Play delivers a compatible file without video conversion; transcoding asks the server to do more work. File format, subtitles and client support can therefore change the load on the same computer.
For a reader reusing older hardware, a helpful check is to play a representative file on each actual screen and inspect the playback method. A successful session on one device does not establish a fixed number of simultaneous streams or support for every codec.
Our Pi-hole to family-server story follows a similar progression: services become meaningful when people in the house begin depending on them.
Photo Storage Adds a Different Kind of Responsibility
A family media collection and family photographs may share a disk, but their recovery priorities can be quite different. A personal photograph can be irreplaceable. The useful question is therefore where another recoverable copy exists, rather than simply how much free space remains.
The external drives make the physical storage easy to identify. Their presence does not establish whether files are duplicated between them, whether old versions are retained or whether a copy is kept away from the server. The source does not describe those details.
For another household adopting this approach, a small recovery exercise can clarify the plan:
- Choose a few representative photos and identify where their originals live.
- Copy them through the intended backup process.
- Restore them to a different directory and open the recovered files.
- Record which copy remains available if the mini PC or one external drive stops working.
This is a suggested check for readers, rather than a recovery test reported by the creator. It helps distinguish central storage from an independently recoverable backup.
DNS Filtering Makes Server Uptime Matter
AdGuard Home adds a service whose effect may extend beyond the person administering the machine. The official AdGuard Home project explains that it operates as a DNS server and filters requests to advertising and tracking domains.
That role creates a useful planning question: what happens to name resolution when the host is restarted? A family may be able to wait for a media library, while a DNS interruption can make unrelated websites appear unavailable.
Anyone following the idea should record how household devices reach DNS and how to restore normal access during maintenance. The creator does not publish their router configuration, so the existence of an AdGuard icon should not be read as evidence of a particular fallback arrangement.
DNS filtering also has boundaries. It is not a replacement for every browser-level content filter, nor does running it prove that every type of advertisement is blocked.
An Old Smartphone Becomes Part of the Server
The camera use gives another retired device a job. Instead of treating the phone as an isolated gadget, the setup connects it to software on the server.
The motionEye project describes a web interface for the Motion surveillance program. In a household deployment, the camera stream, detection settings and any retained recordings need to be considered together.
For readers exploring a similar arrangement, useful questions include whether the stream survives a phone restart, how the phone receives power and how much recording space is retained. These are configuration questions to test with the chosen phone; the source does not supply a reusable phone model or camera connection recipe.
Upgrade the Constraint You Can Actually Observe
The dashboard is a convenient place to see activity, but one screenshot cannot establish peak load. A system that looks lightly occupied between tasks may behave differently during a media conversion, a photo copy or a camera recording.
Before buying memory, another owner could observe those operations together and note whether applications run out of memory, storage becomes slow or playback starts converting video. Each symptom points toward a different change. More RAM cannot resolve every storage or codec limitation.
The creator came from several years of CasaOS use. The official ZimaOS overview provides the current platform context, while the original post records one person’s experience at the time. Their request for a darker mobile interface should be read as historical feedback.
For readers comparing a dedicated home-server platform, ZimaBoard 2 is a separate option to evaluate against storage connections, applications and maintenance needs. It was not the machine used in this build.
The same planning approach appears in our small homelab story from u/jc-21: decide which role needs to change before replacing equipment.
FAQ
Does this story require Zima hardware?
No. This particular creator uses ZimaOS on a third-party mini PC. Check the current installation guidance for the hardware you intend to use.
Does the post prove 8GB is enough for every family server?
No. It records one setup. Application versions, camera retention, concurrent tasks and media conversion can produce different requirements.
Are the external drives a verified backup system?
The author describes family backups, but does not document the copy layout, retention or restore results. Those need to be checked separately.
Has the planned memory upgrade already happened?
The showcase describes it as a future upgrade. This article does not assume it was completed.
Conclusion
This budget ZimaOS server earns its place through a few useful household tasks. Its media service, photo storage, DNS filtering and camera use connect an older computer to everyday needs.
The practical next step for a similar build is to understand the busy moments and the dependencies. Keep photo recovery clear, know what a restart interrupts and use observed limitations to guide upgrades. Existing hardware can remain valuable when its responsibilities stay understandable.
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.



