Gradius2

The Solution for Seagate 7200.11 HDDs

4,910 posts in this topic

let's not give bad credit to people that do GOOD JObs... if u wanna get mad, get it with those who made the wrong Firmware.. and REFINE it after 3 - 4 months...

On the contrary I seem to be the only one making a distinction. :whistle:

In my personal judgement not only the guys at i365 :thumbup , but also the Seagate engineers are good guys after all, as said an hiccup can happen to everyone, they made a mistake, ok, but they made several other drive models working fine, if they would simply make some public excuses I would forgive them allright.

What I find simply awful are the behaviours of (in no particular order) :realmad: :

  • Seagate Marketing and Company Executives (for trying to deny the evidence for months and later trying to severely underestimate the phenomenon)
  • Seagate Assistance and Customer Care (for simply lying to Customers for a considerable amount of time and for often giving deceiving and incorrect information - and this behaviour has not yet ceased)
  • Seagate Forum Administrator and Mods (for applying senseless censorship deleting reports in the desperate effort to minimize or hide the problem)
  • Seagate Press Office (for avoiding replying to many legitimate questions of bloggers and on-line magazines)

Most probably the Company was afraid of another Class Action, like the one they already had:

http://apcmag.com/seagate_settles_class_ac..._capacities.htm

There were rumours about a (supposedly reknown) Law Firm willing to start such an action:

http://www.bluescreenofdeath.org/?p=91

though the actual said Law Firm site is (alas?) no more :w00t::

http://www.kbklawfirm.com/seagate/index.php

CACHE:

http://209.85.129.132/search?q=cache:rPRvR...mp;client=opera

EXPIRED:

http://whois.domaintools.com/kbklawfirm.com

(please note the date it was first created - I like coincidences :whistle:)

http://gizmodo.com/5130702/1tb-seagate-bar...-gogo-users-say

http://www.electronista.com/articles/09/01...acuda.failures/

http://www.theinquirer.net/inquirer/news/1...7200-11-failing

Pretty quick guys over there in Denver....;)

Nonetheless the Company should IMHO be brought to court for the described misbehaviours.

:hello:

jaclaz

0

Share this post


Link to post
Share on other sites

Hi guys,

just for the fun of it (after having revived 4 out of 5 bad Cudas), I bought a 1TB Barracuda ES.2 to tinker with.

Got the drive yesterday and it's a bit strange to say the least.

The drive seems to have the BSY bug for sure, as the HDD LED is constantly lit when the drive is connected on boot up. The drive even is detected by BIOS sometimes, as having 0MB, as usual with this problem.

But now it gets a bit strange:

The drive spins up, or let's say it tries to and you can hear a good amount of clicking going on. That clicking seems to be caused by the drive moving the heads around quickly. It doesn't sound like grinding on the platter or something. Just like randomly moving the heads without direction. Then it spins down after about 5-10 seconds.

I then connected the drive to terminal using my well working FT2232 USB adapter cable and found the drive to be locked in terminal. Shorted the "read-channels", as seen in some guides, and it unlocked the terminal for sure.

Then I tried to spin down the drive, which worked fine. But on trying to spin up, it got me the well known "ERROR: 1009 DETSEC...". Hmm... drive appears to be dead.

But then I thought let's see what the drive reports using the "Ctrl+A" and "Ctrl+L" key-combinations for some info.

And interestingly enough, it said to have FW-Version "SD35" flashed. Yes, "SD35". Now how can that be? I thought SD35 was exclusive to normal Barracuda 7200.11 drives and the ES.2 Cudas used SN0x (x for 1 through 6 AFAIK) numbering scheme. Or am I missing something?

My first guess is that some dumb*** mounted a 7200.11's PCB to that ES.2 drive. I don't know why, but it would explain the Firmware version. And it would explain the random head movement and failure to spin up correctly. How should it with the wrong info stored in flash.

The question now is: Is there a way to tell if this particular PCB belongs to that particular drive?

And could some people with ES.2 drives perhaps check the output of the "Ctrl+A" and Ctrl+L" key-combinations in terminal? That would be interesting.

I mean I don't need that drive or its data back. I bought it purely for the fun of tinkering and getting it to work again would just be a plus, but certainly is not necessary. I'm just curious as to what happened to that thing.

Thanks in advance!

Greets from Bavaria

MadOCer :)

0

Share this post


Link to post
Share on other sites

