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
March 25th, 2011, 8:50
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.
March 25th, 2011, 9:09
Not compatible. Probably physical problem anyway.
March 25th, 2011, 9:51
drc wrote:Not compatible. Probably physical problem anyway.
what should be the same ?
March 25th, 2011, 11:43
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.
April 8th, 2011, 10:41
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 ?
April 13th, 2011, 8:38
anyone to give me a solution !?
April 13th, 2011, 9:09
Samo is a pro in your country and would be able to take care of it for you
April 16th, 2011, 5:53
stanis_r wrote:what should be the same ?
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.
April 16th, 2011, 5:55
stanis_r wrote: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.
Try a different baud rate. AIUI, early models used 9600bps while recent models use 38400bps.
April 25th, 2011, 4:50
fzabkar wrote:stanis_r wrote: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.
Try a different baud rate. AIUI, early models used 9600bps while recent models use 38400bps.
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.
April 25th, 2011, 5:29
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.
April 25th, 2011, 5:40
BlackST wrote: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.
April 25th, 2011, 5:51
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.
April 25th, 2011, 5:58
exactly, i dont like to do if i havent sufficient information
Powered by phpBB © phpBB Group.