Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Unlocking terminal of Seagate ES.2 in BSY/LED:000000CC state

- - - - -

  • Please log in to reply
37 replies to this topic

#1
johnmar

johnmar
  • Member
  • 2 posts
Here's what I discovered after many attempts in the last few nights.

Terminal of my 2 ES.2 drives was locked (drives were in BSY state) - every 3-4 seconds I received from their terminal message LED: 000000CC....

Standard solution which is widely known for 7200.11 series (ST******AS) doesn't work for locked ES.2 series (ST******NS) !!!

But i've found a way to unlock terminal of my ES.2 drives :) what allows then to repair hd in a standard way (solution from Yura/Okzo).

1. Disk has to be complete (PCB+rest together), NO isolation between the PCB and the rest
2. In the terminal you will see every few seconds message LED: 000000CC ...
3. between these messages you can unlock the terminal by pushing CTRL+Z. It will show a line: "F3 T>" and it will be Unlocked for about 1 second
4. During that 1 second when you see "F3 T>" message but before you receive next "LED:000000CC..." you must short two points shown in the following image (they are known as "read-channel").
Posted Image

You must hold them short about 20-30 or little more seconds.
If you won't see next "LED:000000CC..." and disk will issue few unpleasant sounds then after some time you'll see in the terminal message "Input Command Eror".
Now the disk's terminal is unlocked!
Still holding those 2 pins short issue command /2 and then Z (they're cAsE sEnSiTiVe!).
When disk's engine will stop you will see message "Spin Down Complete" and now you can release the short between 2 pins.

Next do repair with standard instruction (as for 7200.11) - all below is cAsE sEnSiTiVe!:
F3 2>U
Spin Up Complete
F3 T3>/1
F3 1>N1
F3 1>/
F3 T>m0,2,2,0,0,0,0,22
and wait until you'll get message
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000
.....
User Partition Format Successful - Elapsed Time 0 mins 05 secs

Good example (also extended) gave aviko, in post number 529 in topic # 128807
It is at: http://www.msfn.org/...mp;#entry832876

I am a complete amateur (not DR professional), and of course, give no warranty for the described procedure.
It worked for me and my two ES.2 drives are alive now.
Of course, this procedure or the incorrect use might as well burn your disks and data.
I don't assume responsibility for such cases - everything you do at your own risk.

This procedure of ES.2' terminal unlocking is my own discovery, and I'd like to share this knowledge with other poor owners of bricked (in BSY state) ES.2 disks.


How to remove advertisement from MSFN

#2
Laz

Laz

    Newbie

  • Member
  • 29 posts
wonderful ! I have stuff backed up on older es2's and wondered what to do if they come down with 7200.11 "sickness". Thank you

#3
dreamsat

dreamsat
  • Member
  • 1 posts
johnmar
First of all thank you very much!!! I reanimate my HDD and backup data from it!!!
Thank you! Thank you!

But I've been confused with picture. On my TFT I've only seen red square. And first day I tried short point in it. :blushing:
I make picture for those who experience same problemm.

Posted Image

Posted Image

And I can't input /2 command when short that point.
When I enter in terminal after CTRL+Z I short and hold point 8-10sec while head to stop working.
Then release it. And after that input the command.

Thank you again!!!

Edited by dreamsat, 21 March 2009 - 02:35 AM.


#4
NEO_AMiGA

NEO_AMiGA

    Newbie

  • Member
  • 12 posts
Hello

What do you get more then: LED: 000000CC ?
Something like: http://www.irry.com/...hotoseagate.jpg ?

What sounds did your drives make? This one is like spinning up, spinning down, spinning up, spinning down, spinning up etc etc

EDIT: This page says to short on some other places. :blink:
http://babelfish.yah...TrUrl=Translate

EDIT 2: That's the same picture I just noticed. But on the one here in the forum the original red square is retouched and moved...? :unsure:

Edited by NEO_AMiGA, 03 April 2009 - 09:15 AM.


#5
NEO_AMiGA

NEO_AMiGA

    Newbie

  • Member
  • 12 posts
...mkay... It was the newly marked red locations that i had to shorten. Took me several attempts. Tried the other location to. But like after the ten attempt the drive spun down. The terminal settled and I could issue those commands. Loads of odd letters and s*** in the terminal while typing though. Dunno why. But the disk is back and alive. Time to do some back up. Thanks a lot for the guide here!

I did not have to keep the circuit shortened after the drive had spinned down. Because it's a spin down that is the result of the shortening. It takes a while and you will hear some pretty disturbing sounds. Once the drive is down i released my paperclip and issued the commands in the terminal.

Thanks again. beers on me. :thumbup

#6
codsw2

codsw2
  • Member
  • 1 posts
Hello,
Thank you very much Johnmar. You are a life saver. All my daughters first year photos were nearly lost. With your instructions I got all my data back.
Dreamsat, Thank you for the photo. I shortcircuited the pins you specified and it worked like a charm.

I was struggling to get the FT > prompt in the hyper terminal earlier. I got a lot of information from the other thread to resolve the problems.

Dham

#7
kubr

kubr
  • Member
  • 1 posts
Hi,
I have Seagate ES.2 1TB ST31000340NS and hyperterm send me every 60 seconds this message: LED:000000CC FAddr:0024BD19

I thing that I need unlock terminal but my PCB look little bit different.

Posted Image

Please can anyone tell me which 2 pins must be short.

THX

#8
rincon

rincon
  • Member
  • 2 posts

Hi,
I have Seagate ES.2 1TB ST31000340NS and hyperterm send me every 60 seconds this message: LED:000000CC FAddr:0024BD19

I thing that I need unlock terminal but my PCB look little bit different.

Please can anyone tell me which 2 pins must be short.

THX


Hi, This is the unlock pins ... I was tested - successfully :)

