Need Firmware Maxtor 4D040H2

[Amarbir[CDR-Labs]]

Mates ,
I Have This Drive and it has a firmware issue

Model Maxtor 4D040H2
HDA :22A
PCBA :05A
Unique :11A
Code :DAH017K0
Mfg Date :21Mar2002

But The Bad Part Is I Cannot Get the Code Like X,X,X,X Cos The Label There is Gone Not there

Note :Data is Not Imp Drive Recovery Is,Salvation Is Required if You Have Pc 3000 PCI Then I Could Try To Use The Same Too

[N.C.]

Mates ,
I Have This Drive and it has a firmware issue

Model Maxtor 4D040H2
HDA :22A
PCBA :05A
Unique :11A
Code AH017K0
Mfg Date :21Mar2002

But The Bad Part Is I Cannot Get the Code Like X,X,X,X Cos The Label There is Gone Not there

Note ata is Not Imp Drive Recovery Is,Salvation Is Required if You Have Pc 3000 PCI Then I Could Try To Use The Same Too

I have some firmware for these drives, but you need to know the code.

Can't you read out the original fw's part with the code using hotswap?

Janos

[Amarbir[CDR-Labs]]

Mates ,
I Have This Drive and it has a firmware issue

Model Maxtor 4D040H2
HDA :22A
PCBA :05A
Unique :11A
Code AH017K0
Mfg Date :21Mar2002

But The Bad Part Is I Cannot Get the Code Like X,X,X,X Cos The Label There is Gone Not there

Note ata is Not Imp Drive Recovery Is,Salvation Is Required if You Have Pc 3000 PCI Then I Could Try To Use The Same Too

I have some firmware for these drives, but you need to know the code.

Can't you read out the original fw's part with the code using hotswap?

Janos

Janos ,
I Have Two More Drives That Are 4d040h2 But i Am Not sure Of the Code they have will match this ,Will a Hotswap Work In this Case ,Have You ever Tried It .Do You Have Same HDA,PCBA and Unique And Code Matching Mine ,Also If the Dates Match i Will Be sure of a Resolution ,Check Your Collection Please

[shahij]

can u mention the S/N?

[N.C.]

Amarbir,

With hotswap, you have only 2 chance:

1. can read the module with assembly
2. clicking.

