Your Hard Drive Is Not Detected.
It May Not Be Dead.

The sound your drive makes, or does not make, is the single most important clue. Before you download random software, listen closely.

A drive goes undetected for one of three reasons: the PCB has an electrical short (blown TVS diode or failed voltage regulator), the firmware in the service area is corrupted and the drive cannot complete its initialization handshake, or a mechanical fault (seized motor, failed heads) prevents the platters from spinning. Each failure requires a different repair path and falls into a different pricing tier.

PCB / Electrical Failure

A shorted TVS diode or failed voltage regulator on the circuit board prevents the drive from receiving stable power. The platters and heads are typically undamaged. Repair involves replacing the failed component or transferring the ROM chip to a donor board. This falls into the firmware pricing tier ($600 to $900) for hard drive recovery.

Firmware / Service Area Corruption

The drive spins but cannot complete initialization because its internal microcode is corrupted. It may report 0 GB capacity, display a wrong model name, or hang during the BIOS handshake. PC-3000 vendor-specific terminal access (Seagate F3, WD COM) is required to read and rebuild the corrupted firmware modules.

Mechanical Failure

Failed read/write heads or a seized spindle motor prevent the platters from spinning or the drive from reading its own Service Area. The drive may be silent, clicking, or beeping. Recovery requires opening the drive in a 0.02 micron ULPA-filtered clean bench and transplanting donor parts. This is the most expensive tier ($1,200 to $1,500 plus donor cost).

Logical / File System Corruption

The drive hardware is healthy but the partition table, MBR, or file system metadata is damaged. The OS sees the drive as RAW or Unallocated. This is recoverable without opening the drive and falls into the lowest pricing tier ($100 to $250 for standard recovery).

"Not detected" is not a single failure. It describes three distinct breakdowns depending on where the communication chain fails: at the BIOS/UEFI hardware layer, the operating system driver layer, or the file system metadata layer. The required recovery tool and cost change at each level. BIOS-invisible drives need PCB or firmware repair with PC-3000; OS-invisible drives may just need a driver or firmware patch; file-system-invisible drives often need only logical reconstruction.

BIOS/UEFI Not Detected

The motherboard firmware cannot see the drive on the SATA or NVMe bus. No entry appears in BIOS storage settings. This means the drive fails the initial identification handshake entirely. Common causes: dead PCB with a shorted TVS diode, seized spindle motor, or firmware corruption in the Service Area that prevents the drive from reporting its model string. No operating system or recovery software can address a device the BIOS cannot find. Hardware-level diagnosis with PC-3000 is required.

OS Not Detected (Visible in BIOS, Missing in Disk Management)

The BIOS sees the drive and reports its model and capacity, but Windows Disk Management or macOS Disk Utility does not list it. The drive responds to the SATA/NVMe handshake but stalls during initialization. For NVMe drives on 11th Gen+ Intel systems, Intel VMD can hide drives unless the RST driver is loaded. If VMD is not the cause, the firmware translator module or defect list is corrupted and requires firmware-level repair.

File System Not Detected (Shows as RAW, Unallocated, or Unknown)

Windows Disk Management shows the drive as Unknown, Unallocated, or RAW. The hardware works and firmware is intact; only the partition table or file system metadata (NTFS, APFS, exFAT) is damaged. This is the most favorable scenario for data recovery. Professional imaging followed by file system reconstruction can recover data without opening the drive. Do not format the drive or run chkdsk.

Here is what diagnosing a not-detected drive actually looks like.

Why a dead drive might just be a PCB issue.

Fixing a locked Seagate firmware.

If the drive becomes visible after swapping cables but Windows prompts you to format it or shows it as RAW, the file system has sustained logical damage. Stop using the drive and review the steps for corrupted hard drive recovery before taking any repair actions.

When a hard drive won't enumerate on the SATA bus, consumer diagnostics are useless because they depend on the operating system seeing the drive first. PC-3000 connects at the ATA register level and communicates with the drive's controller directly, bypassing BIOS and OS entirely.

Four-Branch Diagnostic Tree

Every non-detecting drive falls into one of four failure categories. PC-3000's first job is determining which branch applies, because each one requires different tools, donor parts, and pricing.