Posted Image

Edited by rincon, 27 December 2009 - 05:19 AM.


#9
rincon

rincon
  • Member
  • 2 posts
x

Edited by rincon, 26 December 2009 - 07:50 PM.


#10
dcstudio

dcstudio
  • Member
  • 1 posts
Dear ALL,
Thanks for POST!! it's work!!
i also rescue my ES.2 Hard Driver!

#11
Chilli

Chilli

    Newbie

  • Member
  • 30 posts

4. During that 1 second when you see "F3 T>" message but before you receive next "LED:000000CC..." you must short two points shown in the following image (they are known as "read-channel").
Posted Image



For my ES:2 I disconnected the heads at the moment you described.
I could accomplish this by loosing all screws around the head connector (at unpoweerd disc), tightending the head connector screw a bit, so that it gets contact again, making procedure like you described and instead of short cutting just quick opening the connector screw.
After spin down you can tighten the screw again.

Maybe better for people that have no solder equipemnt or another PCB revision.
Also the motor connector can be "disconnected" by unscrewing, if needed.

Regards
Stephan

#12
Rousie

Rousie
  • Member
  • 3 posts
Hi Guys,

Been a keen reader of this forum for some time, and finally joined up...

Got the same problem here with my 1TB 7200.11, and the response from the Terminal when connected is:
RST 0x20m
(P) SATA RESET
LED 000000CC FADDR: 0024CDC9

Now, i've looked at my PCB and it's different to both of which are posted here.

Could anyone kindly take a look and let me know which pins i need to be shorting out?

Posted Image

Many thanks,
Dean

#13
drgonzo7

drgonzo7
  • Member
  • 2 posts
  • OS:XP Pro x86
I spent many hours trying to fix my ES:2 before finding this thread and realising our drives worked in a different way - arrgh! Anyway, I also tried the 'shorting the two points' method, but either I wasn't skilled enough to get the timing right, or I wasn't shorting the correct points! I then tried the 'disconnecting the heads' method below, and with a slight modification of the method, managed to get to the elusive 'F3 T>' command prompt at last! My method was to loosen then screws on the right hand side (as you look at the PCB with the SATA & power connectors at the top) around the head connector, and then hold the PCB down onto the head connector with my finger - as soon as the 'F3 T>' message appeared, I released my finger from the PCB, and with the right timing, this disconnected the heads (I found this easier than quickly opening the connector screw). Once you've got the 'F3 T>' prompt, you just follow the instructions available elsewhere in these threads (you can tighten the screws once you've got spin down)