Both are harmless. (if you don't let the drive clicking for hours)

I have found first this:

DAH017K0
HDA 22A
PCBA 05A
Unique: 22A

Date 22JUL2002, Singapore
Assembly: CMCB
SN: D27KW4KE

The drive has IBM FRU, so, check the LBA too! This has: 78156288

This is enough close, or need to find anoter?

Janos

[Amarbir[CDR-Labs]]

Amarbir,

With hotswap, you have only 2 chance:

1. can read the module with assembly
2. clicking.

Both are harmless. (if you don't let the drive clicking for hours)

I have found first this:

DAH017K0
HDA 22A
PCBA 05A
Unique: 22A

Date 22JUL2002, Singapore
Assembly: CMCB
SN: D27KW4KE

The drive has IBM FRU, so, check the LBA too! This has: 78156288

This is enough close, or need to find anoter?

Janos

Janos ,
My LBA Is 80043264 .Drive S/N As Shahij Wanted is D249S5LE

I Need Boot File ,Resource File ,Rom "Might Be" ,Firmware ,Ram File If Possible

[shahij]

i have
4D040H2-DAH017K0-D24NNTEE
LBA: 80043264

[N.C.]

Janos ,
My LBA Is 80043264 .Drive S/N As Shahij Wanted is D249S5LE

I Need Boot File ,Resource File ,Rom "Might Be" ,Firmware ,Ram File If Possible

In this way, this drive is useless for you.
I have closest, i am sure, but needs to look again in the collection...


Janos

[Amarbir[CDR-Labs]]

i have
4D040H2-DAH017K0-D24NNTEE
LBA: 80043264

Well ,
Then Gimme the Same

[Amarbir[CDR-Labs]]

Janos ,
My LBA Is 80043264 .Drive S/N As Shahij Wanted is D249S5LE

I Need Boot File ,Resource File ,Rom "Might Be" ,Firmware ,Ram File If Possible

In this way, this drive is useless for you.
I have closest, i am sure, but needs to look again in the collection...


Janos

Well ,
send What You Have Like This I Will Try Atleast

[shahij]

in which address will i send it?
yahoo or msn?

[N.C.]

I have found 2 similar:

4D040H2
HDA: 22A
PCB: 03A !
Uni: 11A

DAH017K0
LBA: 80...

The differences:
SN: D21..., D20...
KMDB, NMCB
07NOV2001, 22SEP2001

Janos

[shahij]

Three conditions are applicable for maxtor drives

1. Same Model (4D040H2)
2. Same Code Number (DAH017K0)
3. First 3 digits of the SN same (D24XXXXX)

[N.C.]

Three conditions are applicable for maxtor drives

1. Same Model (4D040H2)
2. Same Code Number (DAH017K0)
3. First 3 digits of the SN same (D24XXXXX)

This is not always true unfortunately.
My last 2 drive is uncompatible, because have different head/preamp manufacturere. (only clicking, i have tried)
Additionally, my first, have IBM FRU, different LBA, and different FW structure as well.

You need to match more part.

Additionally, the 3rd number in the SN is unimportant, i am almost sure. (>95%)

Janos

[Amarbir[CDR-Labs]]

Hi ,
The Drive Booted Off the Loader of the Other Drive i Had aT Home ,I Backed Up the entire firmware of That To the Patient and Now the Patient Works Fine ,Detected and all ,But If I Scan The Drive All Sectors Are Bad .I Plan To Do a Zerofill To Regenerate the Translator .Thats Currently Going On .Also i Uploaded To SA-A And Not To SA-B .In My Case SA-A And B Are Different .Also Something Funny Happened Once Before I Repaired the Drive and all ,then i Cleared G and P List ,the Drive again Lost Its Working And Became Romulas ,I Had To Do The Same again Before i Could Try Translator Regeneration of Zerofill As Salvation Calls It


PS :Nc An Shahji You Were More Then Helpful

[Amarbir[CDR-Labs]]

Hi ,
Latest Develeopment is That,I Have The entire SA-A Replaced With the DONOR firmware ,Do You People Advice This ? .Or Its Better To Replace Bad Modules Only ,Module 51 and 100 Appear Bad in All 4d040h2 drives in salvation tool .I Also Tried Scanner Donor SA-B And Got Lots of Errors .I Have No Answer Why If i Could Read SA-A From donor Properly Why So Many Errors In SA-B .I Also Replaced Donar SA-A Modules To Patient SA-B ,Lots of Modules Got Copied And Lots of Them did Not .Does 4d040h2 have functional SA-B ? .I them cleared P and G List ,But Like Last time The Drive did Not Loose Its Parameters and Become Romulas Again .Then i Zerofilled the Same ,Now i am Scanning to Defects And the Defect Count Is already Reached 7K .

PS :I did Keep the Backup of The Patient SA-A Not SA-B ,I will Upload the Entire SA-a of the Saved Patient Drive Back to the patient and then replace the defective modules from donor and do this experiment again .Might be i will not get these many bad sectors .Does the firmware in these maxtors keep some information in the original SA thats unique to a drive ? .Rameez your suggestions are welcomed as you have vast experience in this .If i Concentrate on SA-A and then Make it Perfect then i Could Upload the SA-A To SA-B

[BlackST]

Have you ever heard the word 'adaptives' ? This is the key.

[irs]

hi Amarbir,
as i see salvation hd doctor don't advice about the modules that are unique for the drive like pc3k does.
i always prefer to back up modules and groups of the drive and fix only the corrupted modules which are needed to acces the datas (i don't mind selfscan and other not vital modules ...).
Without right adaptives modules it's hard to write again in sa (users, correct me if i'm wrong).
If you left the sa-b as it was may be you can try with a bootloader-B and try a r/w test, if it works write back the original adaptives on sa-a.
I hope this can work

[N.C.]

Keep that in mind:

If the drive can't read something or some module have checksum error, or uncompatible with the other parts, the drive try to mix up the SA-A and the SA-B!
Trying to read the bad/missing modules from the SA-B, if the corresponding module is unavailable in SA-A!

Additionally, BlaskSt have right!
If you kill the original adaptives, you will have only a minimal chance to recover the SA again....

Janos

[BlackST]

Missed a thing : need data or the drive?