hdd busy

26 views
Skip to first unread message

bel gharti

unread,
Jun 4, 2026, 9:20:13 AM (5 days ago) Jun 4
to datarecovery...@googlegroups.com
hello sir  can   anyone help me  hdd is busy


Family:................................. : Diablo3S
Techno mode key......................... : Ok
 
Debug Stop Code......................... : 1A102 - HOST DEBUGSTOP RESET TIMEOUT
 
HDD Status sector....................... : Ok
 
RAM:
System controller (SoC)................. : 88i9446C0 (0xA5C0)
HDD Info reading........................ : Ok
Heads number............................ : 1
Cyl Count............................... : 256
 
ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 330 212
SA regions address...................... : by default
Module 02 access........................ : Granted
 
WWN..................................... : 0000000000000000
 
SA SPT.................................. : 0
 
ROM Modules:
ROM version............................. : 15.ABC
Module 4F F/W version................... : 001500AB
Overlay F/W version..................... : 15.ABC
Servo F/W version....................... : 05.67
 
Head Map Reading Error.................. : Head map check sum error
 
Relocations............................. : 0 (0)
Read ROM DCM............................ : Ok
 
Power up log reading.................... : Ok
Power up load dir data.................. : No
Power up load permovl................... : No
Power up load CFG data.................. : No
 
 
DCM in module 47........................ : Module ID 47 reading error Device Error Detected: "FM ERR HEADER II SIGNATURE INVALID"
DCM in module 0A........................ :
 

0B.bin
20B.bin
0A.bin
4F.bin
30.bin
47.bin
bult.bin
ROM_15-ABC_15-ACC_05-67.bin

pbzcbf...@gmail.com

unread,
Jun 4, 2026, 1:42:00 PM (5 days ago) Jun 4
to DataRecoveryCertification
The ROM has been modified. That's why PC3K is complaining about errors in the ROM modules. I don't know if this "problem" is in addition to the original problem.

Offset(h) 00   02   04   06   08   0A   0C   0E   10

00000000  524F 594C 0400 1E00 0B02 0100 3BE3 F5B2 3030  ROYL............00
00000012  3033 3030 3030 0000 0002 0000 0A12 0201 0018  030000............
00000024  0003 1890 02E4 0905 00E4 0905 0012 010A 004E
00000036  0000 1900 0000 E007 0000 0000 0012 010B 0019
00000048  0100 1900 00EA FC07 0000 0000 0012 010B 0219
0000005A  0100 1900 00EA EC07 0000 0000 0012 0130 0000
0000006C  0400 1900 0000 D007 0000 0000 0012 0147 0000
0000007E  0800 1900 00EA E407 0000 0000 0012 0102 009C  <-- module 0x0D has been replaced with module 0x02
                                               ^^

00000090  0000 1900 004E E007 0000 0000 0012 014F 0000
000000A2  0400 1900 00EA E007 0000 0000 0000 0000 0000
000000B4  0000 0000 0000 0000 0000 0000 0000 0000 0000
000000C6  0000 0000 0000 0000 0000 0000 0046 02FF 0F03
000000D8  0000 1905 0000 0000 0000 1905 0000 CC06 005C
000000EA  4B03 0000 980D 0000 0000 0000 0000 0000 0000
000000FC  0000 0000 0000 0000 0000 0000 0000 0000 0000
0000010E  0000 0000 0000 0000 0000 00FF



Message has been deleted

pbzcbf...@gmail.com

unread,
Jun 4, 2026, 2:28:29 PM (5 days ago) Jun 4
to DataRecoveryCertification
Your bult.bin ROM is OK.

