[BetKing]

The PSU I used and have been using, and it's almost 20 years old (15-16), but I dare you to say it's not any good. It was built in "the good old days".

It's been through hell and back, and still works 110%

[mundy5]

dude, that's awesome; sometimes the older electronics are more stable and longer lasting than today's cheaper component driven systems.

BetKing, on 22 May 2010 - 09:08 AM, said:

The PSU I used and have been using, and it's almost 20 years old (15-16), but I dare you to say it's not any good. It was built in "the good old days".

It's been through hell and back, and still works 110%

[zzbao]

HI，I have a problem
My HDD is ST3500320NS,product of Thailand

I use a USB-TTL Connect HDD and PC

and I Run HyperTerminal,and i press CTRL+Z,i don`t see "F3 T>" only a “Right Arrow”。

i don`t know why

Attached File(s)

•  01.JPG (95.46K)
  Number of downloads: 13

This post has been edited by zzbao: 30 May 2010 - 12:14 AM

[VideoRipper]

Well, my Chinese is a bit rusty, so I don't know either

It looks like you haven't set the correct baudrate (or any of the other
settings), but it's a bit hard to tell with these Chinese characters.

The correct settings should be:
 comsettings.png (19.67K)
Number of downloads: 9

You might even have forgotten to properly the ground wires or swapped
the TX- and RX-line.

What RS232 -> TTL convertor are you using, BTW, I hope it's not a CA-42

Greetz,

Peter.

This post has been edited by VideoRipper: 30 May 2010 - 06:49 AM

[UzY3L]

Hello!
I managed to salvage a Seagate from a friend but when I tried to "resurrect" it, it gave me this :
F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.141 msecs
F3 2>U

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 26.717 secs
R/W Status 2 R/W Error 84150180
F3 2>/1

F3 1>N1

Unable to load Diag Overlay

So, am I to understand that the drive has no chance?

[UzY3L]

Sorry for the double-post. If someone can merge this for me I would be extremely grateful!
The drive's motor sound ok until we get to the "U" part. It sounds like it's spinning back up but it does some weird mechanical sounds and then, the error I have just posted.

[mahmoudxp]

hello
i have a hdd samsung 250Gb SP2504C that have same problem , mean bios not recognize it ! can i use same method for reset firmware in samsung hards ?

[jaclaz]

mahmoudxp, on 31 May 2010 - 01:27 AM, said:

hello
i have a hdd samsung 250Gb SP2504C that have same problem , mean bios not recognize it ! can i use same method for reset firmware in samsung hards ?

It seems pretty much like a non-target :
http://www.msfn.org/...-read-me-first/

@UzY3L
Sometimes it happens because of BAD contacts (not enough current passing through):
http://www.msfn.org/...howtopic=142565
or because you used a too thick cardboard/whatever and a pin is slightly bent.
Check contacts and try again.

jaclaz

[dhilip1]

My HDD Seagate 500GB ..is bricked i think..from yesterday my PC is not detecting it... i dont have any backup... i want to recover my data ...please tell me whether i can followo the guide posted here or i should give it to seagate? if i give it to seagate will they recover my data? please tell me

i have read the whole doc.. I will try 'www.mapleleafmountain.com' method... thanks to evryone!

This post has been edited by dhilip1: 31 May 2010 - 07:54 AM

[UzY3L]

jaclaz, on 31 May 2010 - 02:44 AM, said:

mahmoudxp, on 31 May 2010 - 01:27 AM, said:

hello
i have a hdd samsung 250Gb SP2504C that have same problem , mean bios not recognize it ! can i use same method for reset firmware in samsung hards ?

It seems pretty much like a non-target :
http://www.msfn.org/...-read-me-first/

@UzY3L
Sometimes it happens because of BAD contacts (not enough current passing through):
http://www.msfn.org/...howtopic=142565
or because you used a too thick cardboard/whatever and a pin is slightly bent.
Check contacts and try again.

jaclaz

Hello, jaclaz!
I checked the contacts, everything is working as it should. But now I get a repetitive clicking sound when trying to "U" my motor. I get the same DETSEC error but the drive remains powered-up, despite the clicking sound.
Any solutions or is it a mechanical failure?