Cheers

Damian


4. During that 1 second when you see "F3 T>" message but before you receive next "LED:000000CC..." you must short two points shown in the following image (they are known as "read-channel").
Posted Image



For my ES:2 I disconnected the heads at the moment you described.
I could accomplish this by loosing all screws around the head connector (at unpoweerd disc), tightending the head connector screw a bit, so that it gets contact again, making procedure like you described and instead of short cutting just quick opening the connector screw.
After spin down you can tighten the screw again.

Maybe better for people that have no solder equipemnt or another PCB revision.
Also the motor connector can be "disconnected" by unscrewing, if needed.

Regards
Stephan



#14
TheMeekGeek

TheMeekGeek
  • Member
  • 2 posts
  • OS:Windows 7 x64
Hi, from a novice's point of view... what exactly did you use to short the two points? did you solder etc?

#15
VideoRipper

VideoRipper

    CSI Eastwood City

  • Member
  • PipPipPip
  • 330 posts
  • OS:none specified
  • Country: Country Flag
I think he just used a bent paperclip :whistle:
To C the BASIC things in life, use Delphi

#16
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,225 posts
  • OS:none specified
  • Country: Country Flag

Hi, from a novice's point of view... what exactly did you use to short the two points? did you solder etc?


I think he just used a bent paperclip :whistle:



...unless johnmar was EXTREMELY fast in soldering:

....
4. During that 1 second when you see "F3 T>" message but before you receive next "LED:000000CC..." you must short two points shown in the following image (they are known as "read-channel").
....

and very, very, VERY fast in de-soldering:

You must hold them short about 20-30 or little more seconds.


The usual method is a pair of tweezers. ;)
Bent tip ones are handy for this:
Posted Image

jaclaz

#17
TheMeekGeek

TheMeekGeek
  • Member
  • 2 posts
  • OS:Windows 7 x64
Thank you chaps

#18
sadalmelik828

sadalmelik828
  • Member
  • 2 posts
  • OS:none specified
  • Country: Country Flag
Hello,
You could tell me the complete procedure to revive a Barracuda ST3250310NS
thanks

#19
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Hello,
You could tell me the complete procedure to revive a Barracuda ST3250310NS
thanks


Hi sadalmelik828,

You basicly follow the first post of this topic. What they do not tell you is you need a converter for Hyperterminal to talk to your disk. You can get more info on the converters in the thread on the 7200.11. See Read-me-first especially point 10&11 for info regarding converters. (Also the guide by CarterinCanada (link in READ-ME-FIRST)) Remember that that is a different procedure with different commands. Just read that to get a feel for the converter setup.
Jack of all trades, master of none, though ofttimes better than master of one.

#20
mirkelam

mirkelam
  • Member
  • 2 posts
  • OS:Windows 7 x64
  • Country: Country Flag
may thanks for this!!

it took me 2 hours to geht the input command error.. to get access..

i have the same es.2 as you johnmar

with normal points from you johnmar it didn't work after the LED-- error message ctrl+z nothing happened!

i had to short your 2 points and the other 2 from this translated page on post #4.. switched this points then the other 2 points.. and somehow it worked!

my litte brother made the commands in hyperterminal :D many times ctrl+z needed.. omg!

and now i have copied everything down big thanks for this guide!

p.s. never again seagate!!!!!!!!!!!!

#21
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,225 posts
  • OS:none specified
  • Country: Country Flag

my litte brother made the commands in hyperterminal :D many times ctrl+z needed.. omg!

An interesting use of a little brother.... :thumbup ... and a few people are still convinced they are only a nuisance....;)

