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

Bricked HDD does not always make sounds when you put power on (they sometimes just behave like a typical brick newwink.gif). Try the whole procedure carefully again. Did you try the suggestions in the FGA # 4?

Good news; the strange fact here is that the HD did make a startup noise, and now it doesn't...

Share this post


Link to post
Share on other sites

It seems to me like you missed some (most) of the actual Read-me-first (the part that says DO NOT use a CA-42 cable unless you know what you are doing :whistle: ).

Anyway, it is possible that you simply "bent" a little the contacts (by using a too thick piece of paper) :unsure:.

The general idea is to always check if the interface can communicate with the HD AFTER a successful loopback test but BEFORE loosing the screws/inserting the cardboard.

It is possible that you fried the PCB :ph34r:, but not very likely :) (you should have seen smoke coming out of it, or visible burns on a chip or your power supply would have shut down because of a shorted TVS diode).

A good idea would be to completely remove the PCB, thoroughly verify visually contacts AND clean them, then try mounting back the PCB tightening the screws firmly (compare with Isaac Asimov's take on this):

http://en.wikipedia.org/wiki/Risk_(short_story)

http://www.rogerclarke.com/SOS/Asimov.html#Expt

* The ambiguity and cultural dependence of terms

Any set of "machine values" provides enormous scope for linguistic ambiguity. A robot must be able to distinguish robots from humans. It must be able to recognize an order and distinguish it from a casual request. It must "understand" the concept of its own existence, a capability that arguably has eluded mankind, although it may be simpler for robots. In one short story, for example, the vagueness of the word firmly in the order "Pull [the bar] towards you firmly" jeopardizes a vital hyperspace experiment. Because robot strength is much greater than that of humans, it pulls the bar more powerfully than the human had intended, bends it, and thereby ruins the control mechanism.

See here for reference:

:hello:

jaclaz

From your description, I really don't think I fried pcb. This is good news :)

I'll try to clen headers, hope that's the problem. Thanks so much !!

UPDATE:

I just noticed that if I keep ear very close when I plug-in the power I can hear a very low periodical (0.5 sec) "tik" ...note I'm not asking help specifically on the procedure, I'm just asking if in your opinion my HD is still alive and if I should keep trying the procedure, maybe buying a serial adapter or something more successful.

Edited by kikko

Share this post


Link to post
Share on other sites

Thanks JACLAZ for pointing me to the right direction, and also for posting up a wealth of information on this site. Yes, I was in a hurry.

You should take it a little easy though... seems like you are angry half the time in all your posts and might be becoming a bit of a RACIST, lol... read "only two little indians remain" in...

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page__st__3345

Seriously though, thank you. Will spend some time looking around the other pages to get my HD issue resolved.

Edited by novajohn23

Share this post


Link to post
Share on other sites

I just noticed that if I keep ear very close when I plug-in the power I can hear a very low periodical (0.5 sec) "tik" ...note I'm not asking help specifically on the procedure, I'm just asking if in your opinion my HD is still alive and if I should keep trying the procedure, maybe buying a serial adapter or something more successful.

Bricks are known in some cases to still have a heartbeat newwink.gif Try some open heart disk surgery (with this fix) to revive it.laugh.gif

Share this post


Link to post
Share on other sites

You should take it a little easy though... seems like you are angry half the time in all your posts and might be becoming a bit of a RACIST, lol... read "only two little indians remain" in...

I am not at all "angry", I am simply (and "by design" ;)) VERY grumpy as this approach usually allows for messages to better go through when normal, plain approaches, like writing tutorials and howto's that are not read do fail. :whistle:

jaclaz

Share this post


Link to post
Share on other sites

Been going through everything here trying to figure out the right setup for what I have but so far unsuccessful! Before I describve what I'm doing, I have searched and looked all over the internet but found no relevant information.

I have a USB to TTL adaptor I bought from someone on ebay. There is no brand name on it, all I know about it is that it has the prolific chipset, then has connectors for rx, tx, gnd, 3.3 & 5v ... I have tried using it but whenever I use hyperterminal or putty I get an error saying it could not connect to com3 - I tried in XP and on my windows 7 machine but no go. Seems to be non function - would this be the right assessment? I also tested with a loop back (only with rx/tx connected together) and did nto get a reply but was able to send the data (as per the read out from 232analyzer).

I went to radioshack to see what they had onhand and found a usb to ttl cable for scanner radios - has the ftdi232bm chip on it, successfully installed in windows 7 (and in windows xp) and can get the loopback working no problem. I'm assuming the other cable is a ground. I cannot get to the f3 > prompt to do anything to the drive - and it is a good, working drive i'm testing on!

In the main guide i didn';t see anything really mentioned about grounding, but in the other read me it says to ground everything. I tried just using the sata power connecter from my desktop to the drive, then the rx/tx from the usb adaptor and got nothing. I then attached the ground from the adaptor to the drive, got nothing. Finally I grounded the adaptor to one of the black ground cables coming from a power connector in the computer, also grounded the hdd to the same one - so everything that has a ground is connected to the black ground cable from the PS in my desktop.

