Hello everyone

I'm getting ready to try the BSY fix on my Maxtor 7200.12 drive, and since the fix is intended for Seagate drives and I couldn't find any tryouts on Maxtor's versions, and since my drive is the rare 7200.12, and since I found different procedures with different steps. I'm thinking that I might get stuck in the middle of the procedure, the orders I issued resulted in different outcome than what it supposed to give. I was wondering what should I do at this point to take a break and gather more info without breaking the drive beyond repair?.. should I cut the power off? Should I disconnect terminal connection? Is there a "point of no return" during this procedure?

Any piece of info is much appreciated



Seagate 7200.12 BSY thread:
viewtopic.php?t=18907&start=20#p143165&mobile=on&mobile=on

If it's a 7200.12 drive then it is a Seagate. Just resold by Maxtor under their name. What's the full model number of the drive, you'll get much more insightful answers if you actually post enough information for us to help.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

My drive is a Maxtor DiamondMax23 STM31000528AS, Maxtor's version of Barracuda 7200.12 ST31000528AS. I've researched it and there are some mere differences between the two, so I just wanna cover my bases in case I encounter an unexpected outcome.

What makes you think your drive suffers from the BSY bug?

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

The drive never had any problem or physical damage before or after the issue. Something went wrong during firmware update which left the drive in this state. I did not diagnose the drive with mhdd. I think its a BSY state because the symptoms matches. and I thought that the steps of the BSY fix is partly diagnosing. I mean that I thought that the diagnosing could be done through terminal commands.

I'm afraid the Internet fix for the BSY bug is not applicable to 7200.12.

What you can do, is power on the drive having terminal connection and post terminal response here. This way we can determine what's wrong with the drive.
Depending on what went wrong during the update, this drive may be easily fixed or be completely FUBAR.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Also, Maxtor/Seagate BSY bug needs a completely different approach in some cases.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Okay, let me get this straight. So I power on the drive with terminal connection without isolating PCB contacts or shorting read channels or anything?.. Then I still need an answer to my original question. Is it safe to quit during terminal connection? Is there a safe way to quit or just unplugging and powering down everything is fine?

Yes on both your questions.
Assuming the config is right, you can quit terminal connection any time. Just remove the cables or shut down your computer.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Well.. The issue I'm having right now is that I can't establish a terminal connection with the drive. I was trying to get a post from the terminal (without actually tying the fix. not yet.). I'm using a USB-TTL PL2303HX adapter, the drive is connected to the adapter with GND,TX,RX wires, and using an external PSU to power up the drive. My setup has passed the loop test. but when connected to the drive I get no response at all.. like I don't even get the F3 T> prompt when pressing Ctrl+Z. Checked all the connection and they are OK. switched RX and TX wires, no change.

As I understood, 7200.11 PCB should be isolated before the fix, while in 7200.12 drives read channels should be shortened. I haven't done any of these thing as I'm only trying to get a terminal report. Could this be why I can't get any terminal response? Where do I go from here?

Bump...

Hello,

7200.11 and 7200.12 have the same terminal configuration. Try to connect the terminal for 7200.12 (Maxtor) like 7200.11 (there is description on forum) and put in the terminal listing here.

Maybe you swapped RX and TX pins. First, dont connect PL2303 TX wire, but try to test both pins on HDD with RX wire. Once you know which is definitely RX and which TX you can also connect PL2303 TX pin

No..You can do it. i salvage 3 st31000524as disk.

you don^t need isolate. and after the power connection you must press ctrl z 2 second later. not later or before..