Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 2
  [ 25 posts ]  Go to page 1, 2  Next
  Previous topic | Next topic 
Author Message
DeVlL
 Post subject: Strange disk failure WD2500BEVT
PostPosted: September 1st, 2020, 6:33 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
Hi all.

I've been reading the forum for a long time but so far I haven't registered. But now I have a similar case of the thread op.

I have a WD2500BEVT unit that has a bad PCB, (the MCU chip was physically broken). Buy the PCB that corresponds to you. Before moving the U12 chip from the damaged PCB I wanted to first test the donor PCB to see if it starts the motor, in this aspect I start the motor but as we all know it clicks of dead in the absence of changing the u12 chip to the new PCB. The next step was to move the U12 chip to the donor unit. And here comes the problem, when I connect it to the computer again it does nothing, it has no indication of starting the engine. I checked the welds and they were good. The next thing I did was to put back the U12 chip that came from the donor and I started again like at the beginning but with the click of dead.

The next step was to read the U12 chip from the bad PCB with an external programmer. I did several readings and they are all edentic, so he got it right. The next thing I did was put the donor PCB chip in and burn the original bad PCB bios to it. I did erase chip, write and verification. Everything OK.

The next step was to put the new PCB back on the disk and the exact same thing happens to it, it does practically nothing.

Conclusion: I think the bios of the damaged PCB must be corrupt. It's weird because looking at Hex format you have data.

Could a bios reconstruction be done with the backups I have of the original and the donor?

It is assumed that the adaptives could be removed from the original.

Thank you and greetings.
Top
 Profile  
 
BGman
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 1st, 2020, 8:35 
Offline

Joined: September 30th, 2005, 7:33
Posts: 849
The original ROM is not compatible with the donor PCB. Check the white labels on them.

P.S. Post the full model name, family name, etc. if you want to be helped .
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 1st, 2020, 10:26 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
Hi.

WD2500BEVT - WXF1A7013817

These are the complete data of the PCBs:

ORIGINAL PCB
SEGRAFIED ON THE PLATE PUTS: 2060-771672-004 REV A
ON THE LABEL IT SAYS: 2061-771672-F04 AA XT AB42 EFBH B 0001110 1 111

DONOR PCB
SEGRAFIED ON THE PLATE PUTS: 2060-771672-004 REV A
ON THE LABEL IT PUTS: 2061-771672-F04 AC XS AB60 5GKA 6 0005160 1165
Top
 Profile  
 
colanco
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 1st, 2020, 11:34 
Offline

Joined: December 6th, 2012, 8:49
Posts: 290
Location: españa
Can you upload the file with the content of the original rom?
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 4:33 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
colanco wrote:
Can you upload the file with the content of the original rom?


Hi.

I attach the two rom. The ORIGINAL and the ROM of the DONOR

Regards


Attachments:
WD2500BEVT WXF1A7013817 BIOSCORRUPTA.zip [406.81 KiB]
Downloaded 369 times
Top
 Profile  
 
colanco
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 11:53 
Offline

Joined: December 6th, 2012, 8:49
Posts: 290
Location: españa
The original rom code is corrupted. At least the header.
Top
 Profile  
 
jcarlosmor
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 13:51 
Offline

Joined: August 5th, 2020, 22:27
Posts: 19
Location: Mexico
colanco wrote:
The original rom code is corrupted. At least the header.


Hello,

Which cases could corrupt the header? Do you know length of header for Caviar WD400 and WD800 drives? (I believe the header are maybe the first 256 bytes. I am correct?)

Thank you in advance.
Top
 Profile  
 
fzabkar
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 14:11 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15538
Location: Australia
The first 0x100 bytes are garbage. I have extracted the ROYL modules.

Code:
Analysing backup.rom.DONADOR.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
---------------------------------------------------------------------------
    0  5A 40   04     120 -  151C      18AC0     13FC  13FC    06   06   OK
   20  01 64   01    151D -  A5D1          0 c   B7E8  90B4    E5   E5   OK
   40  02 51   01    A5D2 -  FC2A       E464 c   7AB0  5658    24   24   OK
   60  03 26   01    FC2B - 103BB      16208 c    950   790    95   95   OK
   80  04 87   03   103BC - 1061C    4000080 c    36C   260    8C   8C   OK
   A0  05 82   03   1061D - 10E1D    4003DEC c    C04   800    97   97   OK
   C0  06 57   03   10E1E - 114FA   24000008 c    C1C   6DC    B7   B7   OK
   E0  07 FF   01   114FB - 2A79B   2401D000 c  20978 192A0    85   85   OK
  100  08 7B   01   2A79C - 32E50   24048800 c   AC50  86B4    19   19   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FEE1

