HDD GURU FORUMS

How such problem can be solve?


0039: 1 : B : 33731: 17:Yes : Ok : Ok : 34E3490D :008000CN:Loaded part of microprogram code
0037: 0 : Dr : 33748: 1:Yes : Ok : Ok : 4F4B4658 :00010000:Gain Call Data Module
0037: 1 : Dr : 33748: 1:Yes : Ok : Ok : 4F4B4658 :00010000:Gain Call Data Module
002D: 0 : Dr : 33749: 450:Yes : Ok : Ok : 33324919 :008000CN:Debug Log
002D: 1 : Dr : 33749: 450:Yes : Ok : Ok : 33324919 :008000CN:Debug Log
002E: 0 : B : 34199: 450:Yes :Error: Ok : D5FBC099 :00020004:Loaded part of microprogram code
002E: 1 : B : 34199: 450:Yes :Error: Ok : D5FBC099 :00020004:Loaded part of microprogram code
00B5: 0 : Dr : 34649: 160:Yes : Ok : Ok : 39F3A9E5 :008000CN:WRRO Log Module
00B5: 1 : Dr : 34649: 160:Yes : Ok : Ok : 39F3A9E5 :008000CN:WRRO Log Module
006B: 0 : B : 34809: 4:Yes : Ok : Ok : 690F285B :008000CN:Loaded part of microprogram code
006B: 1 : B : 34809: 4:Yes : Ok : Ok : 690F285B :008000CN:Loaded part of microprogram code
003A: 0 : : 34813: 12:Yes : Ok : Ok : E486CFB4 :00000100:
003A: 1 : : 34813: 12:Yes : Ok : Ok : E486CFB4 :00000100:
0028: 0 : Dr : 34825: 16:Yes : Ok : Ok : 4F440A52 :00030000:Factory Self Test script
0028: 1 : Dr : 34825: 16:Yes : Ok : Ok : 4F440A52 :00030000:Factory Self Test script
003B: 0 : : 34841: 16:Yes : Ok : Ok : 4F7548A1 :00030000:
003B: 1 : : 34841: 16:Yes : Ok : Ok : 4F7548A1 :00030000:
003C: 0 : : 34857: 16:Yes : Ok : Ok : 4F44423F :00030000:
003C: 1 : : 34857: 16:Yes : Ok : Ok : 4F44423F :00030000:
003D: 0 : : 34873: 16:Yes : Ok : Ok : 4F44423E :00030000:
003D: 1 : : 34873: 16:Yes : Ok : Ok : 4F44423E :00030000:
003E: 0 : : 34889: 16:Yes : Ok : Ok : 4F44423D :00030000:
003E: 1 : : 34889: 16:Yes : Ok : Ok : 4F44423D :00030000:
003F: 0 : : 34905: 16:Yes : Ok : Ok : 4F44423C :00030000:
003F: 1 : : 34905: 16:Yes : Ok : Ok : 4F44423C :00030000:
006F: 0 : B : 34921:1905:Yes : Ok :Error:47E77D84/A05CBEB8:AOZ30000:Loaded part of microprogram code
006F: 1 : B : 34921:1905:Yes : Ok :Error:47E77D84/A05CBEB8:AOZ30000:Loaded part of microprogram code
0116: 0 : : 36826: 6:Yes : Ok : Ok : 34EE4830 :008000CN:
0116: 1 : : 36826: 6:Yes : Ok : Ok : 34EE4830 :008000CN:
0118: 0 : : 36832: 26:Yes : Ok : Ok : 71092727 :008000CN:
0118: 1 : : 36832: 26:Yes : Ok : Ok : 71092727 :008000CN:
0119: 0 : : 36858: 5:Yes : Ok : Ok : 833776F1 :0100....:

Hi,

Try to build a good copy of those based on the 2 copies.
After that try to write them back.
If drive can't write, use hotswap.

Can you access data? And Does drive ID ?

I copied all the modules but the problem stay after rewriting tham again.
It seems like it didn't affect the drive at all.
I have access to the data. This drive has 4 heads.
I mannaged to save the data from 3 of those 4 heads but have problem from the last.
I checked the heads with PC3000 and it showed me that all of them are good.
I don't a donor for that drive. Is there any other way to solve that issue and get easy access to the data from the last head?


Regards,

You may find that those modules are protected and dynamic (restricted access by MCU FW) and therfore PC3k cannot read them. Quite typical of servo related code etc etc etc

Try read module by ID and you will see

Looks like could be problem with checksum/header. Sure you can repair this within the utility. You tried this?

Lot's of times WD utility says heads are fine when they are'nt.

Bosse

mr_spokk wrote:Lot's of times WD utility says heads are fine when they are'nt.

Bosse

That's right, sometimes this is the case.

You will need to change heads on this drive I suspect.