Interesting issue WD5000AVDS-63U7B0 - seqence 5click.

[pikus_09]

Hello everybody, today have a intresting issue with my WD5000AVDS-63U7B0(native PCB 2060-701640-001 internal ROM). So pcb I borrowed from the disk wd10evds-63u8b0 (pcb: 2060-701640-001 rev A) dragfly2 (both were identical) that I think borrow. So I have uploaded Rom native did it go ok, then I loaded the loader and started to upload the original modules. Went ok. I click restart ..... And hear the sequence 5 clicks then second off 5 seconds of silence clicks 5 clicks and the motor stops. I conclude that the head is not in SA. Moreover, I ruled out Bad in SA, because the scan SA Area is not found any Bad sectors, further blocking loading FW, makes it sees MOD 01 and a list of modules and module check did not show any irregularities. I was thinking almost the same situation as with wd Black. You had maybe a similar situation to mine? Any suggestion?
I Used Full WD Marvell 9C, Sediv at this time not work(licence bye bye).
Standard, Head test in SA suggest all head good.

[pikus_09]

Why did you borrow PCB from other drive ?

Because native PCB have bad internal ROM. Patient PCB is full compatibile with AVDS.

Was your PCB dead ?

Native PCB is bad, because internal ROM is dead.

Did the drive stop working with native PCB ?

Native PCB is Dead(internal ROM is BAD) Situation takes place on the PCB borrowed

Do you have full backup of SA modules and ROM from original drive ?

Yes, I have full backup ROM, modules

If you have "original modules" then i guess you were playing with firmware tools on the drive when the drive "died"....

Did you run ARCO or SS on it to "kill it" ? Did you use something like calibrators or format SA or whatever ?

NO, any calibrators, Self tests, and ARCO. Only Write Oryginal SA modules, and ROM.

Is the native PCB still functional or did you kill it or it's ROM ?

5x write Native PCB is dead, patient PCB from WD10EVDS-63U8B0, when fully work perfect.

If native PCB is still ok then :

1 - Restore ROM from backup.
2 - Block SA access if needed.
3 - Power off/on.
4 - Change regions on RAM to original ones.
5 - Load overlays.
6 - Load DIR from file (backup) to RAM.
7 - Write all modules from backup to drive.
8 - Write original ROM again or restore regions.
9 - power off/on.

Smile !

I try, but your method nothing changem because problem is the same. seqence 5 clicks, and motor spin down.

I like the part of the
Quote:
Sediv at this time not work(licence bye bye).

Yeah, yeah I know you're jealous of this

[pikus_09]

Try another PCB from the exact same drive model and family with the same pcb revision ?

AVDS is Drag Fly 1 Family, EVDS is Drag Fly 2 Family. And
Native and patient PCB are the same 2060-701640-001 REV A
AVDS stricker 2061-701640-700 AD
EVDS stricker 2061-701640-300 AAD1
both drives are Green AV-GP.

If drive stopped working from one day to another without you using tools on the drive then most likely bad heads/pre-amp.

Drive have BAD internal ROM a long time, so I decided to check or even works at all, so I borrow PCB from to EVDS to AVDS.
So, if heads are bad, preamp, how You explain the fact that the scan area SA, test heads, confirmed the efficiency of the surface, heads? Check module shows all the modules OK? Similar problem with my WD Black WD2002FAEX

I find it amazing that SeDiv people don't supply new license to users of the tool when something like this happens. People are supposed to pocket out $700 or more on that stuff then you change a simple setting on BIOS or you change some hardware that dies like a memory module or pci card or you upgrade your AV software and then .... license bye-bye and you have to buy-buy another copy for more $700 ?

Yeah I know, such a policy Sediv.


Did you kill ROM using firmware tools ? If yes then problem is most likely pcb/rom. Yes, Native PCB kill SHIT WDR 3.2, 3 years ago.

[pikus_09]

Are you saying that you can READ ALL MODULES OK with the new PCB ?

Yup, provided that Block Loading FW, click check all mods, and WD marvel Check all good in both copies of modules.

If so then most likely you have WRONG ADAPTIVES or translator is not properly initialized because of, for example, bad head.

well, Adaptives? may be.
MOD 30 and 35 are clear, and not SA defect list, head test suggest Head 0 and Head 1 OK, read/write, and Scan SA Surface.

Maybe you messed up really bad and modules that you uploaded are no longer original ?

SA copy, and ROM is oryginal from WD5000AVDS-63U7B0
Microcode version: 09000070, OVL 11: 00900071.

