Maxtor D540X-4K (MX4K040H2) shows 20Gb, T0NF

[N.C.]

Hello,

I have one old maxtor 40GB, wich is clicking first.
(2 clicks, the RPM is changing, 2clicks again.
I know, this is tipical head problem.
The pcb is tested on another hdd, good.
The pream is measured, ok.)

I have replaced the headstack from my donor drive.
Now the hdd spin up, no clicking, and do usually normal recalibration sound.
After this, the BIOS shows up the drive is 20GB.
The Linux shows error message while trying to read the MBR (and the first sectors after the MBR).

The MHDD find the drive, the LBA is 40G, the drive DRDY DRSC.
But if i try to read the smart, ABRT, can't read.
If i try to scan, the drive shows T0NF, ABRT,ERR and, HPA!

And one more thing:
If i try to read the drive, it repeats the normal recalibration sound again, and again....

Somebody have an idea?

Thanks,
Janos

[BlackST]

Check 1F and 18, also check for trash in overlays.
Remeber : you changed the head stack so maybe the adaptives may not match EXACTLY the transplanted head stack.
You want the data or the disk ?

[N.C.]

Check 1F and 18, also check for trash in overlays.
Remeber : you changed the head stack so maybe the adaptives may not match EXACTLY the transplanted head stack.
You want the data or the disk ?

Thank you for the answer!

I need the data.
I forget to write this in previous post, my donor drive had also calibration problem before i dissasembled it.
It was a working drive, but sometimes only clicking (if i remember right), and the smart is showed increased calibration retry count values.
But this is my only one donor drive for this model. :S

Oh, and i still no have pc3000.
So can't check the overlays and the adaptives. :-/

You suggest to try again the HeadExchange?

Thanks,
Janos

[BlackST]

Unless you have another donor and want to try... The density is low so a perfect match is not critical. These drives sometimes develop strange problems related to adaptives , in fact a selfscan solves. Another thing: maybe head tilt or elevation?

[N.C.]

Unless you have another donor and want to try... The density is low so a perfect match is not critical. These drives sometimes develop strange problems related to adaptives , in fact a selfscan solves. Another thing: maybe head tilt or elevation?

At this time i have no donor, for do the HE again, but i can undo the first attempt to test whats happening.
Tilt or elevation?
It could be, but i don't think so.

Anyway, the drive have only 2 heads.
And the showed capacity is the half of the original.
This is interesting.
Do you think, if i start selfscan, it can solve this problem?

I think if i have a little time, i will try to assemble again the donor drive after undo the HE.

Somebody have other suggestion?

Thanks for all, and BlackST too!

Janos

[BlackST]

Selfscan maybe solve the adaptives issue but will TOTALLY DESTROY DATA.

[N.C.]

Selfscan maybe solve the adaptives issue but will TOTALLY DESTROY DATA.

Do you think about the smart self-tests? The short and long?

I used these tests on Maxtor DM9-10 but never destroys the data for me!
Only do some reallocations.

Are you sure?

Thanks,
Janos

[trubarevacki]

Only if I am not too curious: How did you start selfscan without PC3000. It seams that selfscan and smart - self test is not the same thing; maybe I just mis understudying something.

[trubarevacki]

The first thing you should try is NHPA. Are you tried some maxtor factory test on that hard?
My opinion, of course, just an opinion.

[N.C.]

Only if I am not too curious: How did you start selfscan without PC3000. It seams that selfscan and smart - self test is not the same thing; maybe I just mis understudying something.

First, i thank you for the answer!

No, i have mis understuding something, exactly the selfscan-selftest pair.
I think about only the smart self test, what i can start from linux smartctl or mhdd, if i think right....
But BlackST have talked about the selfcan, what i cant start.

Thanks,
Janos

[N.C.]

The first thing you should try is NHPA. Are you tried some maxtor factory test on that hard?
My opinion, of course, just an opinion.

I have already tried the NHPA, but not works. First BUSY, and ABRT, failed.
No, i have no tried the factory tests.
I am generally affraid the non-readonly methode tests and settings, with a swapped headstack.
I only try this if i have no other chance.

In this case, i will undo the HE, because i can do the exchange with a minimal risk, and i can test the donor's heads on the right place.

Thanks
Janos

[trubarevacki]

selfscan exactly!! I was, until now, thinking that selfscan can only be start by some manipulation in SA. How you do that without PC3000?

[N.C.]

selfscan exactly!! I was, until now, thinking that selfscan can only be start by some manipulation in SA. How you do that without PC3000?

No way, i know.
But there can be other solution also.

The drive was previously a working one, and the head is dead.
If i replace the HDA, and the drive gets alive again, but not working properly, the problem is about the HDA.
I need to find another donor, thats what i only can do at this time.

Thanks,
Janos

[trubarevacki]

You can be on the right way, but why drive has HPA flag set? Some process mess something in firmware, is'nt it?

[N.C.]

You can be on the right way, but why drive has HPA flag set? Some process mess something in firmware, is'nt it?

I have a little knowledge about this model, but only have 2 head, and 40GB.
I think, if one of the heads weak or absent, the fw can disable, and set the HPA flag?
I am not sure, but this is interesting anyway.

This is only theory.
When the drive spin up, and reach DRDY DRSC, not shows the HPA.
The HPA appears only when i try to read somethink, like parameters, or smart or else...

[trubarevacki]

Yes, that is interesting... In my opinion, it is too old drive and, in my logic, because of low data density, should not have to be to many implicit about heads. I suppose it should work with some
module manipulation.

[N.C.]

Yes, that is interesting... In my opinion, it is too old drive and, in my logic, because of low data density, should not have to be to many implicit about heads. I suppose it should work with some
module manipulation.

Yes, i understand.
But you have right, without professional FW tool, i can't do that.
Additionally i can't buy it for only this case, what the customer wont pay more than 300$.
I will do the HE again with another donor, and if the drive looks like this time, i will give up.

Thanks,
Janos

[trubarevacki]

I wish you success !!

[pepe]

Hi,

BlackST: This is a Quantum type Maxtor... it seems U are talking about the classic maxtor drives with mod 1F and 18...
NC: This drive is extremely sensitive to donor head compatibility. If your donor heads were not in perfect condition it can be that only one head is working, that's why it shows only 20GB. However if U had perfect donor heads it is still very unlikely they would match the patient drive. Not an easy task...
IMHO selfscan has nothing to do with this problem.

pepe

[N.C.]

Hi,

BlackST: This is a Quantum type Maxtor... it seems U are talking about the classic maxtor drives with mod 1F and 18...
NC: This drive is extremely sensitive to donor head compatibility. If your donor heads were not in perfect condition it can be that only one head is working, that's why it shows only 20GB. However if U had perfect donor heads it is still very unlikely they would match the patient drive. Not an easy task...
IMHO selfscan has nothing to do with this problem.

pepe

Thank you Pepe!

I will try again, and let see whats happening...

Janos