Call us — 01483 901310
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Portable Drives · The Fall Was Not the Measure

It Did Not Fall Far and That Is Not the Question

His enquiry contains a reassurance he has offered himself and a symptom that does not fit it. A drive he dropped: "though it didn't fall far or onto anything hard, something has gone wrong. The laptop recognises it when I plug it in, but the connection is not stable and th"en it drops out. Height is a poor measure of what an impact does — and a drop producing an unstable connection rather than a noise points somewhere quite different from most impact cases here.

MediaExternal hard drive following a short fall — enumerating on connection; connection not sustained; no abnormal acoustics reported
Reported situationDrive dropped a short distance onto a soft surface · recognised by the host on connection · connection not remaining stable · dropping out during use · no unusual noise described · contents required
Fault classConnection instability following impact — connector, board or internal cabling disturbance indicated rather than mechanical damage
Equipment usedOperating state at the moment of impact established before assessment · drive removed from the enclosure and connector and internal cabling inspected under magnification · current draw measured on a controlled bench supply · imaged write-blocked on a stable native connection

The decode: what actually determines impact damage

Why height is the wrong measurement: what damages a drive is deceleration, not distance. A short fall onto a hard floor stops the drive abruptly and transfers a large force; a longer fall onto carpet spreads the stop over a greater distance and transfers far less. The same drop onto two surfaces produces two quite different events, and "it didn't fall far" describes only one of the two variables.

The variable that matters more than either: whether it was running. A drive that is powered down has its heads parked on a ramp at the edge of the platter, clear of the surface and mechanically secured — that is what parking is for. A drive that is spinning has its heads flying microns above the surface, and an impact at that moment can bring them into contact. So a gentle knock while running is worse than a harder fall while off, which is the opposite of most people's intuition.

Why his symptom argues against mechanical damage: heads striking a platter produce noise — clicking, ticking, or grinding — and a drive that has been damaged that way generally fails to present at all. His drive enumerates. It is recognised, it engages with the host, and then the connection is not sustained. That is not the signature of a damaged mechanism.

What it is the signature of: something in the physical connection path disturbed by the impact. A USB socket whose solder joints were stressed. A board flexed enough to fracture a fine trace. Internal cabling between the bridge and the drive partly unseated. All of those produce exactly this — a connection that works and does not hold, changing with movement, cable position or handling.

Why that is comparatively good news: a disturbed connection is a physical repair on undamaged storage. The drive itself may be entirely intact behind it, which is a far better position than a mechanism that has been struck.

What must not happen, and it is the natural response: holding the cable at an angle, wiggling it, or repeatedly reconnecting in search of a stable position. Each of those loads the very joints that were disturbed, and it is how an intermittent connection becomes a broken one.

What is worth reporting: whether it was powered and in use when it fell, and what it landed on. Two sentences that change the assessment considerably.

On the bench

The operating state at the moment of impact was established before assessment — a parked drive having its heads secured clear of the surface, while a running drive has them flying microns above it, so a gentle knock in use is more damaging than a harder fall when off. The drive was removed from the enclosure with connector and internal cabling inspected under magnification, enumeration without abnormal acoustics pointing at a disturbed connection path rather than a struck mechanism. Current draw was measured on a controlled bench supply and the drive imaged write-blocked on a stable native connection.

The outcome

The impact circumstances established, the connection path inspected under magnification and the drive imaged on a stable native connection. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: height is the wrong measure — deceleration is what matters, and what matters more still is whether the drive was running. Your symptom argues against mechanical damage: a struck mechanism makes noise and usually fails to present, while yours enumerates and cannot hold a connection.

Drive dropped a short distance that now connects intermittently

Don't wiggle the cable or hunt for a position that holds — that loads the very joints the impact disturbed, and it's how an intermittent connection becomes a broken one. Take some encouragement from the symptom, though. A struck mechanism makes noise and usually fails to present at all; yours is recognised and then drops out, which points at something in the physical connection path — a stressed socket joint, a flexed board, internal cabling partly unseated. That's a repair on undamaged storage. Worth knowing that height is the wrong measure anyway: deceleration matters more, and whether the drive was spinning at the time matters most of all.

Dropped drive that connects and drops out?
Stop wiggling the cable — call Guildford Data Recovery on 01483 901310; impact circumstances established first, connector and internal cabling inspected under magnification, imaged on a stable native connection.
Request a quote online →

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.