Pablo #4: The warranty replacement saga
Part 4 of the Pablo saga, in five parts. Previously: Pablo #3. Next: Pablo #5.
September-October 2026 - The failure was documented. The paperwork was not.
By now I had everything except the replacement: SMART histories, BIOS screenshots, Event Viewer logs, smartctl output, a backed-up drive, install media. I wanted exactly one thing - a working SSD under warranty. Not a free laptop, not therapy after dealing with Pablo. Just a working SSD.
"Not an issue, sir."
One of the early responses from support was:
Not an issue, sir.
A wonderfully reassuring sentence to receive about something your computer's firmware has classified as an imminent drive failure. To be fair, one short reply doesn't prove anyone misunderstood - but after weeks of evidence-gathering, I wasn't in the mood to be told everything was fine. I needed practical answers: can it be replaced, where do I take it, what happens to the old drive, does anyone move my data?
The evidence folder, meanwhile, was getting out of hand: SSD label photos, serial numbers, BIOS screenshots, CrystalDiskInfo results, Event Viewer entries, chkdsk output. It even contained a small mystery of its own - the physical label read CONSISTENT S7 while SMART insisted it was a CONSISTENT S6. Product strings don't always line up neatly, so I didn't read anything sinister into it; but Pablo now had more documentation against him than some actual criminals.
Answers, when they came: the service centre keeps the old SSD, no cloning, no data transfer, replacement issued. Understandable as process - and the reason my backups weren't just precaution anymore. I couldn't hand the drive over hoping someone would preserve my files. And at one point support asked me to call, which - with my hearing difficulties - I routed to email instead. Written confirmation beats a remembered phone call when the question is what to carry to a service centre two cities away.
Then the ghosting arc: messages, follow-ups, silence, repeat. Support had the evidence; the drive kept deteriorating on its own schedule regardless. Every extra week was another week of checking SMART counters, avoiding writes, and wondering if the laptop would survive until the next step - while trying to do college and actual work alongside.
Patna, Delhi, and the missing receipt
Eventually, an address: the Patna office. A concrete next step - gated behind the original purchase receipt, which the original owner didn't have handy. Documented failure, weeks of correspondence, and now the whole thing hinged on a piece of paper nobody could find. I couldn't manufacture one, so the owner searched while I waited. Again.
Fallback: send the drive to Delhi's RMA centre via Speed Post, coordinated around a relative who lives there and would be returning later. Two paths, neither instant:
- Find the receipt, proceed through Patna.
- Otherwise, ship to Delhi when the route opens up.
Pablo had decided killing the SSD wasn't enough. He wanted to become a long-running administrative incident.
July went by. August went by. September went by. Then October arrived. I couldn't just buy another drive and move on - no salary makes hardware replacement a casual expense - so every delay week was another week of living inside a problem that had already taken too much. No montage, just waiting, checking, documenting, trying not to make it worse.
Secure erase in ten seconds flat
One responsibility remained before any handover: my data couldn't go with the drive. Deleting folders wasn't going to cut it, formatting a partition isn't an erase, and reinstalling Windows is an OS install, not a wipe. Fortunately the EliteBook hid the answer in its own BIOS:
F10 → Security → Hard Drive Tools → Secure Erase.
F10 > Security > Hard Drive Tools > Secure Erase
estimated: ~2 minutes
actual: <10 seconds
result: Secure Erase complete.
No third-party wiper, no cyber-café improvisation - and welcome news on a failing drive, where I didn't want to grind through manual overwrites whose assumptions don't even hold on flash. I checked twice that I had the right disk selected (the last thing this saga needed was a sequel), started it, and the two-minute estimate finished in under ten seconds.
Secure Erase complete. Weeks of SMART stakeouts, and the finale took less time than making tea. Speed alone doesn't prove which low-level mechanism ran - firmware decides that - but the BIOS reported complete, which was the result I needed. For once the firmware helped instead of warning me about imminent death. Character development.
Booting afterward gave the expected No bootable image found - alarming anywhere else, deeply reassuring here. The installer USB was already waiting.
One thing I checked: the SMART counters did not reset. Erase makes user data inaccessible; telemetry is telemetry. Reallocated sectors stayed reallocated. An empty filesystem is not a healthy drive - Pablo with no data was still Pablo, and the history I'd collected stayed valid evidence.
And then the awkward part: no OS, still needed a computer. Fresh Windows would have to go on - on a drive destined for warranty inspection, purely so the machine stayed demonstrable. All because 256 GB of flash decided to speedrun retirement. But the replacement still wasn't in hand, because the service centre wanted the one thing I didn't have: the receipt. Erasing the drive, it turned out, was the easy part.
October 8 came next - and after everything, it deserved its own chapter: Pablo #5.