Dear PC3k Guru's

In PC-3000 (UDMA), when using Utility to copy data from good donor drive; am seeing SA Head="45510" which prevents loading modules etc. When set SA Head=2, can read modules OK.

Any suggestions?

scegs

Hi Sceggy,

What drivemodel are you talking about ?

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

Dobre

Thx 4 quick response. I've got another damn Maxtor 53073U6 ....

Bizarre!

scegs

Hi Sceggy,

Never got this one.
According to you report i would suppose UDMA has trouble reading its parameters.

I'll look if i can find such a type in my stock and see what UDMA is reporting.
I'll keep in touch.

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

Dobre

PC-3000 does not recognise the drive type, though reads Model, Serial, Firmware, Capacity OK.

HDD Identification has been read
Read roadmap: Ok
Read roadmap extension: Ok
Read zone allocation table: Ok
Read Technological ID: Ok
Read Zone allocation table extension: Ok
SA head : 44510
Ext Model....
HDD structures have been read successfully

In UTILITY STATUS:
Selected family Proxima
Utility status
ROM_SA Check Sum 0000
Loaded ROM Check Sum A5EA
Model (version)
SA head 44510

????

[If change SA head to 2, can do SA surface verification ok, otherwise just Maxtor techno command error. Command: 43 Code: 181 C/H/S : x/x/x etc etc]

In addition, if create a Loader from this drive (with SA head = 2 3 4 5 6 or 7) Service Information -> Loader -> (creates without errors) ; and then attempt to use Loader in safe mode... HDD ID reading OK (well Maxtor DRACO default capacity 20018326 as to be expected), but when execute LDR file loading I get "Error loading firmware. Sector 1/257 (ABR)"...?

Am I missing something, or been working too many 16 hour days....???

scegs

Hi Scegs,

I've seen this situation with other maxtors too.
The problem is that ace has no support for these drives built in the utility.
They probably use other techno commands than the other series, so the settings cannot be identified in a correct way.
Working with the SA on this drive is risky business IMHO

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

Are you sure it's Proxima?

Can't be 100% sure [PC-3000 not clearly recognising it upfront], matches on:

DSP, Lucent, 78L08A, 48LC1M16A1

Rotation of SH6770C semiconductor by 90 degrees.

PCB Marked Maxtor DRACO II 301283100

----
Guess that's the problem with OEM drives!

scegs

This hdd is not Proxima its Nebula . I think UDMA dont support this drive .

Rameez et al..

Nebula might make sense ... and thanks for the additional information.... any tricks on trying to extract SA firmware from the donor to fix a knocking target drive?

Thanks
scegs

so old type you can try use ISA version!
good luck
wawalab

yes wawalab is right only ISA will help u with this version or u can use HDD repair 2.0

Thanks for all your input. Managed to resolve this one....