Helium Drive Data Recovery

Full In-House Helium Recovery

Why does in-house helium capability matter?

Some labs advertise helium drive recovery but open the drive on a standard bench without helium refill capability. In atmospheric air the heads experience the wrong aerodynamic lift for their design, flight becomes unstable, and head-platter contact can strip the magnetic coating from the platters. A failed recovery attempt on a helium drive does not just fail; it can destroy the chance of a second attempt.

Other labs that lack the equipment send the drive to a third party, adding cost, transit time, and a middleman between you and the engineer doing the work. You lose visibility into the process and cannot communicate directly with the technician handling your drive, which is worth weighing when evaluating local data recovery options versus a specialized mail-in lab.

We keep the entire process under one roof. From the initial PC-3000 diagnosis through the head swap, helium refill, and final imaging, your drive stays at our Austin lab. You speak directly with the technician working on your case.

What are the failure modes of helium drives?

Helium Leak and Permeation

Helium atoms are small enough to permeate through micro-imperfections in the welded seal over years of operation. As helium escapes, the gas density inside the chamber rises toward air and the firmware works harder to hold the heads on track. On WD and HGST platforms the loss shows up as SMART attribute 22 (Helium Level) declining from its factory baseline of 100; Toshiba MG platforms report helium condition under attributes 23 and 24 instead. What recovery requires depends on what the loss has already done inside the chamber: a drive whose heads and platters survived may need inspection, reseal, and refill, while a drive that progressed to head-platter contact needs a head swap with fresh helium refill, and possibly platter cleaning.

Preamp Failure in High-Platter Drives

Helium drives with 8–10 platters can have up to 20 individual read/write heads. Each head connects to a preamp IC mounted on the head stack assembly. Thermal stress from continuous operation in enterprise or NAS enclosures degrades preamp components over time. When a preamp channel fails, the associated head stops reading. If multiple channels fail, the drive reports as inaccessible. PC-3000 head maps identify which heads are functional, and we image from working heads first to capture maximum data before swapping to donor heads for the failed channels.

Firmware Corruption

HGST and WD helium platforms are susceptible to translator table corruption from sudden power loss. The translator maps logical block addresses to physical platter locations; if this table is damaged, the drive may report 0 bytes capacity or fail to initialize entirely. Seagate Exos models can experience Service Area module corruption that prevents the drive from completing its startup sequence. Both failure types are repairable through PC-3000 terminal access without breaking the hermetic seal.

Motor Bearing Seizure

Spindle motor failure in a helium drive is the hardest recovery scenario. With 8–10 tightly packed platters, a motor swap requires removing the entire platter stack, transferring it to a donor chassis, refilling with helium, and imaging. If the seized motor caused the platters to shift rotationally, alignment errors compound across every platter surface. The platter damage tier ($4,000–$5,000) covers this scenario, plus helium cost and donor.

Why does helium recovery cost more than standard HDD recovery?

Three factors push helium recovery pricing above standard hard drive data recovery rates: helium gas cost, donor drive cost, and the complexity of working with high-platter-count head stack assemblies.

Helium cost: $400-$800 additional for head swap and surface damage tiers. This covers the helium refill required after opening the sealed chamber. The donor drive is also consumed in the process and can't be reused. A head swap on a 10-platter drive with 20 heads takes longer and carries more risk than swapping 4 heads on a 2-platter consumer drive.

Firmware-level recoveries ($900–$1,200) don't require helium or a donor, because the hermetic seal stays intact. If your helium drive is inaccessible but not clicking, the repair cost is closer to standard HDD pricing. We diagnose the failure type for free and quote the exact tier before any work begins. A +$100 rush fee to move to the front of the queue is available if you need priority service.

Technical Methodologies for Helium Drive Recovery

The sub-sections below describe the bench procedures used on helium drives at our Austin lab. Each procedure is the same regardless of drive vendor; the parameters differ by family.

How pure does the refill helium need to be?

