Hi Gurus,

I have a Seagate 500GB 2.5" HDD. when starts up, it makes some subtle clicks and then turns ready.

Terminal is as follows

RW cmd 002F req=18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 00 00 A0 E1

opts = 00000000

RW Err = 84150180


Any Expert suggestions on how to solve??
Thanks in advance

Hi, you need to send this in. Contact DR-Kiev.

Heads are bad, not DIY

+1 dr-kiev

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

+1 dr-kiev

http://www.angeldatarecovery.com

+1 DR-Kiev

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Dear All,

Everyone working for dr-kiev or its all one person posting from different accounts???
There is nothing I can do???

You asked for expert advice and you had it - no DIY and the nearest REAL EXPERT that can truly help you is DR-Kiev.
Outsourcing is NOT a sin, it is a win-win-win solution !

Not at all, every one who recommended dr-Kiev is from a different country. And since you're in Dubai it makes sense to go to a recommended pro in Dubai.

And no, there is NOTHING you can do. It's a physical issue and requires cleanroom work and expert knowledge. Sorry.

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

You guys , too love me

_________________
Angel Data Recovery

I think there are only 2 persons who can help you in dubai
1) Dr. Kiev
2) God

From my limited knowledge,if seagate spins down its head. Consult Dr. Kiev if Data is important.

In this case seems to stay up, not spindown. Can be some things but the clues lead to head problems or firmware problems (on the platters) - anyway a proper diagnose can pinpoint in a matter of minutes the real problem. Of course if data has at least "some" importance

I have replaced the head with a working one and the error is still there.
Terminal output is still the same..
So it seems its a firmware bug..

Now can someone help..(ofcourse i went to dr-kiev's office but couldn't meet the person incharge over there.. hope to see them shortly ).

The specific meaning of that error really does relate to an inability to read the media (typically heads / pre-amp, but can be other things, e.g. especially if the drive has been dropped). I can guess about what may have caused your drive to report the same error after replacing the heads, but I don't expect you want my guess

Can you supply the full terminal output, from power-on, of that drive now that you have replaced the heads, and then readers can see the current situation?

What is the history of this drive? Used externally or always been inside a laptop? Does the owner admit to any shock/knock? Any different symptoms, before it developed the problem you originally described?

Did you use a cleanroom, or laminar flow bench, or something different?

How many successful HSA replacements on the drive type have you done before - in other words, how confident are you that this replacement was definitely successful? For example, did you move the "new" heads back to the donor (i.e. the original drive where the heads came from) and confirm that the donor drive still works?

How did you check the media state, before doing this HSA replacement?

Your answers may help to confirm or eliminate some possible reasons for your recent update.

I already asked 2 of these 3 questions above
Or was my posting not visible for you?

I use a Luminar flow bench. After replacing the Head in the patient drive the terminal still the same. So to double check and put the new head back to the donor and I could see Hex View and the partitions.



Thru Hex view for HD Doctor

@olivia,

Thanks for the update. Unfortunately there are still several missing answers from earlier questions, and some answers were very short and so are open to different interpretations. Therefore I have limited conclusions. Overall, I see no evidence of your hypothesis of a firmware "bug". I suspect the problem is elsewhere and perhaps related to the gaps in the story. As several members have already said, you'll probably need additional help on this issue (by someone who has the drive in front of him).

I know there is a solution for this by working on the firmware alone.
But nobody sharing it. I am ready to pay for those who like to share the solution for this