1. PCB / Electrical Failure. The drive is silent. No spin, no vibration. The TVS diodes, motor driver IC, or voltage regulator on the circuit board have shorted. The heads, platters, and firmware are intact. Fix: repair the shorted components or transplant the ROM chip to a donor PCB. Falls into the firmware/PCB pricing tier.
2. Firmware / Service Area Corruption. The drive spins normally but won't complete the ATA identification handshake. It may report 0 GB capacity, display a factory alias, or lock in a BSY state. The Service Area microcode on the platters is corrupted. Fix: PC-3000 vendor-specific terminal access (Seagate F3 terminal, WD COM port) to read, patch, and rewrite the corrupted firmware modules.
3. Seized Spindle Motor. The drive is silent because the fluid dynamic bearing motor is physically locked. Common after drops or extended storage in high-humidity environments where the bearing lubricant thickens. Fix: transplant the platters and head stack into a donor chassis on a 0.02 micron ULPA-filtered clean bench, then image with DeepSpar Disk Imager.
4. Catastrophic Head Crash. The heads failed, dragged across the platter surfaces, and deposited debris. The drive may click briefly and then spin down. The platters have visible scoring. Fix: platter cleaning, head swap from a matched donor, then careful imaging through damaged zones with managed read retries. This is the most expensive recovery path.

Hot-Swap Detection for Drives That Won't Enumerate

When a drive's firmware corruption is severe enough that even PC-3000 cannot get a response through the normal ATA interface, technicians use the hot-swap procedure to force the drive onto the bus. This works by borrowing a known-good donor drive's initialization, then physically switching to the patient drive while maintaining bus power.

1. Connect a compatible donor drive (matching model family, firmware revision, and head count) to the PC-3000 and power it on.
2. Wait for the donor to reach the DRDY (Drive Ready) state and complete a full Service Area backup.
3. Issue the ATA Standby Immediate command (E0h) through PC-3000. This stops the donor's spindle motor while the SATA bus remains powered and the ATA link stays active.
4. Without disconnecting the SATA or power cables, unscrew the PCB from the donor's HDA (Hard Drive Assembly) and mount it onto the patient's HDA.
5. Issue a Recalibration command through PC-3000. The patient drive spins up under the donor's PCB, and the technician can now access the patient's Service Area modules in controller RAM to begin firmware repair.

Seagate F3 Terminal Subcodes and Module 0x28 Translator Rebuild

When a Seagate F3 drive cannot complete the ATA handshake, a serial TTL connection from PC-3000 opens a terminal on the drive's debug port. The terminal output identifies which part of the boot sequence failed. BSY means the drive halted while parsing the Service Area microcode. 0 LBA means the drive enumerated but the translator returned zero user capacity, which points directly at Module 0x28 (Volume 3, File ID 0x28), the LBA-to-PBA map. A recurring LED:000000CC FAddr:... string in the terminal loop is a microcode panic for a bad translator or RAP (Read Adaptive Parameters) subfile error, and it blocks the terminal from accepting commands.

On ES.2 and comparable F3 families, the technician interrupts the LED loop with CTRL+Z during the brief window where F3 T>appears, then momentarily shorts the read-channel pins with tweezers to force an Input Command Error and release the terminal. From there the sequence is:/2 to drop to Level 2,Z to stop the spindle, reconnect the PCB to the head stack assembly, U to spin up, then drop to Level 0 and issue m0,2,2,,,,,22 (rebuild the G-List and format the user area partition without certifying defects) or m0,6,2,,,,,22 (regenerate the translator, which clears the format-corrupted flag and resolves SIM error 3005). This procedure is specific to older F3 drives; running it on a Rosewood or other SMR family wipes the Media Cache Management Table and is destructive, which is why a family-aware diagnosis precedes any terminal write.

Module 0x28 is rebuilt by parsing the P-List (factory defect list) and G-List (grown defect list) and recomputing the LBA-to-PBA offset across each Zone Bit Recording band. ZBR stores physically more sectors per track on the outer zones than the inner zones, so a single corrupted zone boundary shifts the mathematical offset for every sector past that point. Deleting a P-List entry misaligns the entire table at once and makes every file unreadable, which is why the P-List and G-List are both backed up before any write operation touches the Service Area. The canonical dump order for a 0-LBA Seagate is: ROM (adaptive data specific to this physical drive), P-List, NRG-List / pending defects, translator Module 0x28, and finally the firmware overlays loaded into controller RAM.

