External Hard Drive Died, No Backup? The Tuesday Click

2026-10-28

It starts as a sound, not a message.

A small, dry tick. Then another. Jonas is standing at the kitchen counter at 8:40 on a Tuesday, one hand on the kettle, and the sound is coming from the grey drive beside his laptop.

He has been a freelance brand designer for six years. Everything lives on that drive. The logo files, the layered originals, the packaging mock-ups for the bakery, the whole folder called Clients_FINAL_real.

The laptop shows a small grey window: The disk you attached was not readable.

He unplugs it. Plugs it back in. Tick. Tick.

His first thought is not about the files. It is, quietly: when did I last copy this somewhere?

The Honest Answer

He knows the answer. He just doesn't want to think it.

There was a plan once. A reminder in the calendar that said back up Friday. It was Friday-ish for a few months. Then a launch came, then a holiday, then a client who wanted everything yesterday. The reminder kept popping up and he kept swiping it away with the thumb that was holding a sandwich.

Now the kettle clicks off behind him and he doesn't hear it.

He opens the cloud folder, hoping. It holds three projects from last spring and a half-synced folder of fonts. Nothing from the last four months. Nothing from the bakery.

He sits down on the kitchen chair, still in his socks, and does the arithmetic nobody likes to do. Which clients are mid-project? Who has final files that exist only here? Which delivered work could someone ask him to change next week?

His stomach does the thing it does when a payment doesn't arrive. A slow drop, like missing a step.

The Call at Ten

There is a call at ten. The bakery owner, Elif, wants to go through the final packaging files before they go to print.

He thinks about cancelling. He thinks about the email he would have to write. Something has come up with my equipment. It reads like an excuse, even though it is true. It sounds like someone who isn't quite a real business.

That is the part he hates most. Not the lost files, though that is bad. The feeling of being the person who should have known better. A professional who charges for care and then keeps his whole working life in one grey box next to the toaster.

He takes the call. He says, as steadily as he can, that he has a technical problem and will send the files by the end of the week. Elif is kind about it. She says, "Of course, take your time."

That kindness somehow makes it worse.

What It Quietly Costs

The next days are a blur of small, tiring jobs. He looks up what data recovery involves and how long it might take. He asks old clients, awkwardly, whether they still have the last versions he sent. Some do. Some don't answer. He rebuilds one logo from a PDF, trace by trace, and bills none of those hours.

He does not sleep well. Every time the fridge hums, he hears the tick.

Nobody warns you that this is the real price. Not only the money, though there is money in it. It is the evenings. The favours you have to ask. The small loss of standing when you tell a client you can't find your own work.

And the thing that stays: the knowledge that it was avoidable. Not through genius or expensive gear, just through something happening quietly in the background while he got on with his job.

The Moment It Turns

A week later, a developer friend comes by for coffee and notices the new drive on the shelf, still in its plastic.

"Is that backed up now?" she asks, lightly.

Jonas laughs, a bit too hard. "Define now."

She doesn't lecture him. She just says what she does: she doesn't rely on remembering. Her machine makes a snapshot of her work on a schedule, keeps a sensible number of old versions, and writes a short log each time, so she can glance at it and see that it ran. If something looks odd, she can run it in a rehearsal mode first, one that shows what would happen without touching anything.

"I stopped trusting myself on Fridays years ago," she says. "Now I trust a log file."

He thinks about that on and off for the rest of the day. Not a better habit. Not more discipline. Just taking himself out of the loop for the one job he has proven he will skip.

A Normal Tuesday, Later

Imagine the same Tuesday, months on.

The kettle is on. The laptop is open. Somewhere in the night, while he slept, a quiet copy of his work was made. Yesterday's version is there. Last week's version is there too. Nobody asked him to remember anything.

He doesn't even check. Or he does, once, glancing at a small text file that says completed, no errors, the way you glance at a locked door on the way out.

If a drive clicked now, he would feel annoyed, then practical. A replacement, a restore, a slightly inconvenient afternoon. Not a drop in the stomach. Not an email to Elif that starts with something has come up.

The call at ten would just be a call at ten.

That is all it is, really. Not a clever system. Just the sense that your work exists in more than one place, and that you didn't have to be brave to get there.

If You Recognise the Tick

If your client work lives on one drive, or a backup "mostly" happens when you remember, you are in very ordinary company. Most people who work alone have a Friday reminder they keep swiping away.

We made Backup & Log Rotation Scripts for exactly this: PowerShell and Bash scripts for Windows and Linux that take incremental snapshot backups, keep a sensible number of older versions, rotate their own logs, and run on a schedule. There is a dry-run mode, so you can see what would happen before anything is touched, and a logfile for every run, so you can see it actually worked.

It comes with a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

You can take a look here: Backup & Log Rotation Scripts

And if your drive is fine today, that is the best moment to look.

An illustrative story, written with AI assistance.