Less pure than most marketing copy claims, ours included until this page was corrected in August 2026. No drive manufacturer or tool vendor publishes a minimum helium purity for refills. What the manufacturers' own patents describe is a wide tolerance band: Seagate's sealed-drive patent (US 7,362,541) targets a fill of greater than 99 percent helium, and Western Digital's (US 8,514,514) describes sealed cavities that can hold helium at 0.3 to 1.0 atmosphere alongside up to 0.7 atmosphere of air. The difference between laboratory-grade helium at 99.999 percent and welding-grade helium at 99.995 percent shifts the average molar mass of the fill by about 0.025 percent, which is nothing to an air bearing. We use high-purity cylinder helium because dry, clean gas is cheap insurance against moisture in the chamber, not because a fraction of a percent of purity separates a working drive from a head crash.

What actually matters is displacing the air. The goal of the refill is a chamber that is overwhelmingly helium rather than a helium-air mix, because the sliders were designed to fly in gas at roughly one-seventh the density of air. A half-purged chamber leaves the heads flying in something denser than their design gas, which is the same condition a leaking drive fails in. Helium cost: $400-$800 additional for head swap and surface damage tiers. This covers the helium refill required after opening the sealed chamber.

Helium Donor Matching: Preamp Revision and HSA Family

Our standard donor-matching process for helium drives extends beyond model number and firmware. The head stack assembly carries a preamp IC whose channel-to-head wiring must match the target drive's preamp revision; an Ultrastar HC520 preamp wired for a 14TB platter map will not address heads correctly when transplanted into an HC530 chassis even though both share the Ultrastar form factor. Micro-jog values, the per-head factory calibration for the physical offset between each head's read and write elements, are tied to the original head stack, so donor heads read off-track until the drive's adaptive parameters are addressed during PC-3000 initialization.

• ✓Seagate Exos X-series: match site code, head map (HM), and preamp revision against the target's Service Area identifier. Same-family donors (Exos X10 to X10) preserve micro-jog tolerances; cross-family substitutions require firmware-level re-mapping. See the Seagate Exos 10TB failure profile for the most common Exos failure modes we see.
• ✓WD Ultrastar DC HC5xx: match DCM field, country code, microcode revision, and HSA generation. HC520, HC530, HC550, and HC560 are not interchangeable at the HSA level even when capacities overlap.
• ✓Toshiba MG08: match HDD code, head count, and firmware revision. MG08 helium platforms utilize TDMR heads and tighter track pitches than the previous MG07 helium line; donor stacks from MG07 chassis cannot be transplanted into MG08 drives. The Toshiba MG08 failure profile documents the HSA and firmware-side failure patterns.

Cross-Generation Donor Matching: Exos, Ultrastar, and MG Helium Families

Helium platform generations are not backward-compatible at the head stack level even inside the same product line. Areal density, track pitch, and TDMR head geometry change between generations, which means the donor must come from the same generation as the patient drive. The matrix below summarizes the boundaries we work within when sourcing donors at our Austin lab.

Capacity alone is not a matching criterion. A 16TB Exos X16 and a 16TB Exos X18 share a marketing label but use different head stacks, different servo formats, and different adaptive parameters in the Service Area. The HSA from one will not address heads correctly when wired into the other. PC-3000 reads the patient's firmware family, DCM, and microcode revision through the diagnostic terminal before any donor is opened for transplant.

Why Air-Filled Donor Heads Fail in Helium Chassis

A common failed-recovery pattern we see from outside labs is an attempt to substitute an air-filled HSA into a helium chassis when a same-family helium donor cannot be sourced. The slider air-bearing surface (ABS) on an air-filled head is etched for the aerodynamic lift profile of atmospheric air at 28.96 g/mol average density. Helium sits at roughly 4 g/mol; lift force at the slider drops by about a factor of seven. An air-filled head transplanted into a helium chassis flies too low, contacts the platter surface within seconds of spinup, and strips the magnetic substrate.

