Athena turns 10

hello ... this seems to be a comon topic but i couldn't find a clear answer so far.
twice it happened.

athena 20g 2b020h1 after selfscan turns 10G.

i read a variant that the number of bad sectors was larger than the capacity of the p-list and that's why it turned 10G.

or is the selfscan module the problem?

What do you know/ think about it?

If you have pc3k, you can go to universal utility and check the max LBA.
If it's not showing you the max lba for this drive, you can correct it.

Let lives good 10, than bad 20 is better.

it has nothing to do with maxlba i think.

the model is now 2b010H1 and attempts to change maxlba lead to 04h error abort.

i know it's better good 10 than bad 20, i just want to understand what happened.

Anything terrible. At passage SelfScan many mistakes were revealed and the decision to make 10 is accepted. It is better, than hang up.

Valera wrote:Anything terrible. At passage SelfScan many mistakes were revealed and the decision to make 10 is accepted. It is better, than hang up.

Valera is right. It has happend to me twice with badly damaged HDD's. I just wonder why 10GB, but not 15?...

Hi Surgentx,

If you have PC3K, check module 33(pivote defect tabel) to see it
is OK or not. If its OK, clear G&P list and do a translation. After that,
when you turn off/on your drive you should have original geometries
of your drive back.
If it is not back, then go and live with 10GB :wink:

Good luck

if you have pc3k and before selfscan read this 2b020h1 full-Firmware,you can rewrite them.and ,if you like,you can see something in 00040001.rpm by WINHEX.
good luck!

pninja wrote:If you have PC3K, check module 33(pivote defect tabel) to see it
is OK or not. If its OK, clear G&P list and do a translation. After that,
when you turn off/on your drive you should have original geometries
of your drive back.

How did you think this can help???

If selfscan finished Ok and acelab tools Ok too

after this you see the same G & P list...

If selscan don't finished Ok - drive usually don't usable.

Changing drive size(make it bigger) via play with translator - impossible.

while trying to work on max lba the drive went into service mode.

well i have done the same things and the second time selfscan was ok - 20GB.

so it wasn't a surface problem.
i don't remember which module was damaged, unfortunely, next time i will write down.

Clearing P&G lists and doing translation can undo some effects
of the selfscan (like limitting the Max/Min Cyl. range).
This a tested solution for Ares64 drive. It worked for me once.

The resulted drive that has original size may or may not be usable.
That is the another problem which was present before geometry
information loose.

BTW, I said you can go back to the original geometries. Does this mean
you can play with translator and make the drive BIGGER ?

Why are you making fun of people?

vi wrote:
pninja wrote:If you have PC3K, check module 33(pivote defect tabel) to see it
is OK or not. If its OK, clear G&P list and do a translation. After that,
when you turn off/on your drive you should have original geometries
of your drive back.

How did you think this can help???

If selfscan finished Ok and acelab tools Ok too after this you see the same G & P list...

If selscan don't finished Ok - drive usually don't usable.

Changing drive size(make it bigger) via play with translator - impossible.

pninja wrote:Hi Surgentx,

If you have PC3K, check module 33(pivote defect tabel) to see it
is OK or not. If its OK, clear G&P list and do a translation. After that,
when you turn off/on your drive you should have original geometries
of your drive back.
If it is not back, then go and live with 10GB

Good luck

Sometimes people surprise me...
1) By clearing P and G list you are killing the translator. Once you clear the G adn P lists - translated get updated.
2) Clearing the P list shifts all your data. For hard drive repair it's ok, but not for data recovery. Maximum what you shoud do is to clear the G list.

Tony wrote:Sometimes people surprise me...
1) By clearing P and G list you are killing the translator. Once you clear the G adn P lists - translated get updated.
2) Clearing the P list shifts all your data. For hard drive repair it's ok, but not for data recovery. Maximum what you shoud do is to clear the G list.

If people need data recovery, when running selfscan bad choice - all data will be destroyed

pninja wrote:Clearing P&G lists and doing translation can undo some effects
of the selfscan (like limitting the Max/Min Cyl. range).
This a tested solution for Ares64 drive. It worked for me once.

The resulted drive that has original size may or may not be usable.
That is the another problem which was present before geometry
information loose.

BTW, I said you can go back to the original geometries. Does this mean
you can play with translator and make the drive BIGGER ?
Why are you making fun of people?

Well, well, well...

All maxtor single head drive have the same capacity after servowriter, i.e. all athenas 20Gb, all Ares 40Gb etc.

After that, selfscan may cut drive to less capacity if he think what drive bad or marketing reason etc.

Drive with different size have many differense, and translator be here at very last stage, look like you don't understand how all of this work.

1. Lets think a little. If selfscan finished ok, then 0x33 (P LIST) and trаslator _MUST_ have identical info. If you clear translator (things called by acelab p-list :wink:

) then HOW right tools can create other translator???

( really acelab create not the same translator, they have difference with track skip )

2. Max LBA stored in other place (not in translator)

3. [censored]

4. did you think what 20GB drive have the same adaptive data as 10GB ( on same physical drive )?

PS usually, if maxtor slim drive don't have serious problem with surface i make him at max capacity, i.e. Athena 10Gb -> 20Gb etc.

PS2 from you post also follows, that if we "clear P&G" & 0x33 we get drive at max capacity (this is thing i called "playing with translator to make drive BIGGER")...

Maybe better to just copy disk module from correct size drive

Will it work maybe ..................

PS2 from you post also follows, that if we "clear P&G" & 0x33 we get drive at max capacity (this is thing i called "playing with translator to make drive BIGGER")...[/quote]

guru wrote::o Maybe better to just copy disk module from correct size drive
Will it work maybe ..................

This is not all :wink:

Fully restore saved modules help the best, but we return to start point in this case :wink: