500gb Spinn normally but does not detect

[mukesh_raval]

I have seagate 500gb Sata hard disk st3500320as and firmware is sd14 which spin normally and it initialise normally but does not detect in bios, i also change logic board with same but it giving clicking sound how to
solve this.

[MadOCer]

I have seagate 500gb Sata hard disk st3500320as and firmware is sd14 which spin normally and it initialise normally but does not detect in bios, i also change logic board with same but it giving clicking sound how to
solve this.

AFAIK the PCB is not your problem if the drive does spin up no problem. You should instead put the original PCB back on and look into the well known firmware issue, also known as the "BUSY"-Bug. There is plenty info and lots of how-to descriptions online.

For example here:

http://www.msfn.org/board/index.php?showtopic=128807

And many, many more online. Maybe even in your native language. Just search.

[poehere]

Changing out PCB board will not solve this problem for you. A DR shop can handle this one and fix it for you and get your data off your drive. Tell us where you are located and we can recommand a person from the forum in your area to do this job for you.

[pcimage]

PCB is not your problem, like poehere says.. seek pro help

[fzabkar]

I have seagate 500gb Sata hard disk st3500320as and firmware is sd14 which spin normally and it initialise normally but does not detect in bios, i also change logic board with same but it giving clicking sound how to
solve this.

Here are repair procedures for Seagate 7200.11 drives:

http://sites.google.com/site/seagatefix/

http://www.msfn.org/board/index.php?showtopic=128807

Tutorial with photos:

http://www.overclock.net/hard-drives-st ... -pics.html

Pinout of Nokia CA-42 cable's Pop-port connector (use pins 6,7,8):

http://pinouts.ru/CellularPhones-Nokia/ ... nout.shtml

See the following technical bulletin:

http://atulchitnis.net/files/seagate.pdf

Seagate were at one time offering free data recovery services to those customers whose drives were affected by the bug. This may still be the case.