6E020L0 BAD SA modules

Hi

I have a 20gb N40p which I would like some guidance with - I have used LDR from an identical drive. The SA structure check says no P/G list. Min Cyl = 0 (should be 412) Max Cyl of -1 (should be 72016)

SA scan says SWAP1,DEFECT log,DATA copy 2 are BAD.

How can I get the drive to recognise it's LBA, and how can I fix the SA defects ?

thanks

david

POST ERASED

Last edited by Tony on April 28th, 2005, 14:55, edited 1 time in total.

Hi Tony - thanks for the reply

even though there are bad sectors all over the SA ?

cheers
david

I would like to ask, how it is possible to use the PC300AT and Set Max LBA if the disk has problem in both list P and G ? magic?

POST ERASED

Last edited by Tony on April 28th, 2005, 14:55, edited 1 time in total.

Pc3000 can't correct BAD sectors in SA.
Boot in Service mode and see if there are checksum error or P&G list are fully missing.
Do a test record of SA.
If they are missing try to rewrite P&G list with same from other device.
Otherway if there are checksum error use build in procedure to fix it.
Do not forget to save original modules from the drive before doing anything with it!
Do not forget to load RAM after loading LDR too.
If you succeed with P and G list recovery MAX LBA will be corrected too.

It's fixing the P/G that's the problem...

The SA firmware structure says that the P/G are missing

SA test test says
-7 errs in swap1 but OK
-169 errs in defect log - BAD - every 3 blocks from 18788 until the end of the defect log
-50 errs in DATA2 - BAD - every 3 blocks from 19830 - 19977

all the errors are 04h

:-(

You need to hide SA defects to U list
Look at this http://www.bvg-group.ru/PRODUCTS/HRT/MAXTOR/maxtor.htm

davidl wrote:It's fixing the P/G that's the problem...

The SA firmware structure says that the P/G are missing

SA test test says
-7 errs in swap1 but OK
-169 errs in defect log - BAD - every 3 blocks from 18788 until the end of the defect log
-50 errs in DATA2 - BAD - every 3 blocks from 19830 - 19977

all the errors are 04h

Hi,

What is the complete model number (6E020L0xxxxxx)?
how about DATA1 and OVLs?
if U can re-write the modules U can possibly get it wotk. if OVLs are OK create an LDR from the defective drive and use that for writing modules.
before writing always do a write check!
at least modules 1E, 21 and 78 must be read correctly. Take into account there are differences in the zone table within the same models and versions.
if module 33 (HUTIL and HUSR) is read (or at least the beginning that contains the defect log), U can restore Plist.
always read modules with Ignore Read Errors checked!
IMHO the other modules can be written from an other drive (Same model)
In case U cannot read P and Glist, write empty ones, then, once working U can restore the file system recovering the shifts manually.

By the way U can use HotSwap as well to read the data off.
in that case first write P and G list read from the patient drive to the donor, then do the hotswap. It might be neccesary to write the zone table as well if it doesn't match the patient's.

have luck!
pepe

thanks for the replies !
before I reply, I have a quick question, as I'm getting some odd results - Are LDR's created in MX_PKR v1.2 compatible with 2.01 ? Reason is I've just read a 1.2 LDR into v2.01 and I'm getting different results - the SA structure has shifted down a loacation

in v1.2 DATA1 started at 04B8, in 2.01 it's 0008
in v1.2 OVL1 started at 2D68, in 2.01 it's 04B8

so for my 1.2 LDR in 2.01 I now have DATA1,SWAP2,DATA2,OVL2 BAD

Same SA blocks faulty though.

should I even bother using v1.2 anymore ?!?!

Posted 13/2/2005, 04:57:

Just done a bin compare of v1.2 and 2.01 LDR files - identical. which means that one of the PCMX_PKR versions is looking in the wrong place for modules ?

Hey hey hey, sometimes I san see here things with sense.
Has hope in this world

update (using v2.01)

FM structure check - all important stuff looks ok, except the area for relocated sectors seems to correspond to an 80gb drive, which neither this, nor it's healthy sister are !

SA surface check - DATA2,OVL2 BAD

accidentally erased the GLIST :shock:

- whoops !
anyways, rebooted and drive & the BIOS correctly ID'd the drive as 20gb, but not using LBA 133, but LGA 100

a new FW structure check says that the Min/Max LBA are correct. ummm ok.
Ran MTL pro on the drive which failed on retries :-(

Spinrite (! I know) could happily see the drive, 2 partitions and showed data flowing through when it did a surface check.
Booted W2k on a spare drive, and could see the 2nd partition fine - copied all data from it - OK!
1st partition appears to be empty (according to OS). Ran an undelete util on the empty partition - and I can see most of the data, but as MFT's are broken, not all the original directory names. A few read & IO errors later, most of data extracted. I have checked a number of files and they seem to be ok - I'm sure winword would moan if they were damaged files.

I don't understand how I managed to erase the GLIST entirely, when the physical location of the modules was damaged. What could I do to prevent the read errors - I presume re-create my GLIST ? from what ?

guys - thanks for all your advice - it has certainly got me thinking in the right direction with this one !