Thank you to u/Far-Information-8683 for sharing a candid first two weeks after moving an older desktop’s services to ZimaOS. A fourth-generation Core i3, 16 GB DDR3 and a separate system SSD became the home for Jellyfin, new self-hosted applications and a Kubuntu virtual machine, while an Immich storage-path problem remained unfinished.
The original Reddit report is useful because it includes both the progress and the friction. The creator wanted less complexity, had existing NTFS data drives to account for, and still needed occasional desktop functionality. This was a practical migration with real constraints rather than a blank machine awaiting an application list.
An Existing Jellyfin Installation Was the Starting Point
The owner already ran Jellyfin on Windows 11. Moving personal laptops to Linux had felt relatively straightforward, but moving the desktop’s server role was a different problem. The goal was to avoid spending scarce time building a complicated homelab.
After a suggestion to try ZimaOS, the creator researched the move and used Gemini to help prepare an execution plan. That is the role reported for AI in this story: planning assistance. The post does not supply that plan or establish that every suggested step was correct, so it should not be reconstructed as a verified installation tutorial.
| Part of the migration | What the creator reported |
|---|---|
| Host processor | Fourth-generation Intel Core i3; exact model not stated |
| Memory | 16 GB DDR3 |
| System drive | 256 GB SSD |
| Existing data | Three NTFS drives that the owner could not format |
| Applications tried | Jellyfin, Linkwarden, Nextcloud, Tailscale and Immich |
| Virtual machine | Kubuntu, reported working |
The presence of existing data is central. It changes the question from choosing an ideal new array to preserving access to files already stored elsewhere. The creator says the NTFS drives could not be formatted, but does not identify the underlying reason. No cause should be assigned from that statement alone.
The First Gains Were Services the Owner Could Actually Use
Jellyfin felt faster to load, according to the owner, and benefited from the server remaining available. That is a personal observation after a migration, without a controlled startup-time comparison. It explains why the change felt worthwhile without establishing a general performance advantage for every configuration.

Linkwarden and Nextcloud were new experiments that the creator had wanted to self-host. The post describes them as working in that initial period. It does not report the number of accounts, synchronization clients or documents involved, so these should remain early deployment experiences rather than scale claims.
The budget i3 family-server story shows another older machine finding a household role through media and photos. Here, the distinctive part is the move from an existing Windows Jellyfin installation while retaining separate data drives and a desktop guest.
The Immich Path Change Did Not End in a Confirmed Fix
Immich initially worked, but the creator then wanted to change an external path and make access read-only. That attempt failed. Repeated uninstalling and reinstalling eventually left the application unavailable, and the owner planned to return to it when time allowed.
This is an important boundary in the account. The post gives no logs, complete volume mapping, version pair or demonstrated repair. It would be misleading to diagnose a specific permission error, declare NTFS responsible, or present the final installation as a fully functioning photo service.
The official Immich external-library documentation is the appropriate reference for readers facing a similar task. It distinguishes import paths from the container access needed to reach files and documents read-only mounting. That context explains what needs checking; it does not establish the cause of this owner’s unresolved problem.
A useful troubleshooting record would preserve the host path, the container-visible path and the exact error before changing more variables. Reinstallation alone cannot tell a reader whether an external location was mounted as intended. These are diagnostic considerations for another attempt, not a recovered sequence supplied by the original author.

A Kubuntu Guest Preserved Occasional Desktop Work
The creator also made a working Kubuntu VM for tasks that still needed a desktop environment. This is a separate success from the container applications. It gave the machine another role without requiring every desktop task to be translated into a server application immediately.
The post does not publish the guest’s CPU assignment, memory allocation, disk size or access method. Those details would matter to someone reproducing it, but they are not needed to understand why the VM was useful: the owner still had occasional desktop work after moving the host toward a server role.
For current virtualization behavior, consult the ZimaSpace documentation. An early user report and the current product documentation answer different questions. The former records what this owner accomplished; the latter is where a reader should check today’s supported options.
Remote Access and Recovery Belong to Different Workflows
Tailscale made remote access valuable to the owner. The post also praises the desktop application’s ability to mount SMB shares and the way attached USB storage became available. These observations describe access to the working server and its files.
The Tailscale network overview explains how participating devices join a private network. It supplies useful context without implying a particular access policy, public endpoint or authentication configuration in this installation. Those are not provided in the source.
Recovery is a further question. A new service such as Nextcloud retains more than the documents visible in a folder. The Nextcloud administration backup guide identifies configuration, data and database considerations. It is a reading reference for a growing installation, not evidence that the contributor already tested a complete restore.
The family photo server troubleshooting account explores a related lesson: application state can matter as much as the files a user first thinks to preserve.
Power Scheduling Was Still on the Owner’s Wish List
The creator wanted more flexible shutdown times and a suspend option during long idle periods. They said electricity use had been measured, but supplied no numerical readings or measurement procedure. The article therefore keeps the motivation while making no savings calculation.

Scheduling also affects availability. A machine serving files, media and a VM cannot be assumed reachable while suspended. That tradeoff belongs to the household’s usage pattern. Readers comparing a purpose-built enclosure can review the ZimaCube 2 personal cloud NAS separately; the actual hardware in this story remains the older i3 desktop.
FAQ
Was Immich fully working by the end of the report?
No. It worked initially, but an external-path and read-only change was unsuccessful. After further installation attempts, the creator deferred the unresolved issue.
Why were the NTFS drives not reformatted?
The owner says they could not format them but gives no specific reason. The source does not establish a filesystem defect, permission diagnosis or required conversion procedure.
Which desktop environment was retained in a VM?
Kubuntu. The creator reports the guest working for occasional desktop tasks, without publishing a complete guest configuration.
Are there measured energy savings to compare?
No numerical measurements are supplied. The owner’s wish for idle suspend and flexible shutdown schedules is feedback from that installation, not a quantified efficiency result.
Conclusion
Two weeks brought meaningful progress: an existing media service moved to ZimaOS, new personal applications became usable, and Kubuntu covered remaining desktop work. The original screenshots give that early transition a concrete form.
The unfinished Immich configuration and power-scheduling requests are part of the same experience. Preserving them makes the story more useful to someone planning a migration with existing data and limited time: a working server can still have clearly identified tasks left to resolve.
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.



