Break Glass: Six Tools You Need Once a Year and Cannot Replace

The Drawer You Hope Stays Shut

Somewhere in most kitchens there is a drawer with a tool in it that gets used once a year. The thing that pulls a broken cork. The wrench that fits exactly one bolt under the sink. You do not think about it for months. And then one evening something goes wrong, and that single-purpose object is suddenly the most important thing you own, because nothing else on Earth will do the job.

Software has that drawer too. This episode is six tools that live in it. You will not touch them this week. You may not touch them this year. But when the day comes, and for these tools the day is usually a bad one, there is no substitute, no general-purpose alternative, no clever workaround. There is just the one right tool, and the enormous relief that someone built it and you remembered its name.

The Photos Are Still There

Start with the worst common version of the bad day. A memory card, a phone, an SD card from a camera. It says it is empty, or it says it is corrupted, or someone formatted it by accident, and a year of photographs appears to be gone. Most people's instinct at this point is to panic, then to start clicking around, which is precisely the wrong thing to do.

The right thing is a tool called PhotoRec, written by a French developer named Christophe Grenier, first released back in two thousand and two. PhotoRec does something quietly brilliant. It ignores the file system completely. It does not care that the index saying where everything lives is damaged or wiped. It reads the raw storage, byte by byte, looking for the signatures, the telltale opening bytes, of known file types. A JPEG starts a certain way. PhotoRec knows hundreds of these patterns, more than four hundred and eighty file types, and it carves the files back out of the raw data directly. Crucially, it only ever reads from the damaged card, never writes to it, so it cannot make things worse. It is the tool you want to already know about before you need it, because the day you need it, you really need it.

The Drive That Is Making Noises

A close relative of that bad day is the hard drive that has started to die. Not dead yet. Dying. Making a faint noise it did not used to make, throwing errors, readable in places and not in others. Every minute it runs, it may be getting worse. Ordinary copying tools handle this badly. They hit the first unreadable spot, they stall, they retry forever, they give up, and meanwhile the healthy parts of the drive you could have rescued are slipping away.

The tool for this is GNU ddrescue, and its strategy is exactly the one a calm expert would use. It grabs all the easy, healthy data first, as fast as possible, getting the most while the getting is good. It writes down a map of what it has rescued and what it has not. Only then does it come back for the difficult, failing regions, working at them carefully. And because it kept that map file, you can stop and resume, swap cables, try again tomorrow, and it picks up exactly where it left off. It treats a dying drive the way a trauma medic treats a patient. Stabilize what you can, triage the rest, never waste effort. You will use it almost never. When you do, it is everything.

What Is Hidden in the Blob

This one is for a stranger kind of curiosity. Somewhere you have acquired a firmware file. The software that runs inside a router, a camera, a smart plug, some little device. It looks like a single meaningless brick of data. But it is not. It is almost always several things packed together. A bootloader, a compressed file system, a kernel, configuration, maybe a few embedded images.

binwalk, created by a security researcher named Craig Heffner around twenty ten, is the tool that sees through the brick. It scans the whole blob looking for the signatures of known formats, the same idea PhotoRec uses, and it also measures entropy, the randomness of each region, because a sudden spike toward pure randomness usually means compression or encryption begins right there. From that, binwalk draws you a map of the hidden interior, and then it can pull the pieces apart so you can look inside. It is the core tool of an entire community of people who reverse engineer the devices in their own homes. A wide tool would never bother to understand firmware this deeply. binwalk understands almost nothing else.

The One Log File at Three in the Morning

Something has broken in production. You have the log file. It is enormous, it is messy, it interleaves three different services, the timestamps are in slightly different formats, and the ordinary tools are failing you. tail can follow a file but cannot scroll backward. grep finds a matching line but throws away the multi-line message it belonged to. less shows one file at a time and understands none of it.

lnav, the Logfile Navigator, written by a developer named Timothy Stack, describes itself, beautifully, as an advanced log file viewer for the small-scale. That phrase is the whole philosophy. This is not big logging infrastructure with dashboards and a monthly bill. This is one person, one terminal, a pile of log files, and a problem that needs solving now. lnav automatically recognizes common log formats, merges multiple files into one timeline sorted by actual time, highlights the errors in red, and, the genuinely clever part, lets you run SQL queries against your logs as though they were a database. For the specific situation of needing to understand a mess of logs right now, on this machine, it is untouchable.

The Database Someone Handed You

Here is a gentler bad day. Someone gives you a file. It is a database, a single SQLite file, or maybe just an awkward CSV, and they say, the answers are in here somewhere, good luck. You do not have a tool open. You do not want to set up a whole environment. You just need to look.

datasette, built by Simon Willison, one of the original creators of the Django web framework, turns that file into an explorable, queryable website with a single command. You point it at the file, and instantly you have a browser interface. You can click through the tables, filter them, facet them, write real queries, follow the data wherever it goes, and then publish the whole thing as a live site if you want others to see it. It was built originally for journalists, for exactly the moment when a reporter is handed a leak or a public records dump and needs to interrogate it without being a database engineer. It is the fastest possible distance between a mystery file and an actual understanding of what is in it.

The Moment Before You Hit Send

The last tool is for a bad day you can prevent. You are about to share a file. A photo, a document, a PDF, posted publicly or sent to someone you do not fully trust. And as we heard in the previous episode, that file is quietly carrying a hidden passenger. The camera model. The GPS coordinates of your home. The document's revision history. The name of every person who edited it. You did not mean to send any of that. You are about to send all of it.

mat2, the Metadata Anonymisation Toolkit, exists for the sixty seconds before you click send. It strips that hidden layer out. EXIF data from images, author and history from documents, the embedded clutter from PDFs, gone, leaving you with a clean copy that says only what you actually intended it to say. It came out of the privacy community, the same world that worries professionally about how people get found, and it does just this one protective thing. It is a tool you should hope you never have a dramatic reason to need. But the habit of running it is cheap, and the day it matters, it really matters.

The Pattern

PhotoRec, ddrescue, binwalk, lnav, datasette, mat2. Look at when each one gets used. After the deletion. During the failure. In the middle of the incident. The instant before the mistake. These are not tools you live inside. They are tools you reach for at a sharp moment, and the entire value of them is concentrated into that moment.

There is something worth saying about the people who build software like this. Nobody writes a disk-rescue tool because it is glamorous. You write it because you, personally, once watched data die and could not save it, and you decided no one should have to feel that again. The break-glass drawer is, in a real sense, a museum of other people's worst days, each tool a small monument to a problem someone refused to let stand.

So the practical advice is just this. You cannot keep all of these in your head. But keep the shape of them. Remember that the category exists. Remember that when a drive is dying, or a card is wiped, or a log is chaos, the odds are extremely good that some quiet person already felt that exact pain and left a tool in the drawer for you. Your only job is to remember to open it.