still nothing.

Any ideas? Also, would it be prudent of me to attach the ground from the usb to ttl (the one that throws the could not connect to comx error in hyperterminal and putty)to the negative on a pair of batteries and send the + on the batteries to the 3.3 on the usb adaptor? Unfortunatly the item I got from ebay did not have instructions or anything, only the part.

The radio shack scanner cable i'm using is definitely ttl (loop back works) and is model number 20-047

ANY help is greatly appreciated!!

Share this post


Link to post
Share on other sites

ok, nevermind! Got it all working - it was due to a couple factors. Firstly, the drive I was testing with was a 7200.10 - not a 7200.11 - this means you have to use the baud rate of 9600 instead of 38400.

Other thing that was not right was the grounding. It is not at ALL clear what to ground. The cable I used was the 20-047 scanner programming cable from radioshack - they wanted to get rid of it and sold it to me for $8. It has a red, white and ground - the ground is the shield around the cable, black and green inside the cable aren't used and red is rx, white is tx. So - shield = gnd, red = rx, white = tx ... the guide explains to connect the rx and tx clearly and how to do it BUT I had to run a cable from the gnd on the hdd to the gnd coming off the ps of the desktop, then also ground the gnd cable on the adaptor to the same place.

Adaptor rx --> tx on hdd

Adaptor tx --> rx on hdd

Adaptor gnd --> black gnd on power supply

HDD gnd --> black gnd on power supply

for 7200.10 drives use 9600 baud rate (otherwise output is gabled, this is an indication)

for 7200.11 drives use 38400 baud rate and follow this guide! ENJOY!

Share this post


Link to post
Share on other sites

ok, nevermind! Got it all working - it was due to a couple factors. Firstly, the drive I was testing with was a 7200.10 - not a 7200.11 - this means you have to use the baud rate of 9600 instead of 38400.

Hi bryeds,

Glad you managed to fix itthumbup.gifthumbup.gifthumbup.gif

People normally battle to unbrick the 7200.10 drivesohmy.gif. Can you please give a detailed description here for people who has this problem in future. Thanks.biggrin.gif

Share this post


Link to post
Share on other sites

I didn't have a problem with the 7200.10 drive, I just assumed the 7200.10 drive I was testing on would be the same as connecting to the 7200.11. If I fried the 7200.10 by making a bad connection or something, it wouldn't matter, thus the reason to test on it to make sure the cable worked.

On the 7200.11 drive the client had a power surge near their home, a transformer literally blew up, knocking out the power. When they turned the computer back on the system appeared to be frozen but I found otherwise after removing the drive. I searched for info about the drive to replace the circuit board and found the information here. Common BSY issue was all. Fixed not with the $6 part w/ $20 shipping but with a $35 cable I got for $8 at a radio shack dealer in town - an amazing feat considering the closest walmart is 45 min away, there's nothing here, but I was able to find that darn usb to ttl cable!

Share this post


Link to post
Share on other sites

I didn't have a problem with the 7200.10 drive, I just assumed the 7200.10 drive I was testing on would be the same as connecting to the 7200.11. If I fried the 7200.10 by making a bad connection or something, it wouldn't matter, thus the reason to test on it to make sure the cable worked.

On the 7200.11 ... Fixed not with the $6 part w/ $20 shipping but with a $35 cable I got for $8 at a radio shack dealer in town -

OK, so you just tested it with an unbricked 7200.10 to see if you can communicate with the hdd before you actually used it to unbrick the 7200.11?

Share this post


Link to post
Share on other sites

Yes - wanted to blow up the unneeded 7200.10 instead of the 7200.11 I was working on incase I did something wrong! Didn't blow up anything though!

Share this post


Link to post
Share on other sites

Yes - wanted to blow up the unneeded 7200.10 instead of the 7200.11 I was working on incase I did something wrong! Didn't blow up anything though!

Thanks for the clarificationsmile.gif Just thought (or rather hoped) we might have a confirmed case of someone who managed to unbrick a 7200.10, but seems like we have to wait a bit longer.

Share this post


Link to post
Share on other sites

There is a confirmed case of someone fixing it - this is how I figured out that the baud had to be lowered to 9600 to talk to the 7200.10 drives. This is from last october ... Here's the link: http://www.msfn.org/board/topic/133604-seagate-720010-hdds-how-to-fix-bsy-state-too/

Well, NO. :(

That's EXACTLY an example of an UNconfirmed report!

The OP was NOT sure about:

  • what the problem actually was
  • what EXACT steps/procedure he used
  • what THEORY was behind the set of commands he issued

AND he admittedly was "half drunk" at the time he presumably "fixed" the drive.

Since then noone else posted useful/meaningful info.

Mind you I am not saying that what was reported never happened, only that there is very little confirmation about the method used (and on the actual cause of the BSY state - if any ) of the drive.

If you prefer, we know we do not know. ;)

jaclaz

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.

×