Drive Spins but Isn't Detected: PCB, Heads or Firmware?

This failure confuses people precisely because the drive sounds fine. It powers up, hums along, no clicking, no grinding. And then: nothing in File Explorer, nothing in Disk Management, or a drive that shows up with the wrong name and a size of 0 bytes. Let's decode it.

Two minutes of safe checks first

Before assuming the worst, rule out everything that isn't the drive:

• Different cable, different port. SATA and USB cables fail more often than drives. For externals, plug directly into the computer, no hubs.
• Different computer. Kills off driver and OS explanations in one move.
• Check Disk Management (Windows) or Disk Utility (Mac), not just the file browser. A drive that appears there but won't mount is a different (and often less serious) problem than one that's absent everywhere.
• Listen closely once. Steady spin with no clicks? That's this article. Clicking? Stop and read about that instead; it changes the urgency.

If the drive is invisible on two computers with known-good cables, it's the drive. Here's what's happening inside.

The three suspects: PCB, heads, firmware

The circuit board (PCB)

The green or blue board on the drive's belly runs the show: motor control, power regulation, and the interface your computer talks to. A power surge, a bad USB bridge, or a failed component can leave the motor spinning while the data side stays mute. A telltale is a drive that spins but is never even acknowledged in the BIOS. One critical detail: modern PCBs hold unique calibration data for their specific drive in a small chip, so swapping a matching board off another drive (the classic forum advice) doesn't work anymore. The adaptives chip has to move to the donor board, which is microsoldering work.

The heads

Heads can be dead in a way that doesn't click. The drive spins, the heads fly, but the read element can't produce a usable signal, or one head of several has failed and the drive refuses to come ready. These drives often sound perfectly healthy. The fix is the same cleanroom head replacement as a clicking drive, just caught earlier, which is exactly where you want to catch it.

The firmware

Every hard drive runs a small operating system stored partly on its own platters in a reserved area. If those firmware modules corrupt, the drive spins up, reads its service area, chokes, and never announces itself. The famous version is the "translator" fault: the map that converts addresses your computer requests into physical platter locations gets damaged, and a perfectly healthy drive reports as 0 bytes, the wrong model name, or nothing at all. Certain Seagate families made this failure a legend, but every brand can do it. To the untrained eye the drive looks dead; to a lab with firmware-level tools, it's often the best news on this page.

How the lab tells them apart in minutes

The tool of record is a PC-3000, a hardware platform that speaks to drives at the factory level through their diagnostic terminal, below anything Windows can see. It reads the drive's boot chatter the way a mechanic reads an engine code, which is how a spins-but-undetected drive gets a confident diagnosis in the first bench session. That diagnosis is the whole game: head-swap jobs, firmware repairs, and PCB work have different risks, different prices, and different orders of operations, and guessing wrong wastes the drive's remaining life.

What not to do while you decide

• Don't initialize or format. If Disk Management offers to "initialize" the disk, decline. That writes new structures over the ones a lab would use to give everything back with names and folders intact.
• Don't run recovery software against a drive that isn't detected. There's literally nothing for it to scan; some tools will happily hammer the drive with retries anyway.
• Don't swap PCBs from a "matching" drive. Without moving the adaptives chip, the donor board can mis-drive the heads. This one turns easy jobs into hard ones constantly.
• Don't keep power-cycling. If a head is weak, every startup sweep wears it further. A drive in this state has a budget of good reads left; spend them on the recovery image, not on hopeful reboots.

If your drive is an external that vanished, the sibling symptom (detected sometimes, dropping out, or invisible only on some ports) has its own decision tree in our guide to external drives that stop showing up.

One more pattern worth naming: the drive that detects sometimes. It mounts one boot in five, or shows up for a minute and vanishes. People treat intermittent as "mostly fine." A lab treats it as a countdown, because whatever is marginal (a head, a solder joint, a firmware module) is on its way to permanent. If your data matters, the intermittent phase is a gift: image the drive completely the next time it comes up, or better, let a lab do it on hardware that won't hang when the drive stalls mid-copy.

What each diagnosis costs to recover

Ranges, because the diagnostic sets the real number: firmware repairs are often the least expensive of the three, PCB work with an adaptives transfer sits in the middle, and head replacements are the premium tier since they need donors and cleanroom time. Industry-wide you'll see figures from a few hundred dollars for firmware-level work to four figures for multi-fault mechanical cases. At MDrepairs the quote after diagnosis is flat, up front, and final, and if the answer is "this one isn't worth professional recovery," we'll say that on the first phone call rather than after your money's spent.

Frequently Asked Questions

Why does my hard drive spin but not show up in BIOS?

Spinning proves only that the motor and its power circuit work. Appearing in BIOS requires the drive's electronics and firmware to boot fully and announce the drive's identity. A failed PCB component, a corrupted firmware module, or heads that can't read the service area all leave the motor spinning and the BIOS blank. It takes factory-level diagnostic tools to tell which.

Can data be recovered from a drive that spins but isn't detected?

Usually, yes, and often completely. The platters (where your data physically lives) are typically untouched in these failures. Once the lab repairs or works around the failed subsystem (donor heads, repaired firmware, rebuilt electronics), the data reads off normally. These cases tend to have better outcomes than clicking drives because the heads haven't been beating against the platters.

My drive shows up as 0 bytes or the wrong size. What does that mean?

Classic firmware translator corruption. The drive booted enough to announce itself but its internal address map is damaged, so it reports nonsense capacity. Don't format, don't initialize, and don't run partition tools; the fix is regenerating the translator with firmware-level equipment, and done properly it's one of the cleaner recoveries there is.

Will replacing the circuit board fix my undetected drive?

Not by itself on any drive made in roughly the last two decades. The board carries a chip of calibration data unique to your exact drive; a donor board without that chip transplanted will not run the drive properly and can stress the heads. Board-level recovery means moving your adaptives to the donor, which is precision soldering, not a screwdriver swap.

How is this different from a drive that won't spin at all?

No spin at all points at power delivery, a shorted PCB, or a seized motor/stuck heads, a different diagnostic branch with its own fixes. Spinning-but-silent means power is fine and the failure is in electronics, heads, or firmware. Both are recoverable categories; they just start from different first moves at the bench.