Western Digital uses a different file naming convention. On WD SMR drives the dynamic translator is Module 190 (the T2 Translator); Module 32 holds the relocation list. The repair sequence mirrors the Seagate workflow in principle: extract the corrupt module from the Service Area, sort the internal nodes by LBA, identify missing or overlapping nodes, rebuild the valid T2 data, and load it into RAM so the user area becomes addressable. On WD drives with Self-Encrypting Drive locks, the terminal is inaccessible until the drive is booted in Kernel Mode (by shorting the E47 pin on the PCB to ground), the DIR module is uploaded into RAM through PC-3000, and the SED flag is cleared in the Security Subsystem tab before the translator can be touched.

Toshiba MK-series drives fail into a different pattern. Bad sectors trigger a loop of G-List growth and SMART table updates that the drive never finishes, so it never reaches Ready. The recovery path is to clear the SMART records, erase the G-List, read the Control Program modules out of the ROM, and build a Virtual Translator inside PC-3000 so data is read through the utility rather than through the drive's own defect management logic.

Firmware-tier pricing for this work is $600–$900 ($600 for CMR, $900 for SMR). Rush is available: +$100 rush fee to move to the front of the queue. No diagnostic fee; no data, no fee.

Handoff to DeepSpar for PRML Read Channel Imaging

Once the translator rebuild completes and the drive reports the correct LBA count, the user area still has to come off without further damaging the heads. OS-level tools and desktop cloning software wait on the drive's internal retry timers, which on a marginal head means seconds of re-reading the same damaged track. That continuous contact generates heat at the head-platter interface and is how a recoverable drive becomes a platter-damage case.

DeepSpar Disk Imager bypasses host timeouts and talks to the drive's ATA registers directly. The workflow is multi-pass. The first pass reads only fast-responding sectors and skips anything that does not return within a short configured window, building a per-head bitmap of good reads. The second pass targets the skipped sectors, often reading them in reverse, because asymmetric head wear sometimes lets a sector read cleanly when approached from the opposite direction. Per-head isolation means data on the three healthy heads of a four-head drive is imaged first while a failing head is left for last, minimizing exposure.

Modern drives encode data through a Partial Response Maximum Likelihood (PRML) or Extended PRML read channel. The analog waveform from the head passes through a Continuous Time Analog Filter and an FIR digital equalizer, then a Viterbi detector resolves the most probable bit sequence. After a head swap from a matching donor, the electrical impedance of the new stack differs from the factory-tuned channel, and the Viterbi detector starts misclassifying data as noise. PC-3000 Vendor Specific Commands let the technician read raw analogue signals from the head and influence Viterbi decoding decisions so the donor head reads produce usable data.

For the physical connection, PC-3000 Portable III carries native PCIe with shared bandwidth up to 490 MB/s and handles SATA, PATA, USB host, and NVMe lines without a host PC. PC-3000 Express is the lab-based card with up to 150 MB/s per port across six ports (four SATA, two PATA) and no native NVMe. For a BIOS-invisible HDD case the Portable III runs the terminal and the initial diagnostic pass, then the stabilized drive is handed to DeepSpar for the bulk imaging phase.

Head-swap tier work is $1,200–$1,500 plus donor cost. 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. Rush is available: +$100 rush fee to move to the front of the queue. Our HDD work routes back to the hard drive data recovery page for full tier detail.

Why PCB Swaps Fail Without ROM Transfer

The ROM chip on a hard drive's PCB stores factory-calibrated data that is unique to the specific head stack and platters inside that individual drive. This is not generic firmware that can be downloaded.

Seagate F3 ROM: RAP, CAP, and SAP Adaptive Parameters

Seagate F3 drives store three sets of adaptive parameters in ROM. RAP (Read Adaptive Parameters) tunes the preamplifier sensitivity for each individual head. CAP (Controller Adaptive Parameters) calibrates the motor driver and servo controller timing. SAP (Servo Adaptive Parameters) stores the servo track positioning data unique to that platter's magnetic geometry. If any of these are lost or mismatched during a PCB swap, the heads cannot locate servo tracks and the drive clicks or reads at kilobytes per second.

WD Marvell ROM: DIR, Loader, and Kernel Mode Boot

Western Digital ROM chips contain the DIR (Directory) and Loader modules that bootstrap the drive's controller. When the Service Area on the platters is too corrupted to read, technicians boot the drive in Kernel Mode by shorting the E47 pin on the PCB to ground. This forces the controller to load only from ROM, bypassing the platters entirely. The drive reports a default factory ID string, and PC-3000 can then upload replacement firmware modules into controller RAM to repair the Service Area.

