[Gram]

...And yet another successfuly recovered drive - like Jay's (post #2736), a Barracuda 500GB with LC11 firmware. It looks like it's not only the SA/SD batch that fouled up; I wonder how many unfortunates there are round the world who haven't found this or similar sites...
Thanks to all on here for their tips and experiences,
Gram

[VideoRipper]

Good job hwd3r3bsx98webwd and Gram!

Gram, on 15 April 2010 - 03:39 PM, said:

I wonder how many unfortunates there are round the world who haven't found this or similar sites...

What I'm wondering about is how many people considered their data as lost and
swapped or binned the drive and how many actually paid hundreds of Euro's or
Dollars to get their precious data back...

I was originally quoted for €900, ex VAT!

[dooda]

I tried this guide last night.

I went fine until i sent the command: N1
To the SMART erase.
After that I got this:

Init SMART Fail
LED:000000CC FAddr:00239CED


Every minute or so i got another LED:000000CC FAddr:00239CED.

After a while i disconected to start over.

But now i can communicate with the drive. It say COM4 already open.

Anyone have any clues what i can do? Or is it totally bricked now?


It was fun anyhow and thanks to Gradius all you others in this thread.

TIA

dooda

[archangel76]

Help! I'm another victim!

I've read and read and read and I feel like I'm so close but can't get there. Here is where I'm at:

I have a 640gb 7200.11 drive and I think that I have the bsy error, but am not sure (when bios comes up, it just sits there for about 5 mins before moving on with no detection).
I have aldav serial port (not usb) ttl converter that has been mentioned by others.
I can get a loopback connection with no problem. I've turned off echo on winxp hyperterminal.
I have successfully connected to my older 7200.7 160gb drive (at 9600 baud). I hit cntrl-z in hyperterminal and drive info started popping up.
However, every time I try to connect to my 640gb drive at 38400 (8:none:1:none) (and I've also tried 9600 fyi), nothing happens when I hit cnrtrl-z. I've tried it with the board connected and the board disconnected to no avail. I've switched the tx/rx, but as it worked on my 7200.7 drive, it should be working on my 7200.11 drive.

Any helpful hints at this point? I'm pulling my hair out.

[VideoRipper]

dooda, on 16 April 2010 - 07:50 PM, said:

But now i can communicate with the drive. It say COM4 already open.

When you get that message, it means the communication connection was not
closed properly and you can only re-connect after rebooting your computer.

dooda, on 16 April 2010 - 07:50 PM, said:

I went fine until i sent the command: N1
To the SMART erase.
[...]
Or is it totally bricked now?

Actually, issuing the N1-command is the real first step in unbricking the drive,
so nothing's lost (the first two steps are only there to let you gain access to
the diagnostics-mode command prompt).

Though giving an error at this step *could* indicate that the drive is really faulty.

You can start all over again from the top (insultate PCB contacts, spin-down,
re-attach PCB, spin-up) and try the N1 command a second try.

Good luck,

Peter.

[VideoRipper]

archangel76, on 16 April 2010 - 07:58 PM, said:

Any helpful hints at this point? I'm pulling my hair out.

All 7200.11 drives *should* communicate at 38400 Baud, so that should be okay.

Just some pointers:

• Make sure TX, RX and GND are connected correctly
  (TX of RS232 to RX of drive, RX of RS232 to TX of drive, GND to GND)
  
• When the PCB is fully attached to the drive and you only apply power
  to it (so no SATA-data), you *should* hear it spin up as normal
  
• When powering up the drive (with RS232 attached) you should get some
  messages in the terminal display (even without CTRL+Z), like:
  

  LED:000000CC FAddr:0024A051
  LED:000000CC FAddr:0024A051
  

  
  
• When the PCB is not attached to the drive and you apply power to the PCB
  with the RS232 attached, you *should* get a prompt after pressing CTRL+Z
  (keys at the same time)

Apart from that, I can't think of anything else

Good luck,

Peter.

[archangel76]

VideoRipper, on 16 April 2010 - 08:28 PM, said:

archangel76, on 16 April 2010 - 07:58 PM, said:

Any helpful hints at this point? I'm pulling my hair out.

All 7200.11 drives *should* communicate at 38400 Baud, so that should be okay.

Just some pointers:

• Make sure TX, RX and GND are connected correctly
  (TX of RS232 to RX of drive, RX of RS232 to TX of drive, GND to GND)
  
