Hi all,
I have a 2Tb Seagate barracuda [7200.14 / model ST2000DM001 / FW:CC4H / date: 13084] thats no longer detected in bios.

Recently I received a "Windows System Error- Unknown Hard Error". I restarted back into windows, saw the standard "windows recovered from a serious error" message, but before seeing the details, my system froze again. This time though my drive was gone. It doesn't appear in disk management(using a secondary windows install on another drive at the moment) or in bios. I also tried using an external enclosure(dual thermaltake enclosure) and got no detection(the dead drive actually prevents other drives in the enclosure from being detected). When powered, the drive seems to spin normally(no noises other than the drive spinning), though I noticed that once it spins up to a certain degree, it remains constant. I'm hoping some one knows or can help me diagnose whether this is a problem with the mechanical failure (heads, stiction, spindle motor) or PCB problem from the information provided. While I'm not new to electronics repair, I've never attempted to repair a drive before. I will soon be acquiring a TTL adapter for testing purposes.

The majority of data on the drive is no longer backed up, my kids destroyed my backup drive a week before this all happened so I'm hoping to revive this drive. While there is quite a bit of data that's important, the cost of data retrieval is a bit too steep. So I'm hoping for a DIY fix. Any help would be most appreciated.

Mostly, none of the above faults, and maybe firmware problem.
A terminal report would be helpful.


Watchout for DIY risks too (as data is important)

unfortunately the TTL adapter I ordered was placed on back order for the next few days, so it may be a few days before I'll be able to get any readings off the drive. I'm hoping sathyan is right, and that it just a problem with the firmware as I've been reading that their one of the simpler problems to fix.

+1

Hi everybody,
I have a 2Tb Seagate barracuda model ST2000DM001 / FW:CC4B.
My BIOS not only can't detect the HD but the BIOS itself dosen't start if the HD is plugged in.
I thought that maybe is the same problem that backuphero has.
First of all I apologizefor my bad english.
I bought a serial interface MAX3232 RS232 TTL 3V to communicate with the HD, because I thought it was the well known "BSY Seagate" bug, but it seems it's not like that.
When I open the Hyperterminal and press CTRL+Z, the only message I get is a continuously repeat:

LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
...
and so on.
I can't even put any command!

I'm totally newbie in dealing with Hard Disks, any help would be really appreciated.
A question: Buying a new identic hard disk and transplant "the green logic board" from the new one to the "broken" one would help?
Thanks in advance.

Thank you for answering so fast.

Spildit, How can I attract attention of BlackST in this forum?
Is this the way to tag him?

BlackST

Thanks.
I will write to him.
Before I coudln't because I didn't have this right, given that I was a nebie, now I can.
Regards.

oh my god...
I hope it does not happen with my HD anymore ..

my spec HD
ST2000DM001
f / w CC43
date 13 017

whether the older fw spekesifkasi HD also affected by the problem?

seagate does it really have a problem???

Hi everyone
My ST2000DM001 (2To) in external USB Dongle works fine, till windows detects some errors (yellow triangle) and the HD seems disconnected,to use it i must disconnect and reconnect it, CrystalDisk Info tells me too about Some errors.
I buy and second HD to Backup my datas (2To of Music, photos and home movies).
At Home after preparing the new one, the First (ST2000DM001) dont work anymore and are not detected by windows, after power on, he just start spinning and after some seconds, he make some Clicks (11 Clicks) then stops.
Even if i plug it directly to my Sata plug (inside my PC).the same thing happens (11Clicks and stop).
After contacting Sea*ate, they tells me its a OEM product.
And after contacting Tanscend (USb Dongle Manufacturers), they tells that my warranty was lost after i've open the USB dongle.
Now i'm face to a wall.
Is there a way to diagnose what wrong with it (The Heads?, The PCB?, The Preamplifier?.....).
I even tried my old TTL interface but seems dont communicate with it (I just receive random characters in the terminal window).
Anyone have an idea?
Thanks.

Your drive probably got FW or heads problems, to test it is needed to comunicate with drive via TTL

Probably your comunicacions parameters are wrong. i have not info about comunications params here. probably any guru here can write it for you.

Baud rate 38.4k

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

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

Thanks for your answers.
I have a diy RS232 TTL interface that work perfectly with my old 7200.11.
But not with this one.
Is there any schematics around for RS232 LVTTL (i think the problem is the kind of TTL).
The terminal parameters seems ok.
Another thing i noticed, The MCU are very very hot during power on.
Some suggestions?
To resume:
11 Clicks and stop (does this number a code for something, google dont know about it).
No detection in bios.
No traumatic chocs.
Very hot MCU.
Thanks guys.

Hello momo, I have the same problem with ST3000DM001, drive has 10 clicks, and very hot MCU, terminal shows Fail Servo OP =0100 resp 0007 10 times. A colleague has to replacements of PCB !?
What at a friend's terminal displays !? sorry for my English.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

For now, i'm searching how to communicate with the PCB via RS232.
I'm serching for schematics of LVTTL interface.
Seagate seems Cursed.

The I/O voltage is much lower (1.8V) on the latest models.

See this modification:

viewtopic.php?f=1&t=29286
http://img11.hostingpics.net/pics/228167mod18V.jpg

_________________
A backup a day keeps DR away.

Hey Momo, try this terminal: . This terminal works fine in this PCB.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Thats what i'm looking for,
Thanks fzabkar
Thanks pikus_09.
Tomorrow i'll buy the missed components.
Thanks again

MOMO that's no problem.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Hi everyone
My interface is Ok, the tests seems ok.
But now its the hard and dangerous step.
My question:
What commands should i input to first diagnose what wrong then how to fix the different issue?
Is there any sequence of commands to debug the HD without any risk of completely destruct the data?.
Thanks again to everyone and have a nice day.