This Maxtor ID : 02F020J0310211 / KMBA / A8FAA

This Maxtor Drive detected as "Qastor 2F020J0******------------------" in BIOS and the reported LBA size exceed from the original size.... Using PC3K the problem in firmware zone. and the demaged module already repaired.. now the drive can be used as usual. I just only can use this drive for 3 day.. the next the forth day I power up this HDD sound a little noise and can not detected by the BIOS... after Power off and power on again the drive now detected as "Qastor 2F020j0" again..... and restart CPU.. Now the drive can be detected as "Maxtor 2F020J0" but all the partition information has lost.. and must to repartition....
So I still use PC3K to check this drive, but PC3K report there no any problem with this drive... but sometime the problem still exist. sometime detected as Qastor and sometime Maxtor and LBA size not exceed from the original size.....

I dont know what is the problem is ????/ can anybody help me ?????

maybe some tracks in sa zoon is not stable.

Hi,

I would rather think of a contact problem somewhere in the interface lines. If a module gets damaged this way, the checksum doesn't match and drive is detected as its alias, ARES in this case.
This is only MHO.

pepe

Thanks For ur reply...
How can i know the SA zone is not stable ?????
If not stable.. is it possible to repair?????