Active directory flag = 0x00

Identifying SA regions ...

Reg#  Reg size    Reg loc
----------------------------
0x00  0x00031C80  0x00000000
0x01  0x00031C80  0x00042600
0x02  0x00031C80  0x00084C00
0x03  0x00031C80  0x000C7200

Verifying ROYL modules ...

ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
-----------------------------------------------------
000A  OK     0000003E  00000200   0003FFB2   00000000  OK
000B  OK     000000D1  00000200   0003FEE1   00000000  OK
0030  OK     00000400  OK         0003FAE1   00000000  OK
0047  OK     00000400  OK         0003F000   00000000  OK
000D  OK     0000008C  00000200   0003EF74   00000000  OK
004F  OK     00000400  OK         0003F400   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_00\000Bmods and Flash_00\020Bmods

Active directory is 0x0B -- directory 0x20B not present

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 4/4
Head map #1 = 0x0F / 0b00001111
Head map #2 = 0x00 / 0b00000000

DCM = | B | E S G S D 1 O
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE6AB446C20
Model Number = WDC WD6400BEVT-22A0RT0                 
Serial Number =                     


Analysing active 0x4F module ...

ROM version = 0014003R

Analysing active 0x47 module ...

Preamp values
-----------
0  083BC422
1  0931D315
2  0937B31D
3  0835C322
4  02200200
5  02200200

Microjogs
-------
0  0B77
1  0AFD
2  0B21
3  0ACC
4  0A0A
5  0A0A

Head/Media DCM = GS

Code:
Analysing backup.rom.orginal.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
---------------------------------------------------------------------------
  100  08 88   01   2A43C - 32B18   24048800 c   AC70  86DC    AC   AC   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FEE1

Active directory flag = 0x00

Identifying SA regions ...

Reg#  Reg size    Reg loc
----------------------------
0x00  0x0001A333  0x00000000
0x01  0x0001A333  0x00037500

Verifying ROYL modules ...

ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
-----------------------------------------------------
000A  OK     0000003E  00000200   0003FFB2   00000000  OK
000B  OK     000000D1  00000200   0003FEE1   00000000  OK
0030  OK     00000400  OK         0003FAE1   00000000  OK
0047  OK     00000400  OK         0003F000   00000000  OK
000D  OK     0000008C  00000200   0003EF74   00000000  OK
004F  OK     00000400  OK         0003F400   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_01\000Bmods and Flash_01\020Bmods

Active directory is 0x0B -- directory 0x20B not present

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 2/2
Head map #1 = 0x03 / 0b00000011
Head map #2 = 0x00 / 0b00000000

DCM = | B | N S G R H N V
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE25A35CE66
Model Number =                                         
Serial Number =                     


Analysing active 0x4F module ...

ROM version = 0014003V

Analysing active 0x47 module ...

Preamp values
-----------
0  083BA329
1  0639C513
2  02200200
3  02200200
4  02200200
5  02200200

Microjogs
-------
0  0C20
1  0B66
2  0A0A
3  0A0A
4  0A0A
5  0A0A

Head/Media DCM = GS


Attachments:
000Bmods.7z [784 Bytes]
Downloaded 351 times

_________________
A backup a day keeps DR away.
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 15:44 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
colanco wrote:
The original rom code is corrupted. At least the header.


So he was definitely right that it is corrupt.

fzabkar wrote:
The first 0x100 bytes are garbage. I have extracted the ROYL modules.

Code:
Analysing backup.rom.DONADOR.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC LDSC Att PCMBlock RAM size PCMBlk CS
Start ID CS Start - End address RAM / ROM Exp/Act
---------------------------------------------------------------------------
0 5A 40 04 120 - 151C 18AC0 13FC 13FC 06 06 OK
20 01 64 01 151D - A5D1 0 c B7E8 90B4 E5 E5 OK
40 02 51 01 A5D2 - FC2A E464 c 7AB0 5658 24 24 OK
60 03 26 01 FC2B - 103BB 16208 c 950 790 95 95 OK
80 04 87 03 103BC - 1061C 4000080 c 36C 260 8C 8C OK
A0 05 82 03 1061D - 10E1D 4003DEC c C04 800 97 97 OK
C0 06 57 03 10E1E - 114FA 24000008 c C1C 6DC B7 B7 OK
  E0 07 FF 01 114FB - 2A79B 2401D000 c 20978 192A0 85 85 OK
