What Happens During a Hard Drive Head Crash

A head crash occurs when a hard drive's read/write head slider makes physical contact with the spinning platter surface. The slider normally flies a few nanometers above the platter on an air bearing cushion, with the read/write transducers thermally protruded to an active magnetic spacing of about 1 to 2 nanometers. When that cushion fails, the ceramic slider scrapes the magnetic coating and strips away the recording layer. For the end-to-end procedure, see hard drive data recovery.

How Head Sliders Maintain Fly Height

The air bearing surface (ABS) on the bottom of each slider is a precisely etched pattern of rails and channels. As the platter spins, it drags a thin layer of air (or helium in sealed drives) under the slider. The ABS is designed to hold the slider at a constant fly height as it moves across the platter.

Physical shock and contamination can both disrupt that fly height:

• Physical shock: A sudden acceleration from dropping or bumping the drive overwhelms the air bearing's restoring force. The slider contacts the platter.
• Contamination: The slider flies a few nanometers above the platter. That's why a single speck of dust on the platter surface can cause a crash.

Sequence of Events in a Head Crash

1. Initial contact. The slider touches the platter surface.
2. Material removal. The slider scrapes away the 1-nanometer lubricant layer, the 2-3 nanometer diamond-like carbon overcoat, and then the 10-20 nanometer magnetic recording layer itself. What it scrapes off becomes debris.
3. Debris generation. The abraded particles are picked up by the air stream inside the drive. Some particles embed in the slider's ABS, acting as cutting tools that accelerate platter damage. Others land on adjacent tracks and other platter surfaces.
4. Cascading failure. Debris on other platter surfaces causes secondary head crashes on heads that were previously functioning. A single-head crash becomes a multi-surface crash if the drive continues to operate.

Continued Operation After a Head Crash: Platter Damage Progression

When the operating system cannot read files, it retries the read commands. The drive firmware also retries internally, repositioning the heads and re-reading the same tracks. Each retry drives the damaged heads across the platters again, expanding the crash zone. The drive's own error recovery mechanisms, designed to handle occasional read errors, become the mechanism that destroys the remaining data.

Recovery software makes this worse. Scanning a crashed drive with data recovery software forces the drive to attempt reads across the entire platter surface, dragging the damaged heads (and any embedded debris) across every track. What might have been a recoverable case with localized damage becomes an unrecoverable case with wall-to-wall platter scoring.

Another common mistake is the freezer trick: placing a crashed drive in a freezer before retrying. Freezing puts condensation on the platter surfaces & gels the fluid dynamic bearing (FDB) lubricant in the spindle motor. A crashed drive that was still partially recoverable before freezing often becomes unrecoverable after.

Back-EMF Head Retract on Power Loss

Modern hard drives park their heads on a plastic ramp at the outer diameter when power is removed. The retract sweep is powered by Back Electromotive Force generated by the spinning spindle as it coasts down.

When the drive loses power, the spindle motor briefly becomes a generator. The drive electronics route that induced current into the voice coil actuator and steer the head stack assembly off the platter, parking the suspension lift tabs on the static ramp at the outer diameter. The procedure depends on the kinetic energy still stored in the spinning platters.

How Pre-Amplifier Failures Mimic Head Crashes

A pre-amplifier (preamp) failure on the head stack assembly can produce symptoms identical to a mechanical head crash without any visible platter damage. The preamp IC amplifies the weak read signals from each head. When it fails, the drive clicks as the voice coil actuator sweeps back & forth, unable to read servo tracks.

Preamp IC Location & Function

The preamp is a small integrated circuit mounted directly on the head stack assembly (HSA), positioned on the flex cable between the heads & the PCB. Without a functioning preamp, even physically intact heads produce no usable output.

Preamp Failure Symptoms

The drive powers on, the platters spin, but the heads can't lock onto the servo tracks. The VCA sweeps the head stack from inner to outer diameter repeatedly, hitting the actuator crash stops. This produces the same repetitive clicking pattern as a mechanical head crash, but the platters remain unscored.

For a deeper look at how read/write heads function at the electromagnetic level, including GMR & TMR sensor physics, see the dedicated head architecture reference.

Recoverability by Scoring Depth

Whether data survives a head crash depends on how deep the slider penetrated the platter's layered structure.

