A few months ago, I started keeping a second copy of my important files on a separate drive. No real reason. No disaster had prompted it. I just... started doing it, and kept doing it out of habit, the way you keep locking a door even in a neighborhood where nothing’s ever happened.
Last week, something happened.
My laptop started crashing. Not the annoying-but-survivable kind — full black screen, kernel panic, QR-code-on-the-death-screen kind of crashing. Sometimes it would run fine for an hour. Sometimes it died 15 seconds after I logged in. There was no pattern I could trust.
I did what most of us would do: assumed the worst and started testing. Ran a memory diagnostic for four straight hours, convinced I’d find a bad RAM stick. Came back clean. Tried an older version of my OS, thinking a recent update had broken something. Same crashes. Noticed it seemed to die faster when plugged into the charger than when running on battery, so I chased that theory for a while too, sure I’d finally found the culprit.
Then it crashed on battery as well, and I ran out of theories.
Through all of this, the thought sitting underneath everything wasn’t “what’s broken?” — it was “is my work still there?”
Years of code, projects, half-finished ideas, things I’d be genuinely gutted to lose. And every time that thought surfaced, I had the same quiet answer waiting: it’s backed up.
I didn’t have to scramble. Didn’t have to panic-copy files off a dying machine at 1 AM. Didn’t have to bargain with a crashing OS for just one more successful boot to grab something important. The work was already safe, somewhere else, before I even knew it needed to be.
I eventually took the laptop to a technician. It took him less than an hour to find what two days of my own testing hadn’t: the SSD was failing.
Not the memory. Not the OS. Not the charger.
The one part I’d never even suspected.
A failing SSD can cause read/write errors and system instability that make the symptoms look like something else entirely. Sometimes, the problem isn’t where you expect it to be.
₹300 and a spare drive I happened to have sitting in a drawer, and the laptop’s been stable since.
Here’s the part I keep coming back to: none of my diagnosis actually solved the problem. The RAM test, the OS rollback, the charger theory — all of it took time, and none of it found the answer.
The one thing that genuinely mattered through the entire ordeal was a decision I’d made months earlier, for no clear reason, that had nothing to do with fixing anything.
It was about making sure that whatever broke, it wouldn’t be able to take anything from me.
That’s the real lesson, I think. You can’t always diagnose your way out of a problem quickly, and sometimes the thing that’s actually wrong isn’t the thing you’d ever think to suspect.
But you can make sure that whatever eventually breaks — hardware, software, doesn’t matter — it only costs you time, never the work itself.
Redundancy doesn’t prevent the failure. It just makes sure the failure doesn’t get to matter as much.
— Nikhil Gautam
Top comments (0)