Switch to full style
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
Post a reply

Seagate st16000ne000rom is damaged

August 13th, 2025, 6:40

Any kind person can help me fix my damaged rom

Re: Seagate st16000ne000rom is damaged

August 13th, 2025, 6:42

This is the terminal prompt.
Attachments
mmexport1755073386018.jpg

Re: Seagate st16000ne000rom is damaged

August 13th, 2025, 6:46

Damaged ROM

Re: Seagate st16000ne000rom is damaged

August 13th, 2025, 9:51

aggc123 wrote:Damaged ROM

And?
Where is the damaged ROM file? The ROM from another similar disk will not work. It is unique for each copy.

Re: Seagate st16000ne000rom is damaged

August 13th, 2025, 10:05

Hello thank you for your reply The rom file is too large and cannot be uploaded

Re: Seagate st16000ne000rom is damaged

August 13th, 2025, 14:45

aggc123 wrote:Hello thank you for your reply The rom file is too large and cannot be uploaded

Then you're doing something wrong. Upload the binary, not text, if that's what you're trying to do.

Re: Seagate st16000ne000rom is damaged

August 14th, 2025, 13:46

Hello sir, thank you for replying again. This is my ROM file
Attachments
patient1.zip
(295.52 KiB) Downloaded 29 times
patient1.zip
(295.52 KiB) Downloaded 23 times

Re: Seagate st16000ne000rom is damaged

August 14th, 2025, 14:07

Your ROM cannot be repaired. The adaptives contain junk. Also, the second half of your ROM is empty.

Does your PCB have two ROMs? If so, then you need to dump both because they are RAID-ed (special RAID 0).

Re: Seagate st16000ne000rom is damaged

August 14th, 2025, 15:15

Without native adaptives - a brick...

Re: Seagate st16000ne000rom is damaged

August 14th, 2025, 15:32

SWM wrote:Without native adaptives - a brick...

One of the adaptive modules contains NVcache. That is consistent with a RAID 0. Everything before 0xBFFFF is OK. That's the first stripe.

Re: Seagate st16000ne000rom is damaged

August 14th, 2025, 15:55

fzabkar wrote:Everything before 0xBFFFF is OK. That's the first stripe.

Sorry, that should be "everything before 0xB0000 is OK".

Re: Seagate st16000ne000rom is damaged

August 15th, 2025, 14:57

Thank you very much for your reply. There are indeed two ROMs, and now my drive is indeed a brick. I am uploading the second ROM now, if my drive is still salvaged.
Attachments
patient2.zip
(468.45 KiB) Downloaded 19 times

Re: Seagate st16000ne000rom is damaged

August 15th, 2025, 16:27

I have assembled the RAID. It looks OK, but F3RomExplorer doesn't work with it. I think that's a deficiency of the tool rather than a problem with the RAID. That said, I haven't verified the CRCs. If you have PC3000, you may be able to do it yourself.

What have you done to your drive, if anything, to brick it? What is the history? I could manually check all the CRCs, if necessary.
Attachments
ROM_RAID0.7z
(623.65 KiB) Downloaded 21 times

Re: Seagate st16000ne000rom is damaged

August 15th, 2025, 17:07

The main header has a bad 16-bit checksum.

Code:
Offset(h) 00       04       08       0C

00000000  301C0000 70090000 00000000 00050600
00000010  00000000 17000000 087E0200 72B90000
00000020  1D000000 22000100 1D000005 23000105
00000030  0B00000A 0500100A 0400C00A 1700D00A
00000040  0600000B 1E000015 00000016 00000000
00000050  E8480000 FFFFFFFF FFFFFFFF FFFFFFFF
00000060  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00000070  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00000080  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00000090  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000A0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000B0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000C0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000D0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000E0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000000F0  FFFFFFFF FFFFFFFF FFFFFFFF 72C10000

This bad, too.

Code:
Offset(h) 00       04       08       0C

00050000  301C0000 70090000 FFFFFFFF FFFFFFFF
00050010  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050020  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050030  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050040  0600000B 1E000015 FFFFFFFF FFFFFFFF
00050050  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050060  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050070  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050080  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
00050090  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500A0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500B0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500C0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500D0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500E0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
000500F0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

