Lacie Network Drive with Seagate Barracudea 7200.12 clicking

[clickofdeath]

Hey, I've got an old Lacie network drive that has a Seagate Barracudea 7200.12 1TB drive clicking now. Wondering if this is something I might be able to fix relatively easily on my own? I was reading about some firmware issues with these drives but think that this one is one of the newer ones but am unsure.

[jermy]

post a terminal log

[clickofdeath]

how, the drive does not mount

[jermy]

no need for the drive to mount

what is written next, you do only if the drive has usual sound
if there is any unusual noise from your HDD (knocking, beeping, clicking Etc.)
DO NOT power on the hdd

connect a TTL cable to your hard drive
open hyper terminal or something similar
setup the right settings
then power on the drive
copy paste the log here

[clickofdeath]

Ok, so there is clicking sound. I might buy that TTL cable anyways and learn how to use it later though. Seems neat. How do I acquire terminal logs? The firmware is cc46.

[jermy]

How do I acquire terminal logs?

already told you

connect a TTL cable to your hard drive
open hyper terminal or something similar
setup the right settings
then power on the drive
copy paste the log here

The firmware is cc46.

terminal log has nothing to do with the firmware ver.
all seagate (and samsung) HDD's producing a log

[clickofdeath]

I see. I'm on a mac. Can I use OS X Terminal for this? If so, what commands should I enter to acquire the log once connected.

[labtech]

No command. If the settings are correct, the log should begin populating with drive output upon powering on.

[clickofdeath]

OK, I ordered that converter. When it arrives would this be a good guide to follow? I'm totally new at something like this but it seems as though this is the correct path to troubleshooting and possibly resolving the problem. I just might need a little guidance how to proceed.

http://translate.google.com/translate?h ... &sandbox=1

Thanks for your help.

[jermy]

whatever you do, DO NOT issue any command

[labtech]

OK, I ordered that converter. When it arrives would this be a good guide to follow? I'm totally new at something like this but it seems as though this is the correct path to troubleshooting and possibly resolving the problem. I just might need a little guidance how to proceed.

http://translate.google.com/translate?h ... &sandbox=1

Thanks for your help.

No, it is not.
Why not search and read here on this forum about 7200.12 series instead of assuming from random internet sites? The drive on that site is 7200.11. Needless to say, clicking will more than likely not allow in your case to resolve the problem.

Data recovery is a complex field with many details that have to be aware of. So, as an inexperienced person, randomly selecting "a solution" results 99.99% of the time in disaster.

[DRUG]

OK, I ordered that converter. When it arrives would this be a good guide to follow? I'm totally new at something like this but it seems as though this is the correct path to troubleshooting and possibly resolving the problem. I just might need a little guidance how to proceed.

http://translate.google.com/translate?h ... &sandbox=1

Thanks for your help.

No, it is not.
Why not search and read here on this forum about 7200.12 series instead of assuming from random internet sites? The drive on that site is 7200.11. Needless to say, clicking will more than likely not allow in your case to resolve the problem.

Data recovery is a complex field with many details that have to be aware of. So, as an inexperienced person, randomly selecting "a solution" results 99.99% of the time in disaster.

Wise words of wisdom... If data is valuable, just hand it to a reputable DR lab in your area and who knows the price will be cheaper then you are expecting ? (you can't assume the same price after you tried some "internet stuff" on your drive).

Good luck

[clickofdeath]

The data isn't that valuable I'm just taking the opportunity to try to learn more about this and have some more tools available to troubleshoot and/or possibly recover stuff.

[clickofdeath]

Ok, I received the converter. Before I begin I just want to run through things again. I'm going to connect to the RX, TX, and GND... the RX from the drive should go to the TX on the converter, and vice versa correct? I want the PCB removed from the drive, and if I was facing the drive connectors with the drive upside down (label on the bottom)... the pins from right to left are RX, TX, GND, and the 4th one is I don't know. Then, after I've connected things... I open up whatever terminal program of my choosing. (I was going to use CoolTerm for OS X)... go into Serial Port Options set the Port to the converter (I've already installed the CP210x USB to UART Bridge VCP Drivers for Mac), set the baudrate to 115200, Data Bits to 8, Parity None, Stop Bits 1, and leave Flow Control for CTS, DTR, and XON unchecked... and then connect... and then what? Wait for a text to start flowing in? How long should one wait... 30 seconds? 1 min? This is all while the PCB is NOT connected to the hard drive and does NOT have it's power cable connected to it?

[clickofdeath]

Ok, I've got CoolTerm for OS X hooked up and am able to get a log each time I connect but it's all garbled text. But it's the same amount each time... just 4 lines.

Code:

..à.à.ü.ü.àà.àààüü..à.ü..à.à.ü.ü.à.à.üü...à.à.üà.àà.à.àà...à...ü...àà...à.ü..üàà..à.à...à..ü.üà.àà.ü.ü.ü.à...ü.üà...ü.à.üàü.à..ü.ü..ü.à.ü...à..à.à.............ü...à..à.üà..à.......à.ü....à.ààüü.ààüàü....à..à.à.üàà.....à.à.à.ü...ü...à...ü..à.à.ààààààà..àà.à...à.à.ü.ü.àà.àààüü..à.ü..à.à.ü.ü.à.à.üü...à.à.üà.àà.à.àà...à...ü...àà...à.ü..üàà..à.à...à..ü.üà.àà.ü.ü.ü.à...ü.üà...ü.à.üàü.à..ü.ü..ü.à.ü...à..à.à.............ü...à..à.üà..à.......à.ü...


What am I doing wrong here... how can I get it to display something readable. Or does this mean the drive is toast?

[labtech]

Terminal settings seem wrong.

[clickofdeath]

I've attached the settings in CoolTerm I'm using...

With the PCB upside down while I'm facing the connectors (power on my right hand side)... 4th pin on left is empty, 3rd is ground, 2nd is going to RX on the USB and 1st is going to TX on USB.

Attachments

[fzabkar]

The baud rate should be 38400bps.

[clickofdeath]

That worked! Well, I got a log...

Now what?

Code:

Rst 0x20M
Servo Processor Is Reset.

RW: Disc Ctlr Initialization Completed.


ExecuteSpinRequest

No HOST FIS-ReadyStatusFlags 2002B001


[labtech]

As expected behavior. 99% confident the drives spins down within seconds and clicks stop, correct? If so, just confirmed what was suspected: mechanical failure.