Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4759 replies to this topic

#2351
iuliangt

iuliangt
  • Member
  • 4 posts
  • Joined 03-January 10
it is very nice that people try to solve problems by them own, butt an expert will be always an expert.... he knows think, that's WHY im writting this post: try first speaking with those from seagate, open a case like me, and your problem will be solved if the harddisk is one of those thats fails.
Here is what i DO:

on 1 of January my MAIN DATA storage HDD went missing in BIOS (over 20 GB of personal FOTO - like all my life, more than 80 GB of personal video) and NONE where ever backed UP because i trusted SEAGATE to be a good BRAND. I got crazy in 2 days.... then i start searcing the WEB - GOOGLEIIITTTT for my problem, i found this forum and many more, a lot of videos on your tube of how i can revive my HDD, butt also found UP that seagate do RECOVER the DEAD HDD, and i try with them first because they Are PRO after all (not all of them, especcialy those who work on FIRMWARE development)

so last week, after I document most of the web resources, I Opened a case on seagate forum, talk to some DUDE's on chat, and all redirect me to Netherlands i365 HeadQuarters (I am from Italy - Rimini area), The Guys from Netherlands where more than nice to me, they told me everything, and on Thursday 17:45 i drop my HDD to a TNT depo, on Friday 11:45 the HDD was receive in Amsterdam - Main Labs... at 15: 30 it got to the tehnicians and at 15:45 the hard drive where SOLVED, all data recovered (Firmware flashed) , saturday and sunday are dead days... and Monday my HDD where shiped back, Tuesday at 12:30 i got my HDD back HOME, and start backing UP all my data to : 1 TB external Drive (Movies/Music/and other stuff) 1of80GB+1of120GB+1of 250GB small HDD where i putt all my pictures and videos (that's right = TRIPLE BackUP of my very important data) i'm considering also 1 pack of DVD .

so first just stay and think one moment, if u dont want to loose all data, try the professional first, or ask some professional HELP, if u dont have important data .. don't bother buying cable that don't work or wait for parts, from my search on eBay i found cables that where made especially for this type of problem (already tested), consider that is 1 year and 1 month since the problem of BSY and 0 LBA problem beggin, people are resourcefull, and will make money out of everything. Just Start Your search on Ebay, or other Search Engine with Seagate Fix :)

Thanks Gradius That even if he did'nt discover the SOLUTION, he try to understand IT and Share IT with all of US with HDD problem
Thanks avikus for perfetting the solution, and all of U that are still here helping people that are in NEED.

And ThanKs i365 TEAM for reviving my HDD.

PS: I'm at page 61 on this tread, and still reading true :)


How to remove advertisement from MSFN

#2352
lcoughey

lcoughey
  • Member
  • 5 posts
  • Joined 24-March 09
  • OS:none specified
  • Country: Country Flag
aha,

I suspect that your problem is much larger than a firmware issue. In this case, if your data is important to you, send it to a qualified data recovery lab for an assessment...before it is too late.

Error 1009 DETSEC 00006008
Spin Error

This implies a problem with the drive spinning. Could be a problem with the motor itself, or the PCB.]

Elapsed Time 7 mins 17 secs
R/W Status 2 R/W Error 84150180

This implies that the heads are unable to read/write the drive. It could be because the drive is not spinning, at least not to full speed. Or, it could be that the heads are bad. Again, get a professional to assess the drive...otherwise, just get your warranty replacement. This is not a DIY job.

Good luck!
Luke

#2353
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,689 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

PS: I'm at page 61 on this tread, and still reading true :)


...wait until you get here:
http://www.msfn.org/...o...807&st=2323

The linked to post was the consequence of a number of reports about people that were told by Seagate that :
  • they would have NOT attempted Recovery of the data
  • they would EITHER recover the sent drive OR send back ANOTHER working one
  • they would NOT refund ANYTHING BUT a working drive should the sent drive be lost or damaged during shipping forth and back
  • they would provide DATA Recovery through i365 at a cost ranging from $300 to $600

