ACE Laboratory
Software and hard ware complex
Pc-3000
Ver 11
For diagnostics and repair
Of any HDD IDE(ATA)
Seagate Western Dig Conner
Samsung Kalok Xebec
Quantum IBM HP
Fujitsu Teac Daeyoung
pc-3000 complex
Purpose
The hardware and software complex “PC-3000” version 10.10 is designed for diagnostics and repair of any HDD with IDE interface of all modifications (ATA, ATA-2, ATA-3, ATA-4, UltraATA, E-IDE, UDMA66) and advanced factory mode repairs and restoration of widely used HDDs: Conner, Daeyoung, Fujitsu. Hitachi, IBM, Kalok, NEC, Quantum, Samsung, Seagate, Teac, Western Digital, Xebec, with the help of specialized technological utilities (see utilities list).
PC-300 Software, version 11
Universal software
Pc-3000 SHELL
Graphical user interface for PC-3000 complex for fast and convenient start of utilities.
PC-3000AT Ver. 5.08
Universal tester for diagnostics and repair of HDD of any type.
PC-DEFECTOSCOPE Ver2.10
Universal program for search and hiding of unstable and bad sectors.
PC-ACIDENT
Ldentification utility for Westem Digital HDDs of the AC family
Technological utilities
HDD manufacturer
PC-3000 utility
HDDs that can be restored
IBM
PC-IBMAVA
IC35L120AVVA07, IC35L100AVVA07, IC35L080AVVA07, IC35L060AVVA07, IC35L040AVVA07, IC35L020AVVA07.
PC-IBMAVR
IC35L060AVER07,IC35L040AVER07, IC35L030AVERO7, IC35L020AVER07, IC35L010AVER07.
PC-IBMDTL
DTLA-307075, DTLA-307060, DTLA-307045, DTLA-307030, DTLA-307020, DTLA-307015, DTLA-305040, DTLA-305030, DTLA305020, DTLA-305010.
PC-IBMDPT
DPTA-373420, DPTA-372730, DPTA-372050, DPTA-371360, DPTA-353750, DPTA-353000, DPTA-352250, DPTA-351500.
PC-IBMDJN
DJNA-372200, DJNA-372730, DJNA-371350, DJNA-370910, DJNA-352500, DJNA-352030, DJNA-351520, DJNA-351010.
SEAGATE
SEAGATE
PC-SEAGATE
ST38641A, ST36531A, ST34321A, ST32110A, ST33232A, ST32532A, ST31722A, ST31720A, ST31277A, ST31276A, ST31012A, ST3853A, ST3852A, ST3636A.
PC-ST51270A
ST32140A, ST51270A, ST51080A, ST5851A, ST5540A.
PC-ST9810AG
ST9810AG, ST9630AG, (Φopm-Φaktop 2”)
PC-ST9817AG
ST9816AG, ST9546AG, (Φopm-Φaktop 2”)
PC-ST9655AG
ST9655AG, ST9550AG, ST9385AG, ST9300AG, ST9240AG, ST9150AG, (Φopm-Φaktop 2”)
PC-ST3850A
ST3850A
PC-ST3630A
ST3630A
PC-ST3660A
ST3660A, ST3295A
PC-ST3491A
ST3491A, ST3391A, ST3250A.
PC-ST3290A
ST3290A, ST3243A, ST3145A, ST3123A.
PC-ST3655A
ST3655A, ST3550A, ST3390A, ST3385A, ST3285A, ST3283A.
PC-ST3144A
ST3144A, ST3120A, ST3096A.
PC-ST1144A
ST1144A, ST1102A.
PC-ST351A/X
ST351A/X
PC-ST157A
ST157A
WESTERN
DIGITAL
WESTERN
DIGITAL
PC-AC450AA
WD450AA, WD300AA, WD153AA, WD75AA.
PC-AC307AA
WD307AA, WD205AA, WD153AA, WD102AA.
PC-AC272AA
WD272AA, WD205AA, WD172AA, WD136AA, WD84AA, WD43AA.
PC-AC205AA
WD205AA, WD172AA, WD136AA, WD102AA, WD64AA
PC-A313000
WDAC313000, WDAC310200, WDAC28400, WDAC26400, WDAC14300.
PC-A310100
WDAC310100, WDAC38400, WDAC26400, WDAC24300, WDAC13200.
PC-A38400
WDAC38400, WDAC37100, WDAC25400, WDAC24300, WDAC12500.
PC-A36400
WDAC36400, WDAC35100, WDAC24300, WDAC23200, WDAC12100.
PC-A35100
WDAC35100, WDAC34300, WDAC23400, WDAC22500, WDAC11700.
PC-A34000
WDAC34000, WDAC3200, WDAC22500, WDAC22000, WDAC11200.
PC-A33100
WDAC33100, WDAC32500, WDAC22100, WDAC21600, WDAC11000.
PC-A32500
WDAC32500, WDAC32100, WDAC21600, WDAC21200, WDAC1850.
PC-A31600
WDAC31600, WDAC21000, WDAC1540.
PC-A21200
WDAC21200, WDAC1635.
PC-A31200
WDAC31200.
PC-A31000
WDAC31000, WDAC2700, WDAC1365.
PC-AC2850
WDAC2850, WDAC2635, WDAC1425.
PC-AC2700
WDAC2850, WDAC2700, WDAC1425.
PC-AC2540
WDAC2540, WDAC1270.
PC-AC2420
WDAC2420, WDAC1210.
PC-AC2340
WDAC2340, WDAC2250, WDAC1170.
PC-AL2170
WDAL2170
PC-CU140
WDCU140
PC-AC2200
WDAC2200
PC-AC2120
WDAC2120, WDAC160
PC-AC280
WDAC280, WDAC260, WDAC140
PC-WD9X
WD93044A, WD95044A, WD93024, WD95024A
QUANTUM
PC-QUAS
Fireball Plus AS 60, 40, 30, 20, 10.
PC-QULM
Fireball Plus LM 30.0, 20.5, 15.0, 10.2.
PC-QUKX
Fireball Plus KX 27.3, 20.5, 13.6, 10.2, 6.8.
PC-QUKA
Fireball Plus LA 18.2, 13.6, 9.1, 6.4.
PC-QLCT20
Fireball lct 20 LC 40.0, 30.0, 20.0, 10.0.
PC-QLCT15
Fireball lct 15 LC 30.0, 20.4, 15.0, 7.5.
PC-QLCT10
Fireball lct 10 LC 30.0, 20.4, 15.0, 10.2, 5.1.
PC-QLCT08
Fireball lct 08 LC 26.0, 17.3, 13.0, 8.4, 4.3.
PC-QUCX
Fireball CX 20.4, 13.0, 10.2, 6.4.
PC-QUCR
Fireball CR 13.0, 8.4, 6.4, 4.3.
PC-QUEX
Fireball EX 12.7, 10.2, 6.4, 5.1, 3.2.
PC-QUEL
Fireball EL 10.2, 7.6, 5.1, 2.5.
PC-QUSE
Fireball SE 8.4, 6.4, 4.3, 3.2, 2.1.
PC-QUST
Fireball ST 6.4, 4.3, 3.2, 2.1, 1.6.
PC-QUTM
Fireball TM 3840, 3200, 2550, 2110, 1700, 1280, 1080.
PC-QUSR
Sirocco SR 2550A, 1700A.
PC-QUSG
Pioneer 2.0, 1.0.
PC-QUBF
BigFoot 2500, 1250.
PC-QUFB
Fireball 1280, 1080, 640, 540.
PC-QUTR
Trailblazer 850, 420.
PC-QUMV
Maverick 540, 270.
PC-QULT
Lightning 730, 365.
PC-QUTB
ProDrive LPS 540, 270.
PC-QURR
ProDrivee ;PS 420, 340, 210, 170.
FUJITSU
FUJITSU
PC-FUJMPG
MPG3409AT, MPG3307AT, MOG3204AT, MPG3153AT, 3102AT
PC-FJMPGH
MPF3409AH, MPF3307AH, MPF3204AH, MPG3102AH.
PC-FUJMPF
MPF3204AT, MPF3153AT, MPF3102AT.
PC-FJMPFH
MPF3409AH, MPF3357AH, MPF3307AH, MPF3256AH, MPF3204AH, MPF3153AH, MPF3102AH.
PC-FUJMPE
MPE3273AT, MPE3224AT, MPE3204AT, MPE3170AT, MPE3136AT, MPE3102AT, MPE3064AT, MPE3032AT.
PC-FJMPEE
MPE3346AE, MPE3303AE, MPE3260AE, MPE3216AE, MPE3173AE, MPE3130AE, MPE3084AE, MPE3043AE.
PC-FJMPEH
MPE3273AH, MPE3239AH, MPE3204AH, MPE3170AH, MPE3136AH, MPE3102AH, MPE3068AH, MPE3034AH.
PC-FUJMPD
MPD3173AT, MPD3130AT, MPD3108AT, MPD3084AT, MPD3064AT, MPD3043AT.
PC-FJMPDH
MPD3182AH, MPD3144AH, MPD3137AH, MPD3102AH, MPD3091AH, MPD3068AH, MPD3045AH, MPD3023AH.
PC-FUJMPC
MPC3102AT, MPC3096AT, MPC3084AT, MPC3064AT, MPC3043AT, MPC3032AT.
PC-FUJMPCH
MPC3065AH, MPC3045AH.
PC-FUJMPB
MPB3064AT, MPB3052AT, MPB3043AT, MPB3032AT, MPB3021AT.
PC-FUJMPA
MPA3052AT, MPA3O43AT, MPA3035AT, MPA3026AT, MPA3022AT, MPA3017AT.
PC-FUJTAU
M1638TAU, M1624TAU, M1623TAU, M1636TAU.
CONNER
PC-CONNER
CFA1257A, CFA1080A, CFA850A, CFA810A, CFA540A, CFA425A, CFA340A, CFA170A, CFS1275A, CFS850A, CFS540A, CFS425A, CFS420A, CFS270A, CFS210A, CFS105A, CP30544, CP30344, CP30245, CP30204, CP30124, CP30174E, CP30084E, CP30104H, CP3000, CP3044, CFP2005S, CFP1080S, CFP1060S.
Seagate CABO: ST31621A, ST31275A, ST31081A, ST3541A.
MAXTOR
PC-MX740L
D740X-6L:MX6L080J4, MX6L060J3, MX6L040J2, MX6L020J1.
PC-MX540K
D540X-4K:MX4K080H4, MX4K060H2, MX4K040H2, MX4K020H1.
PC-MX7xxx
72004A, 71670A, 71626A, 71336A, 71260A, 71084A, 71050A, 7850AV, 7546A, 7541A, 7540A, 7425AV, 7420AV, 7345A, 7270AV, 7245A, 7213A, 7170A, 7135AV, 7131A.
PC-MX7120
7120A, 7080A, 7060A, 7040A.
PC-MXLXT
MXT-540A, LXT-535A, LXT-340A, LXT-213A, LXT-200A.
SAMSUNG
PC-SAMSNG
SV-1296A, SV-0844A, SV-0643A, SV-0432A, VG-35120A, VG-34202A, VG-33402A, VG-32502A, VG-31702A.
PC-SAMVG6
SV-1296A, SV-0844A, SV-0643A, SV-0432A.
PC-SAMVG2
VG-35102A, VG-34202A, VG-33402A, VG-32502A, VG-31702A.
PC-SAMWA
WA-33203A, WA-32543A, WA-32163A, WA-31273A, WA-31083A.
PC-SAMWNR
WNR-32501A, WNR-32101A, WNR-31601A, WN-32543A, WN321620A, WN-31273A, WN-316025A, WN-312021A, WN-310820A, WU-32543A, WU-32165A.
PC-SAMSTG
STG-31601A, STG-31271A.
PC-SAMPLS
PLS-31274A, PLS-31084A, PLS-30854A.
PC-SAMSHD
SHD-30560A, SHD-30420A, SHD-30280A, SHD-3212A, SHD-3211A, SHD-3172A, SHD-3171A, SHD-3122A, SHD-3121A.
TEAC
PC-TEAC
SD-3540N, SD-3360N, SD-3250N.
KALOK
PC-KALOK
KL3120A, KL3100A, KL3040A, KL383A, KL343A.
DAEYOUNG
PC-DX3120
DX-3120A, DX-3060A.
PC-300 SHELL
1.Introduction
The PC-SHELL software is designed for more convenient work with the PC-3000 complex. When PC-3000 SHELL is launched, a table of drive manufacturing firms and corresponding PC-3000 utilities appears on the screen. The first line in the table is occupied by the UNIVERSAL UTILITIES, PC-3000AT, and PC-DEFECTOSCOPE utilities correspond to that entry. Window switching is performed with the help of (Enter) or (Tab) keys (utility selection and start) and the (Esc) key (to return and exit PC-3000 SHELL). When a utility is selected, a list of The PC-3000 complex version is indicated in the PC-3000 SHELL title as follows:
PC-3000 Shell Ver.XXX
When X.XX is the current version of the PC-3000 complex.
《PC-3000 SHELL》includes 3 files:
shell.com-launches the shell program, is always resident in memory;
sh_main.pgm-the main program shell part, loads from the memory when utilities are launched;
shell.cfg-configuration file.
HDD power control
The use of the additional adapter PC2KPWR allows manual controlling power of the driver under test. Manual control is done in the resident mode after launching utilities from the shell (shel.com). You can get HELP on “hot keys” having launched shell.com? At present the following combinations are available:
[Alt][shift][+]or [F11]-power on;
[Alt][shift][+]or [F12]-power off.
Using these keys you can control power at any moment (in any mode) of the utilities’ work.
Purpose
Utilities of PC-3000 software and hardware complex can be used for service maintenance of Quantum drives now belonging to and supported by Maxtor. Basic repair capabilities:
Correction of damaged data structures in drive firmware;
Hiding physically damaged parts of drive surfaces using reserved space provided by the manufacturer;
Isolation of malfunctioning surfaces;
Viewing data protection password.
We have also reviewed repair methods for electronic boards of the drives as well as causes of specific malfunctions.
Attention! The success of utilities’ usage depends on the level of operator’s proficiency. Incorrect use of algorithms implemented in the utilities may irreversibly damage a drive or prevent restoration of its data.
Structure of drive families
Family
Model name
Mac.capacity
Spindle speed, rpm
PC-3000 utility
Fireball EL
EL
10.2
5,400
Pcquel.exe
Fireball EX
EX
12.7
5,400
Pcquex.exe
Fireball CR
CR
13.0
5,400
Pcqucr.exe
Fireball CX
CX
20.4
5,400
Pcqucx.exe
Fireball lct08(LA)
Lct08
26.0
5,400
Pcplct08.exe
Fireball lct10(LB)
Lct10
30.0
5,400
Pcplct10.exe
Fireball lct15(LC)
Lct15
30.0
5,400
Pcplct15.exe
Fireball lct20(LD)
Lct20
40.0
5,400
Pcplct20.exe
Maxtor D540X-4K
MX4KxxxHx
80.0
5,400
Pcmx540k..exe
Fireball Plus KA
KA
18.2
7,200
Pcquka.exe
Fireball Plus KX
KX
27.3
7,200
Pcqukx.exe
Fireball Plus LM
LM
30.0
7,200
Pcqulm.exe
Fireball Plus AS
AS
60.0
7,200
Pcquas.exe
Maxtor D740X-6L
MX6LxxxJx
80.0
7,200
Pcmx740l.exe
Basic options for repair of Quantum drives
The PC-3000 package utilities for the above-listed drives provide for the following repair operations:
drive testing in factory mode;
restoration of the drive hardware service data;
reading of the drive’s ROM;
restoration and correction of the drive ID area (logical parameters, model name, serial number);
low level format;
modification of the drive configuration (isolation of defective surfaces, isolation of defective areas);
modification of cache configuration, ECC control and automatic defects’ relocation;
review and checking of the service data structure;
loading of a program for service data access (LDR file);
review of hidden defects tables;
review of drive S.M.A.R.T. table and resetting it to factory defaults;
physical and logical surface scanning for defects, and, based on the results, addition of revealed defects to the defects table;
hiding of defective sectors;
hiding of defective tracks;
creation of an automatic surface testing routine for a drive and running it;
launch of a drive’s self-testing routine (SELFSCAN).
Preparation for work.
-Connect the PC-3000PRO tester cable to the IDE connector of the drive being tested.
-Connect the power cable to the drive being tested.
-Switch on the power. If a PC-3K PWR power supply adapter is present, the power supply is switched on automatically at utility start. Power may be switched on without turning the PC off first. Damage to the PC-3000 PRO controller in that mode is unlikely; however its output cascades may be damaged in cases when a burnt-out electronic board is connected.
-Start a utility corresponding to the connected drive’s family using the shell.com command shell for convenience.
-Auxiliary utility files are located in the same directory with the utilities. Please see details regarding auxiliary files in Section 10.
Attention! Utility tests have lots of options. It is recommended that novice users work with default test options.
Utility usage.
5.1 Launching the utility
After utility start it reads a drive’s ID area. If a drive does not process the command for ID area reading the following error message appears:
Unidentified logical drive parameters
Default values used-“Final LBA”=1000
Then a “Model selection” window appears, where you should select the model for the connected drive. After model selection the utility will read the 8th configuration page and verify the number of magnetic heads for the selected model and the connected drive. In case of mismatch the following message appears:
Model adjusted according to the number of physically present head
If a drive does not allow reading the 8th configuration page the following message will appear.
Error reading CP#8 (page containing the number of physically present heads)
Then and analysis of connected heads is performed (CP14) together with the zone allocation table (CP10). In case of errors the following messages are output:
Error reading CP#14 (heads control page)
Error reading CP#10 (zone allocation page)
Errors arising in the process of initialization are ignored and parameters that could not be recovered from the drive are replaced with default values, which may lead to incorrect operation of surface testing routines. After initialization the program will bring up the main operating modes menu:
Servo test
Surface scanning
Firmware data
Drive ID
Logical scanning
S.M.A.R.T.table
Defects table
Automatic mode
SELFSCAN Exit
5.2 Servo test.
Servo test routine performs low level formatting individually for each physically present magnetic head. Tracks that cannot be formatted may be added to defects table. This explained in detail in Section 8.1.
5.3 Surface scanning.
Surface scanning means testing of physical parameters of the surface. This command is explained in detail in “Drive surface testing” section.
5.4 Firmware data.
Firmware data represents a set of commands for work with drive’s firmware. Selection of that option brings up the following menu:
Work with ROM
Work with disk firmware zone
Modification of configuration
Load an LDR file to drive RAM
Spindle stop
5.4.1. Work with ROM.
Work with ROM command brings up a submenu containing just one option entitled “Read ROM to file”; its start requires to enter a name for the file to which ROM will be read.
5.4.2. Work with disk firmware zone.
Work with disk firmware zone is a set of routines meant for work with the portion of drive’s firmware recorded on disk surface. Selection of that option brings up the following submenu:
Check firmware structure
Write/read firmware
Read configuration pages
Write configuration pages
Read modules
Write modules
Detailed COM log
Security subsystem
5.4.2.1. Check firmware structure.
Check firmware structure command accomplishes reading of all structural units in drive’s firmware (modules and configuration pages) and performs their interpretation thus checking them for accuracy. A job report is output in a list form. It can be saved to file by pressing [F2]. Firmware checking procedure takes several minutes. That is caused by the presence of unused modules with unformatted sectors in the firmware zone.
5.4.2.2. Write/read firmware.
Write/read firmware is a set of commands that allow to create a database file containing drive’s firmware.
Extract FW from database command can be accomplished in two ways. One way is to unload the database contents in the form of configuration pages and modules to a specified directory. The other way is to write modules to a connected drive.
Add FW to database command performs reading of modules and configuration pages from a connected drive recording them to the database. The procedure will request a header for a database record at launch.
Delete FW from database command outputs a list of headers for firmware records present in the database and offers to select records for removal. A record is deleted by pressing [Enter]. Pressing [Esc] cancels the operation.
5.4.2.3 Read configuration pages
Read configuration pages command accomplishes reading of configuration pages to respective files. You can selectively specify pages for reading.
5.4.2.4 Write configuration pages
Write configuration pages command write configuration pages form respective files. You can perform selective recording. In case of size mismatch the following message appears:”~CP00.CP file size differs from expected. Continue?”
5.4.2.5 Read modules
Read modules command reads modules to files. You can read modules selectively having marked them by pressing [Space]. If a module is read with and error all successfully read sectors preceding the failing one are recorded to a file and the recording operation stops. If a file has zero size it indicates an error in the very first module.
5.4.2.6 Write module
Write modules command records modules. In case of size mismatch the following message will appear. “~Modf1.rpm file size differs from expected. Recording impossible.” Just as with reading, you can also write modules selectively.
5.4.2.7 Detailed COM log
The command allows switching on and off data output to diagnostic port of the drive. Please see details on QUANTUM diagnostic port in the description of PC-QUANTUM utility.
5.4.2.8 Security subsystem
Security subsystem represents commands for work with ATA passwords. It is present in the utilities for those drive families that support password user data protection:
Review password information command reports on passwords present in a drive.
Clear passwords command removes data protection.
5.4.3. Modification of configuration
Modification of configurations is a set of commands for changing the manufacturer-defined configuration.
5.4.3.1 Change configuration parameters
Change configuration parameters option serves for control of cache parameters. ECC control and defects relocation in standard mode of operation. Please see details in section 9.3.
5.4.3.2 Software heads deactivation
Software heads deactivation means switching heads off by means of editing firmware zone and allows to adjust drive’s firmware for work with a different number of magnetic heads without modification of existing adaptive data for still operational head/surfaces.
5.4.3.3 Zone removal
Zone removal means exclusion of zones from logical translation. Please see details in Section 6.7.
5.4.4. Load LDR file to drive RAM
Load LDR file to drive RAM command offers to input an LDR file for its subsequent loading to drive. Then the loading procedure follows with a drive restart. The selected file should correspond to the connected drive’s family.
5.4.5. Spindle stop
Spindle stop commands to switch the drive to an energy-saving mode when the drive parks its heads and stops the motor (required for hot swap operations).
5.5. Drive ID
Drive ID option serves for modification of logical parameters, model name and its serial number.
5.6 Logical scanning
Logical scanning is a drive surface test utilizing logical parameters. This command is described in detail in Section 8.2.
5.7. S.M.A.R.T table
S.M.A.R.T table represents a set of commands for review and modification of S.M.A.R.T data.
5.7.1 View S.M.A.R.T table
View S.M.A.R.T table command outputs a report containing a table of values for S.M.A.R.T attributes.
5.7.2 Load S.M.A.R.T (external module)
Load S.M.A.R.T (external module) command will requests a file with * .sma extension containing S.M.A.R.T module with factory defaults. An *. Sma file can be obtained by plain renaming of module ID=70h from a drive with required values of respective attributes.
5.7.3 Clear S.M.A.R.T. parameters
Quantum drives have a command for self-initialization of S.M.A.R.T. attributes. Using this command you can assign best values to all SMART parameters except for relocated sectors count.
5.8 Defects table
Defects table is a set of commands for work with defects table.
5.8.1. View defects table
View defects table command outputs a report containing a table of relocated defects, their total number and zone allocation. Please see detailed description of work with defects table in Section 8.4.
5.8.2 Add LBA defect
Add LBA defect command allows to enter logical LBA defects manually.
5.8.3 Add phys. Sector
Add phys. Sector command allows to enter physical sector defects manually.
5.8.4 Add physical track
Add physical track command serves for addition of one of more physical tracks.
5.8.5 Group into tracks
Group into tracks-prior to running this procedure you should enter a limit of grouping into tracks, the a search for tracks will be performed in the defects table looking for tracks containing the number of defective sectors equal to – or greater than the specified limit. Discovered tracks are added to defects table as tracks while previously hidden sectors belonging to such tracks are removed form the table.
5.8.6 Import of log. defects table
Import of long. defects table accomplishes loading of the defects table saved in PC-3000AT or PC-DEFECTOSCOPE programs.
5.8.7 Clear defects table
Clear defects table command accomplishes clearing of the defects table.
5.8.8. Export defects table
Export defects table command records defects to a file in a format specific for Quantum drives. The file has a *.qdt extension. If this command is selected you’ll be prompted for a file name without extension.
5.8.9. Import defects table
Import defects table command allows to write to the drive a previously saved (exported) table of defects. Command start will bring up a list of files with *.qdt extension. File selection is performed by pressing [Enter]. Then you’ll be prompted to enter destination for the selected defects table.
5.8.10. Work with module 60h
Firmware module ID=60h contains copy of factory defects table that may be handy during restoration of translator module ID=61h. This command forces reading the module and outputs a report on defects contained in it. Then you can run “Export defects table” and the utility will ask for a file with *.qdt extension. Restoration of ID=61h using the ID=60h module data module is reviewed in detail in Section 6.5.
5.9 Automatic mode
Automatic mode allows to create a sequence of tests and launch it. Please see an automatic mode description in the section devoted to Quantum TM.ST, and SE drives.
5.10 SELFSCAN
SELFSCAN starts a drive’s self-testing program.
5.10.1 Status review
Status review is a command that outputs a repot on current status of SELFSCAN tests. In case of successful completion the keyword value is “PASS”.
5.10.2 Start SelfScan
Start SelfScan is a command activating the self-testing program already present in the drive and used at the manufacturing factory. This command changes the keyword to “SELFSCAN”.
5.10.3 Load SelfScan
Load SelfScan command loads an external module of SELFSCAN tests contained in a *-sso file. You should select a module corresponding to the family of the connected drive and press [Ente].
5.10.4 Stop SelfScan
Stop SelfScan command discontinues automatic start of SELFSCAN tests at drive power-up. This command changes the “SELFSCAN” keyword to “STOPPED”.
Drive firmware
Head and disk assembly (HDA) in Quantum drives bears a painted label consisting of two lines (Fig 6.1).The first line contains a family code and the second-firmware version number. The same line is present in CP4. For example, CP4 record reads: AIY.1312; the second line of HDA label in that case will be: 1310. Please note that the last symbol in the lower line of HDA label will always be 0, regardless of the symbol in the actual firmware version stored in CP4.
Unfortunately there is no way to tell the ROM version by PCB itself, but incompatible versions are encountered in AS and D740-X6L families only.
Fig. 6.1. Location of label indicating the version of firmware recorded in HAD
6.1. Firmware structure.
“In preparation of this chapter we used materials kindly provide by Vadim Agulov ( alien@serv.neta.ru) and Lev Koriagin (hdd3k@cef.spbstu.ru).”
Quantum drives control firmware consists of two parts. The main initial firmware part is stored in shadow ROM combined with the processor and disk controller in a single chip. Some “sample” shipments of drives also are equipped with external ROM with serial access. The second additional firmware portion is recorded in the drive’s firmware zone as a set of modules. Those modules contain besides code some data, for example, defects table, S.M.A.R.T. tables, etc.
“CHECK FIRMWARE STRUCTURE” command (para. 5.4.2.1) in case of its successful completion outputs a report on firmware contents and settings. In the beginning of the report you can see the values of configuration parameters (see section 9.3). Then general information on configuration pages follows with details on several pages. The report completes with the information on modules that constitute a firmware zone. Even in functional drives some modules are either read with a checksum error or with reading errors. Please refer to Section 11 of this manual for information on modules that may contain errors irrelevant for drive’s operation.
Table 6.1.1. Sample module’s report.
#
ID
Cy1
Head
Sec
Length
Famcod
Rev
Status
1
0E
-3
0
0
1
36
A03
OK
Purpose of modules required for operation of Quantum drives belonging to families reviewed berein:
ID=0Eh-module with settings for reading firmware zone (firmware zone adaptives).
ID=65h-firmware zone defect table.
ID=06h-loadable overlay.
ID=05h-module containing data.
ID=00h-module containing data.
ID=01h,11h, 12h, 13h, 14h, 15h, 16h, 17h-loadable overlays.
ID=61h-module containing the translator and implicitly stored defects table.
ID=66h, 62h-modules pertaining to the defects’ relocation system.
ID=08h-module containing all the configuration pages.
ID=09h-module containing data.
ID=7xh-modules containing S.M.A.R.T system table.
Modules that are not essential for functioning in user mode:
ID=60h-module with factory log of relocated defects.
ID=2hh, 3xh . 4xh-modules of self-testing program (SELFSCAN).
The following modules are critical for data safety (they cannot be copied from another drive):ID=0Eh, 05h, 08h, 6xh.
Possible values of FamCod (family code) column are shown in the Table 6.1.2.
Table 6.1.2
Family
Family code, hex
Family
Family code,hex
EL
1F
Lct20
39
EX
2B
D540X-4k
44
CR
2D
KA
2C
CX
31
KX
32
Lct08
2A
LM
37
Lct10
36
AS
35
Lct15
41
D740X-6L
3B
6.2 Firmware saving
Firmware saving commands are “ADD FW TO DATABASE” (para.5.4.22), “READ CONFIGURATION PAGES” (para.5.4.2.3) and “READ MODULES” (para.5.4.2.5).
“ADD FW TO DATABASE” accomplishes addition of all firmware zone modules and configuration pages to a resource file. Resource files for drives, EL, CR and CX are compatible with earlier versions of utilities for those families, but they also contain configuration pages which were not added to the database previously. It is recommended to indicate drive model and firmware version when entering a record name in a database. For example:”lct10 5GB A03.093A”.
“READ CONFIGURATION PAGES” command allows to read configuration pages (or CP) of a drive. Read CPs are placed into QUxx_MOD directory, where xx is the family name. Prior to the operation of CP reading a list of CPs available for reading appears on screen, where you should select the necessary ones by pressing [Space] or choose the option “SELECT ALL”. After pressing [Enter]the selected pages will be read to the respective subdirectory. If the directory already contains CPs with the same names repeated reading procedure will overwrite them without warning.
“READ MODULES” command allows to read program modules of a drive. The process of reading and the subdirectory where the modules are written to are the same as with reading of configuration pages. If a module cannot be read the file with its copy will have zero size.
Since the drive uses a one-time programmable ROM, you need not create a database of programs contained in ROM.
6.3. Firmware transfer
The transfer is accomplished by writing previously saved firmware to a drive. The utility allows to transfer firmware using two methods: as a whole and separate modules. Transfer of whole firmware is reasonable only when most modules are corrupt. But frequently it’s impossible to write firmware if modules with adaptive data are damaged. If corrupt modules are few (for example, ID=61h and ID=71h) it is sufficient to write just those modules from a firmware copy of the same model.
“EXTRACT FW FROM DATABASE” command. If you select the “WRITE TO DRIVE” option all modules or configuration pages will be written to the firmware zone. Recording is performed according to a map of physical modules’ location read from the drive before recording starts. If for some reason the map is not output or output with errors, recording will be impossible in the first case while in the second records will appear in the wrong place, where the drive will not expect to find them after restart. There is no opportunity to select a group for writing during recording of either modules or pages.
“WRITE CONFIGURATION PAGES” command allows to write configuration pages to the firmware zone or to driver RAM. Prior to the operation a list of all CPs available for writing in the QUxx_MOD subdirectory will appear on screen, where you should select (by pressing [Space]) required modules or choose the “SELECT ALL” option. Upon pressing [Enter] the selected pages from the QUxx_MOD subdirectory are recorded to the firmware zone or drive RAM depending on the selected method.
“WRITE MODULES” command allows to record modules to the firmware zone. Prior to the operation a list of firmware modules available for writing in the QUxx_MOD subdirectory will appear on screen, where you should select (by pressing [Space] required modules or choose the “SELECT ALL” option. Upon pressing [Enter] the selected modules from the QUxx_MOD subdirectory are recorded to the firmware zone.
6.4. Safe mode
A major part of control firmware and its data are stored on disks and loaded to RAM during HDD initialization. In case of malfunction (incorrect data in firmware zone or unreadable modules) drive firmware cannot start and thus access to magnetic surfaces (for writing or reading) is impossible. In such condition all standard ATA commands return ABRT error or incorrect data.
In case of an error during firmware reading from respective zone the drives reviewed in the manual automatically switch to a protected (unlike the previous families – TM, ST, SE and earlier ones that required setting a jumper to initiate the safe mode). When such drive reports on readiness you can perform firmware initialization to operable condition by loading an LDR file or using hot swap method.
6.5. Firmware data restoration
“In preparation of this chapter we used materials kindly provided by Vadim Agulov (alien@serv.neta.ru) and Lev Koriagin (hdd3k@cef.spbstu.ru).”
PC-3000AT utility allows to detect incorrect firmware functioning. In the case after “PC3000AT.EXE” start the drive returns ABRT error (DSC, DRDY, ERR and ABRT LEDs are on while the rest are off).
The idea of restoring firmware data is writing of modules that are not recognized (cannot be read) by the drive or contain inaccurate information. Drive modules can by subdivided into the following categories judging by the methods of their restoration:
Restorable through recording from another drive.
Restorable through generation of their contents.
The first category includes loadable code overlays and tables irrelevant for drive settings, for example modules containing S.M.A.R.T parameter tables. The second category includes tables of defects, translator (sometimes combined in one module) and tables of adaptive data for surface access.
The method for restoring the modules belonging to the first category is rather simple:
Drive switches to safe mode immediately after heads leave the parking area. If you monitor the messages output to COM port you can make assumptions as to which module causes the problem.
We load an LDR file. LDR file is loaded to RAM by the “LOAD LDR FILE TO DRIVE RAM” command (para. 5.4.4). The drive will make sound similar to calibration. If the loading procedure completes with an error, the drive is very likely to have malfunctions in electronics or troubles with servo field detection by one or several magnetic heads.
We load CO10, preferably from another drive of the same model. This step is necessary to adjust the number of sectors per track in the firmware zone.
We check firmware data structure and find damaged modules (with incorrect checksum or reading error). Modules that have just one unreadable copy while the other one is readable with a correct checksum are assumed to be functional.
We overwrite discovered malfunctioning modules with correct ones from another drive of the same model.
Attention! Only damaged modules are overwritten provided they are necessary for the drive. The rest should be left as they are.
Some modules cannot be restored using the above method, here belong such modules as: ID=0Eh, ID=65h, ID=08h, ID=61h, Besides, if you record either ID=0Eh module or ID=08h module or both of them from another drive, adaptive settings will be erased and it will be erased and it will be impossible to write anything to the firmware zone using the above restoration algorithm.
ID=65h module is a defects table of the firmware zone. Most frequently the module contains no hidden defects, therefore it can be copied from another drive with a great probability of success.
ID=08h module contains all the configuration pages (CP). It is impossible to record it through the 《WRITE MODULES》option, thus its restoration requires to write all the CPs to the firmware zone.
Translator module (ID=61h) can be regenerated using probably intact module ID=60h. That operation can be carried out using the “Work with module 60h” option (para. 5.8.10); during the procedure a list of defects is output that can be saved to a *.qdt file. After that you should rewrite the ID=61h module using the “Import defects table” option (para. 5.8.9).
Attention! If you wish to preserve factory defects table you should keep in mind that during work with the defects table the copy of the factory defects table will be automatically erased by the drive; thus prior to modifying the defects table you should either export the ID=60h module or just save the module to a file and record it back to the drive, if necessary.
Attention! Hot swap operations may render the commutator/preamplifier chip inoperative.
6.6. Heads deactivation
Heads can be deactivated using either software or hardware methods. Hardware deactivation is hardly feasible since you’ll have to open the HDA thus we shall not review it here.
Software heads deactivation cannot be achieved by simple recording of firmware for a model with a lesser number of heads since we have to preserve adaptive parameters calculated for heads and surfaces of each drive. During initialization the drive detects connected heads and if the firmware does not match their number a malfunction occurs-magnetic-head assembly (MHA) knocking and spindle motor stop. The LED indicator shows error code with intermittent flashing.
Software deactivation consists in re-adjustment of drive firmware preventing the use of one of connected magnetic heads in the process of translation. Quantum has implemented such adjustment capability in its products. The only limitation of that method is that firmware zone locate under the deactivated magnetic head must be read without errors in synchronization of rotation (head assembly knocking).
The method of deactivation differs for some of reviewed drive families, therefore it is described in Chapter 11.
Attention! The defects table should contain no records for the deactivated head.
6.7.Area isolation
Apart from the opportunity to exclude heads from the process of translation, Quantum drives also allow to exclude heads from the process of translation, Quantum drives also allow to change the number of physical sectors individually for each zone. In the EL, EX, CR. KA. KX, LM drive families the number of sectors per track is indicated for all heads in a zone, while in the lct08, lct10, lct15, lct20, D540-K, AS and D740X-6L drive families the number of sectors per track is indicated also individually for each head.
In order to exclude a zone from thee translation process you should set the number of sectors per track to 0. The changes will enter into force as soon as you perform servo test and at least one defect is added to the P-list table. If no defects are added the translation routine will not be recalculated taking into account the excluded zones.
Area isolation algorithm:
We’ll have to make sure that the zone, for example, zone 1 (data zones’ numbering begins with one) has a large number of defects during Surface scanning (Section 5.3).
Firmware data-Change configuration-Isolate are [Enter].
Press [Enter] on the record of zone 1, then set SPT to 0. If a drive has its own zone table for each head, you’ll see a menu, where you can select exactly the head for further correction, In order to isolate a zone in that case you have to set SPT to zero for each head.
After zone table editing the defects table is erased.
Perform Servo test (Section 5.2) and Surface scanning (Section 5.3)
Hide the defects discovered during stage 5 in a defects table.
Perform logical testing and make sure that the zones have been isolated correctly.
Attention! It is not recommended to leave the value of sectors in a zone less that half of the factory default. That may lead to errors during work with that zone. Isolation of zones in the middle of a disk with operable zones before and after an isolated zone also may cause incorrect drive functioning in user mode.
7. Low level drive format
Low level drive format is started by the “SERVO TEST” command. Command parameters:
Initial cylinder:0
Final cylinder: 13844
Add defects: P-List
Limit of grouping into tracks: 64
Initial and final cylinder values determine the formatting range. Defective sectors discovered during testing can be added either to P-List or to G-List. Switching is performed through the “Add defects to” option by pressing [Space].
Low level formatting is performed according to physical parameters of tracks and heads in conformity to zone allocation and the number of magnetic heads. The testing procedure measures the time it takes the drive to format one track. If servo fields are faultless the time for their decoding will be approximately equal and the respective diagram in that case will look like a slightly stepped horizontal line. If servo fields of some track turn out to be corrupt, their decoding time will increase drastically. The diagram will show a spike in the corresponding section. In case of an error the spike will be yellow. The spike height (longer formatting duration) allows to judge about the degree of servo fields corruption in the current track. Before the test the existing drive defects table is loaded and if happens to contain a hidden track, such track will be skipped during formatting. In order to speed up the test in cases when the number of discovered defects exceeds the value of “LIMIT OF GROUPING INTO TRACKS” the defective track will be added to the defects table, its remaining sectors will be skipped and formatting will proceed to the following track.
Pressing [Esc] during the test will interrupt the measurement for current surface and skip to measuring the next surface. After measurement completion a table containing numbers of defective sectors and tracks is output, with every record accompanied by a respective error code. If an error code is missing, the defect was recorded after the critical time had run out. Pressing [Enter] will move all the discovered defective sectors to the defects table. If there is no need to hide the defects, please press [Esc].
Isolation of zones or heads deactivation will be correctly translated by the drive only if it successfully completes low level format. During formatting of tracks in isolated zone formatting will take considerably less time than the same procedure for an active zone. Therefore the diagram will show a spike on the border between an isolated zone and an active one.
8. Drive surface testing
Testing allows to reveal defective sectors in a drive’s effective area. There are several algorithms and approaches to the search for defective sectors. This section is devoted to review of some variants of searching for defective sectors in factory mode as well as their relocation in the defects table.
8.1. Surface scanning in factory mode
Surface scanning in factory mode is started by the “SURFACE ACANNING” command (Section5.3).
Test parameters:
Initial cylinder: xxxxx
Final cylinder: xxxxx
Passes: 3
Retries of a defect: 3
Critical time (ms): 300
Perform writing test: No
Test all heads: Yes
Add defects to: P-LIST
Initial and final cylinders parameters determine the test range.
Passes parameter defines the number of complete test passes from the initial to the final cylinders. The input range is from 1 to 100.
Retries of a defect parameter determines the test reaction to errors. The test is performed track-by-track and if an error is discovered the test proceeds to sector-by-sector analysis of such track. The number of repetitions for the analysis is defined by the “retries of a defect” parameter. In order to increase the test speed during the first pass the index equal to 1 is always suggested (the value input by the operator is used during all subsequent passes). The index value range is from 1 to 10.
Critical time means the wait period for reading (and writing) operations. If the set limit is exceeded, the sector is considered to be defective. Input range is from 40 ms to 999 ms. The default value is 3000 ms. The critical time value should be decreased very cautiously. Setting a value, which is too small (it depends upon specific drive, the testing computer, etc.), may lead to detecting false errors. Besides the drive periodically performs re-calibration procedure, which can also be interpreted as error.
Perform writing test (No/Yes)-if the writing test is set on the testing quality will be slightly better, but it almost doubles the test duration. Switching writing on/off is performed by the keys [y]-yes and [N]-No or [Space]. Switching the writing test on is recommended for individual defective surface parts with an indication of the test range.
After the surface scanning procedure is performed the table containing all the detected physical defects represented in PCHS (Physical CHS) notation appears on the screen. Pressing the [Enter] key moves all the defects to the PL defects table. Formatting procedure should be performed after that.
Test all heads (Yes/No)-test can be performed for some of the heads. That is achieved using the No option. Switching is executed by the keys [Y]-yes and [N]-No or [Space]. Then the heads that are to remain untested should be defined. This mode is used for preliminary estimate of the magnetic surfaces condition, if a large number of errors on such surface(s) impedes performing the test.
Add defects to P-LIST or G-LIST. Switching is accomplished using the [Space] key.
In order to perform surface scanning for physical parameters compliance it is recommended to run a servo test first, but even without it the testing should run correctly. After the testing procedure a table containing numbers of defective sectors will appear on the screen. Pressing the [Enter] key will move all the defective sectors to the defects table.
The test setup menu contains recommended parameters by default.
8.2. Logical surface scanning
“LOGIGAL SCANNING” option (Section 5.6) starts surface testing utilizing logical parameters.
Test parameters:
Initial LBA position: 0
Final LBA position: xxxxxxxx
Reverse scanning: No
Passes: 3
Retries of a defect: 3
Critical time (ms): 100
Perform writing test: No
Verification instead of reading: Yes
Add to: P-LIST
Initial and final LBA position parameters determine the test range.
Reverse scanning defines testing direction. Switching is performed using the [Y] key for “Yes” and [No] for “No” or [Space]. A drive reads data ahead therefore direct scanning is somewhat faster than reverse.
Passes parameter determines the number of complete test passes from the initial to final LBA. Input range is from 1 to 100.
Retries of a defect parameter determines the test reaction to errors. The test is performed block-by-block in LBA notation and if an error is discovered the test proceeds to sector-by-sector analysis of such block. The number of repetitions for the analysis is defined by the “retries of a defect” parameter. In order to increase the test speed during the first pass the index equal to 1 is always suggested (the value input by the operator is used during all subsequent passes). The index value range is form to 100.
Critical time means the critical time value for sector reading. If the set limit is exceeded, the sector is considered to be defective.
Writing can be switched on in the test and verification procedure can be replaced with reading. Testing quality in such case improves, but its duration increases, too. Switching writing on/off and substitution of reading instead of verification is done using [Y] key for “Yes” and [N] for “No” or [Space]. The surface test is based on an adaptive algorithm - detected defects are not addressed during subsequent passes. This procedure considerably decreases test duration for drives with a large number of defects. Please keep in mind that testing duration depends heavily on the number of defective sectors in a drive: the greater their number is the longer the test will run.
Add defects to P-LIST or G-LIST. Switching is accomplished using the [Space] key.
Upon completion of surface scanning procedure, the table of all discovered logical defects in LBA notation appears on the screen. Pressing [Enter] key translates all logical defects into physical ones and displays them on the screen; second pressing [Enter] appends all the defects to previous records in the defects table.
8.3. Drive self-testing
There are two possible methods of drive self-testing, i.e. factory self-testing mode and S.M.A.R.T. self-testing.
Factory self-testing can be initiated from the utility using the “START SELFSCAN” or “LOAD SELFSCAN” command. Prior to scanning you’ll have to clear the defects table. During the start keyword will change to SELFSCAN and the status information will be cleared. After loading you’ll have to switch off power supply of the drive, disconnect the power and interface cables and connect the drive to a separate power supply source. After power-up the drive will initialize and recalibrate itself, switch off its LED and make a one minute pause. After that the drive will light the LED and start self-testing procedure, during which the LED will blink indicating the current test number. Testing completion will be indicated by slow uniform blinking in case of error during the testing procedure and by frequent blinking if the test has been performed correctly. You can monitor self-testing progress through a terminal connected to an HDD COM port (please see PC-Quantum utility description).
Since factory self-testing modules in most drives are inoperative successful completion of testing is unlikely. If a drive cannot pass the tests, it will restart testing after switching the power off and on again. In order to discontinue the testing process you should perform the “STOP SELFSCAN” command (para. 5.10.4).
S.M.A.R.T. self-testing is a universal drive testing mechanism supported by many manufacturers of ATA hard drives. Please see details regarding that mode in the PC3000AT utility description.
Attention! When self scanning mode is activated such drive overwrites some of its firmware modules and restores them during the testing procedure. If self-testing ends with an error some of the modules will be inoperative, which will lead to inoperability of the whole HDD. Therefore prior to starting the self-testing procedure you should save all the firmware modules.
8.4. Relocation of defects
Defects tables in Quantum drives are stored in one module ID=61h. A defects table is read using one method, which outputs both P-list and G-list while defects addition is accomplished using various methods. Defects can be added to G-list one by one only while to P-list defects are added as a whole at once. That means that loading just one defect will erase previously relocated defect will erase previously relocated defects both from P- and from G-list. Therefore addition of a defect to P-list requires to read first the defects table, add a defect record to it and then load it back to the drive. Since the loading procedure provides no sign as to which table should contain the defect, addition of just one defect to the P-list forces automatic conversion of all G-list data to P-list.
A sample report on the defects table output by the “VIEW DEFECTS TABLE” command is shown in Table 8.4.1. The list column shows the list of defects pertaining to the current defect (P-or G-list) indicating also whether a track is hidden. Error code structure is reflected in the Table 8.4.2.
Table 8.4.1. Sample report on the defects table
#
Error code
Cylinder
Head
Sector
List
1
24H
126
0
34
P
2
2CH
457
1
697
P (TRACK)
3
42H
344
0
202
G
Table 8.4.2. Error code structure in the defects table
Bit in error byte
Value
Bit in error byte
Value
0
inline spain ID
4
Reserve BAD sector
1
Inline spain ID
5
Inline defect
2
factory defect (P-list)
6
Auto reassign
3
Unused, always 0
7
Irreparable error
Example: error code 24H means a factory defect and an inline defect.
“ADD LEB DEFECT”, “ADD PHYS. SECTOR”, “ADD PHYSICAL TRACK”, “IMPORT LOG. DEFECTS TABLE”, “GROUT INTO TRACKS” and “IMPORT DEFECTS TABLE” commands force G-list merging into the P-list.
Defects hidden in the P-list are skipped during PCHS translation to logical LBA. If a track is hidden, the drive does not get positioned to it. Clearing the P-list defects will force translator recalculation and thus appearance of previously hidden sectors in the drive’s logical data space. If a P-list is cleared in a drive containing recorded data, the data will be shifted to the maximum LBA side. A defect hidden in G-list is replaced with a reserved sector, therefore addressing a relocated sector requires time for repositioning to the place, where the substituted reserved sector actually resides. Such an operation leads to a slow-down during reading of sectors relocated through G-list.
If all the copies of ID=61h module are inoperative the “CLEAR DEFECTS TABLE” command is insufficient to restore the translator’s functionality; the malfunction will manifest itself during random reading. The drive will produce a knocking sound with the MHA hitting against a limiting stop. Such situation is corrected by hiding at least one defect in P-list with subsequent correct translator regeneration.
If a drive has just a few defective sectors you can skip testing physical parameters of the drive and proceed to logical drive testing, which should be sufficient. The procedure will be considerably faster and won’t cause a serious quality decrease. Toggling ECC correction off (please see Section 9.3) prevents self-restoration of unstable sectors and it will be easier to identify them.
9. Modification of drive configuration
Drive configuration is understood as drive’s firmware settings.
9.1. S.M.A.R.T. attributes
The “VIEW S.M.A.R.T. TABLE” command tells the utility to output a report on current values of S.M.A.R.T. parameters. You can restore the attributes to their factory value using the “LOAD S.M.A.R.T (EXTERNAL MODULE)” or “CLEAR S.M.A.R.T. PARAMETERS” command. In the former case you’ll have to specify an *.sma file containing a previously prepared module. Such clearing method does not influence in any way ID=t and ID=195 parameters since the drive calculates them at power-up based on the number of sectors hidden in G-list. In order to set them to factory defaults, too, you’ll have to perform the procedure of defects transfer from G-list to P-list.
After the factory SMART values are recorded you should switch the power off and on. If this step is skipped and the command “VIEW S.M.A.R.T. TABLE” is selected at once, the drive will record the old values back to the disk.
“CLEAR S.M.A.R.T. PARAMETERS” command forces the drive to carry out a procedure of S.M.A.R.T attributes’ restoration independently and without loading an external module.
9.2. Drive ID
The utility allows to modify logical parameters and serial number. In order to enter the changes you should select the “DRIVE ID” command. The maximum LBA can be set below the factory value to force the drive identification as a lower capacity model. There is a serial number restriction, namely-the third figure on the left indicates the number of physically present heads. If the number is input but it does not match the number of actually present heads the drive will be unable to initialize (heads will be knocking at power-up, then the spindle motor will stop). If 0 is input instead of the number of heads in the serial number the drive will not check the match.
9.3. Modification of configuration parameters
Modification is accomplished using the “CHANGE CONFIGURATION PARAMETERS” command. All reviewed Quantum drive families provide an opportunity of drive setup according to the following parameters:
Prefetch on :Yes
Cache on :Yes
Automatic writing reallocation :Yes
Automatic reading reallocation :Yes
Continuous reading :Yes
Early correction on (ECC) :Yes
Retries before correction :8
ECC correction scope :32
Write cache on :Yes
Irreparable errors reallocation :Yes
Parameters pertaining to automatic defects relocation:
Automatic writing reallocation
Automatic reading reallocation
Irreparable errors reallocation
All those three parameters should be set to “No” in order to switch off automatic defects relocation by the drive during work.
Parameters of reading errors’ correction using the ECC:
Early correction on (ECC)
Retries before correction
ECC correction scope
Switching those parameters on can decrease the number of logical defects while their disabling can respectively increase the number.
Caching and prefetch parameters:
Prefetch on
Cache on
Continuous reading
Write cache on
Those parameters influence the general drive performance but switching the writing cache on may cause data loss in case of unexpected power shutdown in the process of writing.
10. Auxiliary utility files for Quantum drives
The main *.exe utility files of the complex are supplemented by auxiliary service files. The names of those files coincide with utility name while their extension corresponds to the file type:
/utility’s name/.rsc - microprogram resources’ database file used for hardware data writing/reading and included in the supplied kit;
/utility’s name/.log – text file for the drive test results generated by the utility at the first program launch and appended with with every subsequent drive test. The file contains all the settings and test results. Data on the automatic drive test performance is also written to this file;
/utility’s name/.sma – file contains the ID-71h module containing factory values of S.M.A.R.T. attributes. It is used in the SMART parameters rest operations.
Other file names are selected by user, but their extensions are determined by the utility depending on their types
*.qdt – file containing a drive’s defects table in binary formal;
*.tsk – task file, which is used for settings’ saving in automatic test mode;
*.bin – file contains firmware for the drive’s ROM, and it is created during firmware reading from ROM;
*.rpm – technological files of the drives’ resident firmware nodules. During the reading procedure they are copied to their respective directory.
*.log files can be viewed as regular text files; *.bin files can be viewed as binary files.
11.Description of Quantum drive families
The families are combined into groups by similar construction peculiarities and methods of repair.
Heads locations are similar for all families and shown in Fig. 11.1.1.
Fig.11.1.1. Magnetic head assembly for installation of 8 magnetic reading/writing heads.
11.1. Peculiarities of EL, EX, and CR drive families
Table 11.1.1. demonstrates the mode composition of drive families. Junior model in the family contains 2 heads. The maximum number of disks for those families is 4.
Table 11.1.1. Physical and logical geometry of EL, EX, and CR drive families.
Family
Model
Capactiy,
Gb
Number
Of disks
Number
Of heads
Physical
cyls
Set./track
Maximum LBA
EL
EL2.5A
EL5.1A
EL7.6A
EL10.2A
2.5
5.1
7.6
10.2
1
2
3
4
2
4
6
8
9624
9624
9624
9624
310-185
310-185
310-185
301-185
5,008,500
10,018,890
15,032,115
20,044,080
EX
EX3.2A
EX5.1A
EX6.4A
EX10.2A
EX12.7A
3.2
5.1
6.4
10.2
12.7
1
2
2
3
4
2
3
4
6
8
11,550
11,550
11,550
11,550
11,550
349-208
349-208
349-208
349-208
349-208
6,306,048
10,018,890
12,549,960
20,044,080
24,901,632
CR
CR4.3A
CR6.4A
CR8.4A
CR13.0A
4.3
6.4
8.4
13.0
1
2
2
3
2
3
4
6
12,515
12,515
12,515
12,515
403-250
403-250
403-250
403-250
8,418,816
12,549,960
16,514,064
25,429,824
Electronics boards contain the same firmware version and are compatible within one family. A PCB from one family cannot be installed to a HAD from another family because of shadow ROM use in the processor and differences in the reading/writing channel chips.
11.1.1. External view of control boards in EL, EX and CR drive families
11.1.2. Software repair
Depending on the condition of the drive being repaired its restoration may require some specific operations. For example, if at power-up the drive doesn’t spin up the spindle motor, or spins it up and stops, then most probably the defect consists in malfunction of the electronics board, which needs a repair. If spindle motor spins up, but instead of recalibration sounds you hear monotonous strokes of the positioner hitting against the limit stop, then the defect indicates incorrect drive servo system operation and may arise from:
Malfunction of servo channel in the control board;
Malfunction of the MHA preamplifier/commutator microcircuit located inside HAD;
Malfunction of MHA;
Heavy corruption of servo fields or a shift of magnetic disks’ package after an impact (one sign indicating that the drive took an impact is greater noise of spindle motor operation and case vibration).
In any of these cases but the first one, software restoration of such drive is impossible. If after switching power on the drive spins up the spindle motor and unparks the magnetic heads, but while entering the PC-3000AT program generates the ABRT(04h) error, or errors appear one after another while reading drive surfaces, then it means that the drive can’t read hardware data from the disk. That kind of defect may arise from:
Data reading/translation channel malfunction;
Servo modules corruption;
Incompatibility between the hardware data version and the firmware recorded in the control board ROM.
In such case ensure that the control board is functional and begin the firmware data restoration as described in Section 6.5. If after switching power on the drive initializes, recalibrates, and its drive ID is read, but testing reveals bad sectors, then the restoration should be performed according to step 8.
Sometimes drives of those families demonstrate a malfunction as follows: the drive is operational but form time to time it begins to knock with its heads. This problem is not related to drive electronics. It is caused by improper factory assembly of an air lock.
Drives of EL, EX and CR families support software heads deactivation. The operation requires to use the “SOFTWARE HEADS DEACTIVATION” COMMAND. The changes will enter into force after translator recalculation performed upon addition of defects to the P-list.
Hiding of defects is accomplished using three commands of the utility:
Servo test allows to detect seriously damaged areas and determine malfunctioning head and test the heads individually.
Surface scanning procedure uses factory reading mode that allows to discover a greater number of defects than surface testing in regular user mode.
Logical testing actually does not differ much from the tests run by the PC3000AT utility except for the fact that the defects discovered while scanning are appended directly to the P-list.
Defects conversion from G-List to P-List can be accomplished through export to a *.qdt file with subsequent import form the very file. During the operation the information of defect presence in the G-list gets lost and all the defects are hidden as P-list records.
Fig. 11.1.2. External view of control hoard in the EL drive family.
11.1.3. Peculiarities of electronic components repair
Electronic components in EL, EX and CR drive families usually exhibit either failures of ATA interface of burnouts of motor controller microcircuit or they stop working completely; in that case the preamplifier/commutator chip suffers, too. Preamplifier/commutator in CR drive family is powered from a 8V source. Therefore in cases when supplied critical voltage can damage commutator in EL and EX drive famil8ies, in the CR drive families it is protected by the 8V voltage transformer.
Fig. 11.1.3. External view of control board in the EX drive family.
11.1.4. Boards identification
Control boards in EX and CR drive families have the following differences:
-EL bears the following label: “ECLIPSE MP1”;
-EX bears the following label: “ECLIPSE PLUS MP1”;
-CR bears the following label: “CORONA MP”.
Fig. 11.1.4. External view of control board in CR drive family.
11.2.Peculiarities of CX, lct08, lct10, and lct15 drive families
Table 11.2.1. demonstrates the model composition of drive families. Junior model in the family contains 2 heads. The maximum number of disks for those families is 3.
Table 11.2.1. Physical and logical geometry of CX, lct08, lct10, and lct15 drive families.
Family
Model
Capacity
,Gb
Number
Of disks
Number
Of heads
Physical
cyls
Sect./
track
Maximum
LBA
CX
CX6.4A
CX10.2A
CX13.0A
CX20.4A
6.4
10.2
13.0
20.4
1
1
2
3
2
3
4
6
15,597
15,597
15,597
15,597
512-307
512-307
512-307
512-307
12,594,960
20,044,080
25,429,824
39,876,480
Lct08
LA4.3A
LA8.4A
LA13.0A
LA17.3A
LA26.0A
4.3
8.4
13.0
17.3
26.0
1
1
2
2
3
1
2
3
4
6
19,123
19,123
19,123
19,123
19,123
539-309
539-309
539-309
539-309
539-309
8,421,840
16,514,064
25,429,824
33,906,432
50,859,648
Lct10
LB5.1A
LB10.2A
LB15.0A
LB20.4A
LB30.0A
5.1
10.2
15.0
20.4
30.0
1
1
2
2
3
1
2
3
4
6
20,596
20,596
20,596
20,596
20,596
590-338
590-338
590-338
590-338
590-338
10,002,825
20,044,080
29,336,832
39,876,480
58,633,344
Lct15
LC7.5A
LC15.0A
LC20.4A
LC30.0A
7.5
15.0
20.4
30.0
1
1
2
3
1
2
3
6
28,242
28,242
28,242
28,242
632-338
632-338
632-338
632-338
14,688,290
29,336,832
39,876,480
58,633,344
Electronics boards contain the same firmware version and are compatible within one family.
11.2.1 External view of control boards in CX, lct08, lct10, and lct15 drive families
Fig.11.2.1. External view of control board in CX drive family.
11.2.2. Software repair
In addition to paragraph 11.1.2. we can tell that lct08, lct10, and lct15 drive families exhibit translator module (ID=61h) malfunctions. Evidently, the problem appears during an attempt of defects’ self-relocation. You can toggle defects relocation by the “CHANGE CONFIGURATION PARAMETERS” command.
Right after LDR file loading modules may be recorded incorrectly since together with the LDR file an inaccurate table of firmware zone allocation is also loaded. In order to record a correct version of the table you should load to RAM CP10 configuration page, thus making it possible to work correctly with the firmware zone.
Modules that may contain reading errors or checksum errors irrelevant for drive’s correct operation are listed in Table 11.2.2.
Table 11.2.2.
Family
Module descriptors, hex.
CX
D7, D9, 43, 5F, A3
Lct08
96, 42, 45, 47, 4D, 4E, A3, B4-B9, D5, BA-BD, 51-53
Lct10
42, 45, 47, 4D, 4E, A4, B4-B9, D5, D6, BA-BD, 51-53, F0
Lct15
42, 47, 4D, 4E, A3, B4-B9, D5, BA-BD, 51-53, F2-F5
In lct08, lct10 and lct15 drive families heads deactivation through CP14 is replaced with deactivation accomplished using the zone allocation table. The method of deactivation remains the same as with zone’s isolation (Section 6.7).
Fig. 11.2.2. External view of control board in lct08, lct10, and lct15 drive families
11.2.3.Peculiarities of electronic components repair
Malfunctions of electronic components in those drive families are very frequent. Their cause remains the same: burn-outs of TDA524HT spindle motor controller chip or its substitute- AN8428AGK. Such a malfunction is obviously caused by its overheating during the process of drive operation and poor quality of chip soldering at the manufacturing factory. When the microcircuit burns out it also damages one or several 1.1 Ohm resistors connected in parallel in the spindle motor control circuit (please see a schemer at the end of this manual).
There is one more quite peculiar malfunction, namely knocking sound during drive operation. They are definitely caused by the TDA5247HT microcircuit. Its substitute AN8428AGK does not demonstrate such behaviour. The methods of eliminating such malfunction are covered with sufficient details at the technical support site: http://www.acelab.ru/pc-3000UserSupport/ in 《Repair peculiarities》=＞《Quantum》section.
In case of TDA5247HT malfunction incorrect surface recording or reading are also possible.
Drawings remark: where no measurement units are indicated the marking is understood directly, that is-as the label of the respective element. That applies for resistors and microcircuits.
Circuit diagrams of motor control unit in Quantum CX and Quantum lct08, lct10, lct15 are shown in fig. 11.2.3., 11.2.4. respectively (in the end of this manual).
11.2.4. Boards identification
The PCBs of lct08, lct10 and lct15 drive families do not have major differences, therefore they can get mixed up easily; however they are not interchangeable and there is no sense in modifying a PCB of one family to suit another because their system controllers contain shadow ROM and such modification would require to transfer that controller and the reading/writing channel chip. Marking of the latter allows to tell the boards from each other quite easily:
Family
Marking of the writing/reading channel microcircuit
Lct08
MS241C3 34
Lct10
MS241C3 34S
Lct15
MS241C3 30S
11.2.5. PC-Quantum utility and diagnostic serial port usage
In LCT08, LCT10 and LCT15 drive families one can perform drive diagnostics using the PC-KALOK adapter and a PC-Quantum adapter. Please see the description of the method for work with drives via the serial port in the description for PC-Quantum.
11.3. Peculiarities of KA, KX, LM, AS, and D740X-6L drive families
Table 11.3.1. demonstrates the model composition of drive families. Junior model in KA, KX, LM drive families has 2 magnetic heads while in AS and D740X-6L families (technological name-VQ) it has just one. AS and D740X-6L drive families have the same diagnostic connector as the one described in paragraph 11.2.5.
Table 11.3.1. Physical and logical geometry of drive families with RPM-7200.
Family
Model
Capacity
,Gb
Number
Of disks
Number
Of heads
Physical
cyls
Sect./
track
Maximum
LBA
KA
KA6.4A
KA9.1A
KA13.6A
KA18.2A
6.4
9.1
13.6
18.2
2
2
3
4
3
4
6
8
13,845
13,845
13,845
13,845
273-160
273-160
273-160
273-160
12,594,960
18,041,184
27,067,824
36,094,464
KX
KX
KX6.8A
KX10.2A
KX13.6A
KX20.5A
KX27.3A
6.8
10.2
13.6
20.5
27.3
1
2
3
3
4
2
3
4
6
8
16,878
16,878
16,878
16,878
16,878
466-280
466-280
466-280
466-280
466-280
13,385,856
20,077,041
26,771,672
40,160,988
53,550,304
LM
LM10.2A
LM15.0A
LM20.5A
LM30.0A
10.2
15.0
20.5
30.0
1
2
2
3
2
3
4
6
21,223
21,223
21,223
21,223
528-372
528-372
528-372
528-372
20,066,251
29,336,832
40,132,503
58,633,344
AS
AS10A
AS20A
AS30A
AS40A
AS60A
10.2
20.5
30.0
40.0
60.0
1
1
2
2
3
1
2
3
4
6
35,136
35,136
35,136
35,136
35,136
649-375
649-375
649-375
649-375
649-375
20,066,251
40,132,503
58,633,344
78,177,792
117,266,688
D740
X-6L
MX6L020J1
MX6L040J2
MX6L060J3
MX6L080J4
20.5
40.0
60.0
80.0
1
1
2
2
1
2
3
4
58,970
58,970
58,970
58,970
882-481
882-481
882-481
882-481
40,132,503
78,177,792
117,266,688
156,355,584
Electronics boards contain the same firmware version for KA, KX and LM drive families and are compatible within one family. In AS and D740X-6L drive families board revision has major significance. Incompatibility between firmware version and HAD will render the drive either totally inoperative or cause incorrect functioning in technological mode (correct use of utility algorithms for restoration of firmware data and defects relocation is then impossible).
11.3.1. External view of control boards in KA, KX, LM, AS, and D740X-6L drive families
Fig. 11.3.1. External view of control boards in KA, KX, and LM drive families.
11.3.2. Software repair
Modules that may contain reading errors or checksum errors irrelevant for drive’s correct operation are listed in Table 11.3.2.
Table 11.3.2.
Family
Module descriptors, hex.
KA
02, 51-55, D9, D7, 56-5E
LM
D9, A3, 41, 02, D7, 52-5E
AS
D7, D9, 94, 20, 31, 28, 42, 40, 5C, 47, 4D, 4E, C0-C2, B1-B9, D5, D6, BA-BD, F1-FA.
Fig. 11.3.2. External view of control boards in AS drive family.
11.3.3. Peculiarities of electronic components repair
Fig 11.3.3. External view of control boards in D740X-6L drive family.
The qualitative difference in electronics of drives with spindle speed 7200 PRM is manifested in the presence of a-5V source and a different motor control microcircuit – L6264.
The circuit of spindle motor controller and –5V source is practically the same in KA, KX and LM drive models and is a little different in Quantum LM drives. Its scheme is shown in fig. 11.3.4. The circuit differs considerably in AS and D740X-6L drive families but the philosophy behind the motor controller circuit remains the same.
Drives belonging to LM family quite frequently demonstrate disruption of 20 Ohm resistors connected in parallel. That is caused by malfunction of L6264 microcircuit. Its replacement together with damaged resistors repairs the malfunction.
Circuit diagrams of –5V transformer in KA, KX, and LM drive families and –5V transformer in AS and D740X-6L families are shown in fig. 11.3.4., 11.3.5. respectively (in the end of the manual).
11.3.4. Peculiarities of loading LDR files in AS drive family
“-Compatibility tests have been performed by Vadim Aulov alien@serv.neta.ru who had also provided the pcquas25.ldr file.”
AS drive family has some incompatible firmware versions therefore loading an LDR file belonging to an incompatible version may either cause error or incorrect HDD operation. At present pcquas25.ldr has been proved to be compatible with A1Y, 15xx, A1Y25xx, A1Y45xx firmware versions; while pcquass33.ldr loader is compatible with A1Y.13xx, A1Y33xx firmware versions.
11.4. Peculiarities of lct20 and D540X-K drive families
Table 11.4.1. demonstrates the model composition of drive families. Junior model in the family contains 2 heads. The maximum number of disks for those families is 2.
Table 11.4.1. Physical and logical geometry of lct20 and D540X-4K drive families.
Family
Model
Capacity
,Gb
Number
Of disks
Number
Of heads
Physical
cyls
Sect./
track
Maximum
LBA
Lct20
LD10.0A
LD20.0A
LD30.0A
LD40.0A
10.0
20.0
30.0
40.0
1
1
2
2
1
2
3
4
33,518
33,518
33,518
33,518
721-385
721-385
721-385
721-385
20,044,080
39,876,480
58,633,344
78,177,792
D540
X-4K
MX4L020J1
MX4L040J2
MX4L060J3
MX4L080J4
20.0
40.0
60.0
80.0
1
1
2
2
1
2
3
4
54,982
54,982
54,982
54,982
950-486
950-486
950-486
950-486
39,876,480
78,198,750
117,266,688
156,301,488
Electronics boards of those families are sometimes equipped with external FLASH ROM. In most cases the boards are compatible, but you should pay attention to the version of firmware code and firmware data on disks.
Lct20 and D540X-4K drive families are equipped with the same diagnostic connector for serial port as the one described in paragraph 11.2.5.
11.4.1. External view of control boards in lct20 and D540X-K drive families
Fig. 11.4.1. External view of control boards in lct20 drive family.
11.4.2. Software repair
Modules that may contain reading errors or checksum errors irrelevant for drive’s correct operation are listed in Table 11.4.2.
Table 11.4.2.
Family
Module descriptors, hex.
Lct20
07, 3E, 45, 41, 47, 4E, 51-53, B1-BD, F1-F5, C3-C7
D540X-4K
07, 54-56, 33, 41, 42, 47, 4D, 4E, A4, A5, B1-B9, D5, BA-BD, 51-53, CE
Methods of restoration for those drive families are identical to the above-described ones.
Fig. 11.4.2. External view of control boards in D540X-4K drive family.
11.4.3. Peculiarities of electronic components repair
In lct20 and D540X-4K drive families just as with previously discussed families the motor controller microcircuit AN8411SH remains the weak place. Its replacement usually repairs malfunctions.
12. Glossary
The section contains terms (in bold type) used in this manual with respective explanations.
MHA-magnetic-head assembly.
Logical sector-512-bytes data block read in standard drive operation mode.
Firmware-combination of firmware codes and data controlling drive operation.
Program modules-service data subdivided into functional parts, each with its own header and checksum.
Servo field-a record on magnetic surface required for synchronization of disk rotation and head position. Servo fields are recorded at the manufacturing factory using complicated equipment. Servo marking is individual for each drive.
Firmware zone-surface portion allocated for service data storage.
Service data-a portion of drive firmware recorded on magnetic disk surface.
Configuration pages-blocks of data that allow to configure drive’s firmware.
Factory mode-a set of ATA commands used by the manufacturing factory during the process of drive production and kept secret.
Translator-drive firmware module performing the function of LBA sector translation to PCHS taking into account relocated defective sectors.
Physical sector-512-byetes block obtained in factory mode of drive operation. Access to such sector is accomplished using the parameters of its physical location on the surface, namely by physically present heads and sector.
Physical track-a track consisting of physical sectors.
ECC-Error Correction Code. Each sector on drive’s surface is supplemented with 32 bytes of error correction code. It is necessary for restoring information that has been read from the sector in case of insignificant errors. If the data cannot be restored an “irreparable error” appears.
HOT SWAP-a method of loading resident firmware code from the firmware zone modules in case when they cannot be read by the drive from the surface for some reason.
LDR file (Loader)- a resident firmware code portion that has to be loaded to drive RAM in order to have an opportunity for recording the firmware zone that cannot be read for some reason. Of course, that code portion is written using codes of the drive it is meant for, and not for x86 architecture.
Physical CHS (PCHS)-physical cylinder, head and sector.
P-list and G-list-Names of defects tables. P-list is generated using factory mode only. G-list can be supplemented with defects during drive operation and also using the standard assign ATA command.
Test duration becomes considerably shorter in that case. The surface test is based on an adaptive algorithm-detected defects are not addressed during subsequent passes. This procedure considerably decreases test duration for drives with a large number of defects. The test of WDAC35100 (Pentium 120, 1 pass, write off, verification instead of reading) takes 30 minutes.
After the surface test procedure the table containing logical structure defects in LBA presentation appears on the screen. Pressing the [Enter] key will bring the menu, which allows to select the defects relocation mode:
Relocate defects using regular method(Assign)
Add defects into P-List
Add defects into G-List
When the first menu item is selected the defective sectors are relocated using the standard Assign procedure, physical numbers of relocated sectors are added to the G-List. One disadvantage of this method is in the impossibility of relocating defects with identifier error (IDNF) and also long positioning in the drive end during drive operation performed for reading (writing) of reserved sector.
Selecting any of the other two menu items does not relocate defective sectors. All the logical defects are transformed into physical and placed into a table depending upon the selected menu item, to the P-List or G-List.
Formatting with P-List or G-List is necessary for defects relocation using the second and third menu items and also for defects relocation using skipped sector method (to prevent the drive form positioning into the reserved area).
Attention!
Normal conversion from logical LBA presentation into physical PCHS presentation is possible only if the translator is complete and functional.
6.4.7. S.M.A.R.T. table
S.M.A.R.T. Table-allows to view S.M.A.R.T. parameters of the drive. You can read in detail about S.M.A.R.T. in the PC-3000AT tester description.
6.4.8. Defects table
Defects table-allows to view, add, clear defects table or perform defects grouping:
View defects table. This command allows to view the table of relocated defects of the drive. Viewing defects tables allows to estimate the quality and status of the used magnetic disks of the drive.
Add LBA defect. This command adds a logical defect in LBA presentation, which was detected. For example, by PC-3000AT. After addition all logical structure defects are translated into physical and placed into the defects table P-List or G-List at operator’s option. Formatting is required after adding defects to the table.
Add physical track. Allows to enter physical defective tracks manually. This command is necessary for detection a suspected defect, which cannot be discovered by means of surface scanning. For example, if the following defects appeared in the table after SURFACE TEST:
Ct1:383 Head: 1 Cy1:384 Head:1 Cy1:385 Head:1 Cy1:387 Head:1
Ct1:390 Head: 1 Cy1:391 Head:1 Cy1:392 Head:1
You will notice that the defect is scratch, but the table does not contain cylinders 386, 388, 389. It is recommended (if the number of defects is less than 100) to enter the missing tracks into the defects table and also one track from each side of the scratch, in our case it will be 382 and 393. After adding the defects formatting must be perfomed.
Import of logged defects table. This command allows to add values from *.dft file to the defects table (P or G-List at you option). Such file is generated, for instance, by Defectoscope 2.10 software or any other program. The *.dft file structure is described in the appendix for the Defectoscope utility. After adding the defects formatting must be performed.
Move G-List to P-List. This command adds the contents of G-List table to the contents of P-List table, G-List is cleared during this procedure. This mode does not influence the drive operation in any way but it allows to increase the S.M.A.R.T. parameter Relocated Sector Count.
Clear the defects table. After execution of that command the defects table will be reset-the number of defective sectors become equal to 0. The user has to select, which table should be cleared.
Group into track. This menu item allows to group into defective tracks those defective sectors, which already are entered into the defects tables. When you enter the mode the message. LIMIT OF GROUPING INTO TRACKS appears, after which sector defects are grouped into defective tracks in both P-List and G-List tables. The input range is from 1 to 50.
6.4.9. Automatic mode
Automatic mode allows to scan the drive in automatic mode without operator intervention. When this mode is selected two lists appear on the screen: TASKSLIST and AVAILABLE TASKS. Before testing starts a test program must be created or a previously created one loaded.
Test program creation.Use the [Ins] key to create a test program-the bright cursor rectangle moves from the left window TASKS LIST to the right window AVAILABLE TASKS, where you can select one of the suggested tests:
Servo test
Surface scanning
Formatting
Logical scanning
After test selection press [Enter]- this will bring you to the start menu (similar to the normal, non-automatic operation mode, see description of this test). After making corresponding adjustments you will come into the errors menu:
Relocate errors detected during test: No
Maximum number of errors allowed: 32767
Switching the errors relocation after the test ins performed by [Y]-Yes and [N]-No-keys or the [Space] key. The maximum number of errors allowed shows what number of errors is acceptable for normal test completion. If this number is exceeded, the test is interrupted as well as all following tests. This parameter should be set based on the defects table capacity and the drive capacity for defects relocation. The recommended values-1000 for servo test and 2000 for surface scanning. Actually this figure should be equal to zero for logical surface scanning, since all the defects should be discovered and relocated during surface test by physical parameters. But in face logical surface scanning may reveal a small number of defects, as a rule not greater than 100. Note that formatting must be performed after logical structure defects detection and relocation.
When all options are selected pressing [Enter] will add the selected test into the TASKS LIST window and you will be able to move on to linking the next test. If a new test has to be added before one of those, which are already in the TASKS LIST, place the cursor (bringht rectangle) over that test and press [Ins]. If you need to add a new test after the existing one, place the cursor after the test in the TASKS LIST.
Editing test program. In order to edit the test parameters of the created test program place the cursor in the TASKS LIST over that test and press [Enter]. If you wish to remove some test, place the cursor over the test name and press [Del], for adding a new one-press [Ins].
Load/save test. Press [S] key to save the test and enter the file name without extension, which is assigned automatically -*.prg. When entering the file name keep in mind that the test program will be suitable for a certain model of a certain drives family, because the number of heads, cylinders and other individual parameters are written in the test setup parameters. Therefore it is recommended to use a corresponding model name for naming the file. The file will be stored in the current PC3000 subdirectory.
Press [L] to load a test program and select the test from the list of programs located in the current PC3000 subdirectory, it switches on *.prg name filtering or the file name can be entered manually-by inputting full path to the file.
Test start. Press [R] to start the tests. All the tests are performed one by one until completion. All the test setup parameters and results are recorded into a/utility name/*.log file. Testing can be interrupted by pressing [Esc] if necessary. It is necessary to select, what should be interrupted – current test or the entire testing sequence. If an overflow of maximum allowed error number counter takes place during a test or if the formatting terminates with an error, emergency completion will take place with corresponding message about that in the log file. When the testing sequence is complete test results are output to the display (same data will be written to a log-file).
The test program, which was created or loaded remains resident until exit from the utility, i.e. you can exit from the AUTOMATIC MODE, run tests manually, record drive description parameters and the program will remain resident and ready for execution.
Exit-exits form the utility.
6.5. Brief technical description of WDC AC35100 and WDC AC34000 drive families
Electronic circuit boards of WDC AC35100 and WDC AC34000 drive families are shown in pictures 6.5.1. and 6.5.2. correspondingly.
6.5.1. Disk firmware data information
The drives have 5 cylinders (disk firmware zone) from –5 to –1 for recoding disk firmware data, which is duplicated over sides 0 and 1. The disk firware data is stored as separate modules, which together form controlling operating system.
Disk firmware structure:
TRACKS DIRECTORY;
CONFIGURATION SECTORS;
P-LIST DEFECTS TABLE;
G-LIST DEFECTS TABLE;
DISK FIRMWARE MODULES.
Microprocessor ROM contains complete firmware set for write and read operations and also for disk firmware zone formatting. That is, there is no necessity for prior loading a resident microprogram in order to write disk firmware data. There are many versions of disk firmware data and microprocessor firmware for each drives family and most of them are incompatible with each other. The microprocessor firmware version is indicated on the 27C516 ROM chip case or on the microprocessor case in the following form: 62-xxxxxx-yyy, where:
62-HDD family membership:
xxxxxx-drive family number (sometimes it differs even within one family)
yyy-firmware version number for that family.
For example, for WDC AC35100 drive the firmware version is 62-602221-063, for WDC AC34000-62-602210-062.
The firmware version is not marked in any way one the HAD and you can find it out by reading the drive description area only. In the drive description the “firmware version” line consists of two parts: xx.xxCyy, where C is some letter of Latin alphabet:
xx.xxC- controlling microprocessor firmware version
yy- version of disk firmware data, written inside the sealed block.
For example, 21.10N22- microprocessor firmware version is 21.10N and the disk firmware data version is 22.
Incompatibility of disk firmware data version and microprocessor firmware leads to unpredictable result. As a rule, the drive functions normally in usual (user’s) mode, but in the factory mode a part of commands ends in 04h (ABRT) error. For example, low-level formatting ends immediately after it starts with and error or the translation from ABA to PCHS presentation is not functioning.
Picture 6.5.1.1. Location of magnetic surfaces in 3-disk models.
Two-disk models have disks 1 and 3, an assembly ring is placed instead of disk 2. One-disk models contain lower disk 1 only.
Picture 6.5.1.2. Location of magnetic surfaces in 2-disk models.
Picture 6.5.1. Appearance of electronic controller board of WDAC35100 drive family.
6.5.2. Initialization
When the power is switched on the drive performs initialization:
RESET formation
Self-diagnostics 1
Model setup
Spindle motor start
Self-diagnostics 2
Un-parking of the magnetic heads
Reading disk firmware data
Recalibration start
Setting readiness (Waiting for ATA command)
The drive setup for a concrete model of given drive family is performed with the help of configuration resistor soldered on the MHB. When the drive is powered on its microprocessor analyses its resistance and sets itself up for corresponding drive model, see tables 6.5.2.1. and 6.5.2.2.
Table 6.5.2.1.
WDAC35100 model:
Configuration resistor on the MHB
WDAC35100
11K
WDAC35300
39K
WDAC35400
∞(resistor not installed)
WDAC22500
5.9K
WDAC11700
7.9K
Table 6.5.2.2.
WDAC34000 model:
Configuration resistor on the MHB
WDAC34000
11K
WDAC33200
39K
WDAC22500
∞(resistor not installed)
WDAC22000
5.9K
WDAC11200
7.9K
Picture 6.5.2. Appearance of electronic controller board of WDAC34000 drive family.
6.5.3. Changing drive’s configuration
When it is necessary to reconfigure the model (to switch off defective sides) you can use the hardware method, employed by the manufacturer during production- changing the configuration resistor value.
But specifically for repair purposes the drives of these families have the opportunity of software isolation of any defective side except for sides 0 and 1. This allows to switch sides off on-the-fly and switch on previously isolated sides. Therefore it is recommended to use the software repair method for HDD repairs. The utilities provide the SOFTWARE HEADS SWITCHING-OFF mode, see paragraph 6.4.3.
The hardware method for isolating defective sides is recommended for switching off side 0 or 1 only, but in any case the logical parameters should be corrected in the drive description area to match the new model.
Sometimes drive testing reveals vast corruption of ending data zone cylinders, which makes the attempt to relocate defects from that area useless. Such peculiarity is caused by the fact that the deformations caused by the rotation drive unit of magnetic heads reach their park in this area. Moreover, defects relocation procedure causes the drive to skip defective areas, data zone shifts further to the center of the disk, which makes new defects appear. Therefore, if a drive shows defects in the end of data space, it is recommended to show a smaller logical cylinder number in DRIVE DESCRIPTION AREA (PC-3000AT software can be useful for detection the end cylinder). This, will naturally lead to a decrease in the drive’s capacity.
6.5.4. Peculiarities of hardware changing of the configuration
When this method of changing configuration is selected it is recommended to install the configuration resistor not in the HAD, but immediately in the controller board, over the J1 pin between 12 and 16 contacts. Reconfiguration procedure can be performed from upside down, I, e.. by switching off defective sides and magnetic disks. You can use tables 6.5.2.1. and 6..5.2.2. for reconfiguring the drive. A shunting resistor installation is not possible for all models, for instance, it won’t allow you to transform a WEAC35100 model into a WDAC34300 model, therefore the conducting line to contact 16 of J1 is cut on the PCB and the configuration resistor is installed parallel to C42 or C*capacitor (see picture 5.5.1., 5.5.2). One model problem appears when a 3-disk model (for example, WDAC35100) is reconfigured into a single-disk model (for example, WDAC 11700). The spindle motor controller chip in 3-disk models works with a greater starting current during motor start, while for single-disk models this current is lower. Therefore such reconfiguration (The number of disks is not reduced) problems with spindle motor start may be possible. One more note! It should be kept in mind that in 2-disk models the disks are located in the 1st and the 3rd positions (disk 2 is missing, see picture 5.1.2), therefore if a WDAC35100 drive is reconfigured into a WDAC23400 model, sides 2 and 3 should be isolated in WDAC35100.
Software reconfiguration does not change the starting current of the spindle motor because the number of disks remains the same and the microprocessor “knows” about that. Besides there is no necessity to take into account the location of magnetic disks in a stack since it is done automatically.
6.5.5. Magnetic heads switching
The necessity for heads switching arises in drives with 2 or more disks when magnetic head (or side) 0 or 1 is damaged while the rest remain functional. As it was mentioned above, software cannot switch them off, that is why we have to “cheat” the microprocessor by using the switching of magnetic heads selection lines.
The purpose of heads switching is in changing the normal order for selecting magnetic heads in such a way that the defective side 0 or 1 changed places with any other functional sides of the stack with subsequent software switching off of the former sides 0 or 1. A small logic circuit in miniature SOIC case is added for that purpose to the magnetic heads selection scheme. It is located on the same side as the elements of the drive controller board. The scheme is built depending upon the number of the side or sides to be switched off. Already existing U8 invertors of the controller board can be used for switching with the H0-H2 lines, disconnection of regular inverter and sending the signal by is practically the same as switching an additional inverter! In order to achieve that you will have to raise “into the air” the inverter output of corresponding Hx line and connect the input of that inverter with the load resistor, see pictures 6.5.1.1. and 6.5 .1.2.
It is necessary to format the service area and write service data into it after heads switching procedure. WDAC35100 and WDAC34000 drive families use the magnetic heads selection scheme shown in picture 5.5.5.1. and 5.5.5.2. correspondingly. Tables 6.5.5.1-6.5.5.5. show logical states of the magnetic heads switching schemes for WDAC35100 and WDAC-34000 drive families.
Table 6.5.5.1.
WD35100 drive family, (model)
WD3400 drive family, (model)
He ad
H2
H1
H0
WDAC35100
WDAC34000
0
0
0
0
1
0
0
1
2
0
1
0
3
0
1
1
4
1
0
0
5
1
0
1
Table 6.5.5.2.
WD35100 drive family, (model)
WD3400 drive family, (model)
He ad
H2
H1
H0
WDAC34300
WDAC33200
0
0
0
0
1
0
0
1
2
0
1
0
3
0
1
1
4
1
0
0
Table 6.5.5.3.
WD35100 drive family, (model)
WD3400 drive family, (model)
He ad
H2
H1
H0
WD AC23400
WD AC22500
0
0
0
0
1
0
0
1
2
1
0
0
3
1
0
1
Table 6.5.5.4.
WD35100 drive family, (model)
WD3400 drive family, (model)
He ad
H2
H1
H0
WD AC21500
WD AC22000
0
0
0
0
1
0
0
1
2
1
0
0
Table 6.5.5.5.
WD35100 drive family, (model)
WD3400 drive family, (model)
He ad
H2
H1
H0
WD AC11700
WD AC11200
0
0
0
0
1
0
0
1
6.5.5.1. Heads switching examples
Example 1.
| 课件名称： | 硬盘维修参考资料 |
| 课件分类： | 计算机 |
| 课件类型： | 参考资料 |
| 文件大小： | 1.3MB |
| 下载次数： | 3 |
| 评论次数： | 2 |
| 用户评分： | 7.5 |
- 6. 硬盘维修参考资料：硬盘故障提示信息中文含义
- 7. 硬盘维修参考资料：硬盘数据恢复教程
- 8. 硬盘维修参考资料：硬盘数据恢复知识
- 9. 硬盘维修参考资料：硬盘电路板测试及维修技巧
- 10. 硬盘维修参考资料：硬盘维修
- 11. 硬盘维修参考资料：硬盘维修入门教材
- 12. 硬盘维修参考资料：硬盘维修原理
- 13. 硬盘维修参考资料：硬盘维修彻底揭密
- 14. 硬盘维修参考资料：硬盘维修恢复说明1（一）
- 15. 硬盘维修参考资料：硬盘维修恢复说明（一）
- 16. 硬盘维修参考资料：硬盘维修资料2
- 17. 硬盘维修参考资料：硬盘缺陷的分类
- 18. 硬盘维修参考资料：硬盘诊断要领
- 19. 硬盘维修参考资料：硬盘软故障完全修复手册——数据结构篇
- 20. 硬盘维修参考资料：维修硬盘资料1
- 21. 硬盘维修参考资料：美钻的硬盘
- 22. 硬盘维修参考资料：解开硬盘逻辑死锁的另几种有效方法！（简易）
- 23. 硬盘维修参考资料：钻石硬盘维修实战手册（1）
- 24. 硬盘维修参考资料：钻石硬盘维修实战手册（2）