Check modules. If all ok can't you SS the drive ? Are ROM compatible with overlay ?

I checked mods and all mods OK, contains OK, CRC and header OK, provided that block loading FW, Yes, no problem, I can take pictures, work with this disk. if only I the PC with this disk.

[pikus_09]

Self-Scan the drive ?

How I perform a self test, if not detect the drive?

Do a full internal format with P and G list ?

No, Because Drive can't read SA.

[pikus_09]

What this is strange?

[pikus_09]

Because, Drive read modules when Block loading Firmware. When restart FW to normal state then begins seqence 5 clicks, pause 5 clicks pause 5 clicks, and spin down.
Do you understand me?

[hpw333]

Because, Drive read modules when Block loading Firmware. When restart FW to normal state then begins seqence 5 clicks, pause 5 clicks pause 5 clicks, and spin down.
Do you understand me?

firist thing if you sure that 2 pcb are compatible
do these steps

1- region map edit + change 01 address in both copies
2- reset hdd
3- load overly
4- is your hdd spin up or spin down ??
if up then test heads
if down then change pcb and write good rom (256 kb ) then do these steps again

[pikus_09]

firist thing if you sure that 2 pcb are compatible
do these steps

Yes 2 PCB are compatybile.

1- region map edit + change 01 address in both copies
2- reset hdd
3- load overly
4- is your hdd spin up or spin down ??

In this case My Hdd Spin Up, not spin down

if up then test heads

Yes, Spin Up, not spin down, and Test Head in Sa Area is good, and SA Scan defet shows no bad sectors in SA area.

if down then change pcb and write good rom (256 kb ) then do these steps again

Other PCB 1640 in 256K ROM like 2060-701640-002 REV A is not work with my drive, because native PCB have MCU 88i8945 in internal ROM(192K).

[jermy]

Other PCB 1640 in 256K ROM like 2060-701640-002 REV A is not work with my drive, because native PCB have MCU 88i8945 in internal ROM(192K).

Have you tried to increase the file up to 256K (filled with 0xFF) ?

[hpw333]

upload your modules stuff here
write new full FW For your HDD
and you need to be sure that all key module is ok if you need your data back
if you need only repair your HDD
just write new Firmware for your hdd
till me if it detected without any problem or no

[pikus_09]

Have you tried to increase the file up to 256K (filled with 0xFF) ?

Yup, and Drive not spin Up.

upload your modules stuff here
write new full FW For your HDD
and you need to be sure that all key module is ok if you need your data back
if you need only repair your HDD
just write new Firmware for your hdd
till me if it detected without any problem or no

Tomorrow attach full Back Up FW. I'm sure in 100% that modules are good(checksum, headers)
Yeah, right I need repair my drive, because this drive is empty, and shame thrown away.

BTW, Thank you for all replies, really thank you Friends for Help.

[hpw333]

Have you tried to increase the file up to 256K (filled with 0xFF) ?

Yup, and Drive not spin Up.

upload your modules stuff here
write new full FW For your HDD
and you need to be sure that all key module is ok if you need your data back
if you need only repair your HDD
just write new Firmware for your hdd
till me if it detected without any problem or no

Tomorrow attach full Back Up FW. I'm sure in 100% that modules are good(checksum, headers)
Yeah, right I need repair my drive, because this drive is empty, and shame thrown away.

BTW, Thank you for all replies, really thank you Friends for Help.

For Refurbishing this is nice case for repair
let me know after you change Fw is your HDD detect normally or no

[pikus_09]

For Refurbishing this is nice case for repair
let me know after you change Fw is your HDD detect normally or no

Ok,
Certainly I inform, can actually content modules are damaged, despite the efficient checksums and headers. Intresting

[hpw333]

For Refurbishing this is nice case for repair
let me know after you change Fw is your HDD detect normally or no

Ok,
Certainly I inform, can actually content modules are damaged, despite the efficient checksums and headers. Intresting

i see all your replies again
why you make problem so difficult although it need only 5 min for Repair ?

your heads ok , your pcb good , so problem must be in FW

you Region map edit , load overly , no cliking , hdd spin up , this mean prb in FW

your problem may be in one of the following modules

1- 02 or 03
2- p-list or translator

this mean 02,03,31,33 0ne of this modules is reason for cliking
and spin down
you can know reason after write new FW with same microcode

i wait for you to change firmware and give Result for HDD Detect nomrally or no

[pikus_09]

Hi friends and inform your max 2-3 day because now I'm not responding . Ehh my brain is not work property. must back to health, and then back to this issue, sorry friends really sorry

[Martin]