I am happy :) to know that the good i365 guys, when contacted directly, provided a different arrangement.

BTW, how much was the total cost? :unsure:
Or was it ALL at Seagate's or i365's expenses, including the shipping back and forth?

This said, I personally find the risk of damage or lost during the shipping to be very high, if you have ever seen how packages are usually handled in airports or storehouses you know what I mean ;), and in my view higher than that of fixing at home.

About this:

and NONE where ever backed UP because i trusted SEAGATE to be a good BRAND.

unfortunately the "because" is moot, you should NEVER, and when I say NEVER, I do mean NEVER, trust ANYONE with the safety of your data.
This time it happened to Seagate, but each and every maker has had some "bad" model, and in any case, even if you get a "perfect" drive, there is ALWAYS Murphy's Law around, trying to prove itself right.
Having data on a single media, no matter the manufacturer, is very, very, VERY risky.
ALWAYS make multiple copies, two at the very least, three much better, of ANYTHING you think of value.


jaclaz

#2354
the$#!Za.

the$#!Za.
  • Member
  • 6 posts
  • Joined 21-January 10

Hi all,

As I said earlier I've a Seagate Barracuda 500 Gb (ST3500820AS) not recognized by BIOS and I've tried to follow the guide but the result was:


Hi aha.

I read in another forum someone with that exact error. He started over again from the beginning this time he said he screwed the PCB to the hard drive tighter than before to make sure the heads touch nicely and it worked.

Have you tried recovering drive more than once ??

#2355
iuliangt

iuliangt
  • Member
  • 4 posts
  • Joined 03-January 10
jacklaz all was at the expensive of i365 TEAM, the transport and everything, i did not pay one eurocent, what i can confirm U is that the Seagate DUDE'S redirect me QUICK to i365 Netherlands, and when i say quick i say 1 kick in the B**T...

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


indeed for transport u are right, the package must me perfect (i putt 4 CM of protective foam, not 2...), and i did all i known about packaging, more than this u are right regarding keeping all the important data (personal FOTO and Video) on a single drive , no matter what the brand is, is very risky. That's way now im backing up my important data to 3 external HDD, 1 pack of DVD and even consider upload them to gmail (7GB of free space/mail).

trust me when i say i drop HDD's on the flor and nothing happen , they are still running with no problems, not even BAD sectors, and i see HDD so damage externly that u dont imagine it will work and they did. even so i had multiple MAxtor and Samsung drives that made some bad sectors becouse I move the unit around in the house, one maxtor from 24 kb of Bad Sectors made 35 GB in 2 months, no program was working to secure the bad sectors.

now about this tread; :) wish me luck, i receive an CA-42 Cable that seems to activate COM3 (ArkMicro Chip inside i think), and i want to test it on an very old Maxtor 320 GB, that last year on februarie drop DEAD and he has same simptoms as BSY.; not shown in BIOS butt is working perfectly... (atleast i hear it working). the only problem is that i dont have a new firmware... and is not on the page of HDD market as bad firmware , so im still loocking for an Firmware Update for him..

The model is DiamondMax 21
STM3320820AS, firmware 3.AAE.

PS: The previosly 2 CA-42 CABles prove to be innefective, did not activate any COM, even after i instaled the drivers (payed 14 euro each 2, and this one that work i payed 3 Euro..)
PS2: BTW i remember one old 80 GB Seagate have a pin on the P-ata Contact that was broken... what can i say i putt another thing that looks like a pin and solderit there and is still working :)


BTW thank U for still beeing active on this tread.

regards,
iulian

#2356
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,689 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

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/se..._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.kbklawfir...agate/index.php
CACHE:
http://209.85.129.13...mp;client=opera
EXPIRED:
http://whois.domaint.../kbklawfirm.com
(please note the date it was first created - I like coincidences :whistle:)
http://gizmodo.com/5...-gogo-users-say
http://www.electroni...acuda.failures/
http://www.theinquir...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

