|
Here's my anecdote: In 2006, while sitting at my desk playing a video on the hard disk drive of my Thinkpad T22, I held a single neodymium magnet (harvested from an old hard disk drive) about 6 inches from the left side of the unit (where the ~40GB-ish Travelstar 2.5" PATA disk was located). The video froze, Windows XP blue-screened, and the hard disk drive started emitting a ~10Khz whine. I jerked my hand away from the PC immediately when the whine started. BIOS would no longer detect the disk on that machine, or any other I tried it on (on both USB-to-PATA and honest-to-goodness motherboard PATA controllers). The drive spun up but made a repeated ticking sound (I assume seeking back and forth looking for servo tracks). I sent the drive to Kroll Ontrack (because, stupidly, I had billing data that wasn't backed-up on the drive). The report I received back indicated that 80% of the drive's sectors were unreadable. As an aside: The data I was looking for was ASCII text and Kroll Ontrack was completely unhelpful in just sending me a bitstream image of the drive so I could grovel thru looking for data I needed. Being plain ASCII, their "file carving" tools didn't locate any of the data. (They sent me a "preview" of the data they'd located, and while it got lots of Microsoft Office-format files, it didn't have any ASCII text files). I offered them a 3x multiple of the rate they asked for file-level recovery to simply send me the bitstream image of the disk that they'd already made. They wouldn't do it, and wouldn't even let me pay to talk to somebody who understood what I was saying. I ended up taking a major loss on the billing data I destroyed. I'll never recommend them to anybody. I won't ever play with neodymium magnets around spinning rust media again. |
1) external magnet messed up heads movement closed control loop (internal drive's magnets + voice coil + positioning marks on the platters), and as a result head actual position became different from what controller thought it was.
2) control loop tried to correct itself, repeatedly failing, all while head kept moving across the platters, while controller was still thinking it's elsewhere.
3) controller was writing to disk, so it overwrote data in highly irregular tracks that followed erratic head dance. some of that overwrote positioning markers.
4) when recovering, even though 99.9% of data was still there, controller failed to position the head on erased markers, so reported "unreadable sectors"