Page 1 of 1

Sagate ST500DM002 busy problem

Posted: 18.10.18, 10:29
by procurement
HELLO
I have a SEAGATE ST500DM002 hard drive with busy problem,
i changed his PCB as well as his Head but the busy problem remained,
I appreciate any help...
Thanks

Re: Sagate ST500DM002 busy problem

Posted: 18.10.18, 10:43
by GuideRecovery
can we see terminal log ?
changing head without properly diagnosing the problem was not a good idea... :)

Re: Sagate ST500DM002 busy problem

Posted: 22.10.18, 09:22
by AJ2008
Probably it was not heads to start with.

You need to check Terminal log, I imagine you will see LED:47 or something similar error.

you need to short read channels during initialization and try to retain T> where you can look to correct any issues such as relocation or translator but bear in mind that this model uses additional defects for translation that is not preserved with translator regeneration

Re: Sagate ST500DM002 busy problem

Posted: 07.11.18, 10:27
by procurement
"Probably it was not heads to start with.

You need to check Terminal log, I imagine you will see LED:47 or something similar error.

you need to short read channels during initialization and try to retain T> where you can look to correct any issues such as relocation or translator but bear in mind that this model uses additional defects for translation that is not preserved with translator regeneration"
****************************************************
Hi
Thanks for your reply
Can you give me more details about how can I short the read channel?

Re: Sagate ST500DM002 busy problem

Posted: 07.11.18, 11:43
by AJ2008
You really should post the terminal log here to be sure the right advice is given to you - at this stage there could be a number of issues taking into account the physical repairs undertaken and the initial failure resulting in constant BSY

Re: Sagate ST500DM002 busy problem

Posted: 08.11.18, 11:31
by procurement
unfortunately, the terminal log page is empty and does not contain any information

Re: Sagate ST500DM002 busy problem

Posted: 09.11.18, 11:52
by AJ2008
procurement wrote:Source of the post unfortunately, the terminal log page is empty and does not contain any information

Then most likely you do not have correct connection to terminal - you should at the very least see 'Rst' message on power on.