Analysing bult.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 8F   02     100 -  224F      12800     214E  214E  FB3E FB3E   OK
   20  01 7D   0C    2250 -  276C   88800000      51C   51C    7B   7B   OK
   40  02 48   01    276D -  A0F1          0 c   9B68  7984    CB   CB   OK
   60  03 66   01    A0F2 -  A7EA      11B64 c    898   6F8    4C   4C   OK
   80  04 16   03    A7EB -  AF2F      80220 c    900   744    6A   6A   OK
   A0  05 CD   03    AF30 -  B140   10178C00 c    358   210    89   89   OK
   C0  06 8A   01    B141 - 21555   9039DE00 c  1D76C 16414    85   85   OK
   E0  07 70   01   21556 - 361E6   90000230 c  1BE08 14C90    3C   3C   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 0x7FCEA

Active directory flag = 0x01

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x00034B5C  0x00000000
0x01  0x00034B5C  0x0006CC00
0x02  0x00034B5C  0x000D9800
0x03  0x00000000  0x00000000
0x04  0x00000000  0x00000000
0x05  0x00000000  0x00000000
0x06  0x00000000  0x00000000
0x07  0x00000000  0x00000000

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00003000  N/A        00000000             N/A
000A  OK     0000004E  00000200   0007F000   00000000  OK
000B  OK     00000119  00000200   0007FCEA   00000000  OK
020B  OK     00000119  00000200   0007ECEA   00000000  OK
0030  OK     00000400  OK         0007D000   00000000  OK
0047  FFFF   00000800  01FFFE00   0007F4EA   FFFFFE00  BAD
000D  OK     0000009C  00000200   0007F04E   00000000  OK
004F  OK     00000400  OK         0007F0EA   00000000  OK

ROYL directory module 0x020B found at 0x7ECEA

Active directory flag = 0x02

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x00051900  0x00000000
0x01  0x00051900  0x0006CC00

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00003000  N/A        000509E4             N/A
000A  OK     0000004E  00000200   0007E000   00000000  OK
000B  OK     00000119  00000200   0007FCEA   00000000  OK
020B  OK     00000119  00000200   0007ECEA   00000000  OK
0030  OK     00000400  OK         0007D000   00000000  OK
0047  OK     00000800  OK         0007E4EA   00000000  OK
000D  OK     0000009C  00000200   0007E04E   00000000  OK
004F  OK     00000400  OK         0007E0EA   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 0x20B

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 4/4
Head map #1 = 0x0033 / 0b0000000000110011
Head map #2 = 0x0033 / 0b0000000000110011

DCM = | F | P W M * 9 P C
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 80.00A80
World Wide Name = 50014EE2BA29E29A
Model Number = WDC WD20EZRZ-00Z5HB0                    
Serial Number =                    

PUIS flag byte is 0x00
Unknown PUIS flag type.

Analysing active 0x4F module ...

ROM version = 001500AB

Analysing active 0x47 module ...

Preamp values
-----------
0  0733B31F
1  0937D21C
2  0931B31D
3  0937B31A
4  00000000
5  00000000

Microjogs
-------
0  0000
1  0000
2  0000
3  0000
4  0A0A
5  0A0A

Head/Media DCM = MW

pbzcbf...@gmail.com

unread,
Jun 4, 2026, 5:32:26 PM (5 days ago) Jun 4
to DataRecoveryCertification
I don't know if this problem is similar:

https://forum.hddguru.com/viewtopic.php?f=1&t=31555


bel gharti

unread,
Jun 5, 2026, 1:45:37 AM (4 days ago) Jun 5
to datarecovery...@googlegroups.com


thank  you  sir  for  reply  

hello  sir  i  have  regenerate   rom   and  write  in  hdd   but   problem  same ?

On Fri, Jun 5, 2026 at 3:17 AM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:
I don't know if this problem is similar:

https://forum.hddguru.com/viewtopic.php?f=1&t=31555


--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/32b00dbd-fa9f-4e38-bd99-4565cd58b74an%40googlegroups.com.

D. P. Computers

unread,
Jun 5, 2026, 1:50:28 AM (4 days ago) Jun 5
to datarecovery...@googlegroups.com

pbzcbf...@gmail.com

unread,
Jun 5, 2026, 3:24:51 AM (4 days ago) Jun 5
to DataRecoveryCertification
Reply all
Reply to author
Forward
0 new messages