[jaclaz]

UzY3L, on 31 May 2010 - 04:24 AM, said:

Hello, jaclaz!
I checked the contacts, everything is working as it should. But now I get a repetitive clicking sound when trying to "U" my motor. I get the same DETSEC error but the drive remains powered-up, despite the clicking sound.
Any solutions or is it a mechanical failure?

It is possible:
http://forum.hddguru...d81-t12290.html
but since from what you say the behaviour changed, my guess is still in bad contacts/uncorrect procedure.

Try again from scratch using this guide (if you used the Gradius/Aviko one) - (insulating motor contacts):
http://www.mapleleaf...agatebrick.html
Or use the Gradius/Aviko ones (this thread) - (insulating head contacts) - if you used the above.

jaclaz

[khobar]

First post.

I came upon this forum after my Maxtor/Seagate 1GB drive suddenly stopped working. It is no longer recognized in BIOS and, of course, I am interested in getting it back running again. I've been reading hundreds of postings and seem to have missed one very important one.

I have an RS232/USB cable that uses, IIRC, the CA-42 driver. My question is simple: which end of the cable do I need to keep, and which end do I cut off?

EDIT: Looks like the electronics are in the RS232 part which is male. ****...now have to get a gender bender.

EDIT: Looks like I have more shopping to do. I checked my Com port on the computer and it is fine - pulled out my scope I hadn't used since 1995. Unfortunately, there does not seem to be any activity on the other side of the RS232 adapter. Using the USB pinout (red, white, green, black for +VCC, D+, D-, and GND), I have connected power across red and black, but then I only see a dc voltage on the D+ line. I expected this to be Tx (or Rx). However, there is no activity.

EDIT: I reconnected the two cut ends together and retested the cable - it shows up as a Nokia CA-42B when connected to the USB port. However, the voltages on the RS232 side are very low - Tx-to-GND is at around 0.5V when doing nothing, and pulses between 0.5V and just under 1V. Good pulses though, but something seems wrong.

This post has been edited by khobar: 02 June 2010 - 01:26 PM

[robintay]

hi im in london with a st31000340as dead drive since aug 2009. is there anyone in london who can fix this drive? willing to pay you for the fix.

[93360]

Heya just want to share my experiences and the method that I used to recover my data.

