SavedModePages: invalid signature!

[Bruno]

Hi all,
I have here a Seagate ST31000528AS, FW44.
At arrived, the PCB was burned.
I have canged the ROM to another PCB. Same nocking Sound.
Now i read the ROM by terminal and write it to a same PCB from same type hdd with FW CC36.

The Patient hdd after start first nocking, but Startup an came ready, with capacity (0) MB...

LOG:

HDD family detecting...


Family ID: 3F
Selected family......................... : 3F, Pharaoh
Model by ID............................. : ST31000528AS

Tech Key...

Requesting FW Pkg ver ........ PH0G7B.CCD4.CT0L2H.


Detecting SA Phys Sct Size...
Result.................................. : 512

Detecting UA Phys Sct Size...
Result.................................. : 512

Detecting Max Head number...
Phys. heads............................. : 4

Obtaining Saved Mode Pages File information...
Reading Saved Mode Pages...
Parsing Saved Mode Pages...
SMP Dbl: 0x3C000317 - 0x037FF7FF (0x0000000F)

LBA alignment........................... : 0

Obtaining Registry File information...
Reading Registry File...
Parsing Registry File...

Media Cache
===========
MC is not supported / NVC caching


Collecting Sys Files information...
ID Len
===============
0 4 Reserved Defect Table (SA defect table)
1 2 Drive Information File (DIF)
2 16 Performance Parameter File (PPF)
3 3787 Primary Defect File (P-List)
4 12 Servo Adaptive Parameter File (SAP)
5 4 Manufacturing Information File (MIF)
6 66 Read Adaptive Parameters File (RAP)
7 1 Controller Adaptive Parameters File (CAP)
8 4800
9 1 SMART Configuration File
A 2251 SMART Data File
B 1000
C 64000 Serial Port Test Results File (Self Scan Log)
D 160
E 432 Data Integrity Check (DIC), HEAD 0
F 223 DIC Dummy File
13 8 Disc Registry File (settings, security, etc)
15 100 BGMS File (Directed Offline Scan)
16 2
17 40
19 24 Log File
1A 33 Log File
1B 1 Log File
1C 9
1D 128 Physical Overlay File 0
1E 128 Physical Overlay File 1
1F 640 Physical Overlay File 2
22 80 Drive Self Test (DST), Head 0
23 80 Drive Self Test (DST), Head 1
24 80 Drive Self Test (DST), Head 2
25 80 Drive Self Test (DST), Head 3
2A 9 Saved Mode Pages (HDD settings)
2B 1172 R/W Operating Parameters (translator, etc)
2C 432 Data Integrity Check (DIC), HEAD 1
2D 432 Data Integrity Check (DIC), HEAD 2
2E 432 Data Integrity Check (DIC), HEAD 3
33 4576
34 640 Packed CONGEN XML definition
35 26 SMART Data
3A 4
Collecting Sys File Infos completed

Collecting DT Infos...
ROM:
ID MemOffs Len
===========================
0 6037200 33792 Read Adaptive Parameters File (RAP)
1 6037000 512 Controller Adaptive Parameters File (CAP)
4 4002C00 4096 Servo Adaptive Parameter File (SAP)
602BE00 4096
total 8192
5 6C000 81920 Servo Firmware Table
A 60B4880 2048 Seek Profile
13 60C0A4C 864 Dependent Zone Table for User Area
14 60C0DAC 96 Dependent Zone Table for System Area
15 0 524288 Flash ROM
1B 60BE850 8700 Dependent Zone Group Tables for User Area
1C 60BE710 320 Dependent Zone Group Tables for System Area
1D 6037220 352 VBAR Configuration File
1E 60374B0 2416 Zone Format Parameters File