I complete success after many hours of trial and error. I bought a Chinese CA-42 cable from 'BargainCell' on Amazon for $0.01 + $2.99 shipping.

Stripped back, it only has 3 wires white, yellow, and green. Loopback was perfect with white and yellow. However, no matter how I connected them to the drive I had the 'arrow problem' where Ctrl+Z echoed back and I never received the F3 prompt. I tried several combinations of grounding the green to the PSU cable with no luck. Tried green to the third pin on the drive and this caused a 'no arrow' condition. Then while moving the drive around and POUNDING ON ctrl+z out of frustration, I received ONE lonely F3 prompt as a tease. I knew there had to be a way. I figured out that grounding the green wire to the chassis of the drive did the trick. I proceeded through the directions, and all is now well in seagate land!

Thanks for this thread!

0

Share this post


Link to post
Share on other sites

i am stuck :( , this is my 3'th CA-42 cable, that seems to work (it is a ArkMicro chip activating COM4)

My HDD is a Maxtor DiamondMax21 STM3320820AS , firmware 3.AAE, and does have same simptoms of a BSY HDD (BIOS can NOT see him even if it working fine - no click of dead BTW)

i did all stepts that requiere to identify TX(Green), RX(White) and GND (Red) ; the cable has 6 wires (yellow, blue, orange,green, red, white) (match them 2 by 2)

Green and White are working wonderfull in the loopback conection, butt the Red wire + Green/White only give me garbage characters if i touch them, not when i typed on terminal....(this must be the problem, idk...)

anyway I conect my HDD (all conected PCB from HDD, no card betwen them) to check for the ERROR (Led ERRORS Adress000...) and i have this thing on terminal:

- no GND conected: 0test.th.jpg

-with the ground conected: 1test.th.jpg

Can anyone Help ME? anyone that had this type of ''error''??

it happens the same even on my laptop where i have vista and use PersonalHyperterminal (trial 30 Days)

btw i get the same result of garbage characters and when im trying only with PCB, detashed from HDD....

0

Share this post


Link to post
Share on other sites
i am stuck :( , this is my 3'th CA-42 cable, that seems to work (it is a ArkMicro chip activating COM4)

My HDD is a Maxtor DiamondMax21 STM3320820AS , firmware 3.AAE, and does have same simptoms of a BSY HDD (BIOS can NOT see him even if it working fine - no click of dead BTW)

i did all stepts that requiere to identify TX(Green), RX(White) and GND (Red) ; the cable has 6 wires (yellow, blue, orange,green, red, white) (match them 2 by 2)

Green and White are working wonderfull in the loopback conection, butt the Red wire + Green/White only give me garbage characters if i touch them, not when i typed on terminal....(this must be the problem, idk...)

anyway I conect my HDD (all conected PCB from HDD, no card betwen them) to check for the ERROR (Led ERRORS Adress000...) and i have this thing on terminal:

- no GND conected: 0test.th.jpg

-with the ground conected: 1test.th.jpg

Can anyone Help ME? anyone that had this type of ''error''??

it happens the same even on my laptop where i have vista and use PersonalHyperterminal (trial 30 Days)

btw i get the same result of garbage characters and when im trying only with PCB, detashed from HDD....

Are you absolutely sure that you have set up the RS232 connection just like it should be (38400 bps etc)?

What you get looks like wrong communication setup.

0

Share this post


Link to post
Share on other sites

yes, 38400 8 N 1 N

butt my hdd is DiamondMax 21, not 22 like the version that are having problems.... i search on forums and i dont find him as a major problem, mine it might be that 1% of HDD failing do BSY.. a rare case , maybe in the terminal i must set UP other conection... idk what to say, today il start my search again maybe ill find my answer somewhere... :(

new edit: i did a small test using my other HDD Seagate 7200.11 ST3500320AS , using same set of settings: 38400 8 N 1 N and i got this on screen:

Rst 0x20M

(P) SATA Reset

the PCB is mounted on HDD... that means that the conection is good... the cable works..... i think for the DiamonMax 21 i need another set of Settings.... because is another class of HDD...

can anyone help me?

:) second edit today in no mear 10 min:

THANK You MadOCer ! :) u send me on the right direction :) using settings 9600 8 N 1 N i got this :

4096k x 16 DRAM

GALAXY - 1_Disk S-6D 09-22-06_15:48

Buzz HM SFI

(P)SATA Reset

DiskAccess ReadSector EC=47 at ffffffff.00.0002

DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys

DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys

DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys

DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys

DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Failure!

DiskAccess ReadSector EC=47 at ffffffff.00.022b

Failed sys sect. write! Nwt Er 00 RdWr 15e4c.00.022b

DiskAccess ReadSector EC=47 at ffffffff.00.0080

DiskAccess ReadSector EC=47 at ffffffff.00.0080

Unable To Load Overlay 01|000A

T>

i got no IDEEA what it means, butt :) I HAVE COMMUNICATION :)

any ideea???

Edited by iuliangt
0

Share this post


Link to post
Share on other sites
any ideea???

Yes, but you won't like it. :(

This thread is not populated by hard disk recovery experts, by chance (and hard work, and guessing and a lot more things :)) a specific solution to two specific problems of a specific hard disk model "surfaced", "escaping" the Sancta Sanctorum where this kind of info is kept by the professionals (usually guarded by a couple of leopards ;)).

"Extending" this solutions to ANY problem on ANY hard disk model is simply not going to happen, unless some more specific to your drive model info comes out.

The principles should be the same, but as well as the connection speed, also the internal "language" of the disk is different,

Sadly, you are in the wrong place. :(

See similar examples:

http://www.msfn.org/board/index.php?showtopic=138828

http://www.msfn.org/board/index.php?showtopic=137080

http://www.msfn.org/board/index.php?showto...807&st=1636

jaclaz

0

Share this post


Link to post
Share on other sites

I just realized something simple, yet perhaps quite important.

The ES.2 1TB drive that I have here is named ST31000340NS, but there is a very similarly named 1TB Barracuda 7200.11 drive, known as ST31000340AS.

Could be that someone accidentaly flashed his ES.2 drive with the SD35 firmware for the Barracuda 7200.11. Anyway, in the meantime I thought about it some more and the scenario that someone swapped the PCB becomes more and more unrealistic. So the mistake while trying to flash the drive seems more and more likely.

Edited by MadOCer
0

Share this post


Link to post
Share on other sites

@MadOCer

I think that the NS are the OEM parts. But that might be too easy ;-).

@all

I've a serious problem (sorry for little cross post but this seems the right place):

My ES.2 ST3500320NS Firmware FSC6 (??) has obviously the BSY problem.

(What is FSC6? Where there some fujitsu siemens equiped with it... ?)

My problem: As soon as I disconnect the motor or the heads (or both) the HDD won't communicate anymore.

As long as both are connected, I have communication. I can even send the spin down command by a quick sequence of Ctrl z, /2 and Z (using a terminal with Macros) but than I get the busy reply because I was to quick. I can not make it slower because than HDD goes into it's failure loop (sends busy informatino about all 8s).

I'm really stuck.

What's about the second service connector that is also connected to the same serial interface? Any possibilty to get the drive into bootloader and flash it via serial?

Is the faulty log pointer at a different memory address for every firmware or would it be possible to reset it with a poke to a good state (if a poke could be done before drive get's busy)?

I made a boot disk for ST3500320AS. If I ever can recover my drive from BSY error, can I use this or would I screw up my drive finally? (sorry for not going throuch all 119 pages but I allready get complaints from my family for sticking at the computer all day and night)

Misc.

*) The Serial inputs of the processeor are protected by serial resistors that prevent to blow it's clamping diodes when applying 5V level.

*) I don't knwo why so many use USB to Serial + Serial to TTL, when you can both in one (TTL-232R-5.0V works fine)

*) Rx and TX are correctly in this articel and wrong in some others (you have to cross Rx and Tx of HDD and Computer cable)

Regards

Chilli

0

Share this post


Link to post
Share on other sites

Thanks to all of your for your advices, I successfully recovered my HD using the solution from this post (ie USB cable) : http://www.msfn.org/board/index.php?showto...mp;#entry883939

I had the "Error 1008 DETSEC 0000500D", so stopped the spinned down the motor a second time (using "Z"), screwed up ALL the screws (I had screwed all but the "center" one), and retried spinning up ("U") and it worked !

Cheers

Anonymous

Edited by Anonymous123456
0

Share this post


Link to post
Share on other sites
@MadOCer

I think that the NS are the OEM parts. But that might be too easy ;-).

@all

I've a serious problem (sorry for little cross post but this seems the right place):

My ES.2 ST3500320NS Firmware FSC6 (??) has obviously the BSY problem.

(What is FSC6? Where there some fujitsu siemens equiped with it... ?)

My problem: As soon as I disconnect the motor or the heads (or both) the HDD won't communicate anymore.

