Hi,
i have low level clicking noise, and dont identify from bios, hard drive Seagate 7200.10 80 GB.
I have a donor just the same hdd, only different is firmware. in bad hard drive firmware code is 3.AAD, and the donor firmware is 3.AAC.P/N number is also different. On bad hdd is 9CY011-305, and the donor's number is 9CY011-304. I replace the PCB and the clicking noise disappear, but the bios already can't recognise bad hard drive.
What is the reason to dont identify ?
thanks in advance.

Not compatible. Probably physical problem anyway.

_________________
You don't have to backup all of your files, just the ones you want to keep.

what should be the same ?

read this forum on the steps to build the terminal adapter for ur seagate. Put original PCB on original drive and post the terminal log here. Data in the log can help diagnose original problem.

now i hava a terminal rs232 to TTL adapter . i test the connection with sediv program, its ok.
but when use hyper terminal on windows i cant connect it. the screen is clear. first of all i understand that i should see command prompt.
i find terminal commands,in article here, but it is too hard to know for what they are.
which command i should use to get information and post log here ?

anyone to give me a solution !?

Samo is a pro in your country and would be able to take care of it for you

_________________
You don't have to backup all of your files, just the ones you want to keep.

You need to transfer the 8-pin serial flash memory chip to your donor PCB. This chip stores unique, drive specific information. It will have a "25" in its part number.

That said, your problem doesn't sound like a PCB issue.

_________________
A backup a day keeps DR away.

Try a different baud rate. AIUI, early models used 9600bps while recent models use 38400bps.

_________________
A backup a day keeps DR away.

From forum i understand that to use terminal commands is for Pro users, who don't want to share their knowledges.
i will try replace the firmware with the donor pcb. if clicking sound still exist, that would be impossible for me to fix the drive.
At the last i will tell you.

90 out of 100 it's not firmware problem and no terminal command, at least as someone thinks, can magically fix your drive.
There is a 5% of possible, very rare, but still possible, HW firmware corruption OR a limited failure, in this case the terminal output would be indicative and helpful for a diagnose.

its not helpfull because, cant find guide for commands.

Even if you had all the guides on Earth, you won't fix it if it is a certain problem or another.

Moreover, a wrong command or reckless use of terminal would kill the drive in a flash.

The terminal output AT START is enough to judge at least two-three things.

exactly, i dont like to do if i havent sufficient information