From the outside in, a hard drive platter has a PFPE lubricant film about 1 nm thick, a 2-3 nm diamond-like carbon (DLC) overcoat, a magnetic recording layer, & the substrate itself (aluminum alloy or glass-ceramic). The recording layer is where data lives. Everything above it exists to protect that layer from the slider.

PC-3000 Head Map Diagnostic Workflow

PC-3000 interfaces at the ATA command level, sending vendor-specific commands directly to the drive's onboard processor in factory/technological mode. This allows a technician to disable crashed heads in firmware, force the drive to a Ready state using only surviving heads, & selectively image data from undamaged platter surfaces.

RAM Head Map Editing

Rather than permanently altering the ROM, the technician modifies the head map loaded into the drive's RAM. PC-3000 overwrites the RAM copy to remap the failed head to a known-good head for initialization purposes.

Selective Imaging with Data Extractor

In PC-3000 Data Extractor, the technician builds a map of which LBA ranges belong to which physical heads.

The crashed head is de-selected in the Data Extractor interface. The imager clones all sectors belonging to healthy heads while skipping all sectors mapped to the crashed head. No read attempts touch the damaged surface.

Donor Head Selection for Head Crash Cases

A head crash recovery requires a donor drive that matches the patient on parameters including model number, firmware family, head count, physical head map layout, & preamp revision. Swapping heads from an incompatible donor produces servo errors, failed initialization, or secondary platter damage.

Preamp Revision Matching

Drive manufacturers change preamp suppliers & IC revisions mid-production run without changing the model number. A mismatched preamp amplifies the read signal at the wrong gain, produces timing offsets the channel chip can't compensate for, or throws servo errors on every track. The preamp part number on the HSA flex cable must match.

Adaptive Parameters & ROM Retention

The PCB's serial flash ROM holds factory calibration data that's unique to the original mechanism, including head-specific adaptive parameters & servo calibration tables. During a head swap, the original PCB & ROM stay with the patient drive. The donor provides only the physical HSA. This preserves the patient's adaptive data so the drive can read its own tracks.

Helium-sealed drives follow the same path with added steps. We take the lid off, do the swap, and refill the enclosure with helium under controlled conditions. We don't send helium swaps to other labs. The mechanical, gas-handling, and platter-cleaning steps all happen on our bench. We do helium drive head swaps in-house at our Austin lab, and that includes the helium refill after the sealed chamber is opened. Helium head swaps cost $3,000–$4,500, and helium surface damage cases cost $4,000–$5,000, plus helium and donor costs.

Multipass Imaging Strategy for Crash-Damaged Drives

We image a crashed drive in phases with PC-3000 Data Extractor & DeepSpar Disk Imager. We secure the intact data before we touch the damaged surfaces.

1. Phase 1: Healthy heads, fast reads. The RAM head map restricts imaging to confirmed-healthy heads only. The imager uses tight millisecond-level timeouts, aborting any sector read that stalls. Block sizes start large for speed. When the imager encounters a slow zone, it skips forward by a configurable block count & resumes reading beyond the obstruction. No damaged surfaces are touched during this phase. The goal is to capture every sector that reads without resistance.
2. Phase 2: Donor heads on degraded surfaces, throttled reads. After Phase 1 data is safe on the destination media, donor heads address the remaining surfaces. Block sizes drop to single sectors to minimize the mechanical load on each read. Reverse-direction (backward) imaging reads from the healthy zones toward the damage boundary. That pulls data out of the intact areas first.
3. Phase 3: Aggressive retries on previously skipped sectors. This pass runs only after all other recoverable data is secured on the destination media. The technician configures Data Extractor to ignore soft ECC correction thresholds & uses drive-specific utility commands to alter read-channel retry parameters, forcing the drive to extract raw data fragments from marginal sectors.

The DeepSpar Disk Imager complements PC-3000 during crash recovery by controlling the ATA physical layer (PHY) link directly. DeepSpar enforces millisecond-level hardware resets that prevent the drive from entering its own internal error recovery loops.

Open-Source Read-Map Workflows: ddrescue and HDDSuperClone

PC-3000 Data Extractor and DeepSpar Disk Imager are the high end of crash-drive imaging. GNU ddrescue and HDDSuperClone are open-source tools that take the same approach in software. They copy in phases and skip the bad areas.

ddrescue Mapfile Glyph Table