The reverse case is also unrecoverable: a helium-tuned HSA placed into an air-filled chassis flies too high to read the servo bursts, the read channel reports continuous loss-of-sync, and the drive enters a busy state without imaging a single sector. The slider geometry is fixed at the wafer-fab step and cannot be re-calibrated in the field. Helium and air HSAs are physically interchangeable mechanically but aerodynamically incompatible. Donor matching for helium drives starts from a sealed helium platform, never from a same-capacity air-filled donor.

Helium Loss Diagnosis: SMART Attribute 22 and Hermetic Seal Integrity

SMART attribute 22 (Helium Level) is a WD and HGST attribute. It reports the state of the helium fill as a normalized value that starts at the factory baseline of 100 and decreases as the firmware detects the internal environment moving out of specification; the listed pre-fail threshold is 25, and the raw field mirrors the normalized value rather than exposing a separate measurement. The band between 100 and 25 is wide by design: Backblaze published fleet data showing a drive reading in the 94 to 99 range that kept performing normally. Toshiba MG helium drives report helium condition under attributes 23 and 24 with a threshold of 75, and Seagate Exos drives do not report attribute 22 at all; Seagate's helium telemetry surfaces as an internal pressure reading through the F3 diagnostic terminal, and Seagate documents that when internal pressure drops too low the heads cannot maintain proper fly height.

On intake we read the helium telemetry the family actually provides, through PC-3000 vendor utilities where the host operating system cannot enumerate the drive. A helium attribute trending down from baseline on a drive that still reads is a drive we image immediately, before the environment degrades further. A drive at or below its threshold gets a bench decision, not an automatic verdict: the attribute reports the firmware's view of the gas environment, and the recovery plan depends on whether the heads and platters have already been damaged by unstable flight.

Helium Refill and Reseal Verification

Helium head swaps are performed on our 0.02 micron ULPA-filtered clean bench. After the failed head stack assembly is replaced, the chamber is closed, sealed, and refilled with helium before the platters are spun for imaging. The refill step matters because the head slider is calibrated for helium density, not atmospheric air.

Once the chamber holds its helium fill, the drive is connected to PC-3000 Express or DeepSpar Disk Imager. We image by head map, skip damaged zones on the first pass, and return to weak sectors only after the stable heads have been copied. The donor heads, helium, and reseal materials are all consumables on this tier; pricing for head swap is $3,000–$4,500. Helium cost: $400-$800 additional for head swap and surface damage tiers. This covers the helium refill required after opening the sealed chamber. Helium donor drives must be an exact match. Typical donor cost: $200–$600 depending on model and availability, plus helium refill cost ($400–$800) required after opening the sealed chamber. A +$100 rush fee to move to the front of the queue is available when the customer needs priority on the queue.

PC-3000 Portable III Service Area Workflow on Helium Firmware

Helium firmware repair runs on PC-3000 Portable III or PC-3000 Express with the vendor module loaded for the target family. The Service Area on a sealed helium drive is read through the PCB and the diagnostic terminal; the chamber stays sealed for any firmware-tier recovery. Pricing for this tier is $900–$1,200 because no donor and no helium refill are required.

1. LDR microcode load. When the resident firmware fails to boot the drive into Ready state, PC-3000 issues a vendor-specific loader command (LDR on Seagate, equivalent kernel-mode entry on WD/HGST and Toshiba) that pushes a known-good microcode image into RAM and brings the drive up in safe mode. From safe mode the SA modules can be read, edited, and rewritten.
2. Translator rebuild on Exos. Sudden power loss commonly corrupts the Exos translator and defect tables. PC-3000 reads the surviving SA modules (SysFile 28 static translator, SysFile 35 G-list, SysFile 1B P-list), regenerates the translator against the current defect map, and writes the corrected modules back to the Service Area. The drive then reports its actual capacity through the standard ATA interface.
3. WD/HGST module handling. WD and HGST helium firmware is module-based; PC-3000 reads each module, validates CRC, and replaces damaged modules from a same-family ROM image. Common repair targets include the translator, the SMART log, the defect lists, and the adaptive parameter modules. The hermetic seal stays intact for this entire workflow.
4. ROM extraction and transplant. When the on-PCB ROM has lost its adaptive parameters, the chip is desoldered, read on a programmer, edited to inject the original drive's adaptives, and reflashed. The PCB is then reinstalled on the original sealed chamber.

