August 25th, 2003, 5:10
I have a Maxtor 40 GB slim model with a problem similar to the MPG s from Fujitsu. Infact I had faced the same problem with many of the Maxtor slim models. The drive gets detected in the CMOS setup and in the POST summary screen the system reports that the "<primary master> hard disk fail". When we use the Power Mac utility from Maxtor, it detectes the drive and says read/ SMARt access failure and gives the error code of UK0E02. The model of the drive is Fireball 3 ATA 133 with P/N 294924-001
Can anybody help?
Regards,
Mathew Varghese
Can anybody help?
Regards,
Mathew Varghese
February 2nd, 2004, 14:12
dear friend, would like that first vc is put in a pc for best to tell him/her that to do because in the pc you have access to the setup, if you put in the pc and when detecting to appear he/she finds out the parameters that I can instructed lo
February 2nd, 2004, 15:48
Sorry Carlos i dont understant at all what are you writing,any way i would like to know how to?
regards Nikola
regards Nikola
February 3rd, 2004, 7:35
Me naõ knows, I am not the carlos, but I am terrible of English excuses me
marks daniel:D
marks daniel:D
February 4th, 2004, 17:50
Marcos, your english is even worst than mine 
About the problem with the Maxtor, the solution is similar to the one with the Fujis. You need to re-write the SA. The problem is how.
About the problem with the Maxtor, the solution is similar to the one with the Fujis. You need to re-write the SA. The problem is how.
February 17th, 2004, 8:50
Cant the PC3K do this?
February 19th, 2004, 2:03
Ha-ha!!!
After rewriting SA you will have FULLY dead drive without possibility of repair. By this action you will kill any important for drive's life information: all adaptive modules, tables of translator, defect-lists etc. But problem really is in the Service Area and you will easy repair it with PC3000.
After rewriting SA you will have FULLY dead drive without possibility of repair. By this action you will kill any important for drive's life information: all adaptive modules, tables of translator, defect-lists etc. But problem really is in the Service Area and you will easy repair it with PC3000.
February 19th, 2004, 14:11
When I said re-write SA I wanted to say only the bad modules, not all the SA of course
February 19th, 2004, 16:46
bla bla bla....
can someone put here a real fact from a succesfull repair of this model (Maxtor Ares C64K, remember?)..... if not please don't check my english!!!!!
my part now:
the hdd is detected as: Ares C64K,
possible solution:
tool: PC3000v11 updated
put the hdd from jumpers to start in "safe mode" (autospin disable).
start PC3000 util for this drive, load LDRS and RAM file from a good compatible hdd.
if the hdd doesn't stop in head knocking (for this I have no solution) you will be able to read service area. see what is wrong ant try to repair/rewrite (see automatic repair of some module for data recovery).
in most cases the drive will have some area with BBK. check and repair this too.
this is the easiest case, more problem can occur, and here is when help is most needed.........
Best Regards,
format_b.
can someone put here a real fact from a succesfull repair of this model (Maxtor Ares C64K, remember?)..... if not please don't check my english!!!!!
my part now:
the hdd is detected as: Ares C64K,
possible solution:
tool: PC3000v11 updated
put the hdd from jumpers to start in "safe mode" (autospin disable).
start PC3000 util for this drive, load LDRS and RAM file from a good compatible hdd.
if the hdd doesn't stop in head knocking (for this I have no solution) you will be able to read service area. see what is wrong ant try to repair/rewrite (see automatic repair of some module for data recovery).
in most cases the drive will have some area with BBK. check and repair this too.
this is the easiest case, more problem can occur, and here is when help is most needed.........
Best Regards,
format_b.
February 20th, 2004, 12:40
Normally is not so easy
February 20th, 2004, 15:47
Carlos : yes, not so easy.
Agreed - many drives enter BSY state.
Agreed - many drives enter BSY state.
February 24th, 2004, 4:14
Where would i find PC3000v11?
-Nightcrwler
-Nightcrwler
February 25th, 2004, 13:41
why v.11 ?
v.12 is better !!!!!
v.12 is better !!!!!
March 5th, 2004, 10:06
Ares is very bad drive for recovery
July 28th, 2005, 11:29
You must try exchange head (when do you have donor)
How to
July 29th, 2005, 7:05
digidong wrote:You must try exchange head (when do you have donor)
Qould you explain to us, please, how to exchange a head!
Re: How to
July 29th, 2005, 9:50
BGman wrote:digidong wrote:You must try exchange head (when do you have donor)
Qould you explain to us, please, how to exchange a head!
Sorry, exchange the plate to donor
Re: How to
July 29th, 2005, 12:10
So, first of all you need tool for repair. For example, you can buy PC-3000, or, if you cannot make it, you can buy Maxtor utility of Sergey Kazansky (nickname - Ruterian, you can find this person easy).
Next step is firmware checking. It is a rule, that in these drives P-List is bad and have soft-bads. Only rewrite it with clean module, after that make translator regeneration, and, I think, you will have your data.
Next step is firmware checking. It is a rule, that in these drives P-List is bad and have soft-bads. Only rewrite it with clean module, after that make translator regeneration, and, I think, you will have your data.
Powered by phpBB © phpBB Group.