Lacie Network Drive with Seagate Barracudea 7200.12 clicking

[clickofdeath]

Actually, the clicking isn’t happening when the drive is hooked into terminal. I can also press ctrl + z to get the ascii dialogue prompt but don’t want to enter any commands without checking it with you guys.

[jermy]

is this the complete log ?

[labtech]

How exactly are you testing? The drive should physically behave the same with or without terminal connected.

[galaxy]

PLZ TRY THIS ON LEVEL T/
/2 - Z- /U - m0,2,2,,,,,22

[jermy]

PLZ TRY THIS ON LEVEL T/
/2 - Z- /U - m0,2,2,,,,,22

I don't think it's a good idea

[Dmitri]

PLZ TRY THIS ON LEVEL T/
/2 - Z- /U - m0,2,2,,,,,22

Do you clearly understand yourself what kind of the advice you're giving and why you're suggesting to do that?

[clickofdeath]

Jermy, that log was based solely on what was automatically received from the drive. I also did not leave things connected for much time after it seemed to have stop receiving. Should I leave it connected for a certain length of time to make sure to retrieve all the log data or am I supposed to enter a command to retrieve something specific?

Labtech, I am going to run through the steps again later today to confirm what I am doing and then get back to you with specifics.

Galaxy, are those commands you listed more specific to the 7200.11 than the 7200.12? I've read some conflicting things and certainly would like to progress towards trying some commands out but just want to make sure I'm moving forward carefully first. It seems like some of what you are pointing out is similar to what is found on this page http://translate.google.com/translate?hl=&sl=es&tl=en&u=https%3A%2F%2Felectroclinica.wordpress.com%2F2015%2F07%2F08%2Fdisco-duro-externo-lacie-lc3u2-seagate-barracuda-7200-11%2F&sandbox=1. Which is for the 7200.11 and I can't find it but seem to have read something in these boards about not using the m command for the 7200.12. Need to dig that up.

[clickofdeath]

Ok, Labtech... this is how I'm testing. I have the drive hooked up to the usb converter, plugged into power but not powered on... I connect the USB until CoolTerm detects the port then set the options and select connect... after a few moments I power on the drive and the drive spins up and I acquire that same log. If I press ctrl + z I get

Code:

ASCII Diag mode

F3 T>


And to confirm again I am not experiencing the clicking noise anymore during any of this. Thoughts? Am I doing something incorrrectly?

[labtech]

Very odd that the clicks went away.

What we need is:
1.Terminal connected
2. Power the drive on to capture everything that is displayed in the terminal by the drive's output (we assume the price
3. Describe drive's behavior once powered on and behavior up to 10 seconds (write down specific sounds - spin up, clicks, beeps, spin down, stays spinning, etc - use your ear close to the drive and listen)
4. Post the entire log here, once powered on and drive has been running for at least 10 seconds.

[clickofdeath]

It is very odd. Tried everything again... terminal connected, power the drive to capture everything... (log is the same), drive spins up... then about 10-20 seconds it spins down, left drive powered on for 30 seconds total to see if anything else would be logged.

I'm tempted to connect it back up to SATA to see if it's working again but don't want to power it on and off unnecessarily at this point. What next?

[ddrecovery]

It is very odd. Tried everything again... terminal connected, power the drive to capture everything... (log is the same), drive spins up... then about 10-20 seconds it spins down, left drive powered on for 30 seconds total to see if anything else would be logged.

I'm tempted to connect it back up to SATA to see if it's working again but don't want to power it on and off unnecessarily at this point. What next?

IMHO, professional data recovery is your only option.

[labtech]

Issue the following commands only:
/2 enter
Z enter //will get spin down complete message
U enter //will get spin up complete message or other information

Post what that information is and whether drive clicks or not.

Note: If the drive spins down, I find it hard to believe that it is not causing some sort of click, even soft hard to hear one.

[clickofdeath]

Code:

Rst 0x20M
Servo Processor Is Reset.

RW: Disc Ctlr Initialization Completed.


ExecuteSpinRequest

No HOST FIS-ReadyStatusFlags 2002B001
ASCII Diag mode

F3 T>/2

F
3 2>
F3 2>Z

HighPowerMode
Spin Down Complete
Elapsed Time 0.085 msecs
F3 2>U

HighPowerMode

ExecuteSpinRequest

DiagError 00006008
Spin Error
Elapsed Time 22.332 secs
R/W Status 2 R/W Error 84150180
F3 2>Z

Spin Down Complete
Elapsed Time 10.503 secs
F3 2>

This guy seems to think the solution is to clean some contacts with alchol?
http://www.msfn.org/board/topic/142565-how-to-solve-error-1009-detsec-00006008-fix/

[labtech]

When this entry "R/W Status 2 R/W Error 84150180" shows up, was the drive not clicking? <<it should be clicking
After this entry "R/W Status 2 R/W Error 84150180", did the drive not spin down? <<it should spin down

P.S. You can try cleaning the contacts and see what happens. Statistically, on Seagate, that is rarely the problem.

[clickofdeath]

Ok, because I had taken the PCB board off earlier in this process several of the screws were not tightened down so the PCB board was not making contact with the area behind the screw in the off center area of the board. Now that that is resolved, after "R/W Status 2 R/W Error 84150180" shows up... there is clicking and after that entry, the drive DOES NOT spin down until I enter the Z command.

So based on this, what contacts specifically would you consider cleaning? The ones behind the off center screw? Should I bother with any other commands or just throw this drive in the fire now. I won't be taking it for professional data recovery so if anyone has a hail mary I could try here I'm all ears. Other than that, labtech you are confident now that this is solely a mechanical issue and not a firmware issue?

[labtech]

http://www.hddoracle.com/viewtopic.php? ... 649&p=1789

Well, with what we know so far, mechanical failure is suspect IMHO. Firmware, definitely. Bad sectors, guaranteed.

If you are looking for a magical command that is going to resolve the problems and "fix" the drive, then there isn't one applicable. Simply, because of the drive's condition.

When you get terminal prompt, can check the heads resistance using the following commands for a bit more info on mechanical condition:
/7 enter
X enter //capital X

Post output.

[clickofdeath]

I'll look at the contacts in the daylight. How long should I let that command run? It just kept repeating the same thing over and over again. Thanks for your help.

Code:

ASCII Diag mode

F3 T>/7

F
3 7>
F3 7>X


ExecuteSpinRequest

HighPowerMode

Failed to load overlay 00000004

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669

LED:000000CC FAddr:00287669


[labtech]

It's not returning the correct reply, therefore it seems like the read-write mechanics are toast.
Broken read-write heads need to be replaced with compatible ones in a cleanroom environment along with proper parameter adaptation, which can't quite do without pro tools and experience.

[jermy]

what i think... it's degraded/failing heads
at this stage it "might" be a simple job, using expensive tools like PC3K, DDI Etc.
but first we need to know that everything is fine, because the messages you getting, like:

Code:

No HOST FIS-ReadyStatusFlags 2002B001

and

Code:

LED:000000CC FAddr:00287669

[clickofdeath]

So at this point do I throw caution to the wind and just start entering commands until I destroy the drive? I won't be doing any professional data recovery here but could at a minimum be interesting to dig a bit deeper.