SMART Differential Diagnosis: Helium Loss Event vs Head and Preamp Failure Event

A drive's SMART telemetry narrows the diagnosis before the chassis is ever opened, but only if it is read for what each vendor actually reports. SMART attribute semantics were never standardized in ATA/ACS, so the helium-specific attributes differ per family, while the generic media-damage counters mean the same thing they mean on any drive. The table below is what the three helium families actually expose.

The honest differential is coarser than a table of confident per-attribute signatures. A slow leak shows the helium attribute declining from baseline while the drive still reads; Backblaze's fleet data includes a drive reporting between 94 and 99 that kept performing normally, which is why a declining value is a reason to image immediately rather than a death certificate. An acute head or preamp failure usually presents the opposite way: the drive clicks, fails to reach ready, and often cannot serve SMART at all. A head that cannot lock onto the servo tracks does not keep flying while the firmware logs degraded telemetry; the drive retries and parks, audibly.

Just as important is what SMART cannot tell you. No vendor exposes per-head telemetry through SMART attributes: an attribute is one value for the whole drive, so nothing in the attribute table ties damage or wear to a specific head. Head-level conclusions come from bench work with vendor utilities, not from the SMART table.

Multi-Pass Imaging Strategy for High-Density Helium Media

Helium drives run at tighter track pitch and higher areal density than air-filled drives in the same form factor. The read channel uses Partial Response Maximum Likelihood (PRML) or Extended PRML detection. When original heads degrade or a donor head is installed, the internal channel calibration no longer matches the new head signature, and the read channel reports elevated bit error rates during imaging.

On PC-3000 and DeepSpar Disk Imager, we work the levers the tools actually expose: head-selective imaging so a weak head never blocks a strong one, seek-from-far to settle the servo before each read, per-sector read timeouts, soft-resets between passes, and off-track read attempts above and below the nominal track center. A bad sector that returns CRC errors on the first pass is skipped and re-queued for a later pass under different conditions rather than hammered in place.

The same multi-pass strategy is applied to every drive imaged through our lab. On standard hard drive data recovery cases the BER margins are wider, so fewer passes are required. On helium platforms with high areal density, staged per-head imaging with off-track retries is what separates a successful image from a stalled one.

Post-Head-Swap Helium Refill and PC-3000 Initialization Procedure

The sections above cover donor matching, helium purity, and SMART-based loss diagnosis. The procedure below documents what happens at our Austin lab between the moment the donor head stack assembly is seated and the moment the drive is handed off to the DeepSpar Disk Imager for sector capture. Skipping steps in this chain on a high-capacity Seagate Exos, WD Ultrastar HC5xx, or Toshiba MG08/MG09 patient risks a spinup that looks stable and then degrades during imaging.

Step 1: Head Stack Transplant on the 0.02 Micron ULPA Clean Bench

The hermetic seal on a Seagate Exos, WD Ultrastar HC5xx, or Toshiba MG08 chassis is a continuous laser weld around the perimeter of the top cover. We score the cover inboard of the factory weld and lift it free. CNC milling of the seam is rejected as a procedure even though it is faster; milling generates aluminum and stainless-steel particulates that bypass the recirculation filter inside the head-disk assembly and settle onto the platter surfaces. Once those particles are inside the chamber, every subsequent read is at risk of head-particle contact, and the case stops being a standard hard drive data recovery job and becomes a platter cleaning job.

