Seagate 7200.11 0GB Fix: BSY Firmware Bug

Quick answer: The 0 GB capacity on a Seagate Barracuda 7200.11 (or Maxtor DiamondMax 22) is almost always the BSY firmware bug — update to firmware SD1A via the official Seagate ISO or, if the drive is stuck, use the RS-232/TTL unlock method.

I've seen this exact failure at least thirty times since 2009. The drive spins up, clicks once, then the BIOS reports 0.0 GB or just doesn't see it at all. Windows Disk Management shows a drive letter with no size. No SMART data. No nothing. The drive isn't dead — it's trapped in what Seagate calls the BSY state, a firmware loop where the drive's controller never finishes its boot sequence. The platters and heads are fine. The data is fine. The firmware just decided to take a permanent coffee break.

The affected models are the 7200.11 family, specifically these part numbers:

ST3500320AS (500 GB)
ST3640323AS (640 GB)
ST3750330AS (750 GB)
ST31000340AS (1 TB)
ST31500341AS (1.5 TB)
Maxtor DiamondMax 22 equivalents

Seagate acknowledged this in early 2009 and released firmware SD1A to patch the bug. If your drive still mounts but reports zero capacity, you can flash it. If it's completely stuck, you'll need to unlock it first.

Before you do anything: stop writing to the drive

If the drive shows 0 GB, don't run chkdsk. Don't initialize it in Disk Management. Don't format it. Every one of those actions risks overwriting the partition table or the MBR, and if the drive is just stuck in BSY, the data is still perfectly recoverable. Once you write to it, you're in data recovery territory and paying someone $1,500.

Method 1: Flash the official SD1A firmware

This works if the drive still enumerates in BIOS or Disk Management, even with 0 GB. You'll need a Windows machine with a working SATA port, a blank CD or a USB stick, and a low tolerance for poorly-written vendor tools.

Grab the ISO. Seagate pulled the direct downloads years ago, but the SD1A ISO is mirrored on archive.org and on most data recovery forums. Search "Seagate SD1A firmware ISO" and verify the SHA-1 against Seagate's original release notes. Sketches are common — check.
Boot from it. Burn the ISO to a CD-R or write it to a USB with Rufus in DD mode. Boot the target machine from it. Don't try to run this from Windows.
Disconnect every other drive. Seriously. The updater will happily flash the wrong drive if you give it the chance. Unplug all SATA data cables except the 7200.11.
Run the updater. It'll detect the drive and offer SD1A. Confirm. It takes about 30 seconds. When it says success, power off completely (not a reboot — actually pull power for 10 seconds).
Reconnect and check BIOS. You should now see the correct capacity. Windows should mount the volume. Run CrystalDiskInfo to confirm SMART is readable again.

If the drive doesn't show up in the updater, or the updater reports "no drive found," you're in the BSY-locked scenario. Move to method 2.

Method 2: Unlock the BSY state via TTL

This is the fix that actually works when the drive is completely unresponsive. It involves talking to the drive's diagnostic port over serial. If that sentence made you nervous, stop here and call a data recovery shop — DriveSavers or Ontrack will charge you but they won't brick the drive.

What you need:

A USB-to-TTL adapter (CP2102 or FTDI FT232RL — the cheap CH340 clones are hit-or-miss)
Three jumper wires
HyperTerminal, PuTTY, or minicom
Some patience

On the 7200.11 PCB, you'll find four contact pads labeled TX, RX, GND, and (on some revs) VCC. Don't connect VCC — the drive has its own power. Connect TX on the adapter to RX on the drive, RX to TX, GND to GND. This is a null-modem setup.

Open your terminal at 38400 8N1, no flow control. Power on the drive with the terminal already connected. You should see garbage text or nothing. Press Ctrl+Z — this drops the drive into its diagnostic console.

Type:

F3 T>/1

You'll get back a number. Now the magic command — this is the one that clears the BSY loop:

F3 1>N1

Wait ten seconds. Then:

F3 1>/1

Now power-cycle the drive. It should spin up, report its correct model and capacity in BIOS, and your data will be accessible. Immediately back up everything you care about — the drive is still vulnerable until you flash SD1A, and you should do that right after the backup.

If that fails

There are a few other things this could be. Don't assume BSY just because you read one forum post:

PCB failure. If the drive doesn't spin up at all — no vibration, no clicking, dead silence — you've got a dead PCB, not a BSY bug. Replacing the PCB requires moving the ROM chip from the old board to the new one. Not a beginner job.
Head crash. If you hear rhythmic clicking or grinding, stop. Power it down. That's mechanical, and every additional spin-up grinds more of the platter away. Ship it to a cleanroom.
Wrong firmware already flashed. If someone previously tried to flash a Maxtor firmware onto a Seagate or vice versa, the drive may need a low-level reflash via the vendor's factory tool. That's beyond DIY.

Prevention, going forward

If you've got working 7200.11 drives still in service — and people do, they're workhorses — flash them to SD1A now, before they lock up. Seagate fixed this in later 7200.12 and 7200.14 revisions, so any drive from 2010 onward is fine. Also, stop trusting single consumer drives with anything you can't re-download. Two-drive mirror or nothing. And run SMART monitoring — most of these drives logged reallocated sector warnings for weeks before they got stuck.

The 7200.11 was a good drive with garbage firmware. If yours is showing 0 GB right now, the odds are very good you can fix it today. Don't panic, don't chkdsk it, and don't let anyone tell you it's dead until you've tried the SD1A flash and the TTL unlock.