Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
April 2nd, 2025, 5:10
i got this disk ST4000DM000 2AE166-300 WF 0001 with damaged rom
terminal report always bad CRC Seg:0x06
no way to regen new F3 rom right ? anyone here can check rom and if is possible to patch with a donor rom
i try with donor rom attached but result in crc error
- Attachments
-
- 32432-donor.zip
- (542.32 KiB) Downloaded 426 times
-

- 32432.jpg (61.03 KiB) Viewed 13739 times
-
- 32432.zip
- (554.97 KiB) Downloaded 420 times
April 2nd, 2025, 9:22
Hello, the problem is that some pages are erased from B3000-B6FFF, CAP is completely busted, and the end of RAP too. CAP is not an issue, but RAP is, that block contains some data but i'm not sure if that's something critical, i should check...
pepe
April 2nd, 2025, 10:40
I have attached the repaired RAP. It was recovered from Extra Space.
I can try to build a new ROM with parts from your donor, unless anyone has a better idea.
- Attachments
-
- 00061000_DL_RAPM_repaired.7z
- (104.54 KiB) Downloaded 455 times
April 2nd, 2025, 10:54
yeah, i didn't notice that part is also present at higher addr.
April 2nd, 2025, 11:01
I have repaired and patched the ROM.
- Attachments
-
- 32432_repaired-RAP_donor_CAP_donor-UDSBFW-CELOG.7z
- (377.78 KiB) Downloaded 433 times
April 3rd, 2025, 2:39
fzabkar wrote:I have repaired and patched the ROM.
thank you !
some weird other problem here, first boot with new rom seem ok but hang and no ctrl+z
- Code:
Boot 0x40M
VAB00E
0001
SpinUp
TCC:0013
Trans
Rst 0x40M
VAB00E
0001
LED:0x00000067 FAddr:0x003129EA
LED:0x000000EE FAddr:0x00331194
then after power off and on only
- Code:
CACACA
and rom is broken again, need to program it again... maybe rom chip or pcb fault ?
pcb is 100788341 rev c need exactly pcb+rev rigth ?
April 3rd, 2025, 11:00
All I did was repair the RAP using the partial copy in the Extra Space, and then replace the CAP, UDSBFW and CELOG with the donor's. The latter two segments were clear in the donor ROM, but the patient's segments contained data. You could dump the ROM again and reexamine the UDSBFW and CELOG segments.
April 4th, 2025, 13:43
In the corrupt ROM, the UDSBFW segment has been shifted downward by 0x800 bytes, and its last 0x800 bytes have overwritten the CELOG segment. I have extracted and attached the correct (?) version of this segment.
There are a couple of areas containing 0xBEEF. I don't know what this means.
- Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00001F30 EF BE EF BE EF BE EF BE EF BE EF BE EF BE EF BE
00001F40 10 00 EF BE EF BE EF BE EF BE EF BE EF BE EF BE
00001F50 EF BE 00 08 FC 00 EF BE EF BE EF BE EF BE EF BE
00001F60 EF BE EF BE EF BE EF BE EF BE EF BE EF BE EF BE
It would be interesting to see whether the latest ROM dump has the same corruption.
- Attachments
-
- 0xB7000-0xC5FFF.7z
- (16.78 KiB) Downloaded 453 times
April 10th, 2025, 10:06
update
after swap with new PCB your repaired rom 32432_repaired-RAP_donor_CAP_donor-UDSBFW-CELOG.7z init ok, with donor sn
- Code:
CA
Boot 0x40M
VAB00E
0001
SpinUp
TCC:0016
Trans
Rst 0x40MVAB00E
0001
(P) SATA Reset
- Code:
Model : ST4000DM000-2AE166
Serial : WDH0GLM6
Firmware : 0001
Capacity : 7814037168 (3726.02GB)
Sector size : 4096
Heads number : 6
FW info : Obtained
FW version : V9A2010B0.CCD7.VAB00E.0001
FW package P/N : ---------
FW ID : 00480557
FW creation date : 2016/07/01
FW creation time : 00:01:15
CFW version : V9A2010B0.CCD7.VAB00E.01079778.0
SFW1 version : 0480557.0001
but surface read report all 0 and "inconsistent LBA map". any advice to proceed ?
need to try with correct module 0xB7000-0xC5FFF? can you provide compiled rom ?
thanks
April 10th, 2025, 12:11
ignore last post... with 32432_repaired-RAP_donor_CAP_donor-UDSBFW-CELOG and new pcb i recover everything! previus problem with lba is only related to Rapidspar.
Thanks, thanks thanks!
Powered by phpBB © phpBB Group.