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

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?

They will ask you when you begin the process of a warranty return on the website. One of the fields is the SeaTools Test code.

Share this post


Link to post
Share on other sites

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

Please READ the date when Fatlip made the announcement stuffer senselessly quoted...:whistle:

jaclaz

Share this post


Link to post
Share on other sites

Well, I thought I had this figured out. But can't type anything into the terminal. I am using two AA batteries for the power. So with this I had to run a ground wire from the RS242 to the Ground on the HDD. I must be mising something in the instructions.

Share this post


Link to post
Share on other sites

VideoRipper thank you very much, the problem was simply the "/" before the 2. Sometimes they are simple things you can not see. I just repaired 3 hard drives.

I'm happy;)

Share this post


Link to post
Share on other sites

Great news, a8nsli! :thumbup

(...and another satisfied customer leaves the shop) ;)

Now backup (the most important) stuff and check/swap the drives ASAP :D

Greetz,

Peter.

Share this post


Link to post
Share on other sites

VideoRipper thank you very much, the problem was simply the "/" before the 2. Sometimes they are simple things you can not see. I just repaired 3 hard drives.

I'm happy;)

yes! great news!

now do as VideoRipper says

Share this post


Link to post
Share on other sites

Hi again, and thanks for the help. I've figured out wich cables are wich. But when I type Ctrl + Z in hyperterminal all i get is a arrow pointing right. I've heard that it can be fixed if you swap rx/tx, but that doesn't help. Can it be caused by the wires touching during the fix, and if so, can you just insulate them or have i fried the disk? >_<

Share this post


Link to post
Share on other sites

RX is the receiving line, TX is the transmitting line.

When connected correctly (RX to TX and TX to RX) you *should* get any response when

powering up the drive.

  • If you would connect these lines the wrong way round (RX of COM to RX of drive and
    TX of COM to TX of drive), you won't see any response.
  • If you have chosen the wrong speed (Baud-rate), data-bits, parity and/or stop-bits
    to communicate with, the response will be either gibberish or none at all (depending
    on the chosen speed).
  • If you have chosen the wrong flow control, you might not get any response at all.

For a 7200.11 drive, the settings should be:

  • Bits per second: 38400
  • Data bits: 8
  • Parity: None
  • Stop bits: 1
  • Flow control: None
    OR (if your interface has loopback handshaking):
  • Flow control: Hardware

In case of communication problems, please follow this test:

  • Connect your convertor to the PC
  • Leave the other end of the convertor un-connected
  • Start HyperTeminal (or another terminal program you want to use)
  • Open a connection (for instance with settings: 38400-8-N-1)
  • Type a few characters on the keyboard: the terminal display *should*
    remain empty.
  • Now connect the RX and TX of the convertor to each other (creating
    a loopback connection)
  • Again: type a few characters on the keyboard: this time, you *should*
    see the typed characters in the terminal display.

If above test is succesful, you know that:

  • The convertor works correctly
  • You have successfully identified the RX and TX terminals of the convertor
    (though you don't know which is which for sure, yet)

Now, let's continue to the next step:

  1. Remove the controler-board from the drive
  2. Connect the RX and TX leads of your convertor to the controler-board
  3. Open a connection in HyperTerminal (with settings: 38400-8-N-1)
  4. Apply power to the drive's controler-board (note: the drive itself is not
    attached at this moment!)
  5. In HyperTeminal, the display *should* show something similar to:
    Rst 0x20M

  6. If you now press the CTRL+Z keys (at the same time), the controler-board*should* response with:
    F3 T>


    ...which is the actual prompt you're going to need

If you don't get any response (in step 5), try swapping the RX and TX lines and

try again (don't forget to remove/reapply power when doing this).

Once you have established connection to the controler-board and can communicate

with it, you're ready to (try to) un-brick it.

Good luck and greetz,

Peter.

Share this post


Link to post
Share on other sites

Hi folks,

I'm brand new here and wanted to get straight in on this thread, my ST3500320AS 7200.11 500gb died (suddenly) a couple of days ago, it was part of a raid0 array, and I have months....years worth of stored data and I don't back up often enough (yes I am an id*** for putting so much trust in a raid0 array)

I figured i had the BSY problem as my drive was not showing up in BIOS and not booting up, I have religiously followed the teachings on this and some other forums from some very selfless and clever people and I have collected all the relevant materials for carrying out the fix on this, I ended up getting a dedicatet USB to ttl converter lead from RS components, it works perfectly in hyperterminal and hooked up to the drive, I began the process and got as far as the level 2 part where I enter 'U' and get the 1009 DETSEC spin up error.......now I am much more sensible than to just give up and ask for help when I fall at the first hurdle, I carried on researching the issue and found various peoples solutions for this problem, I really am here now with no other options begging for an assist, I tried EVERYTHING!!! I cant tighten the screws down any more because they will strip the threads if I do, I put the pcb in the oven several times, I have swapped the pcb with the other raid drive which is from a matched pair (thats how I bought them) and I did swap the rom chips.....no change, my only comment is that when i try the spin up command my drive spins up and makes a rythmic clicking sound before stopping and spinning down, sounds like "spin up-whizz-click-click-click-CLICK-whizz-click-click-click-CLICK-whizz-click-click-click-CLICK-spin down", is this bad? should I give up all hope including pro services? is there still likely to be an image on the platters?

the odd thing I had was that after a cople of attempts at this fix the drive started showing up in BIOS, so I thought maybe I had fixed the BSY error by accident and could try the 0lba fix, but no joy, when i go to enter the m0,2,2,0,0,0,0,22 command it just gives an error, it also still shows me that it is still in bsy

I lost my job the day after my comp died so dont want to spend ££££ on pro services, my drive was an OEM so seagate won't touch it.

many thanks in advance for any efforts to help me

Share this post


Link to post
Share on other sites

Had no luck with my first try to get some help :}