The donor head stack is seated using the matching criteria documented in the donor-matching tables above (model, site code, firmware family, preamp revision, microcode generation). During this window the internal chamber is fully exposed to atmospheric air. The slider air-bearing surface on the donor head was etched at the wafer-fab step for the aerodynamic lift profile of helium at roughly 4 g/mol average molecular weight. Air sits at roughly 28.96 g/mol and produces far more lift on that slider than the design gas; if the spindle is energized in this state the heads fly outside their calibrated window, flight is unstable, and head-platter contact becomes a real risk. Every step that follows exists to prevent that spinup condition.

Step 2: Hermetic Reseal Pathway on Welded-Lid Drives

The original laser weld cannot be reproduced inside a recovery lab. Reproducing it would require focusing weld energy onto the chassis after the platter stack is reinstalled, which introduces thermal stress on the head stack assembly and generates metallic particulates that fall directly onto the platters. No recovery lab attempts this on a patient drive. The pathway we use is mechanical bonding of the cover with a high-viscosity lab-grade adhesive applied continuously along the cover-to-chassis interface. The adhesive is selected for low outgassing because outgassing compounds condense onto the platter surfaces during the multi-day imaging window and degrade subsequent reads.

The perimeter bond cures before the helium fill in Step 3 begins, so the chamber forms a closed volume around a controlled fill path. The reseal does not need to match the lifetime specification of the original laser weld; it needs to hold the helium atmosphere stable through the imaging window, which on a 9-platter helium drive with eighteen heads can run several days to several weeks of staged per-head imaging. The head-swap pricing tier of $3,000–$4,500 reflects the consumable cost of the adhesive, helium, donor stack, and the bench time required to execute the purge and reseal under ULPA-filtered conditions. Helium cost: $400-$800 additional for head swap and surface damage tiers. This covers the helium refill required after opening the sealed chamber.

Step 3: Atmospheric Purge and Helium Refill

The goal of the fill is a chamber that is overwhelmingly helium rather than a helium-air mix. The sliders were designed to fly in gas at roughly one-seventh the density of air, and a chamber left partly full of air puts them in the same condition a leaking drive fails in. So the air is purged with flowing helium rather than topped up: we run a continuous helium flow through the sealed chamber's fill path until the residual air has been displaced, then close the fill path. The purity question is covered in the refill section above; the fill quality that actually matters is complete displacement of the air, and the proof of the fill is the drive's behavior at spin-up, watched through the helium telemetry the family exposes and the stability of the first reads.

Step 4: PC-3000 Initialization Before DeepSpar Imaging Begins

A resealed and refilled drive is not connected to a host operating system directly. The donor heads are not factory-calibrated for the patient platters, so direct ATA enumeration either fails outright or, worse, triggers internal defect remapping against the wrong calibration set. The drive is brought up on PC-3000 Portable III or PC-3000 Express, and the four-stage initialization below is executed before control is handed to DeepSpar Disk Imager.

1. SA module read test. The drive is energized through the PC-3000 intelligent power supply and held in safe mode. PC-3000 reads the Service Area modules located on the reserved negative-cylinder tracks. A successful read confirms that the donor heads are electrically compatible with the patient's preamp and controller circuit. A failed read indicates a preamp-channel or head-map mismatch that must be corrected before any further step is attempted.
2. Per-head stability evaluation. PC-3000 commands the drive to read sample sectors across the LBA range for each physical head position. Error rate is logged per head. Any head that produces unrecoverable reads at a rate inconsistent with the rest of the stack is flagged in a RAM head map and disabled for the initial imaging pass; data behind that head is captured later under different read conditions rather than blocked from imaging entirely.
3. Adaptive parameter transfer per family. The donor's factory adaptives are wrong for the patient platters; the patient's original adaptives must be preserved before read-channel lock is achievable. WD Ultrastar HC5xx drives are built on the HGST Command Code Based (CCB) architecture inherited from the HGST acquisition, not the Marvell-platform module taxonomy used on WD consumer drives; ACE Lab supports these families through the PC-3000 HGST CCB utility, whose documented functions include direct Service Area access, translator management, and building the logical head map used for imaging. The patient's Service Area and ROM contents are secured before the donor stack is seated. On Seagate Exos drives, adaptives and translator data live in Service Area system files reached through the F3 serial terminal. On Toshiba MG07, MG08, and MG09 drives, Service Area access runs through the PC-3000 Toshiba module, and an unstable translator is worked around at the imaging layer rather than trusted during capture.
4. Read channel calibration and contamination check. Once adaptives are in place, a short read pass is run and judged by outcome: do reads complete, and at what error rate per head. A partially purged chamber shows up here as unstable reads and climbing pending-sector counts; if that pattern appears, the imaging window is aborted before donor heads are wasted and the drive returns to Step 3. Only when reads are stable across the active head map does control hand off to the DeepSpar Disk Imager, which then runs the staged per-head, off-track-retry strategy documented in the multi-pass imaging section above for the actual hard drive data recovery capture.

