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

Your computer does not see your drive. That does not mean your data is gone. A shorted circuit board, corrupted firmware, or a mechanical fault each have a different fix. We diagnose the actual cause. No generic "bad drive" excuses. No evaluation fees.

Written by

Louis Rossmann

Founder & Chief Technician

Updated March 2026

12 min read

No Data, No Fee

Guarantee

2.49M+

Subscribers

4.9

1,837+ Google Reviews

Since 2008

Established

Repairs on Video

Full Transparency

As Featured In

BBC News CBC News ABC Australia Wall Street Journal Business Insider Vice Fast Company 404 Media

First Question: Does Your Drive Spin?

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

Drive is Silent

Symptom: No vibration, no noise, light might be off.

Likely cause: Electrical short on the PCB, or seized motor.

PCB repair has good success rates if the platters are undamaged.

Spins Up, Sounds Normal

Symptom: You feel vibration, hear it spin, but no data.

Likely cause: Firmware corruption or slow-responding bug.

This is often the cheapest fix. Do not run chkdsk.

Clicking, Beeping, or Grinding

Symptom: Repetitive mechanical noises.

Likely cause: Head failure or stuck heads.

Clicking drive →Beeping drive →

What Causes a Drive to Not Be Detected

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).

PCB and Electrical Failure

Hard drives have a circuit board that manages power and data. If you use the wrong power adapter or experience a surge, the TVS diodes can blow to protect the drive. The board is dead but the platters are fine.

The myth: Just swap the board with a matching one from eBay.

The reality: Modern drives store unique calibration data in a ROM chip on the PCB. If you swap the board without transferring your original ROM chip, the drive will not spin or will click. We repair the original board or perform the ROM transfer properly.

Firmware and Service Area Corruption

Hard drives have their own operating system called firmware, stored on the platters in the Service Area. When this gets corrupted, the drive spins but reports 0GB or refuses to talk to your computer.

Translator bug: Common in WD and Seagate drives. The module that maps data sectors becomes corrupt.
Seagate Rosewood locks: Modern thin Seagate drives often lock themselves in a busy state due to background process errors.
SSD firmware failure: SSDs using Phison controllers can drop into a fallback mode called SATAFIRM S11 or SATABURN, reporting 0 bytes or 8 MB capacity and an incorrect model name. The controller is alive but has lost its Flash Translation Layer (FTL) map.
WD Palmer SMR slow responding: Modern WD portable drives (Palmer family, e.g. WD10SPZX) use Shingled Magnetic Recording with a secondary translation layer. When background garbage collection fails, Module 02 (configuration), Module 32 (relocation list), and the T2 Translator (Module 190) in the Service Area corrupt. The drive clones at kilobytes per second or locks the host system entirely. PC-3000 is required to lock Service Area writing and rebuild the T2 Translator for hard drive data recovery.

In some cases, SMART warnings appear before the drive stops being detected entirely. Once the firmware is too corrupted to initialize, SMART data is no longer accessible through normal tools.

We use PC-3000 hardware to access the Service Area, patch the corrupted modules, and rebuild the translator. This is not something consumer software can do.

Mechanical Failure in Disguise

Sometimes "not detected" is actually a mechanical issue.

Weak heads: The drive spins but the heads are too weak to read the Service Area during boot. It gives up and stays silent.
Seized motor: The drive is silent because the motor is physically stuck. Common in dropped drives.

Mechanical recovery requires opening the drive in our clean bench and using donor parts. It costs more than firmware or PCB repair. We tell you which one it is before we bill you.

Encrypted External Drives

Many external drives, especially WD My Passport and My Book models, encrypt your data through the USB bridge chip in the enclosure.

If you remove the drive from the enclosure and connect it directly via SATA, you will see encrypted gibberish, not your files.

If the USB bridge failed but the drive is fine, we can often repair or replace the bridge. If the drive itself failed, we recover through the original encryption path.

What Does "Not Detected" Mean at BIOS, OS, and File System Levels?

"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.

Not Detected at BIOS/UEFI Level

The motherboard firmware does not see the drive on the SATA or NVMe bus. The drive does not appear in BIOS storage settings. This means the drive is not responding to the initial handshake at all. Common causes: dead PCB (shorted TVS diode or failed voltage regulator), seized spindle motor preventing spin-up, or a completely failed controller chip on an SSD. Software recovery tools are useless at this stage because no operating system can address a device that the BIOS itself cannot find. Recovery requires hardware-level diagnosis with PC-3000 connected directly to the drive's interface. A less obvious variant: the drive spins up normally but still fails BIOS detection. This points to Service Area firmware corruption or a translator module bug (common in WD and Seagate Rosewood families) rather than an electrical or mechanical fault. The drive's microcode cannot complete the identification handshake, so the BIOS treats it as absent. PC-3000 vendor-specific terminal access (Seagate F3, WD COM) is required to read and rebuild the corrupted firmware modules.

Not Detected at OS Level (Visible in BIOS, Missing in Windows/macOS)

The BIOS sees the drive, but Windows Disk Management or macOS Disk Utility does not list it. This typically indicates firmware corruption: the drive responds to the SATA/NVMe handshake but cannot serve its service area data correctly. The drive may report 0 bytes, display a factory alias name, or hang during initialization. For NVMe drives on 11th Gen+ Intel systems, Intel Volume Management Device (VMD) can hide drives from the OS unless the RST driver is loaded. Check BIOS first. If VMD is not the cause, the firmware's translator module or defect list is corrupted and needs firmware-level repair.

Not Detected at File System Level (Visible in Disk Management, No Drive Letter)

