Hmm,
Are you sure about the tx and rx wire going to the right pins, and are you using the correct terminal settings?
Is the drive externally powered?
Have you tried hitting enter and spacebar as well? They seem to get the output going here sometines, but more specifically if F3 is unreachable because of a flood of error messages,or if a session was disconnected before.
Have you tried removing the power off the drive, powering it back on, and immediately (literally just in a few secionds) connecting through terminal? And ofcourse hitting CTRL+z,enter,spacebar?

I'm using this setup:
USB / Serial TTL 5V cable - PL2303HX converter - Raspberry & Arduino (You need to get the plastic thingies off the plugs)
Drive powered by PSU
Converter plugged in, and Win7 did a automagical driver install (prolific)
Converter Green wire on pin, nearest to sata port
Converter White wire on 2nd pin next to green wire
Terminal program,comX connection (converter) with 384000 bits per sec, data transport control=none
Power up drive,immediately connect with terminal program, hit ctrl+z and/or space/enter
Voila! F3

If there's a flood of messages you cannot interrupt,just wait...it sometimes takes 10 minutes or so for the drive to respond to the ctrl+z.

Thank you very much for that advice. I purchased the serial adapter you suggested and followed your directions exactly. Initially there was no output from the drive but connecting the adapter's black GND wire to the third pin from the left of the SATA connector produced the following output:

