Thank you to u/Free_Curve_9931 for sharing a homelab built around one clear priority: keeping family photographs safe. At its center is a second-hand Core i7-6800K system running ZimaOS, with other reused computers handling media preparation, backups and home automation.
The creator’s Self-Hosting Day contribution follows a journey from one laptop to a collection of purposefully assigned machines. The author works as a dialysis equipment technician in Saskatchewan, Canada; computers are the hobby that grew alongside everyday needs at home.
Family Photos Established the First Priority
The contributor singles out the photographs on their wife’s iPhone, particularly pictures of their grandchild, as the data that cannot be replaced. That gives the setup a different starting point from collecting hardware or trying every application available.
Immich brings those phone photographs into the home-server environment. Jellyfin makes the household’s movie collection available, while other machines support importing and preparing media. The lab has grown considerably, but the reason for protecting it remains easy to explain.
The author’s advice to beginners is to start with one machine and one job. In this case, that job was protecting family photos. The larger installation followed from finding additional uses for affordable equipment and gradually making the machines work together.
There is a similar progression in u/2Hard4Him’s Pi-hole-to-family-server story, where a small initial task eventually becomes part of household life. Here, the irreplaceable collection gives the backup decisions particular weight.
A Used X99 Computer Became the ZimaOS Host
The central machine uses second-hand X99 hardware and a Core i7-6800K. The creator began with a different storage operating system before moving to ZimaOS, and describes liking the interface enough to pay for the option that suited the installation.
The contribution names Jellyfin and Immich among the main uses and describes a UPS arrangement with automatic safe shutdown. These are reported features of this particular home setup. The author’s uptime estimate comes from their own Uptime Kuma dashboard and is a personal observation rather than a product performance guarantee.
What makes the hardware interesting is its role within the wider collection. It is the place where household services and data come together, while other computers perform tasks that do not have to live on the same host.
Another locally sourced reuse project appears in Aldnvaz’s second-hand PC ZimaOS rebuild. The two stories use different components, but both make the software useful on equipment chosen around availability and budget.
Media Import, Conversion and Playback Have Separate Homes
The media workflow includes an especially memorable machine: a 2010-era Core i5-650 computer with three DVD drives running Automated Ripping Machine. The creator has an existing DVD and Blu-ray collection and uses the old computer for importing discs when at home.
A separate Ryzen 5500 system with a GTX 1660 Super handles conversion through Tdarr. The creator prefers the main feature and a preferred audio track, keeping the resulting collection focused on how the household watches it.
The Automated Ripping Machine project and Tdarr’s official overview explain the tools behind those tasks. In this account, the important architectural choice is the separation: importing and conversion have their own hosts, while the ZimaOS machine provides the services the household uses.
| Machine or group | Reported role | Detail from the contribution |
|---|---|---|
| Core i7-6800K / X99 PC | ZimaOS home server | Jellyfin, Immich and household data |
| Core i5-650 computer | Disc import | Three DVD drives and Automated Ripping Machine |
| Ryzen 5500 + GTX 1660 Super | Media conversion | Tdarr on a separate computer |
| HP MediaSmart EX470 | Backup destination | Debian, nightly copies and encrypted off-site synchronization; a boot problem was unresolved |
| Dell and Raspberry Pi in the later update | Automation, filtering and monitoring | Dell runs Home Assistant; Pi runs AdGuard Home and Uptime Kuma |
A Separate Backup Machine Also Needed Maintenance
The backup destination is an HP MediaSmart EX470 from 2007, bought unused in its box for a reported $60 and repurposed with Debian. The creator describes pooling smaller drives, taking nightly copies from the ZimaOS server and synchronizing encrypted copies off-site.
That arrangement reflects the importance attached to family photographs. It also comes with a candid complication: at the time of the main contribution, a kernel update had left the HP refusing to boot. The author includes the failure as part of the ongoing work of maintaining reused computers.
The lesson is practical. A backup destination is another machine with its own operating system, updates and failure modes. Giving it a separate role helps organize protection, but keeping it recoverable still requires attention. This story does not report a completed repair or an independently verified restore test.
The ZimaOS backup and storage guides provide further reading for readers planning their own copies and recovery process. The contributor’s installation is a personal example of that work, including a problem that remained open.
The Blue Mini Rack Shows a Later Part of the Lab
In a follow-up reply, the creator adds a photograph of a blue mini rack. The accompanying update identifies the Dell as the Home Assistant host and the Pi as the machine running AdGuard Home and Uptime Kuma. It also names CyberPower and APC UPS units protecting the equipment.

The update helps keep the service map current. The main contribution mentions network ad blocking as part of the lab; the later reply places AdGuard Home on the Pi. Home Assistant on the Dell supports arrival-based lighting, doorbell snapshots and presence for both people in the household.
The creator also reports buying a used full tower for a planned ZimaOS move and a managed switch for learning VLANs. Those purchases point to the next experiments. The contribution does not establish that the case migration or a particular VLAN design was already finished.
FAQ
What runs ZimaOS in this setup?
A second-hand X99 computer with a Core i7-6800K is identified as the central ZimaOS host. It is separate from the Dell and Raspberry Pi shown in the blue-rack photograph.
Where do media importing and transcoding happen?
The i5-650 computer with three DVD drives handles disc importing through Automated Ripping Machine. A Ryzen 5500 and GTX 1660 Super system handles Tdarr conversion.
Was the backup server working normally when the story was submitted?
The main account reports a boot failure after a kernel update on the HP MediaSmart backup machine. It does not describe a completed repair or restore verification.
Does the UPS description establish a particular runtime?
No runtime measurement is provided. The creator reports UPS protection and automatic shutdown, then names two UPS units in the later update.
How could someone compare a compact host for a future project?
Begin with the drive connections, services and space required. The ZimaBoard 2 single-board server is one current platform to compare; this contributor’s central machine remains a reused X99 PC.
Conclusion
Free_Curve_9931’s lab grew around a collection the household cares about. The ZimaOS server, media-preparation machines, backup destination and automation devices each have a reason to be there.
The story is strongest where it keeps both the successes and maintenance visible. Affordable hardware can keep doing useful work, while an update failure, a new rack photograph and the next planned change show why a home lab continues to evolve.
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.