Happy to know there is another happy bunny in the basket :):
http://www.msfn.org/...ic=128727&st=10

jaclaz

#22
mirkelam

mirkelam
  • Member
  • 2 posts
  • OS:Windows 7 x64
  • Country: Country Flag
hehe nice bunnys :P

hmm ok "litte" is he not anymore he is 15 and im 25 hehe^^ and no he helps where he can ;) no nuisance^^

and hm.. ALONE it's not possible to do short pins and input commands..


i should go to the company where that guy said "600 - 800 euro" for data recovery... and laugh at him :P www.attingo.at ^^

Edited by mirkelam, 29 October 2010 - 09:52 AM.


#23
mazoxx

mazoxx
  • Member
  • 1 posts
  • OS:Windows 7 x86
  • Country: Country Flag
Yeepy, done, no shortening on the pcb, i just loosened the screws as mentioned in the earlier posts, walla d done. Thanx to BlouBul for directing me to this thread, i had tried my ES.2 using the method for the 7200.11 but could not get into engineering mode.
What i did:
1) Got a CA-42 Nokia cable opened it up to see which pin is RX, TX and Ground tried the 7200.11 method, no success, but could do a loop back successfully.
2) Got a Nokia DKU-5 tried same as above, nothing could not even do a loop back.
3) Got a USB 232 Convertor (Garmin Cable 1.8m long), used pin 2 RX, 3 TX and 5 GND, could get loop back, first tried the 7200.11 method no results after CTRL+z, PM'd BlouBul who directed me to this thread, redid every thing but i got funny characters after CTRL+Z, resetup trying to see if grounding and insulation was a problem still same problem, just thought the cable was too long maybe thats why i was having the funny characters.
4) Got another CA-42 cable, setup everything, on first go, got in and everything sorted. Replugged hdd, works. Thanx!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

#24
spamenigma

spamenigma
  • Member
  • 4 posts
  • OS:Windows 7 x64
Hi

I've got 2x ES.2 drives that were part of a Raid5 array that have this issue. after trying a usb ttl cable and having no luck I got a nokia CA-42 cable which after a little trial and error it worked and talked to the drive.

I intially got the LED: 000000CE... lines come up and eventually after fiddling again got the ctrl-z to work and did the slightly lift from head connector trick which also worked.

This is what happened next:
F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.155 msecs
F3 2>U

I didnt get a spin up or anything and now the drive just makes a ..... buzzz........buzzz......buzzz....noise rather than attempt to spin up with no communication with the terminal sw. both drives have done the same.
They are Barracuda ES.2 250GB - ST3250310NS

Can anyone help at all please, are they now totalled or is there any more tricks out there that might get me to progress with this?

Many Many Thanks in advance!

#25
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,225 posts
  • OS:none specified
  • Country: Country Flag
Please DO NOT EVER double post. :realmad:
I just replied to your post on the other (WRONG) thread.
http://www.msfn.org/.../page__st__3741

I am re-posting the contents of that here:



Can anyone help at all please, are they now totalled or is there any more tricks out there that might get me to progress with this?


What you report is "queer". :unsure:
"Spin down" is a "normal" and NOT even potentially "destructive" one.
If you:
  • power off the drive
  • completely remove the PCB from it.
  • verify contacs between PCB and drive (which means visually inspecting BOTH contacts on the PCB and the "springy" ones on the HD - checking that no "springy thingy" is bent or "flattened", and clean them thoroughfully with an eraser -the one on a pencil will do - and clean them thoroughfully with isopropyl alcohol or similar solvent, acetone is OK, as long as you do use it carefully, parsimoniously and quickly)
  • re-assemple fully hard disk and PCB
  • try powering it again (without any connection BUT the actual power supply)

What happens? :blink:

Since your disks are ES2 you had to do the "short circuit" trick.
Is it possible that you short circuited "something else" or "also something else"? :ph34r:

jaclaz



PLEASE, let's continue here.

jaclaz

Edited by jaclaz, 27 May 2011 - 12:52 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN