Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

This is the problem that I have. I have the st31000340as 1tb drive from thailand with original firmware sd15, and it recently failed. However, I have been able to access it via the bios and upgrade firmware sd1a. Now, upon returning to windows, the drive is found, and it shows that I have 499 of 931 free. OK. The problem is when I open it up. It takes a few seconds to spool through and find my folders. After the green bar in the status bar reaches full, the folders appear in Explorer. From there, the drive freezes, i cannot copy the data over. Explorer freezes and then I have to click the x and close program. Is my problem different? I'm thinking if I try to do a level format, all the data will be erased. I run seatools from dos and get fail on all tests because it cannot read the drive.

Help?

0

Share this post


Link to post
Share on other sites

Can someone help me with configuring Putty properly to access my USB port, once I have connected my drive with a USB - TTL adapter?

The more detailed the info the better. There appears to be several different settings that need to be adjusted on the left panel of Putty.

Obviously, I do not have a serial port and do not have Hyper Terminal since I am running Vista 64.

Any help is appreciated.

Edited by bill4d
0

Share this post


Link to post
Share on other sites

i tried to boot the pc one day, and it wouldnt.

got the pc to a lab, they said, hd isnt beeing recognized.

didnt take me long to find out all about the 7200.11 seagate saga.

i tried the fix in sites.google.com/site/seagatefix , i didnt have the rs232 to ttl so somone made one for me from a circute i found on the web.

i tried the fix and than, hd was detectble. i could see every file in dos ona different pc than mine i could not load vista on that drive it had some file missing, but it did try to run vista.

i took the drive and conected it to a different pc as a non os drive, just to take the files out.

it was recognized.

it took it a while but it found drive d and i could see all the files there (pics were opening in thumbnails,it was all there) c: wasnt detected and said that drive needed reformating.

i started to copy d: to back up, i got 5 min of backup and d dissapeared. i got about 6 gigs of stuff that was mosly backed up, didnt get the unbacked stuff.

next time i booted both c and d were detected but un avalible, next hd wasnt detected by bios. sometimes it was sometimes it wasnt but c and d werent even in my computer anymore.

and every time i start it gives 3 clicks of death and starts spining.

i sent drive to a data recovery company, after 24 hours they said it had a head crash and nothing is accessible (but i suspect its a company that doesnt try to do anything if it takes too long to fiddle with the drive)

my question is, if it was a head crash how come using the fix revived the hd for a short time,

is it possible i did the fix wrong and the pcb is screwing the hd reading attempts?

all the other company did is open the cover and look, they didnt try anything else.

any sugestions?

(yesterday i got the original rs232 to ttl actually used in the fix from vendor the guy fixing it used mybe using it would work?)

thank you

0

Share this post


Link to post
Share on other sites

Two different questions, and unfortunately NO definite answer.

First question:

Did I do the appropraite steps?

Who knows :unsure:, it is very well possible that your hard disk suffered from ANOTHER problem at that you did all the "RIGHT" steps, but for the "WRONG" problem, or it is as likely that you did the "WRONG" steps on the "RIGHT" problem.

Unless the DIY interface was assembled by a demented moron, it should have made no difference, even if it was put together by a headless chicken, three possibilities:

  1. it works, i.e. you can issue data in the hyperterminal and get feedback
  2. it doesn't work, i.e. you CANNOT issue data in the hyperterminal and/or CANNOT get feedback
  3. it fries the PCB of the drive

Since from what you report #2 and #3 didn't happen, I guess that the converter is OK. :)

i sent drive to a data recovery company, after 24 hours they said it had a head crash and nothing is accessible

That is NOT a data recovery company, it is probably some kind of guy that "recovers" data in his basement or they didn't tell you all, or you omitted to say that you experienced several minutes of a hard grinding noise coming from the hard disk. :w00t:

A "head crash" technically is when, for whatever reason, including verticall acceleration beyond the sustainable one by the drive (i.e. falling) one or more heads come in contact with the magnetic surface of one or more platters.

The damage to DATA is limited to those parts of the disk surface that were actually "engraved" by the contact, unless, as said, the drive has been kept spinning with the head "locked" in contact and the head arm has been made travel on all the surfaces.

