Something got lost in the translation. :-?

BTW, those two ROM RAID examples at the Oracle both have empty containers. One has an empty 0x22 container, the other has an empty 0x23 container. Your F3RomExplorer tool doesn't handle the 12TB ROM.

_________________
A backup a day keeps DR away.

Damaged:
0x50000 - GFDIR
0x50100 - BootFW Container
Damaged or I can't see them because the first two are damaged:
0x50XXX - Boot FW
0x7A000 - IAP
0x7B000 - SFW
CAP, SAP, RAP, Shell - checksums are normal.
It remains to look for a working ROM from FW EN01...

I notice that current Seagate ROMs have a 32-byte section in the IAP segment. This looks like a digital code of some kind. Is this unique and critical?

_________________
A backup a day keeps DR away.

We will find out if the author of the topic finds a working ROM and there will be a continuation...

Thank you all. I currently cannot find a properly working ROM for FW EN01, but I have many ROMs from the same family, including other FW versions and other models such as FW SC02 and SN03. They all belong to the EvansBP series and are shown as the c6 family on PC3000. Are these useful? If not, I will upload the properly working ROM for FW EN01 once I find it in the future.

The ROM stores only the boot code, traps, adaptives and SFW. The main code is in the service area of the disk. It will not work with another version of the FW, the overlay versions on the disk will not match the ROM.

You can try to assemble it from these two.

gold6565, Дякую!
ROM with donor boot container. IAP did not correct - I do not know the format. Maybe it will take off... Frank can disassemble it into two...

Sorry for bad English
I gave two ROMs
One has exactly the same SAP as the patient, which is very surprising.
There is a chance that it should fit.

@gold6565, there is no SAP in either of your two dumps. You have provided only the first ROM of each pair. Are you referring to the contents of the second ROM?

_________________
A backup a day keeps DR away.

SAP modules consisting of three ROMs.

Mine are different...

It's sad that there is no one to check the latest ROM...

Yes, I was mistaken, I looked at the wrong thing.

Hello sir, I'm sorry for being late. I've been searching for a working ROM recently, and I'm lucky to have found it. I'm uploading it now and trying your latest ROM, the damaged drive successfully started, but it still doesn't work properly. PC3000 shows a missing fw. I can use PC3000 to extract a lod file from a working drive, but it seems like I can't write to the damaged drive

Normal working ROM and patient ROM

Or FW is not on the disk, or it was never there? Please take a photo of your disk from the sticker side

"Trans" - overlay from disk is loaded, but does not fit BFW (DiskFWfailed). Looks like an unsuccessful update (the FW version on the disk is no longer EN01). Or BFW has also become unique...
The patient's ROM with BFWContainer "normal operation".

What was the original problem with this drive, before the ROM was corrupted?

_________________
A backup a day keeps DR away.

There are some alarms.