RAM:
ID MemOffs Len
===========================
0 6037200 33792 Read Adaptive Parameters File (RAP)
1 6037000 512 Controller Adaptive Parameters File (CAP)
2 6037380 304 Zone Table
4 4002C00 4096 Servo Adaptive Parameter File (SAP)
602BE00 4096
total 8192
5 6C000 81920 Servo Firmware Table
6 278044 40996 Servo Flaw Table
A 60B4880 2048 Seek Profile
13 60C0A4C 864 Dependent Zone Table for User Area
14 60C0DAC 96 Dependent Zone Table for System Area
15 0 524288 Flash ROM
16 6037200 32 Drive Configuration Table
17 6039240 1216 Temperature Control Configuration
1B 60BE850 8700 Dependent Zone Group Tables for User Area
1C 60BE710 320 Dependent Zone Group Tables for System Area
1D 6037220 352 VBAR Configuration File
1E 60374B0 2416 Zone Format Parameters File
1F 618467C 1224 RW working user preamp table
20 6184B44 72 RW working system preamp table

Collecting DT Infos completed


System Files I/O method detection... ATA(direct)


Reading autotuning buffer............... Ok
Buff Root FAT searching in RAM......... Ok
Searching module table in RAM... ....... Ok
Searching DT table(RAM, WR) in RAM...... Ok
Searching DT table(RAM, RD) in RAM...... Ok
Searching volume 0 file table in RAM.... Ok
Searching volume 3 file table in RAM.... Ok
Searching SMP RAM FID in RAM............ Ok
Searching Non Resident G-List FID in RAM Ok
Searching CFW OVL FID in RAM............ Ok

----------------------



The solution for (0)MB Problem not work.

Log:
Test : Solution for the "Translation violation (0 GB)" problem
HDD capacity restrict. check (SetMax)...
HDD capacity restrict. check (SetMax)... : Error
SMART erase
HDD reply :

Clear SMART is completed.

SMART erase............................. : Error
Solution for the "Translation violation (0 GB)" problem.... : Error


In HD-ID (ROM) the Capaticy is correct, but in HD-ID(Rom) ist 0.

When i try to correct: failed.
Here is the LOG:
Test : Edit HDD ID (terminal)
HDD ID data source...................... : Terminal
Vol..................................... : 3
FID..................................... : 147
Copy.................................... : 0
HDD ID data destination................. : Terminal
Vol..................................... : 3
FID..................................... : 147
Copy.................................... : 0

Reading Saved Mode Pages...
Rd Sys File: vol = 3, FID = 093, Copy = 000...
Receiving file FILE_3_093_0, length = 4608
Parsing Saved Mode Pages...
SMP Dbl: 0x3C000317 - 0x037FF7FF (0x0000000F)
Writing Saved Mode Pages...
Wr Sys File: vol = 3, FID = 093...
XYMODEM send: waiting for receiver...
Blocks count: b1K = 4, b128 = 4
Rd Sys File: vol = 3, FID = 093, Copy = 000...
Receiving file FILE_3_093_0, length = 4608
Verification............................ : Ok
HDD Identification reading ............. : HDD Redynes timeout (60000)

What can i do to solve this Problem?
Thnaks for helpful answer.

[AJ2008]

You try to clear translator without checking for post process defects?

Probably you need to re-write SMART sysfile before translator regen is made, but again you need to consider post process defects (NRG)

[AJ2008]

Also, you say is knocking - can you check that SN in ROM is original?
Does spindle stop after some knocking?

some of these PCB had 2 x 8 pin EEPROM chips - maybe both need to be transferred?

I assume is OK since you can get T> access and read/write 0x93 seems ok

[Nick_TS]

Could you send us terminal output for these commands:

Code: Select all

F3 T>r135
F3 T>/1N1

[Bruno]

Sorry for the delay. In the meantime i have any urgent Cases to solve.

Hi Dimitry
Here is the terminal Output:
F3 T>r135

LED:000000CE FAddr:0029ECD
Rst 0x20M
ASCII Diag mode

F3 T>

F3 T>/1N1

HighPowerMode
Failed to load overlay 00000004
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
LED:000000CC FAddr:002851C7
-------------------------------------------------------------

Hi AJ2008
yes drive noks for ~10 times and then stops nocking, but the spindle rotates.

I dont play with translator.

Yes, serialnumber in ROM is same like Stiker.
Til now i dont have transfered the second ROM, but i remember, in the past i did dis doing.
In the next fiew Minutes i will do, swapping the second ROM.

[Bruno]

Swaping of second ROM DONE, but issue is the same. No changes.
Any Idee?