Where do hard drives fail mechanically (heads, spindle, vibration, helium), and which public signals see it?
Published 2026-10-11
Public sources let you name four mechanical failure points of a hard drive and say which counters watch each, but none of the sources opened gives the share of real-world failures each one causes. Head-disk contact: a Berkeley simulation of a 2.5-inch drive found the head hit the disk at a 400 G, 0.5 ms positive shock but not at 300 G, and at a 2.0 ms negative shock of 1,600 G but not 1,500 G. Vibration: in a 1.8-inch drive test, throughput dropped to zero at 300 to 1,000 Hz below 15 g and recovered when the shaking stopped. Helium: an HGST paper found disk flutter rose fast as air replaced helium and levelled off near 80% air, and Backblaze saw one helium drive's SMART 22 fall to 94 to 99 with no other fault. Spindle: Seagate's documented counters are retries in the last 8 spin-ups and a count of mechanical start failures. Vendor counters (head bitmap, shock, free-fall, high-fly writes, helium pressure) exist, but the sources describe what they count, not how often they warn before a failure.
- Head-disk interface
- Simulated operational shocks on a 2.5-inch drive (Li and Bogy, Berkeley); shaker tests on a 1.8-inch drive from 100 to 1,000 Hz (Chua et al., 2006).
- Helium fill
- One 3.5-inch, three-disk drive run in air, helium and mixtures (Eguchi, HGST Japan); Backblaze's SMART 22 notes of 2015 and 2018.
- Public signals
- ATA SMART attributes and Device Statistics counters for spin-up retries, mechanical start failures, head health, shock, free-fall, high-fly writes and helium pressure.
- Not covered
- Failure shares by cause, bearing wear data, contamination and corrosion, shingled or multi-actuator drives, and vendor warranty terms.
Four mechanical failure points and the numbers the opened sources give
| Failure point | Measured or simulated value (unit) | What happened | Scope of the test | Source |
|---|---|---|---|---|
| Head slap, short positive shock | 300 G survived; 400 G failed (pulse 0.5 ms) | Net air-bearing force went negative before the clearance reached zero, and the slider hit the disk at its inner trailing corner | Simulation, 2.5-inch drive | Berkeley shock report |
| Head-disk contact, long negative shock | 1,500 G survived; 1,600 G failed (pulse 2.0 ms) | The air bearing stiffened and the slider crashed only when the shock's inertia load beat the bearing force | Simulation, 2.5-inch drive | Berkeley shock report |
| Resonance sensitivity | Actuator first bending mode 472 Hz; disk first mode 1,043 Hz (Hz) | A 1,000 Hz shock sat close to the disk's first mode and caused contact after the pulse had ended | Simulation, 2.5-inch drive | Berkeley shock report |
| Vibration soft failure | None below 300 Hz up to 15 g; seen from 300 to 1,000 Hz below 15 g (Hz; g) | Data transfer rate fell to zero and resumed when vibration stopped; no physical damage was recorded | Shaker test, 1.8-inch drive; shaker limit about 15 g | Chua et al. 2006 |
| Disk flutter, air versus helium | Damping ratio of mode (0,0): 1.52% in air, 0.84% in helium; excitation factor 20.7 versus 1.09 | Helium gave much smaller flow excitation; earlier papers cited by the authors put the flow-induced vibration reduction at 10 to 20 dB | One 3.5-inch drive, three 95 mm disks | Eguchi (HGST) |
| Helium loss | Flutter rose rapidly as air entered and levelled off after about 80% air (% air by volume of the mix) | The relation was not proportional to gas density; the authors name transitional, critical and turbulent regions at density ratios of 0.14 to 0.35, 0.35 to 0.6 and 0.6 to 1 | One 3.5-inch drive, controlled mixtures | Eguchi (HGST) |
Helium drives in one operator's fleet: what Backblaze reported
| Item | Value (unit) | What the post states | Caveat from the post or its scope | Source |
|---|---|---|---|---|
| Helium status attribute | SMART 22; starts at 100, threshold 25 (normalized value) | HGST said it is a pre-fail attribute that trips when the drive's internal environment is out of specification | HGST gave no helium amount and no trip points | Backblaze, 2015 |
| Drives reporting SMART 22 below 100 | 1 drive, readings of 94 to 99 (normalized value) | The drive kept performing with no other errors or temperature change | Backblaze says it is unsure whether this was a real signal or a wonky sensor | Backblaze, 2018 |
| Helium versus air AFR at similar drive days | Helium 1.06%; air-filled in Q1 2017, 1.61% (% per year) | The author compared helium drives now with air-filled drives when they had similar drive days | Different models and years; the post calls the lower helium AFR a prediction | Backblaze, 2018 |
| Spin power saving | Typically 20% less energy to spin the platters (percent) | Reduced gas drag lowers the energy needed | A design benefit stated in the post, not a failure measurement | Backblaze, 2018 |
| Helium retention | Not quantified (no unit given) | Backblaze says helium escapes from most containers and that drive makers had to build sealed enclosures to hold it | No leak rate or lifetime is given | Backblaze, 2018 |
Public counters that watch each mechanical failure point
| Counter (ID, vendor) | Unit or form | What it counts per the source | What the source does not say | Source |
|---|---|---|---|---|
| Spin Retry Count (10) | retries in the last 8 spin-up attempts | Retries needed to get the spindle motor to speed; related to, but not the same as, mechanical start failures | How often a rising count precedes failure | openSeaChest wiki |
| Number of Mechanical Start Failures (Device Statistics; NVMe rotational media log has failed spin-up and load counts) | count of events | Times the drive could not start normally; the drive may retry | The cause of a start failure | openSeaChest wiki |
| Head Health Self Assessment (18, Seagate) | bitmap, one bit per head | A bit set to 1 marks a head the firmware judged bad; relates to depopulation reporting | How early firmware sets a bit; older Seagate drives do not support it | openSeaChest wiki |
| Shock Sensor Counter (191) and Free Fall Event Count (254) | count of events | Shocks above the device's rating; free-fall detections, which also trigger an emergency head retract | Whether a counted event damaged the drive | openSeaChest wiki |
| High Fly Writes (189) | count of events | Writes made with the head flying higher than optimal, which can leave a weaker magnetic signal; the page says vibration may affect fly height | A threshold at which data is lost | openSeaChest wiki |
| Pressure Measurement Limit (200, Seagate helium drives) | pass or fail; threshold 1 | Trips when helium pressure is too low, with the stated aim of replacing the drive before data loss | Whether the value drifts before it trips; Seagate's own numbers are not in the sources | openSeaChest wiki |
| Helium_Level (22, WDC/HGST) and Helium_Condition_Lower and Upper (23 and 24, Toshiba) | normalized value | The smartmontools maintainer lists these as helium-related attributes by vendor | What the raw values mean | smartmontools #380 |
Reading the numbers
The most useful thing the opened sources say about head crashes is that they are threshold events with a mechanism behind them, not a slow decay. In the Berkeley simulation the same 2.5-inch drive survived 300 G and failed at 400 G for a 0.5 ms positive shock, and survived 1,500 G but failed at 1,600 G for a 2.0 ms negative shock; the two cases failed in different ways, one by head slap after the air bearing lost force and the other by brute inertia. The pulse width mattered because of resonance: a 1,000 Hz shock near the disk's 1,043 Hz first mode produced contact after the pulse. That is a model of one drive, so it tells you what kind of event to look for, not how many drives it has killed.
Vibration can stop a drive without breaking it. The 1.8-inch test saw throughput fall to zero from 300 to 1,000 Hz below 15 g and come back when the shaking stopped, and the authors tied the low-frequency cases to a suspension flexure mode and the high-frequency cases to the disk's resonance. For anyone reading logs, that points to timeouts or resets that clear on their own and track the physical environment. The sources do not give how common this is in racks; the Seagate wiki only says vibration may affect fly height, and counts high-fly writes as one indicator.
Helium turns a gas-tightness problem into a vibration problem. In HGST's measurements flutter excitation was far smaller in helium than in air (for example 1.09 against 20.7 for mode (0,0)), yet flutter rose quickly as air replaced helium and was near its air level after about 80% air. If that behaviour carries over to a leaking drive, the loss of margin comes early, not late, but the paper tested controlled mixtures in one drive and does not measure leak rates. Backblaze's field notes are thin: one drive out of its helium fleet showed a SMART 22 of 94 to 99 and kept working, and its helium AFR of 1.06% against 1.61% for air-filled drives at similar drive days is described by the author as a prediction, with different models and years behind it. Seagate describes its helium counter as pass or fail, so a fall in it may come as a trip rather than a trend.
Spindle faults have the plainest counters and the least public data. The documented counters are retries in the last eight spin-ups and a count of mechanical start failures, and neither source set gives a failure rate for spindle or bearing faults. The honest summary is that a mechanical fault leaves traces in a small set of counters and in timeouts, but no opened source says how many drives fail each way or how many of them warn first. The earlier notes on this site cover SMART's wider limits and the field studies that do measure drive failure rates.
Related: SSD wear-out signatures, SATA and SAS link failures, what fails most often on HDDs, SSDs and links and the SMART failure-signal note.
Method
Everything here was read on 2026-10-11 from documents opened that day: the Berkeley Computer Mechanics Laboratory report 'Operational Shock Failure Mechanisms in Hard Disk Drives' by Li and Bogy (PDF); the Chua et al. APMRC 2006 conference paper on soft failure of a small form factor drive (PDF from Missouri S&T Scholars' Mine, dated 1 December 2006); the Eguchi paper 'Characteristics of Disk Flutter in Mixture Gas of Helium and Air' (JSME conference PDF, HGST Japan); two Backblaze blog posts by Andy Klein dated 16 April 2015 and 3 May 2018; the Seagate openSeaChest wiki page 'Drive Health and SMART'; and the smartmontools discussion #380 (August 2025 to February 2026). Numbers are copied from the text of those documents. Values that exist only inside figures or images are not used.
Limits
The head-disk numbers come from a simulation of one 2.5-inch drive model and the vibration numbers from one 1.8-inch drive on a shaker limited to about 15 g, so they show mechanisms and thresholds for those drives, not rates for any fleet. The Berkeley text does not print its publication year (its newest reference is dated June 2013). The helium paper uses one 3.5-inch drive with three 95 mm disks filled with controlled helium-air mixtures; it does not measure leak rates over a drive's life. Backblaze's helium and air-filled comparison covers its own 8, 10 and 12 TB drives, mixes models and ages, and the blog's table is an image that was not read; Backblaze itself notes that the two groups have different drive-day totals and calls its conclusion a prediction. The Backblaze SMART 22 observation is one drive in 2018; HGST gave Backblaze a normalized threshold of 25 in 2015 but no trip points or helium amount. The openSeaChest wiki is a Seagate-maintained description of counters, and the smartmontools discussion is a community thread whose attribute table is one maintainer's reply; neither measures how often a counter warns before failure, and attribute meanings are vendor-specific. No opened source gives the share of drive failures caused by head crashes, spindle or bearing faults, vibration or helium loss, so no ranking of these causes is made. The page covers public failure analysis only; nothing here concerns encryption, drive security features, or recovering anyone else's media.
Sources
- 01Li and Bogy: Operational Shock Failure Mechanisms in Hard Disk Drives, Computer Mechanics Laboratory, UC Berkeley (report 13009, PDF) · accessed 2026-10-11
- 02Chua, Yudhanto, Ong, Mou: Investigation of Soft Failure of Small Form Factor HDD under Forced Vibration, APMRC 2006 (Scholars' Mine copy, 1 December 2006) · accessed 2026-10-11
- 03Eguchi: Characteristics of Disk Flutter in Mixture Gas of Helium and Air, HGST Japan (JSME conference paper, 2017) · accessed 2026-10-11
- 04Klein: Do Helium-Filled Hard Drives Perform Better Than Air-Filled Drives?, Backblaze blog, 3 May 2018 · accessed 2026-10-11
- 05Klein: SMART 22 Is a Gas, Gas, Gas, Backblaze blog, 16 April 2015 · accessed 2026-10-11
- 06Drive Health and SMART, Seagate openSeaChest wiki (GitHub) · accessed 2026-10-11
- 07how to determine unknown (Helium level) attributes, smartmontools discussion #380 (GitHub) · accessed 2026-10-11