Case notes · Logical & corruption · SDR-2025-1113
Dropped, and Apparently Unharmed.
A fall with an unnervingly cheerful sequel. There is no clicking and the blue light shows
, and to the owner's eye all appears ok
. Windows concedes the unit exists and offers to safely remove my book
— but hands over no drive letter, no volume, nothing you can open. Eight terabytes, stranded halfway into being seen.
Seeing the same thing yourself?
0800 6890668
The translation.
Quiet was the genuinely encouraging part: falls that ruin mechanisms seldom do it discreetly. When a unit spins evenly and announces itself on the USB bus but produces no volume, the harm almost always sits above the hardware — partition structures left inconsistent when impact ripped the connection away mid-update. This range brings its own catch, too. My Book units encrypt on the bridge board, which marries the disk to its enclosure electronics; the pair goes on the bench together or not at all.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| ACE Lab PC-3000 Express | Put the mechanism on record as healthy before calling this a logical fault | Talks to drives using maker-specific commands beyond the ordinary ATA instruction set |
| DeepSpar USB Imager | Imaged via the unit's own bridge so the encryption chain stayed whole | Identical controlled reading, this time through a USB bridge |
| R-Studio Technician | Reconstructed the partition and filesystem layout from the copy | Wide filesystem support, with RAID rebuilds you can trust |
In the lab.
Show the mechanics are healthy, don't assume it
Silence is not proof of health, so the unit was tested properly: how it spun up, how each head performed over its surface, what the defect and reallocation logs held. All of it read clean, and that single finding is what made the rest of the job simple.
Copy it via the bridge, not past it
The key for a My Book sits on the bridge board, so the image was taken through the unit's own electronics instead of pulling the bare disk out. Skip the bridge on hardware like this and you get a flawless copy of ciphertext nobody can read.
Mend the partition tables on the image
The fault sat precisely where the symptom said it would: partition structures scrambled at the instant of the fall, which left the unit visible on the bus but its volume nowhere. Repaired on the image, that volume opened with the whole project archive intact.
The result.
A complete recovery, with no folder missing. The keep-it-together rule held throughout — disk and board are married on this unit, and handling the pair as a single patient is why the data survived.
Similar cases on the index.
Other cases in Logical & corruption.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.