PCB-Level Triage on Exos and Ultrastar Helium Drives

A helium Exos or Ultrastar that arrives dead with zero current draw is rarely a head failure. The dominant failure on enterprise helium PCBs is an electronic fuse latched open on the 5V or 12V rail, usually traceable to a backplane power event or a modular ATX cable mismatch upstream. The triage below covers component-level diagnosis on Seagate Exos and WD Ultrastar boards before any chassis opening. The hermetic seal stays intact throughout this PCB-only workflow.

E-Fuse Failure Signature on Enterprise Helium PCBs

Current enterprise PCBs route incoming power through electronic fuses on the 5V and 12V rails rather than relying on transient voltage suppression diodes alone. An e-fuse is designed to sacrifice itself when an upstream event pushes voltage or current outside its envelope, protecting the downstream motor controller and preamplifier interface.

The diagnostic signature is deterministic. With the PCB on the bench and supply voltage applied to the input pad, we read voltage on both sides of the e-fuse. Supply present at the input, 0V at the output, and no short to ground anywhere on the downstream network means the fuse has latched open and the rail is dead at the fuse itself. A multimeter continuity check, a FLIR thermal scan during a brief power-up to confirm there is no hot spot indicating a downstream short, and a resistance check from the output to ground complete the bench triage. When the signature matches, the fuse is the single point of failure and the rest of the PCB and the head-disk assembly inside the sealed chamber are intact.

E-Fuse Bypass vs ROM Adaptive Transplant

The terms e-fuse bypass and ROM adaptive transplant describe two different repairs for two different states of PCB degradation. Competitor write-ups routinely conflate them. We treat them as separate procedures with separate decision criteria.

E-fuse bypass

Board-level microsoldering on the original patient PCB. When the bench triage confirms Vin present and Vout dead at the e-fuse, with the downstream network clean, the damaged fuse IC is removed using hot-air rework (Atten 862 or equivalent) and the Vin and Vout pads are bridged with a short solder jumper or fine micro-wire under a Hakko FM-2032 on an FM-203 base station. The original PCB, ROM, and motor controller all stay on the drive. No donor board is needed. The fuse is removed from the protection path; the operator now assumes responsibility for clean power input upstream during imaging.

ROM adaptive transplant

A separate procedure for a different failure state. When the overvoltage event walked past the e-fuse and destroyed the main controller or motor driver downstream, the patient PCB cannot be restored at the component level. The repair pathway requires an identical donor PCB; the 8-pin SPI flash ROM is desoldered from the patient board and soldered onto the donor board so the donor controller boots against the patient drive's unique adaptive parameters. A direct donor PCB swap without the ROM transplant fails for the reasons described in the next subsection.

Choosing between the two procedures comes down to where the energy went. If the e-fuse caught the event and latched open with the downstream network intact, the bypass is the correct repair and the donor PCB stays on the shelf. If the e-fuse was overwhelmed or shorted through and the downstream silicon was damaged, the ROM transplant is the only path, because a generic donor PCB cannot drive the patient's head stack at calibrated fly height.

Why a Direct PCB Swap Fails on Enterprise Helium Drives

