I needed to register here, to expain to others how I recovered a 1 TB Seagate 7200.10, NOT a 7200.11 drive from the dreaded BSY state.
Let me start by saying that I had the same issue with a 7200.11, and thanks to all the good folks over here, I got that going.
Then the little light bulb lit up in my head...See I have a 7800.10 1 TB drive that I had stupidly placed in a cheap external "made in china" USB enclosure, all plastic, totally entombed. I ran it non-stop, recording the Summer Olympics in HD LIVE from the Canadian commercial free HD live feed for enough events (MPEG-3) to fill the puppy to the rim. Being the middle of the night, and live, I never got to watch them!
Wel, sure as clockwork, The drive went into BSY state when I went to start watching them. Opened the case, and I could fry an egg on the drive, it was painfully hot, and this is certainly what brought this disk down
After reading all the posts and recovering a 7200.11, I dragged this brick out of the closet, with "nothing to loose".
I ripped a MAX-232 hand soldered circuit that I used on a Directv series 2 Tivo, and just removed the extra circuitry for that old use....Never throw out anything!
Hooked up the drive EXACTLY as the 7800.11, but on power up, it was obvious with the garbage on the terminal window, I had the wrong baud rate.
First GUESS, I was right!
Control:8,N,1 No flow.
I downloaded the terminal manual from hddguru and hit cntrl-z, and the prompt was slightly different, I proceeded to play.
BTW, I did not get cntrl-Z to work until I slid a piece of plastic between the PCB and the heads as shown on the other posts. did the same spin down command, removed the plastic, and did a spin up.
BTW, I NEVER even bothered with loosening the T-6 screws!
If you have any thin plastic container that was a peg hook type item, with the super thin plastic, in my case some headphones, it's thin enough to slide in there without even loosening a screw!
I then tried the normal guide for the 7200.11, but it did not like the commands, and gave me an invalid control word error.
I'm assuming that the "22" control word is only for the 7200.11, but it DID take the command:
G-List Erase (cert the reserved cyl):
Notice there is no F3 prefixing the command prompt......
I was half drunk and it took the command but I did not test the drive as it did not give me any confirmation, so I went ahead and placed a second command that it did not error on:
(Drive Configuration restored to defaults)
No response to either command, just an immediate new prompt. I figured I didn't fix anything, but probably bade the break turn to lead.
I removed the serial wires and hooked up the sata cable, and I was so SHOCKED when the bios posted the drive, I dropped my drink and broke the glass on the floor!
Went from a BSY state, with pc not able to detect drive, back to A-OK.
Not sure what command did it, but I played and got EXTREMELY lucky.
Hopefully, an expert will now explain what I did right, before others blindly attempt what I did.
I had nothing to loose, and was VERY LUCKY in my guessing, but I can now see the asshats from data recovery houses getting worried that more information is getting out there...
Edited by scanman1, 07 May 2009 - 08:26 AM.