Logical & corruption · lab log · BHD-2025-9113
Nothing About It Looked Broken.
The bracket under a shelf above a desk in Sutton Coldfield let go during a backup, and the My Book came down with both cables still attached. On it was a household's entire video collection, the camcorder transfers along with it. Afterwards nothing read as broken: it starts up the same as it always has
, there is no odd noise off it
, and Windows is content to offer Eject My Book
. What never arrives is a drive letter.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
That letter is the last item in a chain, and everything ahead of it has to be sound: motor and heads, then the USB bridge, then the partition table, and only then the filesystem. Here the first two links held — the unit announced itself, and it turned at the right speed — and the chain broke at the third. That is the mark a half-finished write leaves behind. The records took the damage; the mechanism did not. One further rule governs enclosures of this type. Decryption happens on the small board inside, which is why disk and board go onto the bench together and stay together. Separate them and every sector you pull back is noise.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| ACE Lab PC-3000 Express | Cleared the heads, the motor and the platters before anybody said logical | Gets at the factory service commands that standard ATA cannot carry |
| DeepSpar USB Imager | Imaged it through its original bridge so the decryption stayed in the path | Standard-speed imaging, taken through the USB bridge |
| R-Studio Technician | Repaired the partition table and the NTFS bookkeeping on the copy | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
Show the mechanics came through the drop
A healthy noise proves nothing here. Spin-up current, read rate on each head, the defect lists, the reallocation counters — all of it went on the meter, and every figure came back where it ought to be. Twenty minutes of measuring turned a frightening job into an ordinary one.
Copy it through its own bridge board
A My Book keeps its decryption key on that little USB board, so the image was taken with the board in circuit and came out readable from the first sector. Pull the bare disk and copy it on a SATA port instead and you get an immaculate image of gibberish: every byte present, none of it any use.
Work on the copy, where slips are harmless
Read back off the copy, the damage was small and freshly done: a partition table that broke off part-way through an entry at the moment both plugs left their sockets. Rebuilt there, with the drive itself never written to, the volume opened first time, folders and dates exactly as before.
How it closed.
Nothing was short. File counts on the copy tallied with what the folders said they held. Disk and bridge stayed one object from the first measurement to the last, and on hardware of this sort that discipline is most of the recovery.
Other pages worth a look here.
Others under Logical & corruption.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.