We are booking in new cases · Weekdays, 9am–5:30pm Urgent case? Call 0800 6890668
MHDR Maidenhead Data Recovery 0800 6890668 Send it in
MHDR / Casebook / More Rattle Than It Should Have, and Now Unseen

Bench log · Portable drives · MHD-2025-6925

Noisier Than It Was, and Now Nothing Finds It.

For a whole summer the Expansion had lived in a toolbox behind the seats of a surveyor's van: wherever the job is, it comes with me. A fortnight of unmade farm tracks, on a barn conversion out past White Waltham, changed that, and it makes a rattling noise the moment it wakes up. She kept using it for several more days. Then it went altogether — Disk Management doesn't even list it — on her own laptop and on the office machine, and I tried a cable straight out of the packet, no change.

Outcome confirmed by the customer No names anywhere

Much the same fault? Call us.
0800 6890668

In everyday terms.

Her own testing had already narrowed it usefully: two different computers, a cable fresh from its packet, and the same nothing from all of them. Whatever was wrong lay inside the casing before the parcel was ever sealed. And inside a working drive almost nothing is meant to move: platters revolving on a bearing, an arm pivoting to carry the heads across them, and that is the whole list. A rattle on start-up says that discipline has gone — a fastening backed out, a component fractured, or slack where the heads are held. Each revolution then offers the loose piece another opportunity.

What the bench used here.

How a job is handled →
ToolWhy we used itWhat it brings
PC-3000 Data ExtractorGoverned the post-rebuild read, surface by surface, under strict limitsThe PC-3000's imaging module, working under firmware-level control
DeepSpar Disk Imager 4Its head map told the five healthy surfaces from the one that was scoredHead map first, then head-by-head reads, holding resets, timeouts and the power line steady
UFS Explorer Professional RecoveryRebuilt the NTFS file system from the image, folder hierarchy and allReads the awkward filesystems others stumble over: APFS, ReFS, XFS, ZFS, Btrfs

The lab work.

01

Identify what is actually loose

Opened under laminar flow, the drive answered immediately. A crash-stop had sheared at the actuator and its fragment was loose in the casing, while the stack itself carried play that no design allows, one suspension bent away from true. Each surface was then examined under the stereo microscope, because heads with slack of that order can touch down on any seek they make.

02

Rebuild the mechanism, then survey what remains

A matched donor assembly replaced the ruined stack and the broken stop together, and what the rebuilt drive was asked for first was a map, not a copy. The result was candid enough: five surfaces reading cleanly and a sixth scored around its outer diameter, which is what those extra days of use after the noise started had cost.

03

One measured pass, and then the drive retires

The read went through in a single unbroken sitting: the healthy surfaces first, the scored band kept until last and taken slowly, with the imager providing whatever patience was required. Donor heads are a loan rather than a repair. The drive gave that one performance and was then retired for good.

How the job closed.

The five healthy surfaces returned in full. What the scored one cost her was part of one chapel survey, every absent file named in the report. Her archive lives on two drives now, neither riding in the van.

The point: A sound the drive was not making a week ago is a forecast. Switch it off at the first one and the losses stay small.

Does any of that match your case?

Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.

0800 6890668