GNU ddrescue tracks the state of every block range in a plain-text mapfile. The mapfile lets the imaging session pause, resume, and avoid redundant reads. Each contiguous block range is tagged with a single-character status glyph.

? non-tried

The block has not been queried yet. Initial state for every range when imaging starts.

* non-trimmed

The initial fast pass hit an error somewhere inside this block. The exact bad-sector boundary is unknown; the range is queued for trimming.

/ non-scraped

Trimming narrowed the bad zone down. The block is queued for sector-by-sector scraping to extract whatever survives inside the failed region.

- bad sector

Scraping confirmed the sector can't be read.

+ finished

The block has been successfully read and written to the destination image. Terminal state; the range is not re-read on subsequent invocations.

Where the open-source path ends and proprietary hardware begins: ddrescue and HDDSuperClone both rely on the drive's own ability to respond to ATA commands. Sometimes the drive is too damaged to identify itself, or it won't stay spun up. Sometimes it needs a head map override to skip a failed head before the rest of the stack can be read, or it needs the translator regenerated after the service area gets corrupted. In any of those cases the imaging has to move to PC-3000, where we can load the firmware in factory mode and adjust the channel chip parameters at boot.

Open-source tools are excellent at squeezing the last sectors out of a drive that still talks; they have no answer for a drive that refuses to.

If a drive begins emitting rhythmic clicking, sweeping noises, or any new mechanical sound mid-imaging, all software operations should be aborted immediately.

What Recovery Looks Like After a Head Crash

Once a crashed drive is open in a laminar flow bench, we inspect the platter surfaces and check:

• How many platter surfaces are scored (visible concentric rings)
• Whether the scoring is localized (a few tracks) or covers a wide band across the platter radius
• Whether debris contamination has spread to other surfaces
• Whether the original heads are physically damaged (bent arms, missing sliders, debris embedded in ABS)

If the platters have localized scoring with intact data areas remaining, a head swap with matched donor heads allows imaging of the undamaged tracks. PC-3000 or DeepSpar Disk Imager reads sector by sector, skipping the scored zones and extracting data from the intact areas. The resulting image will have gaps corresponding to the destroyed tracks, but the recovered percentage depends on how much surface area survived.

In severe cases with full-platter scoring on all surfaces, the magnetic recording layer is destroyed across the entire usable area. No amount of head swapping or imaging can recover data from a platter where the recording layer has been physically removed. For drives with partial damage, hard drive data recovery through selective head imaging can still yield usable results.

Service Area Inspection After a Head Crash

The Service Area (SA) stores the firmware modules, defect lists, and translator tables the drive needs to reach a Ready state.

Module Checksum Verification

A checksum shows whether an SA module is intact. In WD ROYL firmware, modules 102, 103, and 109 are copies of ROM data kept on the platters. Of those, 102 shadows the head map and 103 shadows the adaptives. Module 32 is the G-List in ROYL firmware. On WD device-managed SMR drives, module 190 holds the second-level (T2) translator. Seagate F3 drives keep the P-List, primary translator, and Non-Resident G-List in SysFiles 1B, 28, and 35, in that order. Seagate SMR drives use the Media Cache Management Table (MCMT) to track data held in the media cache.

Virtual Translator Reconstruction

The translator maps logical block addresses to physical block addresses. When a drive's dynamic translator is corrupted, PC-3000 Data Extractor has a virtual translator mode for recovering the data. That mode works from file system metadata and user data.

When Head Crash Cases Reach the Surface Damage Tier

A head crash where debris has spread, multiple platter surfaces show concentric rings, or the recording layer has been stripped to the substrate falls into the surface damage tier.

• Surface / Platter Damage: $2,000. Platter scoring or contamination. Requires platter cleaning and head swap. Typical turnaround is 4-8 weeks; a +$100 rush fee to move to the front of the queue is available where the schedule allows.
• Donor cost is additional. Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.
• 50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.

This tier costs more because there's more mechanical work. Surface damage cases need platter cleaning before we can do a head swap, and the work consumes donor parts. For a full breakdown of the tier system and the decision points between them, see our hard drive data recovery service page and the hard drive data recovery cost breakdown.

If you are comparing labs, our guide on choosing a best hard drive recovery service covers what separates an in-house mechanical lab from a broker. Because all head-crash work is performed at our Austin, TX lab, customers nationwide mail the drive to our recovery lab rather than risk another power-on attempt.

Frequently Asked Questions