Hello to all Respected Sir's

I have a Maxtor Hard disk

On Top Cover: 6E040L051623 (Diamondmax Plus
AAA
Code...................NAR61590
K,M,C,A
On PCB B8FEA

But in PC3000 it detects as
Model.......................... Maxtor 6E040L1 (as you can see on cover its 6E040L051 And detection is different)

Firmware....................... NCR31V30 (And in card its diffrent)

Drive status:
Disk detects ok
No error in modules / firmware

have 3 reading error in Zone 9 but i have fixed them

But when i try to access the disk it gives error in all LBA sector I want Data from the disk
Please help me. its urgent

Thanks and Regards
DF

Is the G-list full?

pcimage

No if I do G list Reading Its Empty. and Same with Plist Hutil and Plist A_PDL reading.

Thanks for your Prompt reply. If U have any Yahoo msn or ICQ

Thanks

In victoria it gives (Failed)
Model : Maxtor 6E040L1
Firmware : NCR31V30
Serial : E1BJZ35E
Disk size : 80293248 LBAs 39205 Mb
CHS: 18415/8/1140 82004 Mb
SMART : Enabled, Errlog, Selftest
CACHE: 2048k; L/A=ON; Wr=ON; ok
Support : LBA, HPA, AAM, APM, DLM, DMAUDMA-6
AAM val : 0 Disabled
APM val : 0 Disabled
Status : *Failed
Spindle : Active
Security : Not supported

darkfroce1
Pay attention to the microprogram
NCR31V30 /NCRxxxxx/ and it should be NAR61590 !

In NCRxxxxx you can't access drive in LBA mode. Usualy NCRxxxxx is used in manufacture process to create NAR61590.
Try in safe with appropriate LDR.

_________________
DataRecovery.bg

Thanks for your prompt reply and correct guidance sir I have accessed the disk in safe mode now it shows the following

HDDs Identivication has been read
1B overlay loading
1C overlay loading
ROM Copy loading
HDD Soft Reset
Overlaies loading
HDD Soft Reset
Ok!

Read roadmap............................ : Ok
Read roadmap extension.................. : Ok
Read zone allocation table.............. : Ok
Read Technological ID................... : Ok
Read Zone allocation table extension.... : Ok
SA head................................. : 3
Ext Model............................... : 6E040L0510623C
HDD has an alternate service area
HDD structures have been read successfully

Module : 78............................. : UBA 24 Reading error : Maxtor techno command error. Command : 53. Code : 0111 C/H/S : 352/3/24



Now When I Read the G LIst . I can See the Defects

RZTBL having read error
RZTbl
UBA 18637 Reading error : Maxtor techno command error. Command : 53. Code : 0111 C/H/S : 386/3/279

787 in P list
52 in Glist





There is error in RZTBL both in Copy0 and Copy1
now how to make drive access the drive in normal mode

Thanks
DF

Please relpy

Thanks

Rewrite the Rztbl module #78 in safe mode then access the drive in normal mode i think that will fix the problem mentioned above .

Thanks Sir

But will it effect the data integrity as both copy0 and copy1 are having same problem. so can I copy Module from another Hard disk or Data base (same firmware and model)

Thanks

yes if u need to save the data then rewrite the bad module from a good one but from the compatible firmware .

Thanks
Full data recovered.

What I did.

I backuped all the modules both copy 0 and copy1 as there was error in copy0 SA and some on copy1.

I created the LDR from the hard disk. and done SA verification along with reassign bad sector by writing. And Bingo . Disk started ok recognized itself correctly along with Code.

and all wanted data recovered.

Thanks to all the respected gugu's

DF

I have similar problem with that drive DATA, Copy 1 error.

DF:
What I did.
I created the LDR from the hard disk. Which hdd ? faulty one?
and done SA verification along with reassign bad sector by writing.
what do you mean? Could you please explain more?

DF could you please tell me step by step ?

Thank you all

Hi

Dear if you have noticed in my case hard disk was detecting faulty with another factory firmware instead of what it should be.so what I did

But I did all these in the guidance of the Hddguru's. I request you to put your problem in forum prior to doing all theses things. as case may be same and case may be vary. Batter take advice.

1 Make drive detect in Safe mode.

2 Entered in the utility through another LDR of same model.

3 Created the LDR file from the hard disk.

4 Re-entered the utility through its own LDR now disk was detecting correctly . Backup ed all the modules copy0 and copy1, in my case copy0 was having error more then the copy1 Plist , glist of copy1 were ok so was bit relaxed.

5 Then I did SA verification with the option Reassign bad sector.

6. came out of utility and re entered normally after removing disk from safe mode.

7 Disk got detected correctly along with firmware and I got 100% data

But I did all these in the guidance of the Hddgurus. I request you to put your problem in forum prior to doing all theses things. as case may be same and case may be vary. Batter take advice.

Thanks

if u have error in data copy 1 that is the structure module no need to load it with LDR or so get a hdd with same firmware code and copy data copy 1 strucure module from the hdd then write it on ur hdd that will fix the error .

Please think twice before taking this advice.

pepe

Yes copying Modules of other hard disk will also change the PList and Glist and this will make data Loss.

DF

Hello to all Respected Gurus

I have a 20GB Maxtor Hard disk

On Top Cover: 6E020L051605 (Diamondmax Plus
ATA/133 HDD
But in my PC-compaq D530- it detects as Model...Maxtor N40P (as you can see on cover its 6E020L051605 And detection is different) in the BIOS when the system is booting
Also,the BIOS detects the HDD as 0.00 MB HDD.
Upon booting,the O.S -win xp couldn't detect the drive

Firmware....................... NAR63G4Z
This symptom started when i fixed the virus issue on the HDD
I want very importantant data from the disk
Please help me. its urgent

Thanks in advance

Most of the times when hdd shows 0mb its a head issue take the drive out of the computer and check if its making clicking noises or not .

Case closed client dont need the data

thanks for support
DF

_________________
DF
www.datatracksystem.net

If the drive doesn't click or beep then most likely it's a firmware corruption.
You need to find someone who can work with drive firmware.
Where are you located?