Firstly big thank you to the OP Gradius2 and Brad Garcia for the simplified method (http://sites.google....ite/seagatefix/)

And just to quickly point out, the diagram for the [Ground | TX | RX] in Gradius2's post worked for me


While Brad's picture has them switched around and didn't work.



Secondly the main reason for me to post this is because of a lack of explanation/results for the problems Wolfdie posted some time ago.
I used the forum search function and also google to find solutions to this problem as this was exactly the same symptoms I experienced with my drive including the "buzz-beep" sound that was attached in Wolfdie's post, however I could not find anything conclusive and hope to change that with this post.

In my opinion this problem bears no relation to the other click-clack sound as posted by mrkimrkonja's on 09 February 2009 - 04:57 AM.
Attached below is the sound file and from what I can hear the drive is spinning up before a series of click-clack noises which leads me to believe that it is an entirely different issue so following my method may not solve anything relating to this problem.

Just to refresh what was posted before:

WolfDie, on 07 February 2009 - 11:25 AM, said:

I've got a 500Gb barracuda 7200.11 ST3500320AS SD15 in BSY

In hyperterminal I've the correct connection but I've a big problem.

 
F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.141 msecs

[color="#4169E1"](here I connect the pcb after a little moment)[/color]

F3 2>U

[color="#4169E1"](here I listen the hdd motor with a little "clic-clic")[/color]

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 7 mins 21 secs
R/W Status 2 R/W Error 84150180
F3 2> 

I've try the 2 methods, with a card or by removing all the pcb ...



Thanks for your help !!

WolfDie, on 08 February 2009 - 12:28 PM, said:

It's the same for me, my disk make a sound every time I power it on.

It has never fallen yet.

my sound is in attachment, he is different from that of mrkimrkonja

I have reattached the sound file below for convenience.


SHORT STORY
===========

I suspect the hard drives that are making this exact sound do not actually have a '0 LBA' or 'BSY' error at all since I think it is more of a mechanical problem to do with the drive being unable to spin up. That means trying to clean the header and motor contacts (as outlined in "How to solve Error 1009 DETSEC 00006008 FIX") will NOT solve the problem, but don't let me stop you from trying.

Essentially all I did to make the drive spin up again was to tilt it onto it's side (from horizontal/flat) while it was powered up and trying to spin up hence causing the beep-buzz noise.
As soon as the drive was in the vertical position I was very surprised to hear the sound of the disc spinning up like normal!
Ofcourse I had done some other things beforehand but I don't know if they actually contributed or not so I will outline the steps I took in the Long Story below.

I've since managed to backup all the data from the affected drive and after updating the firmware I ran SeaTools for Windows with the results for both 'Long Drive Self Test' and 'Long Generic' tests coming back as FAILED. This may or may not be the same case for everyone, the point being to test the drive if you can so that if there are any errors you may be able to RMA the HDD if required.

If your drive returns errors in SeaTools but no "Fail Info icon" appears next to help in the toolbar (which happened to me), you can manually find the code in a 'ABCD1234.log' file (actual file name would be the serial number of your hard drive as seen in SeaTools and also on the HDD label) located in Program Files\Seagate\SeaTools for Windows.


LONG STORY
==========

OK so while following the methods metioned above I found that I had to do a bit more research to fully make it all work.

First of all I purchased a "USB 2.0 to TTL UART 6PIN Module Serial Converter CP2102" off eBay.

You can simply search for that or find them here: http://shop.ebay.com...3911.m270.l1313

I found some terminal cables at home to use but if you don't have any you could also get the "USB 2.0 to TTL UART Serial Converter w/ Terminal Strip" which is basically the same setup I used.


I can confirm that this absolutely works and looks much simpler and easier to do as there is no soldering and the USB port powers the whole device by itself so no 3V batteries or taking apart SATA power cables required either. Just insert one end of the cable onto the header pins and take off the casing on the other end and procede to tape it up like in Brad's tutorial.


The "USB 2.0 to TTL" module I bought also comes with a little installation/drivers CD although if you're using Windows7 the drivers will be installed for you automatically (Silicon Labs CP210x USB to UART Bridge) so just plug it into any USB port.

Next I used PuTTY R0.60 as the terminal program.

Run the putty.exe (no installation) and on the 'Session' configuration panel select the 'Serial' radio button.

Then go to the 'Serial' configuration panel and input the following:

Serial line to connect to: COM* (replace the * with the assignment windows has given the USB module, this can be found in [Control Panel->Device Manager->Ports (COM & LPT)->Silicon Labs CP210x USB to UART Bridge (COM*)])
Speed (baud): 38400
Data bits: 8
Stop bits: 1
Parity: None
Flow control: None

Then click Open and the PuTTY command window should open.

To test if the module is working properly just place a jumper block across the TXD and RXD terminals on the USB module and then type anything on the keyboard to confirm that you can see what you type hence it works. If not then check that you are using the correct COM* assignment and try again.

Next you should unscrew the logic board off the HDD and separate them.

Place a piece of card stock over the head contacts (with a long enough thumb grip to overhang over the edge of the disc enclosure to help pull it out later).


Then replace the logic board, screwing in only the 3 screw nearest the motor contact.


Connect the TXD cable to the logic board's RX pin (as per Gradius2's picture), the RXD cable to the TX pin and the GND cable to the Ground pin. (It's easier if you tape the 3 individual connectors together to form a flat connector to insert into the HDD serial port).

Then connect power to the logic board (I just used my pc's own power suply unit and an extension cable).

You should now be able to press Ctrl & Z together so that a "F3 T>" prompt appears in the PuTTY command window.
If not, then you have the TX and RX cables switched. Swap them around and try again.

Now that you have the "F3 T>" prompt displayed, input the following commands (in bold italics) exactly as shown as they are case sensitive.

F3 T>/2 [Enter]

Wait for the disc to completely spin down, give it about 20 seconds to be safe.

F3 2>Z [Enter]

You should now see the following displayed:

Spin Down Complete
Elapsed Time 0.*** msecs
F3 2>

You may carfully remove the cardstock (don't rip it!) and screw in the rest of the holes near the head contacts. DO NOT try to over tighten the screws as you may strip the torx head on the screws or even slip and damage something even more important.

With the head contacts now reconnected to the logic board, you may now continue the command inputs:

F3 2>U

After a few seconds you should now see the following displayed:

Spin Up Complete
Elapsed Time *.*** secs
F3 2>


HOWEVER if you do NOT see the above message and instead see this:

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time * mins ** secs
R/W Status 2 R/W Error 84150180

Then there are three main possible causes (maybe more, I don't know ):
#################################################################

-If you hear the buzz-beep noise (put you ear next to the hard drive to hear it) AND the 'Elapsed Time' is about 7 minutes long then you are experiencing the same problem that I had. Please refer to the "Error 1009 DETSEC 00006008" section below to see what I did to try and fix it.

-If you hear the click-clack noise after the drive spins up AND the 'Elapsed Time' is about half a minute then you may have bad read/write heads that may be contacting the disc platters otherwise known as the "click of death", but don't quote me on that as I am only speculating. You may refer to the same "Error 1009 DETSEC 00006008" section below to see if it will also (temporarily) fix the problem.

-If you do not hear any noises whether clicks/beeps/clacks and there is no disc spin up sound then you may refer to krishnakantr's thread to clean the electrical contacts.


Error 1009 DETSEC 00006008
==========================
DISCLAIMER: I do not claim that any of the following methods may work and if indeed they are effective at all. No liability shall be placed upon myself if hard drives and/or it's data are permanently lost due to the procedures undertaken below.

Anyway if you are either desperate, run out of other ideas/options or have nothing else to lose then I'd recommend giving these steps a try as I have managed to successfully retrieve my data from a drive with the "buzz-beep no spin up" problem.

-While the drive is powered up and making the buzz-beep noise (or the click-clack noise), turn the drive on it's side and (carefuly, keep the cables plugged in!) shake the drive up and down to hopefully try to release any stiction or bearing/motor seizures.

-If there is no noticable progress, place the complete drive (detach cable, separate logic board from enclosure for convenience) into a zip-lock bag and try to squeeze out as much air as you can before completely sealing it. Then place the drive into the freezer overnight (or a few hours) and try the above step again. You should have the computer already running with the serial cable ready to be plugged into the logic board and the PuTTY command window open and ready to input all the commands again (Ctrl+z, /2, Z, *mount logic board onto enclosure*, U). With some luck the drive may start to spin up again!

If you have managed to get the drive working again, quickly backup all the files you can before the drive warms back up which may possibly cause the drive to seize up again.

#################################################################


So now that you can see the displayed message:

Spin Up Complete
Elapsed Time *.*** secs
F3 2>

Continue to enter the following commands:

F3 2>/1 [Enter]
F3 1>N1 [Enter]

When the prompt returns, unplug the power from the hard drive and wait for the power to cycle down (about 20 seconds to be safe).

Then plug the power back into the HDD and press "Ctrl z" to bring the prompt back up in PuTTY and enter the following:

F3 T>m0,2,2,0,0,0,0,22 [Enter]

After another few seconds you should see the following message displayed:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time * mins * secs
User Partition Format Successful - Elapsed Time * mins ** secs

Do not unplug the drive until you see this message!

Afterwards you may turn off the pc and unplug, remount and connect the hard drive (power and sata) onto the motherboard to test if the drive is working again.

Good luck!

Attached File(s)

•  seagate st3500320as beep buzz.mp3 (101.54K)
  Number of downloads: 112
•  seagate 500gb spinup click clack.mp3 (197.37K)
  Number of downloads: 108

This post has been edited by 93360: 09 June 2010 - 08:05 PM

[khobar]

93360, on 09 June 2010 - 03:25 AM, said:

Heya just want to share my experiences and the method that I used to recover my data.

Firstly big thank you to the OP Gradius2 and Brad Garcia for the simplified method (http://sites.google....ite/seagatefix/)


F3 T>m0,2,2,0,0,0,0,22 [Enter]

After another few seconds you should see the following message displayed:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time * mins * secs
User Partition Format Successful - Elapsed Time * mins ** secs

Do not unplug the drive until you see this message!

Afterwards you may turn off the pc and unplug, remount and connect the hard drive (power and sata) onto the motherboard to test if the drive is working again.

Good luck!

I got to the last part and issued the m0,2,2,0,0,0,0,22 and it's now been several MINUTES and nothing has come back on the term screen. The drive is spinning and is not making any unusual noises, so what does this mean?

I'm dead in the water with everything powered up at the moment.

EDIT: Hey, I went away for another few minutes and now have some stuff on the screen:


F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000

Okay, it finally came back:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000

User Partition Format 3% complete, Zone 00, Pass 00, LBA 00004AA5, ErrCode 000
00080, Elapsed Time 0 mins 30 secs
User Partition Format 3% complete, Zone 00, Pass 00, LBA 0002F7DE, ErrCode 000
00080, Elapsed Time 1 mins 00 secs
User Partition Format Successful - Elapsed Time 1 mins 00 secs
Zone re-format was skipped.

Is this okay? Can I now power things down?

This post has been edited by khobar: 10 June 2010 - 02:56 PM

[VideoRipper]

Yep, just give it a go

Connect it to your PC the normal way and see if it's recognized
in the BIOS (and as the correct size).

Don't forget to update us on the progress

Greetz,

Peter.

[hadnow]

Extremely grateful to all the posts in the forum. I managed to recover my bricked 7200.11 successfully using this method - http://sites.google....ite/seagatefix/

[hadnow]

After all your suggestions was successful in getting the 7200.11 out of the BSY state. A big thank you to all who helped out. I followed the step by step procedure at - http://sites.google....ite/seagatefix/

Now I recalled that I had a couple of other drives which had similar problems where in the drive spins power ons, but is not detected in the BIOS. A problem similar to the BSY in the 7200.11 series drives.

I have a 160GB & 320GB SATA and 80GB & 250GB IDE drives all from the 7200.10 series. They spin fine but are not detected by the bios. Any DIY Fix in this regard via which I could try and fix these drives like the DIY Fix for the 7200.11?

Seems almost similar to the issue faced in the 7200.11 but these are 7200.10 disks and putting a plastic between the PCB and Head the drive does not spin. So am I missing on something. And I think the terminal commands may be different.

I found a post http://www.msfn.org/...oo-t133604.html
but if I place a plastic between the Head & PCB the HDD does not spin. But if I remove the plastic the head does spin, but nothing comes up in the terminal window. Hence is there more to it than what I am doing?

Thanks in advance for all the help.

[VideoRipper]

Electronically 7200.10, 7200.11 and probably a lot (all?) of other Seagate SATA drives
are "Identical", so *in theory* the 7200.11 trick *could* work with the others.

However, this thread is for 7200.11 drives in particular and while its procedure *could*
be used on similar drives, you do it entirely at your own risk and your results may (WILL!)
vary, so only do it when you're at least a bit comfortable with electronics.

We cannot advise you on drives other than the 7200.11 ones here; you will have to start
your own new thread or find a similar one for your specific drive.

Having that said: the PCB on a Seagate drive houses a simple, but effective, diagnostics
environment; even with no drive attached, it should give you a prompt when pressing CTRL+Z
after having connected it to a RS232-TTL level port and applying power to the board.

First get that working before proceding...

Greetz,

Peter.

[bastianber]

VideoRipper, on 10 June 2010 - 03:57 PM, said:

Yep, just give it a go

Connect it to your PC the normal way and see if it's recognized
in the BIOS (and as the correct size).

Don't forget to update us on the progress

Greetz,

Peter.

I used:
F3 T>m0,2,2,,,,,22

as my command, and I have been waiting for the past 12 minutes now without any text showing....does it/ can it take longer? is it ok to take power out and try again?
Help please