All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 10 posts ] 
Author Message
 Post subject: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 6:22 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
Hello,
I have ST500LT012-1DG142. The spindle does not start and the drive remains in BSY.
Terminal said only:
Code:
Bad CRC Seg:0x06
Boot 0x10M


I've read the ROM and PC3k states that ROM images contains critically damaged objects [RAP].

I further checked the ROM information:
Code:
Parsing container segment....... Flash ROM image
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM image

Multipart flash image found. Reparsing...

Parsing multipart flash image....... Flash ROM image

Part 1...

Parsing container segment....... Flash ROM part 1
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 1

Part 2...

Parsing container segment....... Flash ROM part 2
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 2

Part 3...

Parsing container segment....... Flash ROM part 3
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 3

Part 4...

Parsing container segment....... Flash ROM part 4
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: RAP
Parsing segment....... RAP
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... Flash ROM part 4


I've checked the serial number in the ROM - it matches the disk number. I also checked the PCB number and it also matches.
The only unusual thing is that this ROM is 1 MB. All the others I've seen of this model are 512KB.
It looks as if in this drive the ROM has two copies on the chip, but both are identical.

Do you have any idea how to fix this ROM? I've run out of ideas.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 6:45 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
ROM in attachment.


Attachments:
ROM.zip [715.71 KiB]
Downloaded 22 times
Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 12:27 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15539
Location: Australia
The ROM consists of 4 parts. There is a single-bit error in parts 2 and 4.

Code:
Offset(h) 00       04       08       0C

00064230  00000000 00000000 00000000 00000000
00064240  00000000 00000000 00000000 04000000
                                      ^
00064250  00000000 00000000 00000000 00000000

Code:
Offset(h) 00       04       08       0C

000E4230  00000000 00000000 00000000 00000000
000E4240  00000000 00000000 00000000 04000000
                                      ^
000E4250  00000000 00000000 00000000 00000000


Edit:

I see that @E123 has already repaired your ROM in your other thread.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 12:38 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
Duplicate post...


Last edited by andy17d on February 9th, 2024, 12:44, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 12:42 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
fzabkar wrote:
The ROM consists of 4 parts. There is a single-bit error in parts 2 and 4.

Code:
Offset(h) 00       04       08       0C

00064230  00000000 00000000 00000000 00000000
00064240  00000000 00000000 00000000 04000000
                                      ^
00064250  00000000 00000000 00000000 00000000

Code:
Offset(h) 00       04       08       0C

000E4230  00000000 00000000 00000000 00000000
000E4240  00000000 00000000 00000000 04000000
                                      ^
000E4250  00000000 00000000 00000000 00000000


Edit:

I see that @E123 has already repaired your ROM in your other thread.

What I'm wondering is how this error appeared in both copies (in both places).

How did you even find this wrong place? I used the your program to look for a single error, but it did not indicate this location.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 9th, 2024, 13:05 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15539
Location: Australia
andy17d wrote:
What I'm wondering is how this error appeared in both copies (in both places).

This could happen if you are reading a 512KB ROM as a 1MB ROM. Otherwise, I don't understand it, either.

andy17d wrote:
How did you even find this wrong place? I used the your program to look for a single error, but it did not indicate this location.

If you mean F3RomExplorer, that program was written by @E123.

Ace's parsing results suggested that there were 4 parts. I simply searched for "csiD" headers in my hex editor. ("csiD" is "Disc" in little-endian)

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 10th, 2024, 9:40 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
fzabkar wrote:
andy17d wrote:
What I'm wondering is how this error appeared in both copies (in both places).

This could happen if you are reading a 512KB ROM as a 1MB ROM. Otherwise, I don't understand it, either.

I read the ROM using Pc3k. Maybe it misread the chip size.
fzabkar wrote:
andy17d wrote:
How did you even find this wrong place? I used the your program to look for a single error, but it did not indicate this location.


If you mean F3RomExplorer, that program was written by @E123.

Ace's parsing results suggested that there were 4 parts. I simply searched for "csiD" headers in my hex editor. ("csiD" is "Disc" in little-endian)

No, I meant your program, i.e. STROMfix_2.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 10th, 2024, 12:59 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15539
Location: Australia
STROMfix_2 attempts to detect all possible single-bit error candidates in a corrupt ROM segment. You first need to extract that bad segment. The tool does not work on the whole ROM.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 10th, 2024, 13:38 
Offline

Joined: May 14th, 2015, 18:29
Posts: 74
Location: Poland
How did you actually target the right segment? PC3k indicated a problem in RAP. From what I can see, the error was much further (at 64230). RAP segment ended at about 25k offset.


Top
 Profile  
 
 Post subject: Re: Seagate Yarra_5400 - No spin, ROM corruption
PostPosted: February 10th, 2024, 14:09 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15539
Location: Australia
The ROM is actually a 512KB part, not 1MB. (It doesn't make sense for 2 errors to occur at the same location in each 512KB half of a 1MB ROM.)

There are 2 copies of the RAP within the first 512KB. The first copy is OK, but the second copy has a SBE.

    0x1C180 - 0x2558F
    0x5C180 - 0x6558F

I just compared the first half of the 512KB ROM with the second half.

BTW, the free version of F3RomExplorer only detects the first half of the 512KB ROM (256KB), so it doesn't detect the error.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 60 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:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group