You power on the PC, the Seagate Barracuda 7200.11 spins up like normal, but the BIOS never lists it. Windows Disk Management doesn't see it either. Nothing in Device Manager. The drive just sits there, powered and quiet, completely invisible. This is the BSY bug, and it hits 7200.11 drives made between roughly late 2008 and early 2009. Models like the ST3500320AS, ST1000340AS, ST31500341AS, and their 1TB siblings are the usual suspects. The trigger is almost always the same: the drive was powered off mid-write, or the system lost power while the drive was busy. The drive parks itself in a permanent Busy state and never answers the host.
What's actually going on inside the drive
Every Seagate drive has a small firmware area on the platters called the service area. Part of that area stores what Seagate calls the G-list and the SMART data. When the drive is mid-write and power cuts, the firmware tries to update its internal translation tables. If that update gets interrupted at the wrong moment, the drive flags itself as Busy and stays that way forever. It's not a mechanical failure. The heads are fine. The platters are fine. The firmware is just stuck waiting for a handshake that will never come. That's why the drive powers up and sounds healthy but never shows up in the BIOS. It's a logic bug, not a hardware failure.
The real fix: talk to the drive over TTL serial
You can't fix this with a Windows tool. You can't fix it with SeaTools. The drive never enumerates on the SATA bus, so the OS has nothing to talk to. The fix is to connect to the drive's diagnostic serial port directly, bypass the SATA controller, and clear the Busy flag with a firmware command. Once that's done, the drive appears normally and you can flash the fixed firmware.
What you'll need
- A USB-to-TTL serial adapter. The CP2102 and PL2303 chipsets work. Avoid the CH340 clones if you can, they're flaky at 38400 baud.
- Three female-to-female jumper wires.
- A Torx T6 driver to remove the drive's PCB.
- A spare SATA power connector, or a SATA-to-Molex adapter so you can power the drive outside the case.
- PuTTY or any terminal program that lets you set 38400 8N1 and toggle DTR.
- A separate PC that boots fine. You'll use it to run the terminal.
Step 1 — Pull the PCB and find the serial pads
- Power everything down. Unplug the drive.
- Flip the drive over and remove the six T6 screws holding the PCB. The board lifts off. Don't lose the thermal pad between the PCB and the head connector.
- With the PCB flipped over (component side up), look near the SATA data connector. You'll see four tiny round pads labeled TX, RX, GND, and one more. On most 7200.11 boards they're silkscreened. If yours isn't labeled, TX is usually the pad closest to the SATA connector, GND is the one next to it.
Step 2 — Wire the adapter
Cross TX and RX. The adapter's TX goes to the drive's RX. The adapter's RX goes to the drive's TX. GND goes to GND. Do not connect VCC. The drive has its own power. If you connect VCC to the wrong pad, you'll fry the board and turn a fixable drive into a paperweight.
Step 3 — Power the drive and open the terminal
- Connect SATA power to the drive. Leave the SATA data cable disconnected for now.
- Open PuTTY. Set the connection type to Serial, port to your adapter's COM port, speed to 38400, data bits 8, parity None, stop bits 1, flow control None.
- Before opening the connection, set the flow control to RTS/CTS and then back to None while the session is open. Some adapters need this DTR toggle to wake the drive's serial port. If you see nothing after power-on, this is almost always why.
Step 4 — Send the unlock commands
Power-cycle the drive with the terminal open. You'll see the drive print a startup banner within a few seconds. It looks like this:
F3 T>
You're in. Now type each line, pressing Enter after each one. Watch for the drive to echo back F3 T> after every command. If it doesn't echo, your wiring is wrong or the baud rate is off.
/2
Z
U
/1
N1
/2
Z
U
The /2 switches to level 2. Z spins the drive down. U spins it back up. /1 switches to level 1, and N1 clears the SMART and G-list. Then you go back to level 2 and repeat the spin cycle. The whole sequence takes about 30 seconds. When it finishes, the drive drops out of Busy state.
Step 5 — Reconnect SATA and verify
- Power down the drive. Leave the serial adapter attached.
- Connect the SATA data cable to your working PC.
- Boot into the BIOS. The drive should now show up at full capacity. If it shows up but with a wrong size (like 0GB or a few hundred MB), the G-list clear worked but the capacity translation needs one more pass. Repeat steps 4 with the drive connected to SATA.
Step 6 — Flash the fixed firmware immediately
Don't skip this. The BSY bug will come back the next time the drive loses power mid-write. Seagate released fixed firmware (SD1A for most models, SD2B for a few) that patches the bug. Download it from Seagate's support site, burn it to a bootable DOS USB stick, and flash the drive from DOS. Windows can't flash it, the tool needs raw disk access. After the flash, the drive is safe to use as a normal drive. Back up everything on it first, though. The BSY bug doesn't corrupt data by itself, but a drive that's been through this may have weak sectors.
If you're not comfortable pulling a PCB and wiring a serial adapter, this job isn't for you. Send it to a data recovery shop. The commands above are safe, but wiring the adapter wrong can kill the board permanently.
If it still isn't detected
- Wrong baud rate. Some early 7200.11 firmware uses 9600. Try both.
- No terminal output at all. Your adapter's TX line isn't reaching the drive. Check continuity with a multimeter. Also try swapping TX and RX, some boards are labeled from the drive's perspective, not yours.
- Drive still Busy after the commands. The service area is corrupted past the point where these commands help. You'll need a professional tool like PC-3000 to rewrite the translator from a donor drive.
- Drive clicks after the fix. That's a mechanical failure, not the BSY bug. Stop powering it and call a recovery lab.
- Drive shows up but won't mount. The partition table may be damaged from the original power loss. Run TestDisk before you do anything else. Don't run chkdsk, it'll make things worse.
The BSY bug is one of the few hard drive failures you can actually fix at home, and it's satisfying when it works. But the real fix is prevention: flash the SD1A firmware on any 7200.11 drive you still own, and stop trusting these drives with anything you can't afford to lose.