Problem with WD Marvel Demo

[elevtechlift]

I describe how to test heads in previous message

Disable all heads in Head map editor except 0
Restart drive
Try to read Modules

Repeat for each head
Any manipulation with ROM doesn't resurrect dead heads

I know but I don't know how to access the Head Map editor. How do I access it? Right now, I can't find it.

[Vlad]

"Heads" >> "Edit head map in ID0A".

[elevtechlift]

"Heads" >> "Edit head map in ID0A".

I found it and I tried disabling every head except 0. Unfortunately, no where in the editor lets me change the settings so all heads except one can be disabled. The "Ok" button remains disabled even after unchecking every head except leaving one head enabled.

[SRUTSSSSSSSS80]

Do you have a demo version? To manipulate the service, you need to buy the full version

[elevtechlift]

Do you have a demo version? To manipulate the service, you need to buy the full version

Yes. I see...

[Dragan78]

Hi. I use win 10 pro and when I run the programm it write Error checking Driver Signing! and then Driver WdMarv 64 failed to start. And after it close the programm.
What should i do?

[SRUTSSSSSSSS80]

Hi. I use win 10 pro and when I run the programm it write Error checking Driver Signing! and then Driver WdMarv 64 failed to start. And after it close the programm.
What should i do?

read Readme64.txt
To start the driver in the x64 version of Windows 7, 8, 10, run TestModeOn.bat file as administrator and restart the computer.
To cancel this changes, run TestModeOff.bat file as administrator and restart the computer.

[elevtechlift]

What do you want to rebuild?
I said you, SERVO_ERROR_CODE_BASE_SvirActSync means that HDA most probably is dead
Disable all heads in Head map editor except 0
Restart drive
Try to read Modules
If still SERVO_ERROR_CODE_BASE_SvirActSync, then disable head 0 and enable head 1
Try to read modules on head 1
Test all heads in this way
If all heads gives SERVO_ERROR_CODE_BASE_SvirActSync, put drive in the trash, it is not repairable

I bought a 1-month Plus license. I noticed Heads 0 and 1 produced the following error message:

Error reading module Dir, state - SERVO_ERROR_CODE_BASE_SvirLatchHang

Heads 2 through 7 did produce SERVO_ERROR_CODE_BASE_SvirActSync. So what does SERVO_ERROR_CODE_BASE_SvirLatchHang mean? Is there still a chance for the problem HDD to be recoverable in its current state?

[Vlad]

SERVO_ERROR_CODE_BASE_SvirLatchHang - latch that holds HSA in parcking zone when drive is off, doesn't opens...

[elevtechlift]

SERVO_ERROR_CODE_BASE_SvirLatchHang - latch that holds HSA in parcking zone when drive is off, doesn't opens...

I see… I’ll retest the heads again.