ST2000LM007 translator issue

[baldric]

http://blog.acelab.eu.com/pc-3000-f ... ackup.html

recently getting to see more ST2000LM007 model coming in.

i am trying to follow this guide,
my drive is able to read on PC, but can't copy files out.
following the guide to unlock the drive. i was able to read the first few sectors. It will BSY & error if i try to read the last sector.
If i jump to data extractor, I can't view the folders structure too. It will subsequent BSY & error if i try to read the files.


"You have to upload module and system files table in the utility and then check the box of the system file in the sys file tab to read the file."

I don't really get this step here.
can't any1 guide through?

[baldric]

i notice there's this error.
LBA alignment........................... : 0

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

Media Cache
===========
MC : enabled
MC Size : 0x0
MC MCMT Ver is unavailable!!!

---
From the beginning, the drive is able to read folders names from windows.but not able to copy.
the same error occurs in DE.

[AJ2008]

SA is locked, but data area is not but lots of read errors are likely to relate to problems with mediacache or translator - you need to patch your ROM to gain access to SA in order to solve this issue - this process can be searched in the forum it has been talked about in many posts but remember to make backup of any system files before you make any changes.

[baldric]

hi.
i patched the ROM. and backup the SA already.
The log is after patch and unlock following this step http://blog.acelab.eu.com/pc-3000-f ... rives.html

[baldric]

Test : Tech Mode unlocking preparation, (patch)
Parsing container segment....... Flash ROM image
Segment: Sgm $1D
Parsing segment....... Sgm $1D
Segment: BOOTFW_CONT_0
Parsing container segment....... BOOTFW_CONT_0
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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... BOOTFW_CONT_0
Segment: Sgm $1D
Parsing segment....... Sgm $1D
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_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: PROG_INQ_DATA
Parsing segment....... PROG_INQ_DATA
End parsing segment... PROG_INQ_DATA
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: SFW
Parsing segment....... SFW
End parsing segment... SFW
Segment: SHELL
Parsing segment....... SHELL
End parsing segment... SHELL
End parsing container segment... BOOTFW_CONT_1
Segment: SAP
Parsing segment....... SAP
End parsing segment... SAP
Segment: RAP
Parsing segment....... RAP
End parsing segment... RAP
Segment: CAP
Parsing segment....... CAP
End parsing segment... CAP
Segment: Sgm $1B
Parsing segment....... Sgm $1B
Warning! Segment used space check sum is not zero: 00008886
End parsing segment... Sgm $1B
Segment: BOOTFLOADER
Parsing segment....... BOOTFLOADER
End parsing segment... BOOTFLOADER
Segment: Sgm $1E
Parsing segment....... Sgm $1E
End parsing container segment... Flash ROM image

i notice everytime i read ROM from this model , i get this error message.

Warning! Segment used space check sum is not zero: 00008886

is it normal?

[baldric]

weird,
i get a working new good drive.
it came out with the same error .

Warning! Segment used space check sum is not zero: 00008886

Media Cache
===========
MC : enabled
MC Size : 0x0
MC MCMT Ver is unavailable!!!

not sure my pc3000 is faulty or program is faulty.

[AJ2008]

This message is expected and normal - simply ignore it and you will be fine.

If you are worried about quality of the read of the ROM, read it at slowest baud rate over boot code

[baldric]

Source of the post This message is expected and normal - simply ignore it and you will be fine.

If you are worried about quality of the read of the ROM, read it at slowest baud rate over boot code

thanks for the input.for now, really lost what to do about this drive.

[Nick_TS]

Source of the post thanks for the input.for now, really lost what to do about this drive.

Can you read sectors after SA unlocking?

[baldric]

Source of the post

Source of the post thanks for the input.for now, really lost what to do about this drive.

Can you read sectors after SA unlocking?

I can read up to 100,000 sectors.
But will BSY if I jump to last few sectors

[Nick_TS]

Source of the post I can read up to 100,000 sectors.

Did you regenerate the translator on the drive?

[baldric]

Source of the post

Source of the post I can read up to 100,000 sectors.

Did you regenerate the translator on the drive?

No.
i tried writing back the original 28 in system files via ATA(indirect). it was successful , but the last few sectors didn't work too..

[Nick_TS]

Source of the post i tried writing back the original 28 in system files via ATA(indirect). it was successful , but the last few sectors didn't work too..

Could you share V40 output from the drive here?