Modern enterprise helium drives operate at an active magnetic spacing of 1 to 2 nanometers above the platter surface during reads and writes, with Thermal Fly-height Control trimming the slider clearance from a baseline aerodynamic fly height of a few nanometers. To hold that gap across temperature, altitude, and per-head variation, every drive is calibrated at the factory and the calibration data is written to the SPI flash ROM on its PCB. The ROM is keyed to the individual head stack assembly inside the sealed chamber. A donor PCB ships from the donor drive with the donor drive's calibration, not the patient's. The calibration that matters for a clean spin-up and a successful image includes:

• Micro-jog offsets. The physical separation between the read element and the write element on a single head varies head to head because of photolithography tolerances at the wafer-fab step. Micro-jog offsets are the per-head corrections the servo applies so the read element sits over the track centerline when the servo locks to a write-aligned reference. On WD ROYL-architecture drives, Module 47 stores the microjog and servo adaptives alongside the Module 0A head map; both reside in the PCB ROM and are redundantly shadowed on the platters. The HGST-lineage helium families and the Seagate and Toshiba enterprise platforms each keep their equivalent per-head calibration data in their own ROM and Service Area structures; the constant across all of them is that the data describes one specific head stack and travels with the drive, not with the board model.
• Thermal Fly-height Control voltage curves.Each slider carries an embedded heater. The voltage applied to that heater thermally protrudes the read and write elements toward the platter and trims the fly height in flight. The voltage-to-protrusion curve is unique to each head and is stored on the patient's ROM. A donor PCB running its own TFC curves against the patient's heads either flies the elements too high (no read) or pushes them into the platter (head crash and surface damage).
• Preamplifier gain and channel tuning.Read-channel adaptives such as MR bias current and FIR equalizer coefficients are calibrated per head at the factory. The donor PCB's tuning was written for the donor heads. Mismatched tuning leaves the read channel unable to lock even when the heads physically fly correctly.

Powering a helium Exos or Ultrastar with an unmodified donor PCB drives the patient head stack with the donor's adaptives. The servo cannot lock, the drive clicks or spins down, and on a worst-case TFC mismatch the heads contact the platter surface and score tracks the customer was paying us to recover. A direct PCB swap is not a faster shortcut; it is the procedure that converts a firmware-tier repair into a head-swap and platter- cleaning case. The ROM transplant exists because the alternative writes off the data.

SMART Telemetry Differential Diagnosis Across Helium Drive Families

A single SMART attribute ID does not mean the same thing on a Seagate Exos as it does on a Western Digital Ultrastar HC5xx or a Toshiba MG08 and MG09. SMART attribute semantics were never standardized: from ATA/ATAPI-4 onward the attribute bytes of the SMART data structure are vendor specific, and the same ID can carry unrelated meanings on different vendors. ID 240 is Head Flying Hours on Seagate and most hard drives, and Transfer Error Rate on some Fujitsu models. The clearest helium-family example is flying-hours accounting, which an earlier version of this page got wrong; the table below, corrected in August 2026 against real drive telemetry dumps, is what the three families actually report.

What does the flying-hours counter actually measure?

Head Flying Hours is firmware time accounting: the accumulated time the head stack has spent loaded over the platters, counted once for the whole drive. It is not aerodynamic telemetry. Helium loss does not make the counter noisy, and a failed head stack does not freeze position telemetry, because the counter never contained position data in the first place. When a drive stops reaching ready, all of its time counters simply stop advancing, flying hours and power-on hours alike.

The leak-versus-head-failure question is answered by the helium attributes and the drive's behavior, not by flying hours. A leaking drive can keep operating while its helium attribute declines, which is exactly the window in which to image it. A drive whose heads cannot lock onto the servo tracks clicks, parks, and spins down; it does not keep running while logging degraded numbers. The Seagate Exos 10TB failure and Toshiba MG08 failure pages cover the family-specific intake patterns we see on those platforms.

Where do we read these values on the bench?

