Need firmware for pc3k WDC WD20EARS-00MVWB0 25.12E

[Spildit]

Yes, but it would be a mod that is not in use, and fixing that mod wouldn't change anything, as it's a mod that is not in use.

[michael chiklis]

I post the original rom file, and the one after the "repair"

original and repaired rom.rar

(450.41 KiB) Downloaded 344 times

I think the repaired one which WDR calls NewFlash.bin is damaged.
The original maybe is good (the original rom is 2512.bin)

Someone can tell me if NewFlash.bin is really damaged as i think and why does get damaged when i clic on repair?
WDR should fix it, maybe version 3.0 is not good...

Last edited by michael chiklis on April 13th, 2013, 9:51, edited 1 time in total.

[fzabkar]

Yes, but it would be a mod that is not in use, and fixing that mod wouldn't change anything, as it's a mod that is not in use.

I understand that MOD 107 is irrelevant, and I understand that the actual problem is a head fault. I'm just indulging the OP and trying to put his own mind at rest.

[Spildit]

I post the original rom file, and the one after the "repair"

The attachment original and repaired rom.rar is no longer available

I think the repaired one which WDR calls NewFlash.bin is damaged.
The original maybe is good (the original rom is 2512.bin)

Someone can tell me if NewFlash.bin is really damaged as i think and why does get damaged when i clic on repair?
WDR should fix it, maybe version 3.0 is not good...

Yes, NewFlash is damaged because it's missing some part of its code, most likely the code that can't be read on the damaged module.
What i'm saying is that WDR Repairs ROM by reading modules in SA to create the ROM file. If some necessary modules can't be read from SA that part will be missing on the generated ROM.
That is why on the log you have ERROR. It creates the ROM file anyway, but that file will be missing the data from the modules it couldn't read.
The Repair is just a function to copy data from SA on platters to get a new working compy of the ROM. If the copy on the platters are damaged, as it happen on your case, then the copy of the ROM to flash will be damaged too.

Attachments

[michael chiklis]

I did a remote diagnosis with A-FF Repair Station, this is the result:

A-FF Repair Station.JPG (19.62 KiB) Viewed 9607 times

WDR report that the only SA damaged modules are 6F, and 107 and both don't affect the rom repair if i understood right.
Anyway i can't fix them!!

Last edited by michael chiklis on April 13th, 2013, 10:26, edited 1 time in total.

[Spildit]

I did a remote diagnosis with A-FF Repair Station, this is the result:

A-FF Repair Station.JPG

WDR report that the only SA damaged modules are 6F, and 107.
i can't fix them!!

6F it's not in use, 107 it's only used to Regen Rom.
Guess that A-FF is correct and the problem is NOT with the firmware.
Also you have tryed the equivalent to "Fix slow issue" or whatever ... and it didn't work ...
Also when testing heads sometimes you get Head 1 as BAD and sometimes you get all heads ok. Note that only HEAD 1 is displayed sometimes as bad.
My guess is that Head 1 sometimes doesn't work properly while sometimes it read something ..... and that causes the slow down ...

At this point Head Swap is necessary, and the only choice is to send the drive to a pro.

[Spildit]

If you don't need the data depop head 1 and see if it works. If so you will have a working drive with less capacity. You can also self-scan to get rid of possible bad sectors or use the option to format adding the defects to the factory P List.

[Spildit]

If you really need the data on the drive no matter what software you use, you can even have pc-3000, it will not swap the bad head for you.
If you disable the head from RAM using 6.0 or other tool or DDI you will clone the drive with the heads that are left, but ... you will only retrive small text files and stuff like that without damage ....

[michael chiklis]

ok, i end here.
Give me a information please...
If i use WDR 6.0 and disable head 1 on ram, do you think i will be able to image drive on good heads in normal speed?

If i do selfscan i will lose data?

[Spildit]

If i use WDR 6.0 and disable head 1 on ram, do you think i will be able to image drive on good heads in normal speed?

Maybe. If the problem is indeed with the bad head, and if there is just that.

Also you can try to backup all the modules and ROM with 3.0, then depop head 1 and clear translator, rebuild with p-list and try to clone it to another drive. As long as you keep a backup of all modules and ROM you can then turn on the head again.
It's risky, but you can try. Depop the head, try to clone, turn head on again......

If i do selfscan i will lose data?

Yes, you will. For sure. 100 % sure of it.

[michael chiklis]

I need a confirm from a PRO if head depop without ram will make loose all data or if is safe.
If depop doesn't destroy data i will try imaging the drive...

[Spildit]

I need a confirm from a PRO if head depop without ram will make loose all data or if is safe.
If depop doesn't destroy data i will try imaging the drive...

Maybe you will have better luck if you open a new thread and ask just that.

"Will a depop destroy all of my data ? " or something like that.

[Spildit]

And i would also do the head test a couple of times again to see if the same head produces the error again, and if it's allways the same head.
Guess that whatever damaged the PCB also damaged the head.

[mr_spokk]

I can confirm if you disable one head and managed to read the data on the other 5 good heads, the data on the disabled head is still intact.
BUT if the head that is disabled is somewhat damaged in it's "flying capability" then it WILL destroy the surface (data) of that platter.
So it's a high risk for DIY.

[Spildit]

Moving on. Save ROM and all modules,
Try to depop.
Try to read the data from the drive.
If it doesn't work you will have to turn on the disabled head and restore ROM too.

[michael chiklis]

Before to depop head 1, explain me what should I do to reactivate it later?
To turn on it again should i press reset translator and then recalculate translator with p-list?

[Spildit]

Service - Edit Heads Map. You can depop or edit the heads map to pace the heads in service again. You can save the head map first to restore it later. Also if you have a copy of the ROM and of the entire Modules you cal later restore the ROM if the drive changes it's model number, etc ... and also revert the changes that depop have made. But of course, you will most likely not be able to restore any data with that .... so it's at your own risk on experimental level and you assume that will 99% not work and you will loose data !

[Spildit]

Other option is to send the drive in to a data recovery firm

[michael chiklis]

FWIW, MOD 107 doesn't exist in the following resource dump:
http://www.datadonor.net/HD%20Western%2 ... 0MVWB0.rar

Other MODs such as 102, 104, 105 are "NOT_INIT", so they don't appear to be necessary.

Bytes 0x04 - 0x07 appear to be 01 00 1E 00 in the SA and 04 00 1E 00 in the ROM. Maybe that part of the header needs to be edited, too. ???

I downloaded the resource dump linked by "fzabkar" and i took from it module 32 and i wrote into my drive, then i did fast p-list translator recalculation.
Now the drive is faster in mhdd scan and is detect faster also in bios, but i still have the stop issue after few seconds (anywhere in the drive)
I did a test also with option "logical scan" in WDR.

As you can see i get all "?" after few good sectors.
Example from LBA 0:

I get all "?" from lba 326.992

----------------------------------------------

Another example from LBA 500.000.000:

I get all "?" from lba 500.509.184

If i begin scan since lba 500.509.000, i get all "?" from lba 500.509.432

----------------------------------------------

One more example, from lba 1.000.000.000:

I get all "?" from lba 1.001.439.944

If i begin scan since lba 1.001.430.000, i get all "?" from lba 1.002.494.240

This means that they are not really bad sectors, maybe still translator issue?

I guess the module 32 is clean now, but something more should be fix, any idea?

P.S.
I decided to not do head depop.

[Spildit]

Hi again,
I really don't know !
It can be translator issue or damaged head.
It will be nice if we manage to figure out what is going on with the drive.
Maybe someone can provide some hints...