Jump to content

The Solution for Seagate 7200.11 HDDs


Recommended Posts


SUBJECT:

Seagate s/n 9QJ0L9XR

BARRACUDA 7200.11 1 TERA

ST31000340AS (B)

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 :D:P

SORRY FOR MY ENGLISH

Edited by iw8pny
Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

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. :unsure:

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

Link to comment
Share on other sites

Seagate s/n 9QJ0L9XR

BARRACUDA 7200.11 1 TERA

ST31000340AS (B)

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 :no:

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.

Link to comment
Share on other sites

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... :unsure:

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

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.

Link to comment
Share on other sites

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... :unsure:

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

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.

Link to comment
Share on other sites

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.

Well, that will be your problem...

Always connect all the 3 wires to the diagnostics port. :rolleyes:

You could have had it working yesterday, when you (probably) used the power supply

of the same computer as to where the RS232-interface was connected to (since in that

case the ground of the power-connector was used), but this isn't the proper way of

doing things and you'll be creating a "Ground-loop"...

Greetz,

Peter.

Link to comment
Share on other sites

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.

Well, that will be your problem...

Always connect all the 3 wires to the diagnostics port. :rolleyes:

You could have had it working yesterday, when you (probably) used the power supply

of the same computer as to where the RS232-interface was connected to (since in that

case the ground of the power-connector was used), but this isn't the proper way of

doing things and you'll be creating a "Ground-loop"...

Greetz,

Peter.

Can i use the black cable on the ttl-232r-3v3 usb cable for ground? Or should i find a real ground and connect to there?

TIA

doooda

Link to comment
Share on other sites

Can i use the black cable on the ttl-232r-3v3 usb cable for ground? Or should i find a real ground and connect to there?

TIA

doooda

GROUND, when we are talking of low voltage DC doesn't come from "thin air", you have to have ALL the devices you are using have the low side (0V) ALL connected together.

I.e. the BLACK (make sure it is the 0V) of the adapter NEEDS to be connected to the GROUND of the disk AND to the 0V (again BLACK) of the power supply.

This way you make sure they all share the same "base potential" and you avoid the possible loops of data.

In TTL the data is represented by voltage levels that are the differential voltages from a "common base", i.e. the 0 (zero) Volt level.

If any of the devices "leak" a small amount of voltage this "base level" may be higher (or lower) on one device as compared to another device, and this can lead to mis-interpreting the DATA.

jaclaz

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...