This is why the common eBay advice to buy a matching PCB and swap it does not work. The ROM chip must be desoldered from the original board and transplanted onto the replacement, or read via SPI programmer and written to the new board's ROM. Without the original ROM data, the drive will click, spin down, or report incorrect capacity. We perform this ROM transfer as part of every PCB failure recovery.

Certain hard drive families fail to detect far more often than others due to their firmware architecture. Each family requires a different PC-3000 workflow, and applying the wrong procedure to the wrong family will destroy data permanently.

When an SSD disappears from your BIOS or Disk Management, there are no sounds to diagnose; SSDs fail silently. However, if your SSD is scalding hot to the touch immediately upon booting, disconnect it. Do not attempt to recover data via software. You have a shorted PMIC. Otherwise, an invisible SSD is commonly a controller lockup, firmware corruption, or a motherboard configuration issue masking the drive. Try these steps:

1. 1
   Reseat the M.2 drive at a 30-degree angle and check the standoff.A loose connector accounts for many "dead" SSD reports. Never screw the drive directly flat to the motherboard without the proper standoff; bending the drive will crack the solder joints under the controller and permanently destroy it.
2. 2
   Check if the drive appears in BIOS but not in Windows.If you have an 11th Gen or newer Intel CPU, your drive may simply be hidden by Intel VMD. You must inject the Intel RST driver during Windows setup or disable VMD. Otherwise, visible in BIOS but absent in Windows points to a partition or firmware issue.
3. 3
   Try a different M.2 slot or a USB adapter.M.2 is a shape, not a protocol. A SATA M.2 drive in an NVMe-only slot will not be detected. Also, motherboards often share PCIe lanes, disabling M.2 slots if certain SATA ports are in use. A second slot rules out these conflicts.
4. 4
   If you ruled out configuration issues and it is still invisible, the controller is dead.If VMD is disabled, the slot is correct, and the drive is not shorted, a completely invisible drive has a dead controller. Software cannot help. Professional firmware-level tools like PC-3000 are required. See our SSD data recovery service.

SSD Controller Firmware Failures That Cause "Not Detected"

When an SSD disappears from BIOS, the root cause is almost always a controller firmware panic, not a cable or driver problem. Each controller family fails in a distinct way, and each requires a different PC-3000 recovery approach for SSD data recovery.

Silicon Motion SM2258 "BAD_CTX" (Crucial MX500, ADATA SU800)

The SM2258 controller enters a firmware panic called BAD_CTX (Bad Context) when it encounters unrecoverable Flash Translation Layer errors during boot. The drive reports 0 bytes in Disk Management but responds to SATA identification. Recovery requires PC-3000 SSD to inject a loader into the controller SRAM and rebuild the block mapping tables. Software cannot scan a 0-byte drive.

Samsung Phoenix Controller (970 EVO, 970 EVO Plus)

Samsung Phoenix controllers lock up when NAND wear exceeds internal thresholds that Samsung Magician does not report. The drive may cycle between detected and undetected states on each reboot, or disappear entirely after a power cycle. PC-3000 NVMe uses Vendor Specific Commands to access the controller diagnostic mode and image drive contents through managed read timeouts. This falls into the NVMe recovery firmware tier ($900 to $1,200).

Phison E16 PCIe Gen4 Initialization Failure (Corsair MP600, Sabrent Rocket 4.0)

The Phison E16 Gen4 controller can fail its PCIe link training sequence, causing the drive to be invisible to BIOS despite intact NAND. Unlike the SATA Phison controllers that fall back to SATAFIRM S11, Gen4 NVMe controllers provide no fallback identifier. PC-3000 NVMe diagnostic mode is required to access the E16 controller and image drive contents through managed read timeouts. The E16 uses hardware AES-256 encryption, so board repair is mandatory; raw NAND extraction yields only ciphertext.

See also: SSD Shows 0GB or Wrong Capacity

Many data recovery labs charge one high price for everything. They bill you the mechanical rate even if it is just a firmware fix. We charge based on what the problem actually is.

We provide a firm quote after free evaluation. If it turns out to be firmware instead of heads, you pay the firmware price, not a flat "worst-case" tier.