Seagate 7200.11 Shows 0GB? The BSY Fix That Actually Works

You've got a Seagate Barracuda 7200.11 that spins up, sounds normal, but shows 0GB in BIOS or Disk Management — and you're probably worried the data's gone.

Take a breath. It's almost certainly the infamous BSY-state firmware bug. Here's the fix.

The Real Fix: Unlock the BSY State Over Serial

You need a USB-to-TTL (3.3V) serial adapter — the CP2102 or PL2303HX work fine. Open the drive's PCB, locate the 4-pin header near the SATA data port. Pins are: TX, RX, GND, (VCC — skip this one). Connect adapter TX to drive RX, adapter RX to drive TX, and GND to GND. Do not connect VCC.

Open a serial terminal. On Windows, PuTTY; on Mac/Linux, screen or minicom. Settings are 38400 baud, 8N1, no flow control.

Power the drive (SATA power only, data cable disconnected). You'll see prompt output like:

F3 T>

If you don't see anything, hit Ctrl+Z. Now type:

F3 T> /2
F3 2> Z

This spins down the motor. Wait for Spin Down Complete. Now here's the critical bit most guides get wrong — you need to physically reseat the PCB while the drive is powered. Loosen the PCB screws, slide a piece of cardstock under the contact side to break the head connections, wait 10 seconds, pull the cardstock back out, and retighten.

Back in terminal:

F3 2> U
F3 2> /1
F3 1> N1
F3 1> /1
F3 1> Z

Then spin up:

F3 1> U
F3 1> /2
F3 2> Z

Wait for Spin Up Complete. Finally, clear the SMART and reinitialize:

F3 2> /1
F3 1> N1
F3 1> /2
F3 2> Z

Power cycle the drive. It should now show full capacity in BIOS. If it does, immediately clone it with ddrescue or HDDSuperClone — don't trust it as a working drive.

Why This Works

The 7200.11 firmware has a bug where a SMART or event-log write failure throws the drive into a busy state (BSY) and it never exits. The drive reports itself as ready-but-never-responds, so the SATA controller times out and reports 0GB — or doesn't see it at all.

The N1 command clears the SMART error log and event log. The Z commands spin the motor down and back up so firmware re-reads the translated capacity. Reseating the PCB forces the drive to re-detect the head stack without a full power loss (which would just re-trigger the bug from scratch).

I had a client last month — small dental office — with three of these drives from a 2008 RAID array. Two were recoverable this way. The third had a bad head, which is a different problem.

Affected Models

Not every 7200.11 is affected. The notorious ones:

Seagate quietly released firmware updates (SD1A, then SD2B) in 2009 to patch this. If your drive is still on SD15, update it — but only after you've recovered your data.

Less Common Variations

Drive Detected But Shows Wrong Capacity

Sometimes you'll see 32MB, 1.5GB, or a random number instead of 0. Same firmware bug, different failure point in the translation. The BSY unlock procedure above still works.

Drive Clicks Then Drops to 0GB

That's a head crash, not firmware. Don't run the BSY fix — you'll make it worse. Send it to a lab with a clean room.

7200.12 and 7200.14

These have a similar bug but different terminal commands. The 7200.12 uses m0,2,2,0,0,0,0,0,0,0 to clear SMART. Google "7200.12 BSY fix" specifically — don't mix procedures.

Prevention (Yeah, I Know, After the Fact)

• Update firmware now if you've got any 7200.11 still on SD15. Seagate's utility is gone from their site but mirrors exist — verify the hash before flashing.
• Don't buy 7200.11 drives off eBay. Half of them are pre-bricked. If the listing doesn't show a CrystalDiskInfo screenshot, walk away.
• Back up what you have. These drives are 15+ years old. Even with the firmware patched, they're past MTBF. Move data to anything else — a WD Red, an SSD, a cloud bucket, whatever.
• Keep the old drive around after cloning. If the clone fails, you might get one more BSY unlock out of the original. After that, it's usually done.

One more thing — if you're not comfortable pulling a PCB and running terminal commands, pay someone. The cardstock trick can short the preamp if you slip. A data recovery shop charges $300-800 for this. That's cheap compared to losing a decade of family photos.