Interesting to take a look on the registers, usually drive shows error codes according to it's faults correctly.
Actually, here is an answer..

Because, Drive read modules when Block loading Firmware. When restart FW to normal state then begins seqence 5 clicks, pause 5 clicks pause 5 clicks, and spin down.

Additionally, you sad, that drive doesn't spin down after changing 0 region on 1 region.
Problem with FW. Probably, some modules are not correct or not native. Does this drive was anywhere before you? Did you compare SA copies (at least important modules) each to other?

[pikus_09]

Hi, I'm Back to the health.
So back to my theard. So I prepared screen shoot, how does this look:

Write ROM ver: 00900070R
Everything is OK

Load Overlays, and Start erasing Tracks. And again everything is OK

Load Overlays, and Clean SA Area

Writing Oryginal Modules

And Now begins Seqence 5clicks, and Drive is not detect, not work everything.
Succesfully 380 modules Write.

And Head Test:

Code:

Head Test Read/Write
2016-05-29 23:04:16: Çŕďčńü ňđĺęŕ ďî ăîëîâęĺ 0 - Ok
2016-05-29 23:04:20: ×ňĺíčĺ ňđĺęŕ ďî ăîëîâęĺ 0 - Ok
2016-05-29 23:04:54: Çŕďčńü ňđĺęŕ ďî ăîëîâęĺ 1 - Ok
2016-05-29 23:04:57: ×ňĺíčĺ ňđĺęŕ ďî ăîëîâęĺ 1 - Ok

Interesting to take a look on the registers, usually drive shows error codes according to it's faults correctly.
Actually, here is an answer..

everything is show in screens

Additionally, you sad, that drive doesn't spin down after changing 0 region on 1 region.
Problem with FW. Probably, some modules are not correct or not native. Does this drive was anywhere before you? Did you compare SA copies (at least important modules) each to other?

well, Mods important, and critical are the same, and attach full SA COPY(Modules, ROM).

you can know reason after write new FW with same microcode

i wait for you to change firmware and give Result for HDD Detect nomrally or no

Sorry Friend, but I can't write new FW with the same microcode, because I don't have, a compatibile donor FW, themselves FW with WD5000AADS-00S9B0 with the same microcode, unless may be with WD5000AADS-00S9B0?

Attachments

WDCWD5000AVDS-63U7B0_WD-WCAV92752249.rar

Oryginal Backup With My drive WD5000AVDS-63U7B0

(4.9 MiB) Downloaded 606 times

[pikus_09]

I don't know why you did ERASE TRACKS of SA.

Do all again but this time as soon as you LOAD OVERLAYS and you get correct drive detection with S# XYZ go to RAM and EDIT DIR in RAM. Load DIR from you file (mod 01). Save to RAM !!! No go to S/A operations and write all modules. Done.

OK, because erase track I treat as a full-format areas SA. DFL company, and ACE lab recommend Erase Track
before writing Sa mods,Btw, your method not work, sitation the same.

And STOP USING that Restart FW thing. Just power off/on the drive !!!

Ok.

Oh ... and of course ... did you block SA access by editing FW zones on ROM ??? If so go to RAM and edit it back on RAM !!!!

You will want to have correct zones + correct DIR on RAM first and only then you should write modules from backup !!!

Otherwise it will not write or will write to incorrect place !!!!

Ok, I write modules in original correct place, and Click, Click, click, click, click
something seems to me that the PCB is damaged after these hits

[hpw333]

I don't know why you did ERASE TRACKS of SA.

Do all again but this time as soon as you LOAD OVERLAYS and you get correct drive detection with S# XYZ go to RAM and EDIT DIR in RAM. Load DIR from you file (mod 01). Save to RAM !!! No go to S/A operations and write all modules. Done.

OK, because erase track I treat as a full-format areas SA. DFL company, and ACE lab recommend Erase Track
before writing Sa mods,Btw, your method not work, sitation the same.

And STOP USING that Restart FW thing. Just power off/on the drive !!!

Ok.

Oh ... and of course ... did you block SA access by editing FW zones on ROM ??? If so go to RAM and edit it back on RAM !!!!

You will want to have correct zones + correct DIR on RAM first and only then you should write modules from backup !!!

Otherwise it will not write or will write to incorrect place !!!!

Ok, I write modules in original correct place, and Click, Click, click, click, click
something seems to me that the PCB is damaged after these hits

they recommend to Erase tracks and this is useless step
you already format SA , or Write new FW , no need to erase track at this step
and i would like to repair this case online
if you are interest PM Me
or add me on Skype ID : hpwlab