WD20NMVW-11EDZS7

[unknown]

Hello!
The drive in topic shows all sectors ABRT. All modules backed up OK with no error.
After replacing heads the same problem. Back original heads the same problem.

Any thoughts what's the problem?
Thanks in advance.

[mr_spokk]

P/W locked?

[unknown]

No Password and not a translator issue either.
thanks for replies.
Any other thoughts, please?

[labtech]

What is the customer's story on what caused the drive to fail? Also, did anybody else work on the drive prior to arriving to you?

[unknown]

What is the customer's story on what caused the drive to fail? Also, did anybody else work on the drive prior to arriving to you?

As you know, all customers lies. He didn't tell me anything (but the top cover didn't opened before).
My diagnosis from the beginning:
It's USB drive (Shrek LT) spin up normally (not detected) Slow responding and/or bad head/s.
Converted to SATA (MRT never see it's family and no SA access) after some workaround I can backup all mods. and ROM.
After modifying mod 127 MRT can auto detect SA and mod dir.
I can access SA but no access user area (ABRT). (with patient heads and donor heads).

SO, what do you think?
Thanks in advance.

[fzabkar]

After modifying mod 127 MRT can auto detect SA and mod dir.

Isn't that where the password would be stored?

[unknown]

After modifying mod 127 MRT can auto detect SA and mod dir.

Isn't that where the password would be stored?

That's right. For enable/disable SA access too.

- Original ROM modules / head map and active directory of ROM modules.

Checked OK.

- Restore original 127 after patching 02 for disable background media scan.

Already done with no luck.

- If you have PC3K most likely you can decrypt/bypass the encryption.

I don't think it would be the problem. (by the way it's encrypted with aSmedia)

- There might be a problem with encryption keys locking access the LBA.

I think if there's a problem with key the drive will scan normally with encrypted data not ABRT.

And as your forum name sugests .... other possible causes for drive not to allow access to LBA are ... @unknown

You are right until now. Problem still unknown.

[labtech]

As you know, all customers lies

Sure, but when telling them that you need to understand what happened originally, so you can actually resolve the problem, therefore preventing billable hours/fees, then they will start talking. Telling what happened is in his best interest, no? Otherwise, there is no recovery happening.

[pcimage]

As you know, all customers lies

Sure, but when telling them that you need to understand what happened originally, so you can actually resolve the problem, therefore preventing billable hours/fees, then they will start talking. Telling what happened is in his best interest, no? Otherwise, there is no recovery happening.

Yep, we find that in 9/10 times the customer lies about what happened.

So sadly, we have to assume in all cases the the customer is lying about everything until proven otherwise.

Sad but true

[unknown]

The customer swear he was working on win 10 then unplug the drive then after a while he replug it again and the drive fail. That's all.

[rogfanther]

Ah, but :
Why did he unplug the drive and reconnect it after some (little ? ) time ? Maybe because his computer was experiencing some problem ?
Also, did he stop/eject the drive through windows, or just disconnect the cable ?

[Doomer]

Try to disable the SED crypto-engine all together (in module 02) and see if you can read the sectors after that.
If you can then that means the crypto-engine is not initialized properly, it happens sometimes.

[unknown]

Ah, but :
Why did he unplug the drive and reconnect it after some (little ? ) time ? Maybe because his computer was experiencing some problem ?
Also, did he stop/eject the drive through windows, or just disconnect the cable ?

I think this won't make a difference.
Thanks for reply.

Try to disable the SED crypto-engine all together (in module 02) and see if you can read the sectors after that.
If you can then that means the crypto-engine is not initialized properly, it happens sometimes.

I will try and post the results.
Thank you.

[unknown]

Try to disable the SED crypto-engine all together (in module 02) and see if you can read the sectors after that.
If you can then that means the crypto-engine is not initialized properly, it happens sometimes.

Unfortunately, no luck. I am trying from another method.

[fzabkar]

Could the ASMedia bridge be functionally and electrically equivalent to JMicron's JMS569? The latter does not support encryption.

What is the bridge part number? PCB part number? USB VID/PID?

I have collated various data here:
http://www.hddoracle.com/viewtopic.php?f=7&t=1404&p=10066

[Doomer]

Could the ASMedia bridge be functionally and electrically equivalent to JMicron's JMS569? The latter does not support encryption.

There is no encryption by ASMedia
Encryption is done by the drive itself

[fzabkar]

Could the ASMedia bridge be functionally and electrically equivalent to JMicron's JMS569? The latter does not support encryption.

There is no encryption by ASMedia
Encryption is done by the drive itself

If you follow my link to the HDD Oracle thread, you'll see the reason for my question. AIUI, WD has employed at least two different approaches to USB-connected SEDs, and these approaches are related to the type of non-encrypting bridge used.

[Doomer]

If you follow my link to the HDD Oracle thread, you'll see the reason for my question. AIUI, WD has employed at least two different approaches to USB-connected SEDs, and these approaches are related to the type of non-encrypting bridge used.

I don't understand what you mean by "two different approaches"
But ASMedia does no encryption, it's been checked

[fzabkar]

I don't understand what you mean by "two different approaches"
But ASMedia does no encryption, it's been checked

Did you follow my link?

[Martin]

Hello!
The drive in topic shows all sectors ABRT. All modules backed up OK with no error.
After replacing heads the same problem. Back original heads the same problem.

Any thoughts what's the problem?
Thanks in advance.

SED.