Thank you to u/HelpfulWatercress679 for sharing a family-server project with an interruption in the middle. The first computer went to a friend who needed it. Later, a retired HP Mini PC and a modified 3D-printed enclosure brought the project back, this time running ZimaOS with room for older desktop hard drives.
The goal in the original Self-Hosting Day story was to make family files and photos easier to keep together. This is a ZimaOS installation on reused HP hardware. Its distinctive feature is the work required to make a tiny office computer and larger storage devices fit into one practical unit.
The Family Wanted a Simpler Place for Photos
Before the server, saving photos and videos involved the phone, a laptop or desktop, an external hard drive and time to bring them together. The first build tried to replace that repeated handoff with shared storage, photo and video backup, a media player and remote access.
CasaOS was the entry point. After discovering it on YouTube, the creator revived a 2013-era Core i3 computer and began configuring the services. The early difficulties were ordinary ones: storage settings and ports needed adjustment before the intended applications behaved as expected.
That starting point gives the later enclosure project a clear purpose. The family did not need a miniature rack for its own sake. It needed a consistent place for files, with less dependence on assembling several devices every time something needed saving.
Giving Away the First Server Changed the Timeline
About three months into the first project, a friendโs laptop failed. The creator gave the old PC to the friend, putting the home-server plan on hold. That detail matters because the later HP build was a restart with different available equipment, rather than an uninterrupted series of upgrades to the same machine.
The opportunity came through a company device-renewal program. A small HP computer became available, and the creator returned to the family-server idea. The software choice also moved forward, from the earlier CasaOS experience to ZimaOS.

A Tiny PC Needed a Different Storage Enclosure
The replacement computer introduced a physical mismatch: the system was compact, but the available drives were older 1 TB, 3.5-inch hard disks. The creator looked for a printable enclosure, then modified the design to fit the parts actually on hand.
The finished photograph shows the result as a red-and-black unit with numbered drive carriers. It gives the project a much clearer visual identity than a list of containers could. The photo documents the assembled device; the post explains the decisions behind it without presenting a complete fabrication guide.
| Part of the project | What the creator describes |
|---|---|
| Computer | A retired HP Mini PC acquired through a company refresh |
| Operating system | ZimaOS, following an earlier CasaOS installation |
| Storage | Reused 1 TB, 3.5-inch hard drives |
| Enclosure | A selected 3D model redesigned around the available parts |
| Drive connections | Additional SATA connectivity for a machine with limited internal connections |
| Cooling and power | A slim fan, adapters and converters incorporated into the build |
Drive mounting, connectors, cooling and power became parts of the same problem. Solving only the appearance of the case would not have made the disks usable. The account is valuable because it includes those less visible integration tasks as well as the finished enclosure.
For another example of arranging small computers and storage physically, see the IKEA-cabinet mini rack. That build organizes separate equipment in a cabinet; this one concentrates on making a compact computer and its drives work as a single unit.
The App List Stays Close to the Householdโs Needs
The reported applications include Jellyfin, Navidrome, Immich, AdGuard Home, cloudflared, Glances and Deluge. Together they cover media, photos, network filtering, access and monitoring. The file-sharing and family-backup goal remains the reason the hardware exists.
The creator also removed applications that were no longer useful in this installation. Nextcloud was unnecessary for the access methods already in use; Obsidian was primarily a work tool. This is a useful part of the story: the final server is shaped by what the household uses, including decisions to stop running something.
Application roles are worth keeping separate even when they share one box. A media library presents files for playback, a photo application keeps its own collection and metadata, and a shared folder provides file access. Their data can require different recovery procedures. Immichโs backup and restore documentation, for example, covers both its database and the original media.
ZimaOS Is the Common Thread, Not a Claim About the Hardware
The Zima element here is the operating system. The case does not turn the HP computer into a ZimaBoard, and the story does not report a later move to Zima hardware. Readers exploring the same software path can use the official ZimaOS setup guides for storage, sharing, backup and system settings.
The distinction also helps readers compare approaches honestly. Reusing a small PC involves the connectors and enclosure already available; buying a purpose-built board involves a different starting point. The ZimaBoard 2 product specifications are a separate reference for that comparison, not the specification sheet for this HP build.
The closest parallel in our existing stories is the reused-PC ZimaOS family server: both begin with ordinary hardware and a household task. HelpfulWatercress679โs contribution adds a distinctive mechanical project to that software journey.
FAQ
Does the finished build contain Zima hardware?
The reported computer is an HP Mini PC. It qualifies as a ZimaOS user story because the creator uses ZimaOS on that reused machine.
Why did the creator print a different case?
The available 3.5-inch disks and the compact computer needed an enclosure suited to the actual parts. The creator selected and modified a printable design rather than leaving the build in its original tiny-PC arrangement.
Can the photograph be used as a complete build guide?
No. It shows the assembled unit, while the account describes the main integration work. Exact dimensions, wiring and a complete parts list are not supplied.
Why were some applications removed?
They no longer served a useful role in this personal installation. The creator kept the services that matched the householdโs current use instead of retaining every application tried along the way.
Does a family NAS automatically provide a complete photo backup?
A shared location is useful, but recovery also depends on preserving the files and the application data needed to interpret them. Follow the relevant applicationโs backup instructions and keep a recoverable copy independent of the working collection.
Conclusion
This server was built twice, for reasons that had little to do with chasing newer hardware. The first machine helped a friend; the second brought the family-storage plan back using a retired HP computer and disks already available.
The custom enclosure connects those constraints to a visible finished result. ZimaOS supplies the software foundation, while the creatorโs mounting, cooling and connection work gives the reused hardware a form suited to its new job.
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.