▒0025x0▒▒▒][00738@x00▒▒A
@rXC ( 0x4
L npd` ▒
`@@ @rkd▒▒
C▒i
Tp
▒▒0005 ATP▒esY
CS▒*!
1▒% ▒▒х▒▒▒Rck MCS▒▒▒▒=n'▒rrdnt M▒*▒9▒H:▒˫)▒!t apYb
▒▒*C@P ONj1▒RA▒▒▒▒K▒▒▒▒▒
LCMa
T SC▒vlidB
P RY▒▒k▒▒э▒▒9 SWrp ▒j▒▒nqmbdr ▒ Asa[
▒0PS
▒ICR(▒▒▒ Cr▒▒ٽ▒▒▒▒▒▒b1▒qqY` u[▒▒▒000126
"rpinL@Az▒A▒R\\▒t<000▒▒▒▒▒ (9▒▒0007
ocesp@Wrr.,▒▒▒▒ X▒
BP00000000010P▒en▒▒▒▒▒430100▒
(▒ apdArkeV▒▒IX▒▒k▒▒qst frisc_lba:▒▒▒▒▒▒▒▒▒10AD6!▒(a▒hrctiK
Re▒kr\`▒HE5AP%<▒▒ɽ▒in2Z.(▒.d s▒cp`
▒ ds) e`mdnp 010 SV▒▒1 ▒080 Strdo`tr (▒ F눑Ɂ@A00▒▒

There were several more lines of output flashing across the screen similar to the above. This was captured using PuTTY and the settings you provided. Oddly, I can also connect using the same settings in HyperTerminal but receive very little output. Unexpectedly the programs did not produce the same results.

F3 could not be achieved using any combination of CTRL-Z, SPACE or ENTER after any period of time. Then again, it appears that I am having other issues based on the cryptic terminal output.

Could this be a baud rate or settings issue? I unsuccessfully tried other combinations.

Thanks again for all the suggestions and feedback!

make a photo of your connections and write the terminal parameters you are using. you are very close

_________________
If you can keep your head when all about you are losing theirs, you probably don't fully understand the situation. ... Mr Kipling

https://www.mjm.co.uk/

Here are the pics of my connections and terminal settings:


I removed the plastic connectors from the ends of the wires as IMweasel indicated and used heat shrink to insulate the connections. This also creates just enough tension between the three wires to keep them securely connected to the drive serial pins.

@dcsang, I'm wondering whether the TTL voltage levels are mismatched.

Can you measure the voltage levels at the drive and at the adapter, with the adapter disconnected from the drive? AIUI, the drive's I/O voltages are in the range of 0V - 1.8V whereas your adapter may be configured for 3.3V. If so, then it may be that an output of 1.8V from the drive may not be reliably detected as a logic HI by the adapter.

Can you show us a detailed photo of the adapter's PCB? Some bridge ICs can accommodate 1.8V and 2.5V supply voltages for their TTL IO logic. You would need to modify the PCB, though.

BTW, here is the article you may have been looking for:

Tip: How to identify the Read Channel test points:
viewtopic.php?t=28194&p=194300#p194300

_________________
A backup a day keeps DR away.

The drive serial pin voltages are as follows (pin 4 closest to the SATA port):

GND (Pin 2) to TX (Pin 3): -1.8v
GND (Pin 2) to RX (Pin 4): -1.25v

I have two PL2303 adapters using the same Prolific driver. The ONEFROG adapter purchased from hdd-parts passes a loopback test but does not produce any terminal feedback from the drive. The adapter voltage measurements are as follows:

GND (GR) to RX (BL): 2.6v
GND (GR) to TX (Y): 3.55v

The 'USB / Serial TTL 5V cable - PL2303HX converter' recommended by IMweasel produced the terminal output and had the following voltage measurements:

GND (BL) to RX (WH): .2v
GND (BL) to TX (GR): 3.3v

Also, thank you for that article!

It does appear that there is a problem with mismatched voltage levels. There are several versions of the PL2303HX chip, with the most recent version (PL2303HXD) supporting lower I/O voltages (1.8V and 2.5V).

Here is the datasheet:
http://www.prolific.com.tw/UserFiles/fi ... v1_4_4.pdf

That said, support for the lower voltages would require an external 1.8V or 2.5V LDO regulator IC.

_________________
A backup a day keeps DR away.

Good to see you are making progress. I am not aware of the voltage output i get from my cable, i'll post it in the near future.

The terminal settings you are using seem to be fine.
But as for the garbled,cryptic output you are getting...i'd think you are having a ground problem. A ground loop problem to more specific.
I've seen slightly garbled outputs due to total lack of grounding, but a ground loop really makes things worse.
Using the black wire on the 3rd pin would seem right, but this actually makes things worse.
I solved this by putting the drive im working on, in direct contact with the internal bare frame of my computer case. (not the painted outside,as it would not make contact)
So make sure to just connect tx and rx, and ground the drive to your case!

edit: looking back at your pictures...the power plug on your drive seems unusual... are you using an external power source to power the drive?
If yes, do it differently and use an internal plug off your PSU.

This community is awesome!

I was using an external adapter to power the drive and only required the TX & RX wires to produce the attached output once connected directly to the PSU . I still wasn't able to gain F3 using CTRL-Z, SPACE or ENTER but will keep at it and begin researching the output errors. The last line in the txt file repeats several times before the terminal capture appears to stop.

Also, HyperTerminal and PuTTY are now producing the same results. Please continue to share your thoughts and expertise!

Cool that you finally got the setup right... the other rs232 adapters and other terminal programs probably also work perfectly now.
Try again to gain access to the drive by;
disconnecting power off the hdd
start up terminal software and preparing the console with correct settings
reconnect power to hdd
immediately hit connect and hit ctrl-Z etc...

If the drive keeps doing this reallocation stuff, you might not get through instantly. It could take a while...let it be doing it´s thing. The reallocation can be disabled once you can reach the F3 prompt.
Source of these errors are bad sectors, and the LED error seems to be a corruption within the area where the firmware is located.

I would suggest a few things... IF you get in,don`t go experimenting with commands you find elsewhere (especially no commands from pre-F3 drives) . It is very easy to destroy your drive beyond repair, just by tiny mistakes.
You´d best open a new topic, specify your drive, tell how old it is, how it was used, how it started failing, include the errors you now have, if you want to use the data that was on it, or if you just want to refurb the drive for further use.
Now wait until an expert comes along and see what he has to say

See http://malthus.zapto.org/viewtopic.php?f=83&t=557

_________________
A backup a day keeps DR away.

I have been following this thread, but am still stuck with the following. I have used a RS232 connector which I also use to connect to Cisco devices and also used a blue Cisco cable. Through measuring and soldering I connected the TX, RX and ground from the HDD to the connector. But the output stays the same;



What am I missing?

What are the voltages on the Tx/Rx pins at the host end?

What are your port settings?

_________________
A backup a day keeps DR away.

I had a similar problem and was able to fix it. The symptoms were that the drive would spin up and make some noise, but the SATA link wouldn't come up. Linux didn't recognize the drive saying "COMRESET failed (errno=-16)". This is what the drive printed on the serial console when I started out.

Boot 0x40M
Spin Up
TCC-0019[0x000065B4][0x00006A20][0x00006E8C]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0019
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 0A61
Nonvolatile MCMT sequence number 01070EA6
[RSRS] 05A5
ProcessRWError -Read- at LBA 000000000004906B Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000004906B!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Reconstruction: EXCEPTION: Error in Header
Reconstruction: EXCEPTION: Error in first Header disc sector
ReadFooters (Backwards): Segment 05A5 StartLBA 00248358 Starting Footer LBA 00248988
SeqNum 01070EA7
ProcessRWError -Read- at LBA 0000000000049131 Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000049131!

Footer Status = 0000
ProcessRWError -Read- at LBA 0000000000049128 Sense Code=40000087
ProcessRWError -Read- at LBA 000000000004912B Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000004912B!

<snip>
Footer Status = 0000
ProcessRWError -Read- at LBA 0000000000049074 Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000049074!

Footer Status = 0000
Reconstruction: EXCEPTION: Error in Header and ALL Footers.
Continuing after error
Reconstruction: Completed 0: HeadPtr was unwritten
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001A
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
<snip>


I then shortened the two test points that were pointed out in the OP and the one between those two test points.
The drive printed out what I copied below and magically started working again. I was able to recover all my data.

Boot 0x40M
Spin Up
TCC-0026[0x000065B4][0x00006A20][0x00006E8C]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0026
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 0A61
Nonvolatile MCMT sequence number 00000000
[RSRS] 0000
Reconstruction: Completed 1:
[MCMTWS]
MCMainPOR: MCTStateFlags 0000002A MCStateFlags 00000001
MCMainPOR: Feature Enabled...

Starting LBA of RW Request=0000000000087F07 Length=000001AC
ProcessRWError -Read- at LBA 0000000000087F07 Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000089F6F!
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000089F73!
(DOS)STE OGHT: 0x0000000000000000 - 0x0000000000000000 - 0x000512EA - 0x00051308 Count 0068
(DOS)CMP Count 0068
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004C0BE - 0x0000000D - 0x0000001C Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004BF10 - 0x0000000C - 0x0000001B Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004BD62 - 0x0000000B - 0x0000001A Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004BBB4 - 0x0000000A - 0x00000019 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004BA06 - 0x00000009 - 0x00000018 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004B858 - 0x00000008 - 0x00000017 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004B6AA - 0x00000007 - 0x00000016 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004B4FC - 0x00000006 - 0x00000015 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004B34E - 0x00000005 - 0x00000014 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004B1A0 - 0x00000004 - 0x00000013 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000000049009 - 0x000000000004AFF2 - 0x00000003 - 0x00000012 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x000000000014A927 - 0x000000000014D11C - 0x000002BE - 0x000002DC Count 0059
(DOS)CMP Count 0059
(DOS)STE OGHT: 0x00000000048905A0 - 0x0000000004893C59 - 0x00006B71 - 0x00006B8F Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x00000000048BD804 - 0x00000000048BD9D6 - 0x00006B71 - 0x00006B8F Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x0000000002BAE50A - 0x0000000002BB1614 - 0x00004893 - 0x000048B1 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000000137F61 - 0x000000000013A756 - 0x000001D7 - 0x000001F5 Count 0048
(DOS)CMP Count 0048
(DOS)STE OGHT: 0x0000000000148659 - 0x000000000014AE4E - 0x000002A3 - 0x000002C1 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x000000000308848D - 0x000000000308B597 - 0x00005055 - 0x00005073 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000000090686 - 0x00000000000939FC - 0x000000CF - 0x000000ED Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x00000000001456A7 - 0x0000000000147E9C - 0x0000027E - 0x0000029C Count 004A
(DOS)CMP Count 004A
(DOS)STE OGHT: 0x0000000002BA8E07 - 0x0000000002BABF11 - 0x0000485C - 0x0000487A Count 0044
(DOS)CMP Count 0044
(DOS)STE OGHT: 0x000000000014BDC7 - 0x000000000014E5BC - 0x000002CE - 0x000002EC Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x0000000001F0121A - 0x0000000001F0424B - 0x0000346B - 0x00003489 Count 0046
(DOS)CMP Count 0046
(DOS)STE OGHT: 0x0000000001F0504A - 0x0000000001F0807B - 0x00003493 - 0x000034B1 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x000000000279D9A0 - 0x00000000027A1305 - 0x00003B52 - 0x00003B70 Count 0054
(DOS)CMP Count 0054
(DOS)STE OGHT: 0x00000000027941CC - 0x0000000002797B31 - 0x00003B00 - 0x00003B1E Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000002797B32 - 0x000000000279B497 - 0x00003B1F - 0x00003B3D Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000002791910 - 0x0000000002795275 - 0x00003AEA - 0x00003B08 Count 0051
(DOS)CMP Count 0051
(DOS)STE OGHT: 0x00000000027932FC - 0x0000000002796C61 - 0x00003AF8 - 0x00003B16 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x0000000002790DF4 - 0x0000000002794759 - 0x00003AE4 - 0x00003B02 Count 007A
(DOS)CMP Count 007A
(DOS)STE OGHT: 0x0000000002792B94 - 0x00000000027964F9 - 0x00003AF4 - 0x00003B12 Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x000000000191786A - 0x000000000191A89B - 0x00002A76 - 0x00002A94 Count 005A
(DOS)CMP Count 005A
(DOS)STE OGHT: 0x0000000002796A88 - 0x000000000279A3ED - 0x00003B16 - 0x00003B34 Count 0051
(DOS)CMP Count 0051
(DOS)STE OGHT: 0x0000000002796320 - 0x0000000002799C85 - 0x00003B12 - 0x00003B30 Count 0048
(DOS)CMP Count 0048
(DOS)STE OGHT: 0x00000000026F8366 - 0x00000000026F99D9 - 0x00003AE8 - 0x00003B06 Count 004D
(DOS)CMP Count 004D
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A3C20 - 0x00003AE8 - 0x00003B06 Count 004D
(DOS)CMP Count 004D
(DOS)STE OGHT: 0x00000000027A7D9E - 0x00000000027AB79E - 0x00003B2A - 0x00003B48 Count 0047
(DOS)CMP Count 0047
(DOS)STE OGHT: 0x0000000001F0A75A - 0x0000000001F0C039 - 0x000034CB - 0x000034E9 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x0000000001FDF356 - 0x0000000001FE0AA7 - 0x000034CB - 0x000034E9 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x00000000027A34A5 - 0x00000000027A6EA5 - 0x00003B03 - 0x00003B21 Count 0046
(DOS)CMP Count 0046
(DOS)STE OGHT: 0x0000000002795276 - 0x0000000002798BDB - 0x00003B09 - 0x00003B27 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000001891E57 - 0x00000000018957BC - 0x00002440 - 0x0000245E Count 004D
(DOS)CMP Count 004D
(DOS)STE OGHT: 0x0000000001CA9C29 - 0x0000000001CAD58E - 0x00002B67 - 0x00002B85 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x0000000001B87E80 - 0x0000000001B8B78D - 0x0000289B - 0x000028B9 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x00000000001565BF - 0x00000000001599D0 - 0x0000023B - 0x00000259 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x000000000014782B - 0x000000000014A020 - 0x00000298 - 0x000002B6 Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x0000000001ECDC53 - 0x0000000001ECE594 - 0x00002E7F - 0x00002E9D Count 0057
(DOS)CMP Count 0057
(DOS)STE OGHT: 0x0000000001F21A61 - 0x0000000001F24A84 - 0x00002E7F - 0x00002E9D Count 0057
(DOS)CMP Count 0057
(DOS)STE OGHT: 0x00000000018A83B1 - 0x00000000018ABD16 - 0x00002501 - 0x0000251F Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x00000000027A636C - 0x00000000027A9D6C - 0x00003B1C - 0x00003B3A Count 0054
(DOS)CMP Count 0054
(DOS)STE OGHT: 0x000000000018F529 - 0x0000000000192A51 - 0x00000251 - 0x0000026F Count 004C
(DOS)CMP Count 004C
(DOS)STE OGHT: 0x00000000026F7DC9 - 0x00000000026F99D9 - 0x00003AE5 - 0x00003B03 Count 004A
(DOS)CMP Count 004A
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A3683 - 0x00003AE5 - 0x00003B03 Count 004A
(DOS)CMP Count 004A
(DOS)STE OGHT: 0x000000000279E108 - 0x00000000027A1893 - 0x00003B56 - 0x00003B74 Count 0048
(DOS)CMP Count 0048
(DOS)STE OGHT: 0x00000000027F4D6A - 0x00000000027F4F43 - 0x00003B56 - 0x00003B74 Count 0048
(DOS)CMP Count 0048
(DOS)STE OGHT: 0x000000000279BA26 - 0x000000000279F38B - 0x00003B41 - 0x00003B5F Count 0042
(DOS)CMP Count 0042
(DOS)STE OGHT: 0x000000000279D238 - 0x00000000027A0B9D - 0x00003B4E - 0x00003B6C Count 0054
(DOS)CMP Count 0054
(DOS)STE OGHT: 0x0000000001CB8489 - 0x0000000001CBBAC8 - 0x00002C43 - 0x00002C61 Count 0048
(DOS)CMP Count 0048
(DOS)STE OGHT: 0x00000000027A99AF - 0x00000000027AD3AF - 0x00003B39 - 0x00003B57 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x00000000027A3E00 - 0x00000000027A7800 - 0x00003B08 - 0x00003B26 Count 0049
(DOS)CMP Count 0049
(DOS)STE OGHT: 0x0000000000158C61 - 0x000000000015C072 - 0x00000252 - 0x00000270 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x0000000001CA9E03 - 0x0000000001CAD768 - 0x00002B68 - 0x00002B86 Count 0069
(DOS) Refresh Start.
(DOS)CMP Count 0069
(DOS)STE OGHT: 0x0000000001CB9449 - 0x0000000001CBCA88 - 0x00002C4C - 0x00002C6A Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x0000000001CB9609 - 0x0000000001CBCC48 - 0x00002C4D - 0x00002C6B Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x000000000279C71C - 0x00000000027A0081 - 0x00003B48 - 0x00003B66 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x00000000027998D2 - 0x000000000279D237 - 0x00003B2F - 0x00003B4D Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x00000000027A7443 - 0x00000000027AAE43 - 0x00003B25 - 0x00003B43 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x00000000027AAA86 - 0x00000000027AE486 - 0x00003B42 - 0x00003B60 Count 0043
(DOS)CMP Count 0043
(DOS)STE OGHT: 0x00000000027A97D0 - 0x00000000027AD1D0 - 0x00003B38 - 0x00003B56 Count 0043
(DOS)CMP Count 0043
(DOS)STE OGHT: 0x00000000027A1C52 - 0x00000000027A5652 - 0x00003AF6 - 0x00003B14 Count 0040
(DOS)CMP Count 0040
(DOS)STE OGHT: 0x00000000026F961C - 0x00000000026F99D9 - 0x00003AF2 - 0x00003B10 Count 005E
(DOS)CMP Count 005E
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A4ED6 - 0x00003AF2 - 0x00003B10 Count 005E
(DOS)CMP Count 005E
(DOS)STE OGHT: 0x00000000026F907F - 0x00000000026F99D9 - 0x00003AEF - 0x00003B0D Count 004C
(DOS)CMP Count 004C
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A4939 - 0x00003AEF - 0x00003B0D Count 004C
(DOS)CMP Count 004C
(DOS)STE OGHT: 0x00000000026F8AE2 - 0x00000000026F99D9 - 0x00003AEC - 0x00003B0A Count 004B
(DOS)CMP Count 004B
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A439C - 0x00003AEC - 0x00003B0A Count 004B
(DOS)CMP Count 004B
(DOS)STE OGHT: 0x00000000026F8903 - 0x00000000026F99D9 - 0x00003AEB - 0x00003B09 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x00000000027A1894 - 0x00000000027A41BD - 0x00003AEB - 0x00003B09 Count 0045
(DOS)CMP Count 0045
(DOS)STE OGHT: 0x00000000027A6EA6 - 0x00000000027AA8A6 - 0x00003B22 - 0x00003B40 Count 0051
(DOS)CMP Count 0051
(DOS)STE OGHT: 0x00000000027A6AE8 - 0x00000000027AA4E8 - 0x00003B20 - 0x00003B3E Count 0043
(DOS)CMP Count 0043
(DOS)STE OGHT: 0x0000000001F21C3B - 0x0000000001F255A0 - 0x00002E85 - 0x00002EA3 Count 0041
(DOS)CMP Count 0041
(DOS)STE OGHT: 0x00000000011A9CD8 - 0x00000000011AD63D - 0x00001A14 - 0x00001A32 Count 0043
(DOS)CMP Count 0043
PowerState = IDLE1
APM disabled by SPort
HighPowerMode Status 0001 Req 0006
Dither
PowerState = IDLE1
PowerState = IDLE2
(H) SATA Reset

Dear community,

Though not being accessed alot, all of a sudden this drive started clicking now and then. It wasn´t till a week after it started that I decided to find out WHICH of my drives that had this issue, so I fired up HDTune to see where it´d be having issues. It was obvious which one was the bad drive, as when chosen and starting the hdtune speedtest, the clicking happened.

So I took out the drive, and hoped for some magic when hooked up to my USB to sata cable, but now it seems to not anymore show up in Windows. It spins up for 3-5 secs, clicks 2 times quickly and 10 times with more time inbetween and then spins down.

Is this perhaps the BSY error, and what´s the easiest way for me to find out: What´s the simplest and best working cable I can buy for this, where I won´t have to do more modifications than necessary?

Thanks in advance!

Given that it clicks and spins down pretty much guarantees it isn't the "BSY error" and it's a physical issue with the heads and/or media.

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Thanks, is this anything that could be repaired using the console?
Also, now IF it´s a BSY error, would Seagate then recover the data for free as they´re said to do? Entering its serial into the warranty Tool at their side shows me that it nolonger has a warranty. It´s either 1 or 1½ years old.

No, and no.

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

If I'm not mistaken, shorting the 1st and 3rd test points shorts one side of the read channel to one side of the write channel. The read channel pair are TP 1 & 2 (the top two points in your picture), the write channel pair TP 3 & 4. I was unable to get to T shorting as you suggested, but got it easily enough shorting TP 1 & 2.

_________________
Sabo Computer Repairs & Data Recovery

Hi,

I have an ST3000DM001 7200.14 with the PCB 100664987 Rev B



I not understand the explanations.:
Make a bridge between pin 1 and 3 ?
or pin 1 + 2 + 3 ?

This is a bridge welding or just for a moment before power the hd ??

Thanks for your help