Sector access Intruption ??

[siamak5561]

Hi I have ST2000LM007-1R8174 that one copy of sys file 1D2 damaged and i write other copy to dmaged one to get drive fully detect and functional, And i have to say didnt recalculate translator or any touch to sys 35 or 28 BUT I only access until 664258543 and after that from the end of drive nothing, IS this Sector access Intruption?
this is log after try reading beyond 664258543

Code:

Boot 0x80M
---Mrt UnLock---
LockCode:0xB3DCBD6F
LockKey:
Rst 0x80MSrv DETCR init 0x0000
(P) SATA Reset

RAW OFF
PASS
(DOS Table) Worst Count: 00000000 At SU: FFFFFFFF NT: 00000000 OT: 00000000
MSP213
(MC POR Duration): 0000000045
Send Status: COMRESET seen
CSpd= 6Gbps
DSC
Set Transfer Mode selected
Ultra DMA selected
Starting LBA of RW Request=0004F2F69D  Length=FFFFFFFF
ProcessRWError -Read-   at LBA 0004F2F8FE  Sense Code=43110081
Hd 3  Err Blk      4F2F8FE  BER pre -1.764781
Out:
ResetAbortDst

SP Regen FAIL
SP Regen ABORTED
SPRegen [0007|00000081] @LBA=0x04F2F8FEResetAbortDST
ResetAbortDST
(S) SATA Reset

Send Status: COMRESET seen
CSpd= 6Gbps
Starting LBA of RW Request=0004F2F8FE  Length=FFFFFFFF
ProcessRWError -Read-   at LBA 0004F2F8FE  Sense Code=43110081
Hd 3  Err Blk      4F2F8FE  BER pre -1.766003
Out:
ResetAbortDst
R
SP Regen FAIL
SP Regen ABORTED
SPRegen [0007|00000081] @LBA=0x04F2F8FEesetAbortDST
ResetAbortDST
(S) SATA Reset

Send Status: COMRESET seen
CSpd= 6Gbps
Starting LBA of RW Request=0004F2F8FE  Length=FFFFFFFF
ProcessRWError -Read-   at LBA 0004F2F8FE  Sense Code=43110081
Hd 3  Err Blk      4F2F8FE  BER pre -1.657814
Out:
SP Regen FAIL
SPRegen [0000|43160080] @LBA=0x04F2F8FEOut:
Unrecoverable  Error CB
Unrecoverable Read Verify Error Reported
PowerState = IDLE1
VC0


[labtech]

If disabling head 3, could it go passed that LBA?

[siamak5561]

If disabling head 3, could it go passed that LBA?

No from sector 0 until 664258543 image all sectors well with perfect speed, it seem Intruption but its weird because i did not regen translator or any modification to sys 35
I just want to know is this intrupt or not.
and disabling head 3 not useful.

[Dananjaya]

Hi
what is the meaning of this.

"BUT I only access until 664258543 and after that from the end of drive nothing"

"nothing" mean all HEX 00 or read fail. Or repeating same HEX codes with slow reading?
did you backup all important sys files?

maybe translator problem.

[siamak5561]

Read timeout in Data explorer

[siamak5561]

How to know sure this is Sector access Interruption or not?

[siamak5561]

How to know sure this is Sector access Interruption or not?

?

[MindMergepk]

Hi I have ST2000LM007-1R8174 that one copy of sys file 1D2 damaged and i write other copy to dmaged one to get drive fully detect and functional

this doesn't add up, I am sorry, with 1 bad copy of 1D2 there should be no problem in detection.
can we see content of NRGlist ? V40 ?

[siamak5561]

Hi I have ST2000LM007-1R8174 that one copy of sys file 1D2 damaged and i write other copy to dmaged one to get drive fully detect and functional

this doesn't add up, I am sorry, with 1 bad copy of 1D2 there should be no problem in detection.
can we see content of NRGlist ? V40 ?

But it was, after I wrote healthy 1D2 drive become normal,
this is V40

Code:

V40
Nonresident GList                   18 entries returned
Total entries available: 18
          PBA           Len  Flags  Phy Cyl Hd  PhySctr    SFI
           0        12E5DA     40        0  0      0        7
      1A26CE        137838     40        0  1      0    3AE9E
     10866B7           18D      0     63DA  1      0    D5B09
     112B1AB           18B      0     6A82  1      0    C6D63
     224F36A           19F      0     BCE7  1      0   14CC2E
     2E90863           195      0    102C0  1      0     AA5E
     3621D16           190      0    1235E  1      0    A8486
     60E57B1           165      0    213B9  1      0    85653
     76799DA           15E      0    288EF  1      0    67160
     779F18E           15C      0    2965F  1      0    ED1E5
     839F356           150      0    2DFD7  1      0    DEF66
     9177A48           145      0    335C9  1      0    EEEC2
     98359CE           13D      0    36645  1      0   104F62
     9A80C8E           13B      0    36BBF  1      0    F6ECA
     9BFA559           139      0    37EFE  1      0     F2A0
     A0C1514           133      0    39349  1      0    71F17
     A357AE0           130      0    3A871  1      0    722DD
     A370D70           130      0    3A9C4  1      0    7E44B
     A3A19A0           130      0    3AC55  1      0    E862D
     A3F3E4C           123      0    3B13E  1      0    9A837
     AA8C282           125      0    3E153  1      0     6781
     C989790            FD      0    4C879  1      0    97596
     D92CBDB            E2      0    54F96  1      0    7EADB
     DFDED87            D4      0    5907D  1      0    7D888


Attachments

Volume_3 FID_35.zip

(1.71 KiB) Downloaded 399 times

[siamak5561]

I begin to think maybe in some ways I did not know, sys 35 got changed or corrupted, is it possible ? let assume it changed and I dont have orig 35 , what method you suggest for repairing drive?