The CAP, RAP and SAP are all good.

Re: Seagate st16000ne000rom is damaged

August 16th, 2025, 1:23

Hello, sir. First of all, thank you for your reply. I used a programmer to read the ROM and wanted to unlock it via PC3000. There might be an issue with the programmer. After reading the ROM and writing it back, the above prompt appears. The same happens when writing back the original ROM. My PC3000 cannot verify the CRC check code. However, I found that my ROM lacks IAP. Even when I open the ROM with PC3000, the logical head bitmap cannot be displayed. Is there any way to save my hard drive?

Re: Seagate st16000ne000rom is damaged

August 16th, 2025, 6:57

aggc123, In the patient1.bin file, part of the second code container in the address range is 0x50000 ... 0x7FFFF is lost.

Re: Seagate st16000ne000rom is damaged

August 16th, 2025, 13:40

E123 wrote:aggc123, In the patient1.bin file, part of the second code container in the address range is 0x50000 ... 0x7FFFF is lost.

See https://www.hddoracle.com/download/file.php?id=10754

That's a good ROM pair. The second container is empty also, but the directory is OK. I think the first container is corrupt.

RAID-ed ROMs in newer models:
https://www.hddoracle.com/viewtopic.php?p=24761#p24761

Seagate ROM RAID assembly tool:
https://www.hddoracle.com/viewtopic.php?p=24764#p24764

Re: Seagate st16000ne000rom is damaged

August 16th, 2025, 13:59

deleted

Re: Seagate st16000ne000rom is damaged

August 16th, 2025, 14:15

This is in the wrong place, and the header is incomplete:

Code:
Offset(h) 00       04       08       0C

00040000  FFFFFFFF FFFFFFFF 00000000 00050600  ÿÿÿÿÿÿÿÿ........
00040010  00000000 17000000 087E0200 72B90000  .........~..r¹..
00040020  1D000000 22000100 1D000005 23000105  ....".......#...
00040030  0B00000A 0500100A 0400C00A 1700D00A  ..........À...Ð.
00040040  FFFFFFFF FFFFFFFF 00000016 00000000  ÿÿÿÿÿÿÿÿ........
00040050  E8480000 FFFFFFFF FFFFFFFF FFFFFFFF  èH..ÿÿÿÿÿÿÿÿÿÿÿÿ
00040060  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00040070  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00040080  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00040090  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400A0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400B0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400C0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400D0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400E0  FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000400F0  FFFFFFFF FFFFFFFF FFFFFFFF 72C10000  ÿÿÿÿÿÿÿÿÿÿÿÿrÁ..
00040100  FFFFFFFF FFFFFFFF 00000000 00050600  ÿÿÿÿÿÿÿÿ........
00040110  37659038 00000000 087E0200 000089BA  7e.8.....~....‰º
00040120  16400000 15480000 18D80700 10680800  .@...H...Ø...h..
00040130  0E009F02 0300AF02 0000FF04 00000000  ..Ÿ...¯...ÿ.....
00040140  FFFFFFFF FFFFFFFF 64000100 FFFFFF7F  ÿÿÿÿÿÿÿÿd...ÿÿÿ.
00040150  17060313 51000200 80C8F100 0004268E  ....Q...€Èñ...&Ž
00040160  286C1A00 1F211000 26082312 08262020  (l...!..&.#..& 
00040170  20001403 686C1A00 53444E48 2312A400   ...hl..SDNH#.¤.
00040180  FFFFFFFF FFFFFFFF 21000100 0000650E  ÿÿÿÿÿÿÿÿ!.....e.
00040190  A2000200 FFFFFF7F FFFFFFFF FFFFFFFF  ¢...ÿÿÿ.ÿÿÿÿÿÿÿÿ

Re: Seagate st16000ne000rom is damaged

August 17th, 2025, 7:07

fzabkar, Yes, I somehow ... all the same. You can restore the first container if you find something there.
And your "oracle" - read yourself. He says that I was born in the wrong country.
Post a reply