Advertising story · fictional engineer narrator, qualifications and events · illustrative lifestyle photography. Attributed community feedback appears separately.
The print shop closed at six.
At 5:42, I was sitting on the floor beside my desk, an old phone plugged into the wall, a hard drive balanced on my knee, and thirty thousand photos on the phone in my hand.
I needed one picture. Dad, my daughter, a red lighthouse. She was sitting on his shoulders, holding his hair as if it were a pair of handlebars. It was going into the frame I had already bought for his birthday.
I could remember the picture so clearly that I could almost feel the wind that afternoon.
I couldn’t find the file.

I could trace a fault through a control system. I couldn’t find a family photo.
My doctorate is in electrical engineering. I’ve spent sixteen years working on industrial control systems, and I hold a Professional Engineer license.
At work, I’m the person who asks which revision we tested, where the original measurements are, and whether anybody has actually checked the backup. I’ve sat through enough failure reviews to know what “I’m pretty sure we saved it” is worth.
At home, I had a folder called Photos Final.
There was also Photos Final New, an old laptop I kept meaning to empty, and a USB drive with a handwritten label that said “family / check first.”
That evening, none of my qualifications helped. My wife called from the kitchen and asked whether I’d sent the photo to the printer.
“Nearly,” I said.
I hadn’t even worked out which device to search next.
I’d been keeping copies for years. I’d stopped knowing what I had.
The mess had built up through perfectly reasonable decisions.
A new phone arrived. I copied the old camera roll to the laptop before trading the phone in. A holiday filled the laptop, so I bought an external drive. My wife sent me her pictures, and I saved those too. When the cloud account got full, I downloaded an archive.
Every one of those decisions sounded sensible at the time.
The trouble came later, when I couldn’t remember whether a folder held originals, edited copies, or pictures I’d saved from a family message. Sometimes I could find the right trip in three places, with different numbers of files in each.
I’d open one folder, see the beach, and think I was close. Then I’d realize those were the photos from the following summer.
The lighthouse picture might have been on my phone. Or my wife’s. Or the phone she had before the one she was using now.
We had kept so much that keeping it no longer told us where to look.

I was scared to delete anything because I’d already deleted the wrong thing once.
Years earlier, before a trip, I’d cleared some space on my phone. There were two videos of my daughter learning to ride a bike. I checked the thumbnails, kept the longer clip, and deleted the other one.
The longer clip started after she was already riding.
The missing one had the moment she looked back, realized I’d let go of the seat, and carried on anyway.
I searched the recently deleted folder too late.
After that, every cleanup felt like a small examination I could fail. Two similar photos might have different expressions. A short video might contain the bit I cared about. A smaller file might be the only copy somebody had sent me.
I’d select a few hundred pictures, hover over Delete, then cancel.
My solution was usually to copy another folder somewhere else and promise myself I’d sort it out on a quiet Sunday.
Quiet Sundays kept turning into ordinary Mondays.
The cost showed up in moments I couldn’t postpone.
There were little requests I started putting off.
My daughter needed a baby picture for school. Dad wanted the photograph from an old fishing trip. My wife asked for the full-resolution version of a picture I’d once sent her in a message.
I’d say, “I have it. Give me a minute.”
Then I’d disappear into the spare room.
Sometimes I found it. Sometimes I sent a screenshot of the picture because that was the version I could reach. Sometimes the request got buried under the rest of the evening.
The photos were supposed to make it easier to remember people. Looking after them had become another reason to leave the room.
For Dad’s birthday, I had made the mistake of assuming that remembering a photo meant I would be able to retrieve it.
Dad ended up opening an empty frame.
I missed the print shop.
The next evening, I put the frame on the table and explained that I was still looking for the picture. Dad smiled and asked what it was supposed to be.
When I described the lighthouse, my daughter interrupted. She remembered dropping her ice cream afterward. Dad remembered that she’d insisted he finish carrying her even though his back was bothering him.
They were already telling the story. I was still reaching for my phone.
Dad put his hand on my shoulder.
“Come stand here,” he said. “We can take one today.”
We did. It’s a good picture. I’m glad we took it.
But afterward, I kept thinking about the hour I’d spent staring at old folders while everyone else was in the kitchen. I had the memories. I had the equipment. I couldn’t bring the two together when I wanted to.
My friend asked a question I hadn’t thought to ask.
A few days later, I told a friend about the frame. She has children too, and she knew the particular frustration of trying to find a photo while somebody waited beside you.
She asked what I remembered about it.
“The lighthouse. Dad’s coat. A sign by the path.”
“What did the sign say?”
I thought for a moment. NORTH PIER. I could picture the lettering.
She opened ZimaOS Photos on her laptop and showed me how she browsed her own library. What caught my attention first was seeing old camera pictures beside phone pictures, without first choosing a device.
I asked the question I’d been carrying around for years.
“Am I going to have to rename everything?”
She pointed me to the source-folder settings and suggested I start with one trip.
I started with the beach folder because I knew what belonged there.
I checked the Photos documentation, then set up a compatible home server running ZimaOS 1.8 or later.
The first folder I brought over was small enough to inspect. I opened a few originals and checked that the copies on the server were usable before doing anything to the old devices.
Then I added that folder as a source in Photos. Indexing it left the existing folder structure in place.
That mattered to me. I could try the library without committing to an afternoon of renaming files or moving the archive around again.
I added another trip afterward. Then a folder from an older phone.
For once, I could stop after a manageable piece of work and still have something useful.

