Pablo #5: Goodbye, Pablo

Oct 08, 2026· 4 min read

Part 5 of the Pablo saga, in five parts. Previously: Pablo #4.

October 8, 2026.

I finally replaced Pablo. After months - months - I genuinely cannot describe how good that sentence felt to write.

This saga started with a first laptop meant for college, networking, Linux, projects, a future. Instead: SMART stakeouts, BIOS warnings, backups over SSH to a phone, support emails, a missing receipt. July happened. August happened. September happened. October arrived. And now Pablo was out - well, the old SSD still existed somewhere, but as far as my laptop was concerned, the reign of terror was over.

The replacement

Another 256 GB CONSISTENT SSD, this time an SSD S7. Same capacity, same job. Hopefully a less criminal personality - I wasn't expecting miracles, just storage that behaves like storage. What an ambitious dream.

First order of business after months of this: I did not blindly trust the new drive. Baseline first - smartctl -x, full reading:

Initial readings, not guarantees.

Zero. Zero. Zero. Zero. After months of watching counters climb, zeros across the media-error attributes felt unreal. Six power-on hours, nine cycles - practically a newborn, against its predecessor's ~1,800 hours and a small investigative report. Pablo had a criminal record. The new guy had a clean background check.

It also reported 100% endurance, which I noted and then firmly refused to celebrate - the old drive taught me that endurance and health are different questions. This time I had status, attributes, error logs, and a baseline. For once the diagnostics were boring.

Boring was exactly what I wanted.

MonSMART gets a new job

The clean baseline was also MonSMART's fresh start. Monitoring a drive from hour six beats inheriting an already-alarming spreadsheet - and the whole saga had clarified what I actually want from the tool: SMART by default, history always, intrusive stuff (filesystem checks, CHKDSK) strictly opt-in. No check-hammering the drive just because more checks sound thorough.

I'm also toying with an AI-assisted layer: the model explains readings and flags patterns in plain language - but never decides whether a counter moved or invents thresholds. Deterministic measurement underneath, interpretation on top. After Pablo, I have zero interest in a monitor that beams "all fine" at me because one percentage looks nice. Been there. Thanks, no thanks.

Usable, at last

The biggest difference wasn't a benchmark. It was the silence in my head: no more will it boot, will 301 appear, did a counter move, should I copy something right now. Those questions had become part of owning my first laptop. Now there's a replacement with a clean report - not immunity (hardware fails; backups stay), but a start without an inherited failure. That distinction is enormous.

The layout came back too:

C:   99.3 GB total,  69.4 GB free
D:   80.4 GB total,  74.9 GB free
E:   57.9 GB total,  57.8 GB free

Restoration still ahead - files, apps, settings, dev environment, none of which rebuilds itself. But at least that work happens on a drive I'm not negotiating with.

Was it worth losing months? Honestly: no. I learned SMART telemetry, failure modes, secure erase, recovery media, warranty procedure - useful, all of it, and I'd rather have learned every bit of it on healthy hardware. I can value the lessons without pretending the experience was character-building. Sometimes a hardware failure is just a hardware failure, and the best outcome is the replacement arriving so you can move on.

Goodbye, Pablo.

You started as storage in my first laptop. You ended as the lead in a five-part saga of telemetry, warnings, logs, backups, erasure, support tickets, missing paperwork, and one replacement.

You made me learn more about storage failure than I ever wanted to know. You also gave me a real reason to improve MonSMART. So thanks for the education.

But respectfully:

F*ck you, Pablo.

Six power-on hours. Zero reallocated, zero pending, zero uncorrectable, zero logged errors on your replacement.

Let's keep it that way.