#2357
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09
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 :)

#2358
vintagevalves

vintagevalves
  • Member
  • 1 posts
  • Joined 29-January 10
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!

#2359
iuliangt

iuliangt
  • Member
  • 4 posts
  • Joined 03-January 10
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: Posted Image
-with the ground conected: Posted Image


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

#2360
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09

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: Posted Image
-with the ground conected: Posted Image


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.

#2361
iuliangt

iuliangt
  • Member
  • 4 posts
  • Joined 03-January 10
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, 30 January 2010 - 03:02 AM.


#2362
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,689 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

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/...howtopic=138828
http://www.msfn.org/...howtopic=137080
http://www.msfn.org/...o...807&st=1636

jaclaz

#2363
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09
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, 30 January 2010 - 05:17 AM.


#2364
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10
@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

#2365
Anonymous123456

Anonymous123456
  • Member
  • 1 posts
  • Joined 30-January 10
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/...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, 30 January 2010 - 02:09 PM.


#2366
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09

@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, 30 January 2010 - 02:13 PM.


#2367
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10
*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

#2368
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10

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

#2369
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09

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.

#2370
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10

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

#2371
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09

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


I thought you already did that as this is the common method.

Good luck! I fully understand that you don't want to risk you data, at least not any more than necessary.

#2372
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10
Done!
Without jumper
And without cardbord! ;-).

*) I figured out that if you losen the screws, the PCB looses contact to the connector.
*) For each connector there is a screw to to press the PCB against the connector.
--> If you first losen all screws that affect one connector, than you can open and close the contact to the connector with screwing the connector screw in or out.

Attention:
I was wrong: It's not the motor that has to be blanked out, it's the heads (at least at my model).
(was pointed to by: "After the closure of these contacts, the head within 5 ~ 7 seconds klatsayut, then the engine itself stops")

So procedure is:
1) optional: Loosen all screws and lift PCB so far that you can be sure PCB is not stuck at the metal body of the HDD anywhere and remount the PCB
2) Loosen all screws so far that the head connector is dissconnected. Keep in mind that the PCB must not be bent.
3) Tighten only the head connector screw so that it get's contact again
4) Supply power to the disc, wait until you get the LED: blablabla message
5) Keep sending Ctrl Z until you see the F3 T> promt
6) Quickly loosen head connector screw to disconnect heads (it's important to make this very quickly otherwise heads could be at least stressed)
7) If you managed this you have all the time of the world. Continue like described in the guides -> send /2 to change to level 2 and wait 15s and so on

I used terminal V1.9b and made a Makro for each, Ctrl Z, /2, Z.

Regards
Chilli

#2373
alexpalma83

alexpalma83
  • Member
  • 1 posts
  • Joined 30-January 10
Hi guys, i successfully recovered my busy 7200.11 but trying 0 LBA error recovery on the other one i have, the hyperterminal doesn't prompt me the f3 t> beginning message! how can i do? thanks!

Edited by alexpalma83, 31 January 2010 - 04:28 AM.


#2374
Chilli

Chilli

    Newbie

  • Member
  • 30 posts
  • Joined 30-January 10
At the previous post I ment Strg z (low case) or ASCII(026 dec).

Now I have sucessfully recovered the HDD but the flashtool refuses to flash the drive (see attachment).
Maybe because it's an OEM drive?

I don't really know from which OEM vendor or model this is. It might be a coincitance that FSC is short for Fujitsu Siemsn Computers, but might also be that this comes from a charge detemined for FSC.
I guess there is a trick for reflashing OEM HDD?

Regards
Chilli

Attached Files



#2375
MadOCer

MadOCer

    Newbie

  • Member
  • 37 posts
  • Joined 02-August 09
You simply cannot use the standard flash tool on drives that have other firmware versions than the ones listed on the seagate page. If the drive is OEM, you have to contact the OEM for a flash upgrade tool. ;) Or Seagate and ask them, if they are willing to help, given the circumstances.




2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users