Host-side smartctl reads the attribute table, and smartctl -x adds the Device Statistics log. On Seagate Exos, the F3 serial diagnostic terminal reports the internal environmental readings directly; published terminal dumps show a pressure line reading in millibars alongside temperature and humidity. Seagate does not publish the design fill pressure for these platforms, so we treat a single pressure reading as data to record against the drive's history, not a verdict on the seal by itself. On WD Ultrastar HC5xx and on Toshiba MG08 and MG09, Service Area work runs through the PC-3000 HGST CCB utility and the PC-3000 Toshiba module respectively; ACE Lab's documented CCB feature set covers direct Service Area access, translator management, and building the logical head map used for imaging. Telemetry interpretation is the first read after intake; it determines which procedure runs on the bench.

What does a lid breach mean on a 10-platter helium drive?

Current-generation helium enterprise drives in the WD Ultrastar HC570 and HC580 families, the Seagate Exos X22 and X24 families, and the Toshiba MG10 family carry 10 platters in the same 3.5″ chassis. When a customer drive arrives with a damaged hermetic seal or a lid that has already been pried by another lab, the chamber no longer holds its design atmosphere. The drive is operating in a helium-air mix it was never engineered to fly heads in, and every additional minute of spindle time in that state is spent against the data.

Why an Opened Helium Drive Is a One-Time Extraction

Each head flies on a thin gas bearing between the slider and the platter surface. The sliders in these drives were designed for helium at approximately 0.166 kilograms per cubic metre at room temperature, roughly one-seventh the density of air. In a breached chamber the gas is denser than the design point, the lift on every slider is wrong for its etched air-bearing surface, and head flight is unstable. That is why we treat a breached helium drive the way the recovery field treats it: as a one-time extraction. The drive gets a single, deliberately planned imaging attempt, or the platter stack is transferred to a donor chassis that can be sealed and refilled before any sustained imaging is attempted. What nobody can honestly offer is repeated casual spin-ups of a 10-platter drive in open air.

How a Breached Drive Is Imaged

The imaging session runs by head map, the same way as every other multi-head recovery in this article: PC-3000 establishes Service Area access and builds the logical head map, DeepSpar Disk Imager runs per-head sessions against it, and heads that return errors are deferred rather than hammered while the stable heads are captured. On a breached drive the priority is simple: capture as much as possible in as little spindle time as possible, and stop the moment read behavior degrades rather than pushing a failing head into the platter surface.

PC-3000 HGST Module Versus PC-3000 WD Module on HC5xx and HC6xx

The Ultrastar HC5xx and HC6xx families inherit firmware lineage from the HGST helium platform. After the merger the families continued under the WD brand, but the firmware architecture stayed on the HGST side rather than the Marvell-controller side used on WD consumer drives. ACE Lab designates this architecture CCB (Command Code Based) and supports it through the Utility for Hitachi HGST CCB, available since PC-3000 software 7.7.19, with native support on PC-3000 Express and a hardware adapter offered for the Portable units. The documented feature set is Service Area read and write, translator management, background process control, building the logical head map used for Data Extractor imaging, and SMART parameter reset. Selecting the HGST CCB utility rather than the consumer WD module is the correct choice for every drive in this lineage, including HC560, HC570, and HC580 examples that carry WD labels on the chassis.

Can the helium attribute read low on a healthy drive?

It can read oddly, and the published record says so. The WD and HGST helium attribute is computed from a self-heated thermistor's view of the chamber gas, not from a direct pressure gauge, and Backblaze's fleet write-up describes a drive whose attribute 22 wandered between 94 and 99 while the drive kept working, with Backblaze unable to say whether the value meant anything or the sensor was simply erratic. That is the honest state of public knowledge, and it is why we treat helium telemetry as one input to the bench decision rather than a verdict. The deciding evidence is always the drive's behavior under controlled reads: stable imaging means the environment is workable, degrading reads mean the session stops, whatever the attribute says.

Helium Drive Recovery FAQ