This SEAGATE is funny
ST3500413AS JC66 which initializes perfectly, as if FW issue but does not give terminal access even after shorting Read Channel. DRD DSC okay.
Has any one faced this issue ever ?

The drive won't give access to the terminal, as it can't read the SA.
That's either bad heads or SA problems or non-original PCB.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Heads are Okay
PCB Seems native as the sr. no in ROM are matching
Any more suggestions

This drive definitely does not initialize perfectly. In fact, it doesn't initialize at all, based on what I see.

I'm with Dimitry...assuming that it is the original PCB, it is damaged heads or surface damage in the SA.

How did you determine the heads are OK?

_________________
Luke
Recovery Force Data Recovery

And I'm with Luke. The first question is indeed, how do you know that heads are OK?

Also there will be no more suggestions, as all of them are above.

OK, OK. If another suggestion is absolutely indispensable, then I'll throw in one, with a probability of 1%, no more: PCB is damaged in a way that's nearly impossible to notice. To rule this idea out test the PCB with a 100% healthy drive.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

I have one more suggestion...send the drive to a professional data recovery lab for an assessment.

_________________
Luke
Recovery Force Data Recovery

Agree, if you think this drive "initialises perfectly" and are just assuming "heads are ok" then your diagnosis procedure is seriously flawed, with respect.

Outsource it to someone who knows what they're doing.

No offence, just telling it how it is

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

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

Thank you all for the reply



The Patient heads are working fine on the Donor Drive and the Donor remains in the the same state as with the Original heads native heads.
I am assuming the ROM could be original for the reason as the Sr no is matching.
Any suggestions welcome.
Thanks

Unless you accidentally posted the wrong picture, the SN in your picture is not a true SN. It is a generic code. Unlike other F3s, this model is one of those that does not seem to post the SN.

If the heads are good, then the problem is likely related to firmware corruption of some sort. Have ruled out the PCB already, just to ensure?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Please read the answers above carefully.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

When i say SN means i am talking about the Sr No. in ROM
Pls check the attachment
So it looks like SA corruption. Any chances of retrieval ?
Thanks

What does it sound like? What was the donor S/N and manufacturing & date location? What have you tried already? Lots of questions needing an answer before helping...

Sorry if i was not clear here

The above drive starts and sounds like it initialized or as sounds like FW issue.
i have taken following steps.
1) Changed PCB - Works fine on another disk perfectly
2) Changed heads - These heads work fine on another disk perfectly.
3) Attempts to gain terminal access with shorting terminals also failed

S No. S2A43E0Z
SITE CODE : SU
DATE CODE : 12313

Thanks

Huh, unlatching heads and all? All I can think of is that you send it to our lab, we can talk via P.M. if you want to.