On multiple platters drives ONLY ONE surface of ONE platter (where the head crashed and that was used to "broom" all over) will be damaged.

Otherwise it would be a multiple head crash, pretty much rare, i.e. since all platters are "double face" it would mean that all superior heads crashed on all superior surfaces and that all inferior heads crashed on all inferior surfaces, something that I would deem as very, very improbable.

It is usually possible, but you will need to find a reputable recovery company and it will cost you a lot of money :(, to "transplant" the platters from your "deceased" drive to another "alive" one and thus recover at least part of the data.

jaclaz

0

Share this post


Link to post
Share on other sites

Frustrating... finally the generic CA-42 cable showed up and I installed the Nokia drivers that came along with it. The cable is recognized in device manager as a USB to serial controller but no drivers installed.

Tried this on XP and Win 7 machines, same thing.

Any suggestions I can try while waiting for another cable?

Update - I found the prolific driver for the 2303, installed, cable now recognized but get code 10 - this device cannot start. I think the bargain cable is a dud, a few more hours gone...

Edited by dave2698
0

Share this post


Link to post
Share on other sites

i have a problem with this procedure. seems to me that i have done anything correctly, but i cannot connect to the hyperterminal (nothing appears on the screen when i type (i.e. ctrl+z). what can be the fault?

another questions is the foll:

if i will purchase another (similar) 7200.11 hdd, update the firmware and then replace the PCB of the new/working HDD, with the PCB of the daffective HDD, will this work, so as to at least recover my data from the old HDD?

thnaks beforehand for your assistance

0

Share this post


Link to post
Share on other sites
i have a problem with this procedure. seems to me that i have done anything correctly, but i cannot connect to the hyperterminal (nothing appears on the screen when i type (i.e. ctrl+z). what can be the fault?

I have the same prob aswell. => without my visit card the LED 000000CC msg appears in the terminal; with it I can't get in command mode using ctrl+z. I already tried with HyperTerminal and PuTTy

When I patch through RX and TX leads on the cable to test it the cable does seem to work correctly.

Any help is very much appreciated!

My HDD does have the new firmware BTW, maybe that has something to do with it?

Edited by mindcrash
0

Share this post


Link to post
Share on other sites

Wholly smokes...110 pages and still no slowing down

My JBod setup would not rebuild as I had previously posted the question..could a JBod setup be saved?

I used "Carter in Canada's" method and found all the necessary bits and pieces including the special cable he mentions.

It was available from both TigerDirect.com or TigerDirect.ca. This was the SATA to Floppy and Molex connector.

I followed everything he says with the exception of using the breadboard and I used the Windows version of Seagate's fix instead of the hard boot image he recommends.

All 4 drives have been updated to the new firmware and all are working.

Unfortunately, the JBod setup could not rebuild my lost data and all my six years of data was lost.

Still, his method works without a hitch and the stuck 1 terabyte drive was repaired faster than his examples.

JBod setups just don't save their data well under these circumstances.

I don't know the guy, but I was willing to get all the bits and pieces he mentions if there was even the slightest chance of retreiving my data. By the time I paid shipping, it cost me close to what a one 1 terabyte hard drive would have cost but I was determined that I would at least know I gave it my best shot.

To save anybody from searching through these pages for him just copy and paste this link:

http://www.mapleleafmountain.com/seagatebrick.html

As I said in a previous post, I was looking for an easy method that could be used by most people and the parts could be easily found.

This was the best route for me (I hate taking the chance of burning up something with solder or frying something because I didn't ground something.)

Thanx for all the info you guys & gals, you're doing an amazing job of trying to answer everyone's different setup. I learned some things I didn't know before.

0

Share this post


Link to post
Share on other sites
i have a problem with this procedure. seems to me that i have done anything correctly, but i cannot connect to the hyperterminal (nothing appears on the screen when i type (i.e. ctrl+z). what can be the fault?

Already figured this one out for myself. You need to power the brick HDD from the same box as where you connected the drive to. Else RX will work, but TX won't

if i will purchase another (similar) 7200.11 hdd, update the firmware and then replace the PCB of the new/working HDD, with the PCB of the daffective HDD, will this work, so as to at least recover my data from the old HDD?

I wouldn't advise to try this. I never had to do this, but I read enough about it that I'm 99% sure that you will completely frack your HDD without any chance to make it work ever again.

Also note that SD1A has the same probs as SD15. I updated my Barracuda when Seagate made the final (fixed) release of the new firmware and it still managed to brick itself.

So I would advise: unbrick your Barracuda using the given instructions, backup your stuff to a WD or Samsung drive with equal storage size ASAP, then toss away the Barracuda and never buy any Seagate drive ever again. At least that is what I'm planning right now.

Edited by mindcrash
0

Share this post


Link to post
Share on other sites

Thanks, thanks and thanks. Another success history here. I have two hard disk with the same problem and both of them are now up and working perfectly.

The information in Post #1228 was very useful because I used a Nokia CA-42 with the same problem. It needs 3v of external power. As he commented I use a external 3v battery (a button battery).

I also had some trouble with the CA-42 drivers. It olny worked with the originals form the CD that come with the cable.

I'm in Spain, so I guess that the cables sold in Portugal are the same as here. I'm in Extremadura, if anybody need help.

So thanks again to all the people that post in this thread.

0

Share this post


Link to post
Share on other sites

Got a new CA-42 cable. The "old" DKU-5 did not work. Hooked up the CA-42, inserted the paper card between the PCB and head connector, hooked up the HD to an independent power supply and, launched the hyper terminal, everything worked just fine. I used this guide. Got to the point when I should enter: m0,2,2,0,0,0,0,22 HD spins down. Nothing happens for 30 minutes. Turned off. Repeated everything. Tried F712 command and got this response:

Byte:05A1: Expansion = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

This time waited 45 minutes. Nothing. Read another 2 hours not much learned. I've got an SD35 firmware. Maybe that's the issue?

Anyone can help? Please.

0

Share this post


Link to post
Share on other sites

I'm here only to say thanks !!

I'm a man with lucky because from jan-09 i got a ST3500320AS; firm SD15.

I'm used an old usb data cable from samsung cell x486 and work fine; that cable had chip 2303; and google pinouts could see what couples are TX and RX; the only important wire.

How to said; I got a ST3500320AS with the firm SD15; and one day stop and hide from motherboard; whatever; after complete this procedure fine; must be update to last one firmware from seagate or I'm waiting?

Regards.

Edited by Fitap
0

Share this post


Link to post
Share on other sites

Yiheeeeeeeeeeeeyyyyyyyyyyyyyyyy. I did it. +1 for gradius. Actually I used this help. Wohooooooo!!!!

0

Share this post


Link to post
Share on other sites

Hello, I've been reading as many of the posts i have and have tried to follow the instructions carefully.

My drive is a 7200.11 500gb drive with original firmware being SD15.

I cant seem to get any output from hyperterminal at all (tried on two systems) I cant get a code window to type anything in ever for anything. I know i setup the connection correctly, but no output. Some setting im missing perhaps?

Anyways id like to further explain my problem. I contacted seagate regarding my drive and they suggested that I update my firmware before doing anything else. My drive was showing up in BIOS but reading as 0gb, and I could see the drive in device manager but could not initialize it as it was seen as 0gb. I successfully updated the firmware from SD15 to SD1A as instructed by the seagate people. But the drive still displayed 0gb And I am now attempting this fix.

See my photo of my setup below:

http://s308.photobucket.com/albums/kk335/m...nt=IMG_1625.jpg

I've had no luck with hyperterminal as i cant get an output on any level. Ctrl Z does nothing anywhere. Easy fix?

I've also tried switching the TX and RX wires around and it doesnt make a difference.

I'm sure something similar has been posted multiple times and I apologize for the repeat if present.

Thank you ! :hello:

Edited by majorissuez99
0

Share this post


Link to post
Share on other sites
I'm sure something similar has been posted multiple times and I apologize for the repeat if present.

Yes, it has. ;)

I've also tried switching the TX and RX wires around and it doesnt make a difference.

Is the adapter functional (loopback test)?

Has speed, parity, bits and stop set properly?

Is GROUNDING effective? (from the picture it seems like there is NO grounding)

Re-check everything against this:

http://www.mapleleafmountain.com/seagatebrick.html

jaclaz

0

Share this post


Link to post
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.