This is the sixth installment of a series of posts to document “How I recovered my Linux systems…” See the first post and second post for the preliminaries, the third post for diagnostics and disassembly, the fourth post for reassembly and hardware checkout, and the fifth post which completes the hardware and software rebuild of my PC-A system… Now, on to my wife’s system, PC-B…
I’ve taken some time in getting back to this, the penultimate post in this series of “recovering Linux,” mostly to be sure that I’d not been fooling myself into a false sense of it’s-fixed-now as I recovered the second of our two Linux systems, PC-B, which suffered a disk failure at roughly the same time as the first, PC-A, system did. Perhaps not surprisingly, although PC-B seemed to have a hard disk failure similar to PC-A’s, the hardware diagnosis, and thus the fix, took an entirely different turn.
Whereas PC-A’s problem was indeed a hard disk failure (a “disk crash” in the popular vernacular, although nothing actually “crashed”) — readily diagnosed by the audible screeching sound that the disk emitted as it failed — PC-B’s failure mode was, upon subsequent evaluation, quite different. And although I was prepared to take a similar course of action — hard disk replacement, repartioning and reformatting, operating system reinstallation, and data recovery from backup resources — to repair it, things turned out quite differently.