• When the PCB is fully attached to the drive and you only apply power
  to it (so no SATA-data), you *should* hear it spin up as normal
  
• When powering up the drive (with RS232 attached) you should get some
  messages in the terminal display (even without CTRL+Z), like:
  

  LED:000000CC FAddr:0024A051
  LED:000000CC FAddr:0024A051
  

  
  
• When the PCB is not attached to the drive and you apply power to the PCB
  with the RS232 attached, you *should* get a prompt after pressing CTRL+Z
  (keys at the same time)

Apart from that, I can't think of anything else

Good luck,

Peter.

Hmm. I don't hear it spin up. That's probably the issue then. When the board is disconnected, I don't get anything, so that means my board is fried? Am I out of luck? Should I try a different board? I have a 7200.11 1 GB, and the boards look similar, but I'm guessing they aren't compatible.

[VideoRipper]

archangel76, on 16 April 2010 - 09:00 PM, said:

Hmm. I don't hear it spin up.

Ewww... that's bad

I guess it's indeed fried then...
...you don't see any blown-up components on the board, do you?

Some boards *might* look the same, but even with drives of the same type and
model you can never be certain they actually are

You *might* want to try it, but I think chances are slim and you will be doing
it entirely at your own risk

Greetz,

Peter.

This post has been edited by VideoRipper: 16 April 2010 - 09:13 PM

[archangel76]

VideoRipper, on 16 April 2010 - 09:09 PM, said:

archangel76, on 16 April 2010 - 09:00 PM, said:

Hmm. I don't hear it spin up.

Ewww... that's bad

I guess it's indeed fried then...
...you don't see any blown-up components on the board, do you?

Some boards *might* look the same, but even with drives of the same type and
model you can never be certain they actually are

You *might* want to try it, but I think chances are slim and you will be doing
it entirely at your own risk

Greetz,

Peter.

There are no burnt components. I was actually hoping that there were b/c at least then I could say what was wrong. It looks good, but just doesn't spin up.

[iw8pny]

When I write the command U the cursor
remain blinking without response.

Help me

[VideoRipper]

I think you'ld better stay on topic in the correct thread...

There's no sense in starting spin-offs all over the forum

[iw8pny]

VideoRipper, on 17 April 2010 - 02:52 AM, said:

I think you'ld better stay on topic in the correct thread...

There's no sense in starting spin-offs all over the forum

Sorry .. you're right but I don't know how move or delete the post!

[VideoRipper]

A member like you and I can't move or delete topics, only a moderator can.

But don't worry: just re-ask your question in the Seagate-Solution thread
and this one will/might get locked

Don't forget to add as much information as possible in your question.

This post has been edited by VideoRipper: 17 April 2010 - 03:23 AM

[dencorso]

Spin-off thread merged into main thread.

[iw8pny]

SUBJECT:
Seagate s/n 9QJ0L9XR
BARRACUDA 7200.11 1 TERA
ST31000340AS (
P/N 9BX158-568
FIRMWARE SD81
DATE CODE 08422
SITE CODE KRATSG


WHAT HAPPEN:
THE DAY BEFORE IT DIED I HAVE TO SWITCH OFF THEN ON TWICE TO BE RECOGNIZE
THEN SOME DAYS LATER I FOUND THIS FORUM
FOLLOWING LETTER BY LETTER THE INSTRUCTIONS

....BUT ONCE ARRIVED TO

F3 2>U (ALL THE CONTACTS RESTABILISHED AND CLEAN)

STRARTED MY PAINS !

NOTHING.. ONLY THE CURSOR BLINKING
NO MESSAGES

NOTHING SEEMS TO BE BURNED ON PCB

PUT AN HAND ON THE HDD I FEEL PRRRRRRRR PRRRRRRR
MAY BE THE MOTOR SICK?? HOW TEST IT

I'M ABLE TO DO EVERY KIND OF TESTS IN MY LAB
SO SUGGEST ME TEST POINTS OR OTHER

MY BEST .... TO ALL THE GURUS

SORRY FOR MY ENGLISH

This post has been edited by iw8pny: 17 April 2010 - 04:26 AM

[jdognz]

I had the BSY problem and could not see my drive in bios etc. Ran fix and now I can see the drive but comes up with errors on boot. Cannot see in windows and HD sentinel lists drive size as 2048Gb?? Any ideas as to the problem?

[dooda]

VideoRipper, on 16 April 2010 - 08:11 PM, said:

When you get that message, it means the communication connection was not
closed properly and you can only re-connect after rebooting your computer.

I turned the computer and hdd off for the night and now the COM4 port is working fine.

VideoRipper, on 16 April 2010 - 08:11 PM, said:

Actually, issuing the N1-command is the real first step in unbricking the drive,
so nothing's lost (the first two steps are only there to let you gain access to
the diagnostics-mode command prompt).

