Strange Maxtor

[Hexed]

I have a Maxtor SATA DM10 model 6L080M0. Drive spins up OK, no clicking at all. It takes about a minute to come ready though. When it does come ready, it is identified as the correct model and S/N. The LBA though is 199M instead of 156M. Also the auto defect relocation was already disabled. Both copies of Glist can not be read, all other modules seem OK and no access to the data area. I am wondering if someone already messed with this drives service area. Any thoughts?

[pcimage]

You tried clearing the g-list?

[BlackST]

Check "DISK" module for correct content.
All copies of G-list have errors or are trashed ? After making a backup of SA, try a clean module from identical drive.
If you have bad UBAs at G-list position, it's a totally different story.
The fact that relocation has been disabled sounds like someone made some modifications to configuration.... or is it simple coincidence ?

[pcimage]

If the g-list won't clear, check the SA area for defects, especially in the zone with the g-list in (like BlackST intimated)

If you find any, try scanning again with "reassign bad sectors by writing" to see if the bad UBA's clear. Then try and clear g-list again

Of course backup ALL mods, resources and make a LDR first.

[Hexed]

Sorry for disappearing. Was working on other jobs.
It appears None of the second copy of G-List can be read and only first 2 sectors of first copy can be read. The DISK module doesn't look correct. For some reason it has the S/N at offset x24 like it should but the S/N is written again at x30. Looked at a lot of other Disk modules and none of them have the S/N twice. I tried to write clear G-Lists from donor drive but it doesn't work. U-List has correct S/N but first model listed is a 6L100 instead of a 6L080. Not sure if that means anything. Best I can tell is I am going to have to prep a donor drive for hotswaps to get image.
Don't think my HDD tool has option to "try scanning again with "reassign bad sectors by writing".