Seagate 7200.11 BSY Bug Fix: Drive Not Detected

You power on the PC and the drive spins up. You can hear it, feel it, maybe even see the activity light flicker for a second. Then nothing. BIOS doesn't list it. Disk Management doesn't see it. Windows acts like the SATA port is empty. This is the classic Seagate Barracuda 7200.11 BSY bug, and it hits drives built between roughly late 2008 and early 2009, especially the 500GB, 750GB, 1TB, and 1.5TB models with firmware SD15, SD16, SD17, SD18, SD19, or AD14. It also shows up after a sudden power loss, a bad reboot, or a brownout while the drive was writing. The drive isn't dead. The firmware just parked it in a Busy state and forgot how to leave.

What actually happened inside the drive

The 7200.11 family has a small translation layer in firmware that maps logical block addresses to physical sectors. When the drive detects certain events (unexpected power loss, a SMART threshold trip, a bad sector read during a background scan), it sets a flag called BSY in its internal status register and stops responding to host commands. The idea was to protect your data during a fault. The bug is that under a specific set of conditions, the drive enters BSY and never clears it, even after a clean power cycle. It's a firmware dead-end.

From the host's side, the drive looks like it isn't there because it won't answer the ATA IDENTIFY DEVICE command. No IDENTIFY, no detection. No detection, no partition table, no data. The platters are fine. The heads are fine. The motor is fine. The controller is just stuck.

The good news: in most cases your data is still on the platters and fully recoverable. The bad news: this isn't a click-and-fix. You'll need a serial connection and a steady hand.

Before you start

Two things to know before you touch anything.

This fix talks to the drive over a TTL serial port. You'll need a USB-to-TTL adapter that runs at 3.3V logic, not 5V. A 5V adapter can fry the drive's serial pins and turn a recoverable drive into a paperweight.
Do not use this on a drive with valuable data unless you've already tried a professional recovery lab or you're comfortable sending it out if this fails. The unlock commands are safe on paper, but if you mistype a partition-related command you can wipe the translator.

The fix, step by step

You're going to bypass the drive's normal boot, force it into a diagnostic mode, and then issue the command that clears the BSY flag and rebuilds the translator.

Power off the PC completely and unplug the drive. You'll be working on the drive by itself, not inside the case.
Look at the bottom of the drive near the SATA and power connectors. You should see four small pads labeled TX, RX, GND, and either VCC or 3.3V (labels vary slightly by revision). Some boards have through-holes instead of pads. Either works.
Connect your USB-to-TTL adapter. Adapter TX goes to drive RX. Adapter RX goes to drive TX. Adapter GND goes to drive GND. Do not connect VCC or 3.3V. The drive gets power from its own SATA power cable.
Plug the drive's SATA power connector into a known-good power supply, but leave the SATA data cable disconnected. Keep the drive flat and stable.
Open a serial terminal (PuTTY, minicom, or screen will all work) at 38400 baud, 8 data bits, no parity, 1 stop bit, no flow control. If your adapter is 3.3V and wired correctly, you'll see nothing yet.
Now apply power to the drive. Within a second you should see the drive print a diagnostic banner to the terminal. It looks like a version string and some copyright text from Seagate. If you don't see anything, your TX/RX lines are swapped. Power off, swap them, try again.
As soon as the banner appears, press Ctrl+Z. This drops you into the drive's diagnostic prompt, usually shown as a F3 T> or F3 1> prompt. You have about two seconds to do this before the drive finishes booting and the port goes quiet. If you miss it, power cycle and try again.
At the prompt, type:
```
/2
Z
```
The /2 switches to the second command level. Z spins down the drive's motor. You should see a confirmation like Spin Down Complete.
Type:
```
U
```
This clears the BSY flag in the status register. You should see Spin Up Complete or a similar acknowledgment. If the drive doesn't spin back up, wait a few seconds and check the terminal again.
Now rebuild the translator. Type:
```
/1
N1
```
This tells the drive to regenerate the G-list translation table from the on-disk copy. It can take anywhere from 30 seconds to a few minutes depending on capacity. Don't interrupt it. When it's done you'll see a completion message.
Power off the drive. Disconnect the serial adapter. Put the drive back in the PC and connect both SATA power and data.
Boot the machine. The drive should now appear in BIOS and in Disk Management. If it does, immediately copy your data off. Do not trust the drive long-term.

The permanent fix: firmware update

After you've recovered your data, the drive still has the buggy firmware. Seagate released updated firmware for the affected models years ago and it's still downloadable from Seagate's support site. Flash it before you keep using the drive for anything that matters. The firmware update rewrites the BSY handling logic so this doesn't happen again.

If you're going to keep the drive, flash it. If you're not, retire it. Reusing a BSY-affected drive without the firmware patch is asking for a repeat.

If it still doesn't work

A few things to check before you give up.

No serial output at all. Your adapter is probably 5V, or the pins are reversed, or the drive's serial interface is damaged. Try another adapter.
You see the banner but can't catch the prompt. The window is tight. Some techs hold Ctrl+Z down as they apply power. That works too.
The drive spins up but still won't detect after the fix. The translator rebuild may have failed. Try the sequence again from step 6.
The drive clicks. Stop. That's a mechanical failure, not the BSY bug. Professional recovery is your only real option.
BIOS sees it but Windows doesn't. This isn't the BSY bug anymore. Check Disk Management. The partition table may have been corrupted during the original fault.

One more note. If the drive shows up after the fix but with the wrong capacity, the translator rebuild didn't finish. Power cycle the drive and run the N1 step again from the diagnostic prompt.