Open, and work is coming in · weekdays, 9am–5:30pm Faster by phone: 0800 6890668
PDR Plymouth Data Recovery 0800 6890668 Get a price
PDR / Casebook / Everyone Blamed the Port, Not the Disk

Portable drives · job record · PLY-2025-0337

That Noise Was Not Coming From the Socket.

Folded card had been wedged under the cable for two years, and everybody there knew the drill: push it home, then lift it slightly to the left. It worked, so nobody thought any more about it. Then a sound came out of the Backup Plus that none of them had heard from it before — the light on, a single flat note going on and on — and not one machine in the Falmouth workshop would list the drive. There was an offer from a shop up the road to put a new socket in. He rang us instead.

The customer checked and agreed No names published

Sounds like yours? Talk it through.
0800 6890668

Why it happens.

Here is the trap. Where a thing has been going wrong in one particular place for years, that is the place everybody keeps looking. A worn socket does real harm on its own account: transfers that halt part-way, a drive that leaves the desktop and returns, files with holes through them. Reaching inside and holding a spindle still is not on the list. Poor contact costs you signal; it puts nothing solid into the mechanics. When a note runs on until somebody removes the power, the motor is heaving at something immovable, and in a portable that generally means the head stack has come down and taken hold of a disc. The trouble had shifted, in other words, from the plug to the far side of the lid. A new socket would have cured the half that had ceased to matter.

The kit this job called for.

How the job runs →
The kitWhat it did hereWhy we keep it
ACE Lab PC-3000 ExpressTold the two apart: an old socket fault and a stall that had only just startedDrops the disk into its maker's service mode, out of reach over plain ATA
PC-3000 Data ExtractorTook the drive out of its casing and read it directly from a SATA portThe PC-3000 runs the copy through the drive's own firmware
UFS Explorer Professional RecoveryMounted the copy and lifted the restoration jobs out of it one after anotherMounts what other software will not: APFS, ReFS, XFS, ZFS and Btrfs volumes

How it ran.

01

Separating the new fault from the old one

Two minutes on a current-limited supply decided it. Draw climbed and went on climbing, the motor heaving away at something immovable, until the drive shut itself down. Silence. A stall, and nothing to argue about. His account of the plug was true and beside the point. The casing was coming off regardless, which ended the socket's involvement in the job.

02

Stack away, casing put to one side

Opened under clean air, the heads were exactly where the noise had put them: down on the discs, nowhere near the ramp meant to hold them. The stack was lifted off and inspected, and the band of platter it had rested against showed no marking whatever. From that point the drive ran off a plain SATA port. Nothing about two years of packed-out cable came into any of it, and no iron went anywhere near the socket.

03

One pass, over a connection that holds

Free to turn at last, the drive gave up all of it overnight in one pass, first sector to last. Not once did it leave the bus or reset itself, and none of the dropping in and out he had lived with for years happened at all. That was very likely the best read it ever gave, and certainly its last.

How it ended up.

Ten years of the workshop travelled home, checked item by item: progress photographs from each job, scanned handbooks, parts invoices. His brother's house holds the second copy now, and the working copy is checked against it. The card went in the bin.

In short: The old fault takes the blame for the new one, every single time. When the noise changes, cut the power and leave it cut.

Seeing the same thing?

Leave it switched off and post it in. Nothing happens until the diagnosis, which lists what can still be read and what cannot.

0800 6890668