Need firmware

Require firmware for the following hdd :

Maxtor 2b020h11105h3 - kmca - b8fba .

the hdd is a poker drive .

Thanks in advance .

I have B9FBA, do you think it will fit for you?

Hi guys

I searched on the net but can't find fw. backup for this hdd:

Model: 6E040L0711233-KMBA, ide label B8FED, fw. NAR61HA0, Rom crc. 0E8B
Does someone have a backup for this model?...The problem is that G-list show wrong info:

Defects Amount: 11731
Rezerved Area: 1
Capacity: 3196

I tryed erase G-list, rewrite G-list from anothed hdd, erase G-list and P-list but nothing, the G-list shows allways the same info. Of course , because of that, the hdd has random bad sectors on all surface, from begining to the end.

Should i try a selfscan?.....can anyone give me at least a hint?

Thanks

The purpose is not to recover data right?

Yes...you're right.

So you should run the selfscan.

ok send i will try .
TO ccc ,
This is the closest i have if u need just let me know .

6E040L0711233-KCCA-B8FEC-710F

ccc
I think you are searching for somethning you already have and actually imho you do not need. Just follow dmarques advice.

Hi guys

Thanks to all for replying.

To rameez: yes i allready have that fw. backup but is't good for this hdd.....

To Samo and Dmarques: thank you for advice and i'll run selfscan and see what's happening.....but i'm just curious why the G-list keep showing the wrong info even after i rewrite/erase the module?...just for my curiosity...

Thank you all
Rgds

ccc
Maybe you rewrite the wrong module.

Samo wrote:ccc
Maybe you rewrite the wrong module.

[/code]

There is no way that i could miss that module, it's too simple, on this maxtor series the g-list is allways module PN=1B (adress 02c20019)....BTW i tested the write in SA and it says it's ok, i even try to rewrite the copy of g-list , module PN=A7, but still the same wrong info....another weird thing is that all 11731 defects are at LBA 0 and relocation sectors are at the same LBA 0 (this is what it shows).....very weird :shock:

Thanks

Why are you trying to rewrite G-List? Try to erase it, that would make at least some sense.

That's right, best thing is to erase G-List. After that run a scan to the drive.

I tryed to rewrite g-list because erasing it give no result...the info is the same...wrong...

Did you mean a selfscan or logical scan?...because logical scan gives many bad sector witch don't dissapear after relocation.

Rgds

ccc wrote: There is no way that i could miss that module, it's too simple....

It's just because too simple, are simple things really so simple?
/Off
You can boil an egg, and that takes approximately a minute and a half or two. But the funniest part is that this process can't be explained mathematicaly because of too many variables.
/End Off
BTW all drives you memtion have this output of g-list when they are in completely working state.
Defects amount : 11731
Reserve area : 1
Capacity : 3196
I think you are not digging in right direction. What about adding a bad's directly to p-list. Or write + verification/reading. And/or finally commit Selfscan.
For re-use purposes selfscan made things simple

"Passed" or "Spare part"

Just use selfscan after clear GLIST .

Samo wrote:
ccc wrote: There is no way that i could miss that module, it's too simple....

It's just because too simple, are simple things really so simple?
/Off
You can boil an egg, and that takes approximately a minute and a half or two. But the funniest part is that this process can't be explained mathematicaly because of too many variables.
/End Off

Hi Samo

I did't say that the things are simple, i just want to say that finding G-list on that drives is too simple....Anyway i'll try a selfscan on the drive and see if the problem get solved.

Thanks again

Samo wrote:BTW all drives you memtion have this output of g-list when they are in completely working state.
Defects amount : 11731
Reserve area : 1
Capacity : 3196
I think you are not digging in right direction. What about adding a bad's directly to p-list. Or write + verification/reading. And/or finally commit Selfscan.
For re-use purposes selfscan made things simple "Passed" or "Spare part"

Hi Samo

I did a more deep look in the fw. backups from this kind of maxtor series (NAR61HA0) and you're right, the info is somehow correct.....I think the problem is that PC3000 ISA can show correct info from this kind of firmware. Probably PC3000 PCI can handle the drive correctly, but i don't have it, too expensive to me.

So the only solution for this hdd is selfscan.

Thanks
Rgsd

Yes the only thing for this drive is selfscan , but pc3k isa dont start selfscan on poker drives .