Need firmware for pc3k WDC WD20EARS-00MVWB0 25.12E

[fzabkar]

I downloaded the resource dump linked by "fzabkar" and i took from it module 32 and i wrote into my drive ...

I don't know why you did this, but did you match the MOD version?

[pcimage]

The drive has at least one bad head

[Spildit]

The drive has at least one bad head

I totally agree. I think head 1 is gone.
Maybe it's possible to depop, regen translator with p list, then it would be like a drive with less one platter. If you clone that drive you should get blobs of data that can be searched with file carving.
It will not be like DDI with the space for you to fill with the missing data later when you swap heads, but if it reads from the other platters i think that at least some data will be recoverable with file carving.
Of course i might be wrong, but you can restore the modules and rom and the drive will be as it is now.

[fzabkar]

I notice that in the SMART report the Current Pending Sectors attribute has a worst normalised value of 1. This suggests that at one time there were several thousand pending sectors but these have since been returned to service. Sounds like an intermittent fault to me ...

[michael chiklis]

I downloaded the resource dump linked by "fzabkar" and i took from it module 32 and i wrote into my drive ...

I don't know why you did this, but did you match the MOD version?

Yes MOD version is the same

My original mod 32:

mod 32 resource dump:

[michael chiklis]

I notice that in the SMART report the Current Pending Sectors attribute has a worst normalised value of 1. This suggests that at one time there were several thousand pending sectors but these have since been returned to service. Sounds like an intermittent fault to me ...

Could it be a smart issue?
It's possible to disable smart in WDR 3.0?

This was the original smart status:

Smart status now:

[Spildit]

Use mhdd. The command is
Smart off .
WDR 3.0 can clear smart.

[fzabkar]

SMART isn't the reason for your problems. SMART is merely reporting the problems.

AISI, the Raw Read Error Rate, Seek Error Rate, and Current Pending Sectors were clues that the drive had a head fault. Your defect list pointed to head 4, but subsequent testing hinted at head 1.

Your latest SMART results are typical of a new drive which has not yet recorded sufficient activity in order for the SMART data to be statistically significant. That's why you see a lot of "253" values.

[Spildit]

That is because he resetted smart using wdr

[michael chiklis]

Your defect list pointed to head 4, but subsequent testing hinted at head 1.

If i decide to do head depop, should i do it on head 1 or head 4?
Or both?

[Spildit]

i would go for head 1 first. If it doesn't improve anything i would return head 1 to use, re-flash rom and try to depop head 4.

[michael chiklis]

I tried to copy files and folder in dos with NTFS4DOS utility, but i don't understand why it copies only the first file in the directory.
This utility it ignores all other files in the directory when i give the copy command (it ignores also all sub-directorys).
Maybe the problem is due to the issue on drive...

Examples of commands which i tried:
1. "copy e:\foto d:foto"
2. "cd e:\foto"
"copy *.* d:\foto"

Both this commands copy only 1 file of the directory (the first one)

P.S.
With NTFS4DOS i'm able to see all files in the directory (with DIR command), but not to copy all of them!!

Do you know some other dos program which are able to copy files and folders for NTFS sourse partition?

[Vulcan]

Both this commands copy only 1 file of the directory (the first one)

That's expected, because they are the wrong commands for the result that you are requesting. You need to investigate the DOS xcopy command and its options (e.g. /s /e) in order to copy sub-directories. I haven't used NTFS4DOS - any issues with that are a different problem. You need to try the correct DOS command (i.e. xcopy) first

[michael chiklis]

I tried xcopy, doesn't detect ntfs partition!
In NTFS4DOS option /s /e are not able

[Vulcan]

There are other DOS NTFS readers, but I don't know which ones you've already tried... As I explained, when you find one which works for you and which mounts the NTFS partition as a drive letter, you need to understand the limitations of the DOS copy command. Also I didn't see you explain why you are trying to do this from DOS.

[michael chiklis]

There are other DOS NTFS readers, but I don't know which ones you've already tried... As I explained, when you find one which works for you and which mounts the NTFS partition as a drive letter, you need to understand the limitations of the DOS copy command. Also I didn't see you explain why you are trying to do this from DOS.

Because cloning the drive is not an option due to the very low speed (i don't even have those expensive tools for cloning as DDI).
I need to recover only pics folder (which is about 100GB), in dos i can access to the folder directory and i can see all files are inside, but i hadn't luck on copying those until now.

[michael chiklis]

I tried 2 more MOD read with WDR.
1: Read with "by ID" ticked, which i already did few days ago, all module are checked as "good" with green mark.
2. Read with "by ID" unticked, all modules are checked ad "bad" with red mark.

In WDR i get this errors log when i try to read with unticked "by ID".

Someone does know if this is due to software bug or to faulty drive?

[Spildit]

There are other DOS NTFS readers, but I don't know which ones you've already tried... As I explained, when you find one which works for you and which mounts the NTFS partition as a drive letter, you need to understand the limitations of the DOS copy command. Also I didn't see you explain why you are trying to do this from DOS.

Because cloning the drive is not an option due to the very low speed (i don't even have those expensive tools for cloning as DDI).
I need to recover only pics folder (which is about 100GB), in dos i can access to the folder directory and i can see all files are inside, but i hadn't luck on copying those until now.

copy *.* (destination folder) should have worked to copy all files from a normal dos prompt.
I think that the other option will be copy a file at a time ...

[Spildit]

I tried 2 more MOD read with WDR.
1: Read with "by ID" ticked, which i already did few days ago, all module are checked as "good" with green mark.
2. Read with "by ID" unticked, all modules are checked ad "bad" with red mark.

Good MOD read by ID.JPG

Bad MOD read on both head.JPG

In WDR i get this errors log when i try to read with unticked "by ID".

error log on bad MOD read by head.JPG

Someone does know if this is due to software bug or to faulty drive?

MAYBE Head 0 is damaged and the drive is reading SA from the 2nd copy then

[michael chiklis]

SA 2nd copy is on head 1?
If i untick "by ID" i get error on head 0 and also head 1