Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Gradius2

The Solution for Seagate 7200.11 HDDs

Recommended Posts

tried and nothing. continues the same. I turn the HD on, wait to the engine to start spinning, unscrew the screw and then lift up and put a separator. It stops, I try to connect with hyperterminal. Same failure.

Share this post


Link to post
Share on other sites

I turn the HD on, wait to the engine to start spinning, unscrew the screw and then lift up and put a separator.

...and that's what you're doing wrong. :hello:

Since the firmware is stored on the platters, once you apply power to the drive the firmware

is loaded (and fails), resulting in a busy state.

The trick is to only access the controler, before it is even able to load the firmware and

this is done by temporary disabling the drive motor (by separating it from the PCB).

Now you will be able to access the controler (and it only *thinks* the drive is spun up),

so you have to let it *think* the motor is not spinning again, by invoking the spin-down

command.

After that you can re-seat the PCB (remove the separator) and spin the motor up again.

So the correct order is:

  • Remove PCB (or put something between the drive's motor-contacts)
  • Apply the COM-connection
  • Apply power to drive
  • Spin down motor (it actually wasn't spinning in the first place)
  • Re-attach PCB (or remove motor-contacts spacer)
  • Spin up motor (now it will really spin up)
  • Perform commands to get drive out of the BSY state
  • Remove power and COM-connection to drive
  • Connect drive to SATA-port on PC
  • Power up PC
    • See if it recognises it as a drive
    • Check if the drive is not seen as a 0GB drive

If the drive is seen as a 0GB drive, you'll have to perform the additional LBA0-steps.

When the drive is working again: make a backup of your drive ASAP followed by a thourough

test using SeaTools for DOS.

Greetz,

Peter.

Share this post


Link to post
Share on other sites
I turn the HD on, wait to the engine to start spinning, unscrew the screw and then lift up and put a separator.

...and that's what you're doing wrong. :hello:

Since the firmware is stored on the platters, once you apply power to the drive the firmware

is loaded (and fails), resulting in a busy state.

The trick is to only access the controler, before it is even able to load the firmware and

this is done by temporary disabling the drive motor (by separating it from the PCB).

+1 with Peter. You are doing it backwards and that is why you are getting the error messages. As Peter said, you need to put in the separator, screw in the 3 torx screws on the other side and then plug in the sata power. You need to follow the tutorial exactly in its proper order. You cannot mess with things and expect it to work properly. hope you get it working.

Edited by mundy5

Share this post


Link to post
Share on other sites

I believe my steps are correct, please correct me if I'm wrong.

These are my steps:

1 - Remove or separator in the top 3 contacts the controller.

2 - connect rx, tx and mass

3 - connect SATA power

4 - open hyperterminal

5 - Configure Connection COM10, 38400, 8, nothing, 1, none

6 - Ctrl + z

7-T responds F3>

8-type 2

9 And from that step always responds

LED: 000000CC FAddr: 0025BF67

LED: 000000CC FAddr: 0025BF67

Greetings and thanks for the help.

Share this post


Link to post
Share on other sites

Hmmm, indeed the steps look alright (I guess you only mixed up the order when posting).

Luckily I saved my log of HyperTerminal when unbricking my drive and this is what it looked like:

  • Disconnected PCB from drive
  • Connected COM-convertor and
  • Applied power to PCB:
    LED:000000CC FAddr:0024A051LED:000000CC FAddr:0024A051F3 T>/2
    F3 2>Z
    Spin Down CompleteElapsed Time 0.146 msecs
  • With the power still applied to the PCB, I attached the PCB back onto the drive.
  • Spin up motor again:
    F3 2>U
    Spin Up CompleteElapsed Time 6.824 secsF3 2>/1
    F3 1>N1
    F3 1>F3 T>m0,2,2,,,,,22Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
    User Partition Format Successful - Elapsed Time 0 mins 00 secs
    F3 T>
  • After this, I could access my drive again (over SATA)

As can be seen, my error-message at the beginning was different.

Mine:

LED:000000CC FAddr:0024A051

Yours:

LED: 000000CC FAddr: 0025BF67

So... that might be the problem in your case? :unsure:

These are my steps:

[...]

7-T responds F3>

8-type 2

The fact your PCB responds to CTRL+Z is a good thing, but to enter Level 2 diagnostics you'll have to press:

/2

(Slash 2) not just

2

:huh:

Are you sure you've typed the slash ("/") before the "2"? :unsure:

Greetz,

Peter.

Share this post


Link to post
Share on other sites

I would reiterate that there are two "school of thoughts", one that insulates Head contacts and the other one that insulates motor contacts.

If with one set of contacts don't work, use the other one.

jaclaz

Share this post


Link to post
Share on other sites

To be honest: I only followed the initial roadmap by Gradius2 and entirely

removed the PCB from the drive (so both heads, actuator as platter-motor

contacts were isolated), but you'll have to make sure when re-fixing the PCB,

you don't short circuit anything (and fry it)! :wacko:

I just did it for peace of mind: I didn't like the idea the heads would move

over the non-rotating platters at drive startup.

(FYI: the heads hover over the platters by the thin layer of air that is

generated by its rotational force)

Greetz,

Peter.

Share this post


Link to post
Share on other sites

That's great thecola, congrats! :thumbup

Now first:

Greetz,

Peter.

IMHO, WRONG. :(

Correct sequence:

  • Backup the most important data on the drive
  • Verify that the backup is functional contains everything of value to you
  • Find a way to have the drive swapped anyway

Let the guys at Seagate take the responsibility of re-certifying the (existing) drive or giving you a refurbished one.

jaclaz

Share this post


Link to post
Share on other sites

Hey all,

I have a "friend" from these boards coming over tomorrow with a bricked drive. I will get him to film the process and I'll post a video. It should make things much clearer to everyone as to the "power on/off", when and how long etc.

If you are unsure of what you are doing, STOP NOW and wait. It will be worth it.

Check back around 7PM MST Wednesday Jan 21st.

Thanks,

Fatlip

Share this post


Link to post
Share on other sites
IMHO, WRONG. :(

[...]

Let the guys at Seagate take the responsibility of re-certifying the (existing) drive or giving you a refurbished one.

Hehehehe, you could be right there, of course ;)

My drive was faulty (gave an error-message in SeaTools) and I expect others to get the same

result, but you'll have to enter the error message (given by SeaTools) when issuing an RMA.

Knowing how the company Seagate thinks and works (after having found out the hard way myself),

my guess is they will not swap a "Non-faulty" drive under warranty... :}

Greetz,

Peter.

Share this post


Link to post
Share on other sites

My drive was faulty (gave an error-message in SeaTools) and I expect others to get the same

result, but you'll have to enter the error message (given by SeaTools) when issuing an RMA.

Knowing how the company Seagate thinks and works (after having found out the hard way myself),

my guess is they will not swap a "Non-faulty" drive under warranty... :}

Good :), start a new thread titled "Good excuses for having the stupid people at Seagate exchange drives", post in it the error you had.