As long as both are connected, I have communication. I can even send the spin down command by a quick sequence of Ctrl z, /2 and Z (using a terminal with Macros) but than I get the busy reply because I was to quick. I can not make it slower because than HDD goes into it's failure loop (sends busy informatino about all 8s).

I'm really stuck.

What's about the second service connector that is also connected to the same serial interface? Any possibilty to get the drive into bootloader and flash it via serial?

Is the faulty log pointer at a different memory address for every firmware or would it be possible to reset it with a poke to a good state (if a poke could be done before drive get's busy)?

I made a boot disk for ST3500320AS. If I ever can recover my drive from BSY error, can I use this or would I screw up my drive finally? (sorry for not going throuch all 119 pages but I allready get complaints from my family for sticking at the computer all day and night)

Misc.

*) The Serial inputs of the processeor are protected by serial resistors that prevent to blow it's clamping diodes when applying 5V level.

*) I don't knwo why so many use USB to Serial + Serial to TTL, when you can both in one (TTL-232R-5.0V works fine)

*) Rx and TX are correctly in this articel and wrong in some others (you have to cross Rx and Tx of HDD and Computer cable)

Regards

Chilli

Your disk could be locked in terminal, so this link might help:

http://book-lab.ru/7200_11.html

No guarantee though. It did help with the lock on my ES.2, though.

BTW, a little update on my ST31000340NS (BTW, yes it is a OEM disk, but the N just stands for the ES.2 version instead of the A for the 7200.11 standard Barracuda):

My ES.2 really got flashed with the wrong (i.e. 7200.11 SD35) firmware. How Do I know, you ask?

Well, easy enough: As I already mentioned the drive is recognized on boot up and shown in BIOS as 0MB. Well, I had a more precise look today and sure enough it said "ST31000340AS" in BIOS and boot up screen. Now one could guess that someone just screwed on the PCB of a 7200.11 SD35 firmware based drive. You ask why I'm quite sure this is not the case? :D Using the CTRL+L and CTRL+A commands when only having the PCB connected, I got to see the drives serial number (S/N), which matches the printed S/N on the casing. So this PCB does indeed belong to this HDD.

The question remains however, how someone did actually manage to flash a SD35 7200.11 firmware onto a ES.2 drive.

And the even more important question:

How do I get the drive as far as being able to flash back a correct ES.2 firmware. Really strange case. :D

Edited by MadOCer
0

Share this post


Link to post
Share on other sites

*wow*

I have a hard time with the russian page.

Not sure if I need jumper of picture 3 or 4. Guess picture 4 because the print matches closer mine.

Seems to me as we make a shortcut by purpose... Somhow I have no good feeling.

I will postpone the operation to tomorrow.

I'll keep you up to date.

Hope I will not kill the drive...

Regards

Chilli

0

Share this post


Link to post
Share on other sites
The question remains however, how someone did actually manage to flash a SD35 7200.11 firmware onto a ES.2 drive.

I'm still sure that you can flash the firmware over serial via bootstrap.

There you could flash what ever you want.

But I don't think this applies for you disk becaus that would mean someone from Seagate service screwed it up... ;-)

0

Share this post


Link to post
Share on other sites
The question remains however, how someone did actually manage to flash a SD35 7200.11 firmware onto a ES.2 drive.

I'm still sure that you can flash the firmware over serial via bootstrap.

There you could flash what ever you want.

But I don't think this applies for you disk becaus that would mean someone from Seagate service screwed it up... ;-)

I doubt that some Seagate employee screwed it up. Perhaps they screwed up the flash software, in the way that it didn't stop the process, when detecting it was the wrong drive.

Anyway, back to you problem:

You just have to find the pic that shows exactly the same PCB layout as yours. And even if you can't find a match it is possible to locate the points on you own. You would just need some highres pics of the PCBs fronside (the one facing the drive's body). And you should have a digital multimeter, to check for direct connections.

And BTW, it's not that dangerous! You are not shorting power supply pins (i.e. big sparks flying etc.), but low voltage and current signal pins.

0

Share this post


Link to post
Share on other sites
And BTW, it's not that dangerous! You are not shorting power supply pins (i.e. big sparks flying etc.), but low voltage and current signal pins.

I thought rather about shortcutting the predriver of the motor.

And that's why I first will try to apply the cardboard in the moment described at the russian page. Ther is at a 80% chance that it makes the same job as the jumper ;-).

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.