hi pclab
each $ character means a calibration attempt, so this drive is not calibrating well
the preamp and heads are detected (this drive has 2 heads) but it's in age60 like when starting with a loader, try to switch it on Age 50 and check SA modules.
if you changed heads only the CERT...
hi, i think any MCKinley with the right DCM should work, i would keep the same family for areal density match (check SPT values ;) )
about the other values on mdl:
WD2500BEVS-11UST0
customer id 11 is WD Protégé OEM
family id US is mcKinley
customer configuration code T0 should be generation 0...
hi,
if this can help on sorting donors:
WD1001FALS-00E3A0
WD1002FAEX-00Z3A0
WD10EALS-002BA0
WD10EALX-009BA0
belong to the same family (Tahoe 2D) and same SPT on SA (1296)
bye
Luca
ciao
I can't assure anything .... :) i can tell you i used it when having Plist damage and worked, but was not a tampered drive but a damaged.
anyway if you backup all system files you can rewrite them back if you need.
this is the explanation about this option:
... the Format Client Defect...
Ciao Michael
I'm not sure this will fix it but you can try to re certificate user partition using self test defect list.
Try in level t
i4,1,22 to clean glist
m0,6,4,0,0,0,0,22 to re cert udinf ST logs.
Bye
Luca
hi guys
i think there's a misunderstanding the ROM reconstruction was a way to create rom modules without rom overlays on WD drives not F3.
on F3 i think the problem is related to adaptives, RAP and SAP above all.
bye
Luca