Though giving an error at this step *could* indicate that the drive is really faulty.

You can start all over again from the top (insultate PCB contacts, spin-down,
re-attach PCB, spin-up) and try the N1 command a second try.

Good luck,

Peter.

I have no luck to get into diagnostics-mode, it worked once yesterday. What can I do wrong? Or is it something I can do differently?

Little background:
My disk is a 1,5 TB (ST31500341AS) with cc1h firmware. Was ok for a few months the one day i got a message that it got a SMART error and after reboot it was gone.

For this guide i use a ttl-232r-3v3 usb cable with external power supply, i have tried for an PSU too but no success.
My orange cable is connected to the drives RX-pin and the yellow cable is connected to the TX-pin. I have not connected any cable to the ground-pin.

TIA
dooda

[VideoRipper]

iw8pny, on 17 April 2010 - 04:01 AM, said:

Seagate s/n 9QJ0L9XR
BARRACUDA 7200.11 1 TERA
ST31000340AS (
P/N 9BX158-568
FIRMWARE SD81
DATE CODE 08422
SITE CODE KRATSG

First of all: this fix was written for SD15 firmware, so it *might* not work
with other firmware-versions

When you apply power to the drive with the PCB attached, do you hear the motor spin up?
If it's not spinning, the motor-driver on the PCB or the motor itself might be broken and there's
not much you can do about it, I'm afraid

If it is spinning up:

• Remove the PCB or insulate the contacts
  
• Attach RS-232 interface and apply power to PCB
  
• Press CTRL+Z keys at the same time;
  you should get a F3 T>-prompt
  
• Enter: /2 (that's slash and 2);
  you should get the F3 2>-prompt
  
• Enter: Z (that's a CAPITAL Z);
  you should get:

  Spin Down Complete
  Elapsed Time X.XXX msecs
  

• Remove the insulation between the contacts and/or reseat the PCB
  
• Enter: U (that's a CAPITAL U);
  you should hear the drive spin up now.
  
• After a few seconds you *should* get this:

  Spin Up Complete
  Elapsed Time X.XXX secs
  

If you don't hear it spinning up, the drive makes weird noises and/or it takes 1-2 minutes
before an error-message is displayed, you're drive is likely to be defective.

Good luck,

Peter.

[VideoRipper]

jdognz, on 17 April 2010 - 04:17 AM, said:

Ran fix and now I can see the drive but comes up with errors on boot.

I hope you're not trying to boot from the drive itself...

Anyway, the good news it is seen again in the BIOS

jdognz, on 17 April 2010 - 04:17 AM, said:

Cannot see in windows and HD sentinel lists drive size as 2048Gb??

As what type (size) of drive is it seen at PC boot-time?
(Never rely on what Windows is reporting you...)

If it says it's a 0GB drive, you'll have to do the second step in performing
the LBA0-fix (which can also be found in the document at the first page).

Greetz,

Peter.

[jdognz]

VideoRipper, on 17 April 2010 - 05:00 AM, said:

jdognz, on 17 April 2010 - 04:17 AM, said:

Ran fix and now I can see the drive but comes up with errors on boot.

I hope you're not trying to boot from the drive itself...

Anyway, the good news it is seen again in the BIOS

jdognz, on 17 April 2010 - 04:17 AM, said:

Cannot see in windows and HD sentinel lists drive size as 2048Gb??

As what type (size) of drive is it seen at PC boot-time?
(Never rely on what Windows is reporting you...)

If it says it's a 0GB drive, you'll have to do the second step in performing
the LBA0-fix (which can also be found in the document at the first page).

Greetz,

Peter.

Yeah sorry i should have been a little clearer. I have 3 HDD and on bios boot first two are fine then the Seagate hangs and says F1 to continue.
I ran Seatools and it sees the drive but wont run the short or long test.
If i hook the drive up to usb and attach as external then that is when i can see in HD Sentinel but lists as wrong size. Try to run the firmware pdate from windows but it says not matched. Maybe i need to make a firmare bootdisk and try that. OR is there another way i can set drive to correct size? I tried the 0lba fix but same problem still.