I stopped treating the first import as proof that everything was ready.
The first time I tried searching, I was too early.
The pictures were visible, but the content analysis was still running. In the search settings, I could see the readiness progress. That distinction helped me understand why a new photo might be browsable before it appeared in a content search.
I also learned that basic object and image-text searches run locally without a dedicated GPU. Deep visual understanding is a separate option that uses one.
I left the server to work through the library. There was no reason to sit beside it refreshing the same query.
I’d spent enough evenings turning a small household job into a late-night engineering project. This time, I let myself go downstairs.

I found a better way to narrow the search.
When I came back, I tried “lighthouse.” Nothing useful appeared.
I’d read the search guide by then. Basic object recognition has a defined set of categories. It wouldn’t recognize every landmark or understand every description I could invent.
So I tried the words from the sign.
NORTH PIER brought me to a group of pictures I could work through. A photograph of the path helped me identify the right outing. From there, browsing the nearby dates brought me back to Dad and my daughter.
I opened the original and checked the detail. There was her hand in his hair. There was the coat I remembered.
I saved a copy for printing before doing anything else.
It felt good to finish a search with a file I could actually use.

The timeline brought back the rest of that afternoon.
Once I had the date, I stayed a little longer.
I moved through the timeline and found the other pictures from that day. A few were blurred. One was mostly my shoe. There was the ice cream my daughter had remembered, followed by the face she made after it fell.
I’d spent days looking for one image and forgotten that we had taken a whole afternoon’s worth.
Seeing them together made the collection feel familiar again. I could remember the order of things. Dad had carried her on the way back, after the ice cream, when she was tired.
I made an album for him. I kept it short enough that he would actually want to look through it.

I looked for other users who had made this part of everyday life.
Before adding the rest of the archive, I wanted to understand how people lived with ZimaOS after the first enthusiastic weekend.
The feedback that interested me was about ordinary use. Less time maintaining things. A library or service that stayed useful. Help when something needed attention.
The following are summaries of real comments published on Zima’s official community-feedback section. They describe everyday use of ZimaOS overall.
ZIMAOS COMMUNITY VOICES · FEEDBACK SUMMARIES

Mohamed Elallami
ZimaOS community memberA workflow that leaves more time to create
Describes ZimaOS as reducing the time he spends managing his self-hosted setup and fitting naturally into his creative work.

sabiTech
ZimaOS community memberA manageable platform for containerized work
Highlights a lightweight, approachable system for running containers and looking after edge workloads.

Grim Oak
ZimaOS community memberUseful services in one home setup
Reports using ZimaOS for Jellyfin, a book collection, network ad blocking and downloads, with positive feedback on usability and ongoing development.
I made a plan for the pictures that hadn’t been taken yet.
Finding the lighthouse photo solved one request. I still had a phone quietly collecting new pictures every day.
I installed ZimaClient, connected to the server on home Wi-Fi, and chose the albums I wanted to back up. I used a photo-storage folder as the destination instead of filling the small system drive.
For the first transfer, I kept the phone near the router and let it finish. Afterward, I checked a selection of files on the server.
Then I enabled automatic backup. The official phone-backup guide helped me choose what to include and understand the connection settings.
I liked being able to look at progress. Previously, I’d relied on a vague feeling that some service was probably taking care of things.
Now, before putting an old phone away, I had something specific to check.

I could enjoy the awkward formats I used to put off opening.
Our family pictures came from more than phones. I had RAW files from a camera I’d bought before my daughter was born, Live Photos from newer iPhones, and a handful of 360-degree holiday images.
Those files had often become a separate job. I’d tell myself I would open the right software later, or make an easier copy to send somebody.
Photos supports those formats in the same library. Where a particular RAW file’s preview depends on decoder support, I check it before assuming it will display exactly as another one does.
That gave me a reason to revisit the camera folders. I wasn’t just moving them from one drive to the next.
A Live Photo of Dad laughing became one of my favorites. The still image was fine. The second of movement around it was what I’d wanted to keep.
I still checked the backup. I just stopped making fear do all the work.
I hadn’t forgotten the bike video.
Before deleting anything from a phone, I opened files from the server and checked the originals. I kept a separate backup as well, with another copy away from the machine.
I followed the ZimaOS backup guide to plan those copies and tested a restore. RAID could help with drive failure, but accidental deletion needed its own protection.
That gave me a calmer way to decide what to clear from the phone. I could check where a file was and whether I could recover it.
I still kept plenty of imperfect pictures. I just didn’t have to keep every copy on every device because I was frightened to touch anything.
My daughter asked to see the beach pictures. I stayed at the table.
A few weeks later, Dad came over for dinner.
The framed picture was on the shelf by then. My daughter pointed at it and asked whether we still had the one with the ice cream.
I opened the album on my phone.
There was no trip upstairs to find a cable. No request for my wife to check her old phone. No half-hour gap while somebody waited for me to return.
We looked at a few pictures. Dad told the same story about carrying her back to the car. She corrected part of it. He insisted he remembered it properly.
I put the phone down when the food was ready.
It was such a small thing that I might have missed it before. I’d been able to join in while the conversation was happening.

I’d begin with the folder somebody in the family already wants to see.
If your photos are spread across old phones, laptop folders and drives you’re afraid to clear, start with one collection you recognize. Bring it onto suitable storage, verify the files, and add it to Photos.
Give the indexing time to finish. Try a date you remember, an ordinary object in the picture, or distinctive text you can still see in your mind. Open a few originals. Then decide what to bring in next.
You can start with ZimaOS on compatible hardware. Photos is available from ZimaOS 1.8, and the free plan is a way to explore the system before deciding whether you need the larger disk and user allowances.
If your setup needs those allowances, ZimaOS Plus currently costs US$29 for a lifetime license, with unlimited disk and user counts within your hardware’s capacity. Official Zima hardware already includes Plus.
For me, the place to begin was the beach trip. I’d bought a frame for one picture. I ended up finding a way to see the rest of it again.
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.