100 08 7B 01 2A79C - 32E50 24048800 c AC50 86B4 19 19 OK

LDSC = PM Loader Config String (32 bytes)
ID = ID byte of LDSC (byte #0)
CS = Checksum byte or word
Att = Attributes
PCMBlk = Program Code Memory Block
Exp = Expected checksum for PCMBLock
Act = Actual checksum for PCMBLock
c = compressed PCMBlock
size = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FEE1

Active directory flag = 0x00

Identifying SA regions ...

Reg# Reg size Reg loc
----------------------------
0x00 0x00031C80 0x00000000
0x01 0x00031C80 0x00042600
0x02 0x00031C80 0x00084C00
0x03 0x00031C80 0x000C7200

Verifying ROYL modules ...

ID Size (bytes) Address Checksum
dir hdr dir hdr
-----------------------------------------------------
000A OK 0000003E 00000200 0003FFB2 00000000 OK
000B OK 000000D1 00000200 0003FEE1 00000000 OK
0030 OK 00000400 OK 0003FAE1 00000000 OK
0047 OK 00000400 OK 0003F000 00000000 OK
000D OK 0000008C 00000200 0003EF74 00000000 OK
004F OK 00000400 OK 0003F400 00000000 OK

dir - Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr - Module ID/Size as reported in module's header
N/A - Not Applicable
BAD - Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_00\000Bmods and Flash_00\020Bmods

Active directory is 0x0B -- directory 0x20B not present

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 4/4
Head map #1 = 0x0F / 0b00001111
Head map #2 = 0x00 / 0b00000000

DCM = | B | E S G S D 1 O
: : : : : : : : : :
: : : : : : : : : unknown
: : : : : : : : top VCM
: : : : : : : ACA
: : : : : : bottom VCM
: : : : : HSA
: : : : media
: : : preamp
: : latch
: base
spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE6AB446C20
Model Number = WDC WD6400BEVT-22A0RT0
Serial Number =


Analysing active 0x4F module ...

ROM version = 0014003R

Analysing active 0x47 module ...

Preamp values
-----------
0 083BC422
1 0931D315
2 0937B31D
3 0835C322
4 02200200
5 02200200

Microjogs
-------
0 0B77
1 0AFD
2 0B21
3 0ACC
4 0A0A
5 0A0A

Head/Media DCM = GS

Code:
Analysing backup.rom.orginal.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC LDSC Att PCMBlock RAM size PCMBlk CS
Start ID CS Start - End address RAM / ROM Exp/Act
---------------------------------------------------------------------------
100 08 88 01 2A43C - 32B18 24048800 c AC70 86DC AC AC OK

LDSC = PM Loader Config String (32 bytes)
ID = ID byte of LDSC (byte #0)
CS = Checksum byte or word
Att = Attributes
PCMBlk = Program Code Memory Block
Exp = Expected checksum for PCMBLock
Act = Actual checksum for PCMBLock
c = compressed PCMBlock
size = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FEE1

Active directory flag = 0x00

Identifying SA regions ...

Reg# Reg size Reg loc
----------------------------
0x00 0x0001A333 0x00000000
0x01 0x0001A333 0x00037500

Verifying ROYL modules ...

ID Size (bytes) Address Checksum
dir hdr dir hdr
-----------------------------------------------------
000A OK 0000003E 00000200 0003FFB2 00000000 OK
000B OK 000000D1 00000200 0003FEE1 00000000 OK
0030 OK 00000400 OK 0003FAE1 00000000 OK
0047 OK 00000400 OK 0003F000 00000000 OK
000D OK 0000008C 00000200 0003EF74 00000000 OK
004F OK 00000400 OK 0003F400 00000000 OK

dir - Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr - Module ID/Size as reported in module's header
N/A - Not Applicable
BAD - Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_01\000Bmods and Flash_01\020Bmods

Active directory is 0x0B -- directory 0x20B not present

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 2/2
Head map #1 = 0x03 / 0b00000011
Head map #2 = 0x00 / 0b00000000

DCM = | B | N S G R H N V
: : : : : : : : : :
: : : : : : : : : unknown
: : : : : : : : top VCM
: : : : : : : ACA
: : : : : : bottom VCM
: : : : : HSA
: : : : media
: : : preamp
: : latch
: base
spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE25A35CE66
Model Number =
Serial Number =


Analysing active 0x4F module ...

ROM version = 0014003V

Analysing active 0x47 module ...

Preamp values
-----------
0 083BA329
1 0639C513
2 02200200
3 02200200
4 02200200
5 02200200

Microjogs
-------
0 0C20
1 0B66
2 0A0A
3 0A0A
4 0A0A
5 0A0A

Head/Media DCM = GS


Thank you very much for the modules. Is there a way to generate a new rom from those modules?
Top
 Profile  
 
fzabkar
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 18:03 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15538
Location: Australia
The donor and patient have different ROM versions (according to mod 4F) -- 0014003V versus 0014003R. I'm not a DR pro, so others would need to tell you whether these are compatible.

Otherwise you could look for ROM version 0014003V and then use it to rebuild the code section.

_________________
A backup a day keeps DR away.
Top
 Profile  
 
jcarlosmor
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 19:08 
Offline

Joined: August 5th, 2020, 22:27
Posts: 19
Location: Mexico
fzabkar wrote:
The donor and patient have different ROM versions (according to mod 4F) -- 0014003V versus 0014003R. I'm not a DR pro, so others would need to tell you whether these are compatible.

Otherwise you could look for ROM version 0014003V and then use it to rebuild the code section.


Your WDROMVx.exe utility for analyzing WD roms is impressive.

Does only works for new drives or ROYL types?

I had downloaded several versions of your utility to check some WD800BB and WD400BB drives (sabre53, sabre58, mammoth, etc.) and I can not get ahead of some lines in the analysis log file. For instance, I can not get the lines regarding firmware, WWN, serial number, etc.

Is there a method to obtain the serial number, WWN, etc inside ROM dumps for Sabre types, encoded in some type, ascii or hex? Or, maybe the question is, do Sabre roms have embedded in their roms that data?

Thank you in advance.
Top
 Profile  
 
fzabkar
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 2nd, 2020, 23:42 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15538
Location: Australia
The WWN, serial number, etc are extracted from module 0Dh, but not all ROMs have this info.

The most recent WD architecture requires a different tool.

http://www.hddoracle.com/download/file.php?id=8795
http://www.hddoracle.com/viewtopic.php?f=3&t=2762

http://www.users.on.net/~fzabkar/temp/WD/WDnewROM.exe
http://www.users.on.net/~fzabkar/temp/WD/WDnewROM.bas

_________________
A backup a day keeps DR away.
Top
 Profile  
 
BGman
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 3rd, 2020, 2:49 
Offline

Joined: September 30th, 2005, 7:33
Posts: 849
Model Number = WDC WD6400BEVT-22A0RT0
Donor PCB is from Mariner 640GB with 4 heads , FW 143R
The original is Jamaica 250GB with 2 heads, FW 143V
By Hex Editor you should thansfer mod 0A, 0B, 30, 0D, 47, 4F from the original ROM to ROM of drive with FW 143V (Jamaica or Mariner)
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 3rd, 2020, 5:59 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
BGman wrote:
Model Number = WDC WD6400BEVT-22A0RT0
Donor PCB is from Mariner 640GB with 4 heads , FW 143R
The original is Jamaica 250GB with 2 heads, FW 143V
By Hex Editor you should thansfer mod 0A, 0B, 30, 0D, 47, 4F from the original ROM to ROM of drive with FW 143V (Jamaica or Mariner)


Hi.

I mean, would I have to insert the 6 modules that fzabkar sent me in the rom of the Mariner 640GB donor with 4 heads, FW 143R?

Or would I have to find another ROM with the FW 143V?

And in what hex position would I have to do it in the Hex Editor?

Thanks for the help, but I've never done this.
Top
 Profile  
 
BGman
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 3:05 
Offline

Joined: September 30th, 2005, 7:33
Posts: 849
Maybe you should pay somebody that knows how to do it.
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 6:03 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
BGman wrote:
Maybe you should pay somebody that knows how to do it.


This hard drive is for the study of new knowledge. It is not from a client.

I have the MRT tool. Could the ROM be generated from it from the modules?

Thanks for the help.

Regards
Top
 Profile  
 
colanco
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 11:06 
Offline

Joined: December 6th, 2012, 8:49
Posts: 290
Location: españa
DeVlL wrote:
I have the MRT tool. Could the ROM be generated from it from the modules?

:shock: :shock: Short answer, yes.
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 14:58 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
Looking at the hddoracle forum I have found how to insert the modules that fzabkar gave me. I have searched my firmware database and found a ROM from the same WDC family WD3200BPVT-22ZEST0-01.01A01. I have inserted the modules with the Hex HxD Editor.

Here I leave the modified rom so that fzabkar if it is very kind to analyze it with its utility and tell me if it is OK.

Thanks and regards


Attachments:
backup.rom.orginal.Rebuilding.bin.zip [202.77 KiB]
Downloaded 344 times
Top
 Profile  
 
colanco
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 15:28 
Offline

Joined: December 6th, 2012, 8:49
Posts: 290
Location: españa
One question...what did you buy MRT for?

That model has a copy of the modules/ROM in SA....
Top
 Profile  
 
DeVlL
 Post subject: Re: Strange disk failure WD2500BEVT
PostPosted: September 4th, 2020, 18:26 
Offline

Joined: August 31st, 2020, 11:41
Posts: 66
Location: España
colanco wrote:
One question...what did you buy MRT for?

That model has a copy of the modules/ROM in SA....


Buy the MRT for data recovery.

As I already said at the beginning of this thread. The unit does not boot with the original bios. Therefore I do not have access to the SA.

The rom that I generated in the previous message did not work.

But anyway it is already solved.

I found another donor ROM in this forum.

WDC WD2500BEVT-22A23T0-01-01A01-0014001E-WD-WX11A40J2777
Which brings the firmware version 14001E, I added by Hex Editor the 6 modules and now it starts and works perfectly.

I found the usefulness of the friend fzabkar and these are the results of the reconstructed rom.

Code:
Analysing WDCWD2~1.BIN ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
---------------------------------------------------------------------------
    0  5A 40   04     120 -  151C      18AC0     13FC  13FC    C5   C5   OK
   20  01 80   01    151D -  A591          0 c   B784  9074    05   05   OK
   40  02 10   01    A592 -  FB9A       E464 c   7950  5608    EE   EE   OK
   60  03 9D   01    FB9B - 1032B      16208 c    958   790    B4   B4   OK
   80  04 F7   03   1032C - 1058C    4000080 c    36C   260    13   13   OK
   A0  05 F4   03   1058D - 10C1D    4003DEC c    BEC   690    CC   CC   OK
   C0  06 6E   03   10C1E - 111FA   24000008 c    B38   5DC    D0   D0   OK
   E0  07 ED   01   111FB - 29DAF   2401D000 c  20058 18BB4    2C   2C   OK
  100  08 51   01   29DB0 - 32324   24048800 c   AAA0  8574    C8   C8   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x3FEE1

Active directory flag = 0x00

Identifying SA regions ...

Reg#  Reg size    Reg loc
----------------------------
0x00  0x0001A333  0x00000000
0x01  0x0001A333  0x00037500

Verifying ROYL modules ...

ID          Size (bytes)         Address    Checksum
dir   hdr    dir       hdr
-----------------------------------------------------
000A  OK     0000003E  00000200   0003FFB2   00000000  OK
000B  OK     000000D1  00000200   0003FEE1   00000000  OK
0030  OK     00000400  OK         0003FAE1   00000001  BAD
0047  OK     00000400  OK         0003F000   00000000  OK
000D  OK     0000008C  00000200   0003EF74   00000000  OK
004F  OK     00000400  OK         0003F400   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_00\000Bmods and Flash_00\020Bmods

Active directory is 0x0B -- directory 0x20B not present

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 2/2
Head map #1 = 0x03 / 0b00000011
Head map #2 = 0x00 / 0b00000000

DCM = | B | N S G R H N V
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 01.01A01
World Wide Name = 50014EE25A35CE66
Model Number =                                         
Serial Number =                     


Analysing active 0x4F module ...

ROM version = 0014003V

Analysing active 0x47 module ...

Preamp values
-----------
0  083BA329
1  0639C513
2  02200200
3  02200200
4  02200200
5  02200200

Microjogs
-------
0  0C20
1  0B66
2  0A0A
3  0A0A
4  0A0A
5  0A0A

Head/Media DCM = GS


Thank you all for the help and knowledge.
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 2
  [ 25 posts ]  Go to page 1, 2  Next

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 150 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group