Hopefully a few more members with the error will have saved their RMA "cause" and will post there and we can soon have a database of such nonsense errors to feed the Seagate people with.

;)

jaclaz

Share this post


Link to post
Share on other sites

Hey all,

I have a "friend" from these boards coming over tomorrow with a bricked drive. I will get him to film the process and I'll post a video. It should make things much clearer to everyone as to the "power on/off", when and how long etc.

If you are unsure of what you are doing, STOP NOW and wait. It will be worth it.

Check back around 7PM MST Wednesday Jan 21st.

Thanks,

Fatlip

There are already videos on youtube. don't put more time into this unnecessarily

Share this post


Link to post
Share on other sites

I made the test with Seatools and gave me two error codes.

One for short DST: A3EAD262

One for long DST: A3EAD252

I have written an email to Seagate.

Which way did you used to the hd replacement? The one on the website? Where did you wrote down the error codes?

At first glance it worked without any problems (even didn't update the firmware), but mundy5

advised me to do a "Short DST" test with SeaTools for DOS...

...which failed misserably :angry:

--------------- SeaTools for DOS v2.17 ---------------
Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5
Max Native Address 976773167
Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB )
This drive supports Security Features
SMART Is Supported And ENABLED
SMART Has NOT Been Tripped
DST Is Supported
Logging Feature Set Is Supported
POH 5994 Current Temp 23
Started Short DST 2/12/2010 @ 11:37.4
DST -- FAILED - Read Element LBA = 0
Your SeaTools Test Code: A7E7D56A
Short DST FAILED 2/12/2010 @ 11:37.16

...but a "Long DST" test would run (only it took over an hour and a half) :wacko:

--------------- SeaTools for DOS v2.17 ---------------
Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5
Max Native Address 976773167
Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB )
This drive supports Security Features
SMART Is Supported And ENABLED
SMART Has NOT Been Tripped
DST Is Supported
Logging Feature Set Is Supported
POH 5994 Current Temp 23
Started Long Test 2/12/2010 @ 11:38.8
Your SeaTools Test Code: A7E7D55A
DST -- FAILED - Read Element LBA = 963648851
Short DST FAILED 2/12/2010 @ 13:20.9
[ 963580219 -- Repaired ][ 963581115 -- Repaired ]
[ 963582011 -- Repaired ][ 963628659 -- Repaired ]
[ 963629555 -- Repaired ][ 963631507 -- Repaired ]
// JUST A LONG LIST OF REPAIRS HERE //
[ 963993720 -- Repaired ][ 963994614 -- Repaired ]
[ 963994615 -- Repaired ][ 963994616 -- Repaired ]
[ 963995510 -- Repaired ][ 963995511 -- Repaired ]
DST -- FAILED - Read Element LBA = 964028566
Short DST FAILED 2/12/2010 @ 13:21.0
Long Test PASSED After Repair 2/12/2010 @ 13:21.0

I then filled in an RMA, giving the test-code returned by SeaTools ("A7E7D56A")

and I had to ship the drive back to Seagate (after I had done the full wipe) ;)

A couple of days later they return the other drive pictured in my previous post.

So check the drive first with SeaTools for DOS: if it does give you an error test-code

return it to Seagate, if not: I think it's safe to say it's okay (and then you could do

the firmware update if you wish).

Please be aware that SeaTools for DOS does not support all types of SATA chipsets; it

refused to see my drive when connected to a Promise controler (as I soon found out).

Greetz,

Peter.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...