Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Seagate Barracuda 7200.11 clicking sound

June 2nd, 2010, 16:06

Hello!
I have a Seagate Barracuda 500GB which I wanted to recover from a friend. You all know the story : powered down the PC then no HDD in BIOS. Went to the good 'ol RS232 to USB converter but I get a DETSEC error, namely :
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

When trying to spin-up it clicks a couple of time (no major noise) then remains spun. Also, if I use it as a normal drive, without the RS232, it doesn't click (but no BIOS detection either). I have been to "The Sollution for Seagate 7200.11 drives" on the MSFN Forum boards and also to Mr. Carters quite extensive and detailed site http://www.mapleleafmountain.com/seagatebrick.html to no avail. I have scraped clean all of the contacts but the issue persists.
So am I to understand that the drive has a mechanical failure?

Re: Seagate Barracuda 7200.11 clicking sound

June 2nd, 2010, 17:52

Eh, never mind... I thought that I might be able to free the heads from the jammed position by giving it a few bumps but it turns out that built quality on the .11 series is so good that one of the platters was dislodged. 300G shock-proof while offline (yeah, right). So, now I'm certain : it's mechanical!
Someone please close the thread. Thanks anyways, guys!
Love&Peace!

Re: Seagate Barracuda 7200.11 clicking sound

June 3rd, 2010, 13:45

Just curious : you discovered one platter was dislodged BEFORE "bumping" or "AFTER" ? I suspect that the drive originally suffered from shock.

Re: Seagate Barracuda 7200.11 clicking sound

June 6th, 2010, 5:55

just wish i had seen your post BEFORE you decided to get physical.

http://www.mapleleafmountain.com/seagatebrick.html

potentially has 1 command wrong that may actually stop you recovering the device correctly.

The double "click" is correct for this model.
Post a reply