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

ST2000DM001 table code segment is not found

June 20th, 2022, 8:00

Hi there,

I'm stuck this ST2000DM001 I try to access with PC3K
Busy at reading ID
alternative init failed by terminal
I have read ROM via termimnal and BOOT CODE, seems ok to me (comparaison made with a same model ROM)
When I try to init with ROM image, it hangs with a "table code segment is not found"
What can I try now ?

Thanks

Re: ST2000DM001 table code segment is not found

June 20th, 2022, 9:00

Post terminal log

Re: ST2000DM001 table code segment is not found

June 20th, 2022, 9:19

More from this case :

V1 slip G-LIST P-LIST are huge
V2 T-List has 2 entries by head
V40 empty

Head resistance seems ok

Can read and write System files via terminal (ie 93)

Re: ST2000DM001 table code segment is not found

June 20th, 2022, 9:20

At startup, with ctrl+Z :

Code:
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:0029

(P) SATA Reset

RAW OFF
PASS
MCMainPOR: Start:
User Data Base  0043DD60
Check MCMT Version: Current
MCMainPOR: MCTStateFlags 0000000A  MCStateFlags 00020001
MC061: MainPOR: MC off and MCMT empty
MC057: MainPOR: EXCEPTION: POR Failed General  Tms 00000040
MC062: MainPOR: Feature Disabled...
MSP MainPOR: Feature Disabled by AMPS
6Gb Max Speed lowered to 3Gb for Intel bug
Send Status: COMRESET seen
ASCII Diag mode

F3 T>

Re: ST2000DM001 table code segment is not found

June 20th, 2022, 11:47

Clear SMART help me a bit.

Id can be read, all backups are good.

Start to img, but failed at 84000

Try to recover translator, but

Code:
Start scanning...
"Fork" searching: 0 - 3907029167
Verify sectors ext error Device error detected "UNC"
Translation "fork" direction detection ambiguity!
Correct it manually!
LBA : 676216

Re: ST2000DM001 table code segment is not found

June 29th, 2022, 7:38

Did you rebuild the translator (incorrectly)? You have a partial access problem, I hope you backed up the original system files before doing any modifications. Try uploading your original 28 into ram and it should read correctly.

Never rebuild without the original 28. On these drives the correct command to include non resident glist (sys file 35) is m0,6,3,,,,,22 NOT m0,6,2,,,,,22. Assuming it hasn't been wiped from a previous attempt.
Post a reply