wd50ndzw slow read

[SirA]

Hi All. Hopefully someone has experienced this and can shed some light on the possible causes. I have seen quite a bit about WD SA issues causing Slow Reads/Writes, but nothing specifically on this drive.

The drive will read/copy data correctly in DMDE, and will show up and can be cloned in HDDSuperClone. Problem is, copying ~60GB of files took close to 2 months, and cloning is transferring at ~40k/sec.

Does anyone know of any potential fixes, or possible causes for this behavior?

[DRUG]

It's a miracle that the drive is still alive.

That is called Slow Issue and haunts many WD drives.

You can fix it with pc3k or any other hardware tool (even with hddsuperclone, but I have never done it).

Read this:

https://forum.hddguru.com/viewtopic.php?f=1&t=28538

[SirA]

Amazing. I seem to have missed this in my searching. I will definitely look into this and see if this helps at all.

Thank you for your suggestion.

[SirA]

Am unable to get drive to initialize/become ready in WDMarvel. Detects the drive fine, and can read the Serial and Model.

Ran firmware through fzabkar's WDRomv17, and it says bad Module 47. Looked at the exported module 47 and appears to be shot.

Would someone be willing to verify my rom for me?

[michael chiklis]

Acelab say that is not a good idea to do the "slow read" fix on this smr drives, it can cause further issues and will not make the drive fast.
Many pros here just let this type of drives clone slowly as they can, and wait days / weeks.

https://forum.acelab.eu.com/viewtopic.php?f=155&t=10720

[fzabkar]

Am unable to get drive to initialize/become ready in WDMarvel. Detects the drive fine, and can read the Serial and Model.

Ran firmware through fzabkar's WDRomv17, and it says bad Module 47. Looked at the exported module 47 and appears to be shot.

Would someone be willing to verify my rom for me?

There would be two copies of module 0x47, an active copy and an inactive one. As long as the active copy is OK, the drive will spin up.

[michael chiklis]

Acelab say that is not a good idea to do the "slow read" fix on this smr drives, it can cause further issues and will not make the drive fast.
Many pros here just let this type of drives clone slowly as they can, and wait days / weeks.

https://forum.acelab.eu.com/viewtopic.p ... r+slow+fix

WOW !!! Sorry, it's a wd50ndzw ... I was not aware. I did reply as if it were an older drive.

A lot of info still need to be known from new smr drives
I'm still waiting for a solution in the future, i also hope that will come out a soution to repair dynamic translators on smr toshiba drives... very few people know about it and pc3000/MRT still don't have a solution for that.

[maximus]

I am curious if a few tricks can be used to speed this drive reading up using hddsuperclone. Specifically maxing out the cluster size using direct USB mode, and maybe soft/hard resets with the read twice option (see the videos for more info).
https://www.youtube.com/watch?v=yX7HfHH0O6Y
https://www.youtube.com/watch?v=5JqP6HpUP8w

[ddrecovery]

Slow Responding fix in RAM does occasionally work on SMR drives.

[michael chiklis]

The problem on smr hdd is that 2nd level translator get changed (written) while we clone UA, this makes the drive slow... and could break 2nd translator.
The solution from AceLab is to lock writings on UA (at SA level), this will prevent changes on 2nd level translator, faster reading and keep alive weak heads.

[ddrecovery]

The problem on smr hdd is that 2nd level translator get changed (written) while we clone UA, this makes the drive slow... and could break 2nd translator.
The solution from AceLab is to lock writings on UA (at SA level), this will prevent changes on 2nd level translator, faster reading and keep alive weak heads.

That would be great if it worked. I have had 3 cases over the last few months where UA is locked and the secondary translator still gets corrupt.

[ddrecovery]

What about locking writing to UA and then patch 02 on RAM ?
How do you lock writing on UA ?

It is automated via PC-3000.

[michael chiklis]

How do you lock writing on UA ?

Acelab shows how to use TLER command (time limited error recovery)
https://youtu.be/47eXzxZk-0E?t=1458

[michael chiklis]

[ddrecovery]

How do you lock writing on UA ?

Acelab shows how to use TLER command (time limited error recovery)
https://youtu.be/47eXzxZk-0E?t=1458

TLER is different from locking the UA, or were you referring to something else?

[fzabkar]

Try setting the TLER (ERC = Error Recovery Control) level to its lowest possible value using HDAT2.

https://www.hdat2.com/files/hdat2en_481_v10.pdf (page 66)

[michael chiklis]

As i understood from acelab video, TLER does more than setting low value for error recovery control.
It does disable a lot of modules on SA

[michael chiklis]

How do you lock writing on UA ?

Acelab shows how to use TLER command (time limited error recovery)
https://youtu.be/47eXzxZk-0E?t=1458

TLER is different from locking the UA, or were you referring to something else?

Probably i did some confusion, locking writings on UA is another option on pc3000.
I don't own pc3000, i just watch some videos and read on forum about it.

[michael chiklis]

I found where is located the lock UA option


is in the 190 module editing, that's the 2nd level translator module.

[ddrecovery]

Quickest way to lock UA is via the SA menu.

Attachments