Data Recovery Case File · Portable Drives · Deceleration, Not Hardness
But It Landed on Something Soft
His enquiry contained a detail offered as reassurance and worth examining. "I dropped my 2TB Seagate USB hard drive onto a soft surface. It no longer boots, and while it makes a noise when connected, the computer does not recognise it." The drive is almost completely full, and he asked sensible questions about turnaround, delivery and cost. The phrase to unpick is onto a soft surface, because it is offered — entirely reasonably — as a reason the fall should not have mattered. What a drive lands on matters far less than people assume, and the reason is worth understanding: the damage comes from stopping, not from what stopped it.
| Media | Seagate 2TB portable USB hard drive, close to capacity — dropped onto a soft surface; audible activity on connection with no recognition by the host |
| Reported situation | Fall onto a soft landing · drive no longer starting normally · audible noise when powered · not detected by the computer · drive almost completely full · owner able to deliver in person |
| Fault class | Impact damage to the mechanism — deceleration-driven rather than surface-dependent; readiness not achieved |
| Equipment used | No further power-up · laminar flow bench inspection of heads and surfaces before power · matched donor parts as indicated · PC-3000 Express with Data Extractor prioritised head-mapped imaging |
The decode: why the landing surface is not the variable
What actually causes the damage: not the impact with a hard object but the deceleration — how quickly the drive goes from falling to stationary. Inside a hard drive, the head assembly is a light arm on a pivot and the platter stack is a comparatively heavy mass on a spindle, and both continue moving for an instant after the case has stopped. The forces that displace a head assembly, unseat it or drive it into a platter are generated in that instant. A soft landing extends the stopping time somewhat and reduces peak force — but "somewhat" is doing a lot of work, because carpet, a bed or a bag compress by a few millimetres, and a fall from desk height still stops in a very short distance.
Why the height matters more than the surface: the drive arrives at a speed set by how far it fell, and that speed has to be shed. A short fall onto a hard floor and a longer fall onto carpet can produce similar decelerations. This is why drives survive some dramatic-looking accidents and fail from waist height onto a rug — the surface is one factor among several, and it is not the dominant one.
The factor that dominates: whether the drive was running. Powered off, the heads are parked off the data surfaces on a ramp, and falls in that state are frequently survived outright regardless of what the drive lands on. Powered on, the heads are flying nanometres above platters turning at thousands of revolutions per minute, and an impact can drive them into the surface. That single fact changes the expected damage far more than any landing surface does, and it is the detail most worth reporting.
Why his symptoms fit impact damage: a drive that makes a noise and is not recognised has power, and the mechanism is doing something without completing its readiness sequence — consistent with a head assembly that cannot position itself. The noise is worth reporting precisely, because a beep and a click mean different faults.
Why a nearly full drive is worth noting: two practical consequences. Imaging takes longer, and delivery media has to be sized accordingly — a 2TB drive at capacity needs a comfortably larger destination, since a recovery can yield more than the original once duplicates and earlier versions surface.
What to do now: stop connecting it. Every attempt moves a possibly-damaged head assembly across the surfaces holding his data, and after an impact the number of power-ups is one of the largest determinants of what comes back.
On the bench
The drive was not powered on arrival, since after an impact the surfaces are inspected before anything is switched on — their condition sets the plan rather than following it. It was opened under the laminar flow bench and the head assembly and platter surfaces examined, with any scoring located and measured against the intact area. Matched donor parts were fitted where the finding required, and imaging ran on the PC-3000 Express under Data Extractor: head-mapped and prioritised, the healthy expanse captured completely before any damaged zone was approached, in one supervised session, onto delivery media sized above the recovered total.
The outcome
The surfaces inspected before power, the mechanism serviced and the drive imaged in one supervised session. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone whose drive had a soft landing: the damage comes from deceleration rather than from what the drive hit — the head assembly and platter stack keep moving for an instant after the case stops, and that instant generates the forces; a soft surface extends the stopping distance by a few millimetres, which helps less than it sounds, and the height of the fall matters more; but the factor that dominates is whether the drive was running, because parked heads sit clear of the surfaces and flying ones do not. Report that, and stop connecting it.
Drive dropped onto something soft
Don't let the soft landing reassure you into testing it repeatedly. The damage inside a drive comes from deceleration rather than from what it hit: the head assembly and the platter stack keep moving for an instant after the case has stopped, and that instant generates the forces that displace heads or drive them into the surface. Carpet, a bed or a bag compress by a few millimetres, which helps a little, and the height of the fall matters more than the surface does. What matters most of all is whether the drive was switched on — parked heads sit clear of the platters and often survive a fall entirely, while flying heads can be driven into the surface. Say which it was when you ask for help. And describe the noise precisely: a beep and a click mean different faults. Then stop connecting it.
Stop testing it — call Glasgow Data Recovery on 0141 404 0294; surfaces inspected before power, serviced with matched donor parts, imaged in one supervised session onto correctly sized media.
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.