Windows Disk Management shows the drive as "Unknown", "Unallocated", or "RAW". The hardware is functional and the firmware is intact, but the partition table or file system metadata is damaged. This is the most favorable scenario for recovery. The drive's physical components work; only the logical structure is broken. Professional imaging with PC-3000 followed by file system reconstruction can recover data without opening the drive. Do not format the drive or run chkdsk; both actions overwrite the metadata structures needed for recovery.

Watch Real Diagnosis and Recovery

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.

What You Can Safely Try

Safe to Try First

Change the cable.USB 3.0 Micro-B cables fail constantly. Try a new one.
Try a different computer.Rule out a bad USB port or driver issue.
Check Disk Management.Press Win+X, select Disk Management. If you see the drive as Unallocated or Unknown, it is alive but needs help. Do NOT format it.
Listen to the drive.Does it spin? Click? Beep? That tells you which page to read.

Do Not Do This

Do not open the drive.Breaking the seal allows dust in. One particle is enough to cause a head crash.
Do not shuck encrypted drives.WD My Passport drives encrypt data via the USB bridge. If you bypass it, you get encrypted gibberish.
Do not run chkdsk /f.If the drive is failing, this command will stress it and can scramble file fragments. Why chkdsk is dangerous.
Do not swap the PCB without ROM transfer.The calibration data is unique to your drive. Wrong board equals dead drive.

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.

NVMe or SATA SSD Not Detected?

If your NVMe SSD is completely invisible to the BIOS, do not assume the controller is dead yet. It may be hidden by Intel VMD or disabled by PCIe lane sharing. Reseat the drive and try a different M.2 slot first. If it remains invisible after ruling out motherboard configurations, the controller has failed or shorted. Software cannot detect or recover data from a dead controller; PC-3000 firmware-level tools are required.

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
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
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
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
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.

What This Costs

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.

ProblemRossmannDriveSavers / Big LabsFirmware / Not Detected / 0GB Capacity$600-$900$1,000-$2,500Logical Recovery$100-$500$500-$1,500Head Swap / Mechanical$1,200-$1,500$2,000-$7,000+Evaluation FeeNoneFree eval, but fees common elsewhere

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.

Frequently Asked Questions

Can data be recovered from a hard drive that is not detected?

Yes. In many cases, a drive that is not detected has a firmware issue or a failed PCB component, not a catastrophic mechanical failure. If the platters are intact, data recovery is possible using specialized tools like PC-3000.

Why is my hard drive not showing up?

For hard drives, common causes include electrical failure such as a shorted TVS diode, firmware corruption, or mechanical issues like a seized motor. For modern NVMe SSDs, the drive may simply be hidden by Intel VMD or motherboard PCIe lane sharing. It is rarely just a basic OS driver issue, unless you are missing the Intel RST driver for VMD.

Can I fix it by swapping the PCB from another drive?

No. Modern drives store unique calibration data in a ROM chip on the PCB. If you swap the board without transferring the ROM chip, the drive will not work. This requires soldering equipment and knowledge of which chip to move. A botched swap can make recovery harder.

Do I pay if you cannot recover my data?

No. No Data, No Charge means exactly that. If we cannot get your files, you pay nothing for the attempt. You only pay return shipping if you want the original drive back.

Should I run data recovery software first?

Only if the drive is detected and reads quickly. If the drive is not showing up, or if it is slow and unresponsive, running software forces it to work harder. This can turn a recoverable drive into an unrecoverable one. When in doubt, do not run anything.

Why are DriveSavers and other big labs more expensive?

They spend a lot on marketing. DriveSavers is an Apple partner, Ontrack does enterprise contracts; they have big sales teams and advertising budgets. That overhead gets passed to you. We use the same class of equipment; PC-3000, laminar flow benches, donor inventory. The work is identical. The price is not.

Can data recovery software work if the BIOS does not detect the drive?

No. Recovery software operates through the operating system, which requires BIOS-level hardware detection first. If the BIOS cannot see the drive on the SATA or NVMe bus, no software can access the platters. The drive needs hardware-level diagnosis with PC-3000, which connects directly to the drive's interface and bypasses the host system entirely.

What is the difference between BIOS not detected and OS not detected?

BIOS not detected means the motherboard firmware cannot see the drive at all, pointing to a dead PCB, seized motor, or severe firmware corruption. OS not detected means the BIOS sees the drive but Windows or macOS does not list it, which typically indicates a corrupted translator module or, on newer Intel systems, Intel VMD hiding the NVMe drive. BIOS-invisible drives need hardware repair; OS-invisible drives may only need a firmware patch.

Why does my Crucial MX500 or ADATA SU800 SSD show 0 bytes in Disk Management?

These drives use Silicon Motion SM2258 controllers, which enter a firmware panic called BAD_CTX when they hit unrecoverable Flash Translation Layer errors. The drive appears on the SATA bus but reports 0-byte capacity. No recovery software can scan a 0-byte device. PC-3000 SSD is required to inject a loader into the controller SRAM and rebuild the FTL mapping tables to access the NAND data.

Why does my WD My Passport freeze my computer when I plug it in?

Modern WD Passport drives (Palmer and SpyGlass families) use Shingled Magnetic Recording with a secondary translation layer. When background garbage collection fails, Module 02 (configuration), Module 32 (relocation list), and the T2 Translator in the Service Area corrupt. The drive physically works but overwhelms the Windows storage driver with infinite wait states. PC-3000 is required to lock Service Area writing and rebuild the T2 Translator to recover data.

Data Recovery Standards & Verification

Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.

Validated Clean Zone

Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.

Transparent History

Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.

Media Coverage

Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.

Aligned Incentives

Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.

Technical Oversight

Louis Rossmann

Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.

We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.

See our clean bench validation data and particle test video