Maybe this time...

Hi everybody,

I'm sinking into despair after having tried for two days to fix my Barracuda HD. I hope someone could give me some help :}

Ok, this is my HD: 1Gb, ST31000333AS, firmware LC15.

I've been able to set up the connection between the computer and the HD trough a DKU5 cable. I could complete almost all the steps suggested by Aviko, Gradius and some others, getting the expected messages (spin out, spin up...) in the hyperterminal. BUT the last one: when I write m0,2,2,,,,,22 and click enter I clearly hear the HD stops and nothing appears on the screen, no matter how long I wait.

I've tried everything I've found in this forum and nothing works (covering head, motor, both...). If I shut down the HD after N1, as stated in Gradius guide, it seems the HD returns to the busy state and when I power again the HD the hyperterminal doesn't respond.

I've read almost every page in this thread and I've found a few references to this problem of no response after m0,2,2..., but no solution.

Anyone has a clue?

Thanks

Share this post


Link to post
Share on other sites

Hi,

I am having a little trouble with this fix. My HD is a Maxtor DiamondMax 22. I got all the cables made up successfully and went through to clear the BSY state initially. This seemed to work and all the outputs from Hyperterminal were as expected.

I put it back into the pc (a Dell Dimension 5100 if it matters) and it saw the drive in the bios but the capacity was 'unknown'. I figured I'd try the LBA fix, all outputs as expected, put it back in the PC and the drive was not detected by the bios again.

Ok, so went back and did the bsy fix again including the G-List step, now back in the pc and yay! Detected and found the size (500Gb). Powered down, connected all the drives in the machine, powered up and the drive was no longer detected.

Is it just the firmware problem thats stoppin it working fully or is there something I'm missing? I ended up leaving it last night as I was getting tired and didnt want to make a mistake but I'd really like to get this repaired.

Thanks for any insight.

Share this post


Link to post
Share on other sites

I face a strange problem with solution (i have the busy state problem)<br /><br />When I try the loopback test (connecting RX-TX cables together) i can see what i type in the hyperterminal<br /><br />

When i connect the cable to the hard disk and try to communicate with the disk, all I get is strange characters.<br /><br />

I have tried with **38400,8,N,1,N** and also with **38400,8,N,1,Hardware** with no result

post-284493-4089_thumb.jpg

post-284493-4247_thumb.jpg

Edited by karetsos

Share this post


Link to post
Share on other sites

Hi,

according to description my Seagate 7200.11 is in BSY brick.

I have Siemens IP40 RS232 cable for mobile phones (which is voltage level shifter - so I've been told) and i know which wires i need to use (white is RX, yellow is TX, and black is GND) but i heard that i need somehow to power the drivers which are in RS232 connector (Vcc - the red wire in cable). Full info received from a guy who knows Siemens serial cables is following:

"the Vcc is to power up the drivers which are located in the RS232 connector of the cable. Without the power for these drivers you will not get a connection. This cable is a voltage level shifter so you have to connect the

red Vcc cable to the logic-power-supply of the harddisk (normally 5V I suppose). On the RS232 connector for the PC side you will have voltage-levels of about +/-12V which is normal for RS232 connections! Therfore there is a level-shifter-driver included in the RS232 connector which need at least the power from the target device, in your case from the hard disk."

Now, since i am not engineer I would kindly ask people to simply (electronical schemes do not mean much to me as I do not know how to read them, so please be specific and simple as much as possible) tell me how to do this (powering the cable)? My idea about powering the HD was to simply connect the drive to SATA USB external housing - but what about the power to the cable?

Many thanks for assistance :-)

Share this post


Link to post
Share on other sites

I've now managed to get my drive back up and running.

Thanks to the OP for the information, saved a lot of inconvenience!

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