Professional Documents
Culture Documents
¤ ACELab D541X, Fireball 3, Diamond Max Plus 8, Diamond Max Plus 16, Diamond Max Plus 9"
Contents
1. Purpose..........................................................................................................................................................................2
2. Structure of drive families.............................................................................................................................................2
3. Basic options for repair of Maxtor drives .....................................................................................................................3
4. Preparation for work .....................................................................................................................................................3
5. Utility usage ..................................................................................................................................................................4
5.1. Launching the utility ..............................................................................................................................................4
5.2. Utility menu structure ............................................................................................................................................4
5.2.1. Logical scanning ............................................................................................................................................... 4
5.2.2. Disc firmware zone ........................................................................................................................................... 5
5.2.3. Disc ID .............................................................................................................................................................. 6
5.2.4. Defects table...................................................................................................................................................... 6
5.2.5. SELF TEST mode............................................................................................................................................. 7
6. Firmware .......................................................................................................................................................................7
6.1. General information ...............................................................................................................................................7
6.2. Firmware modules..................................................................................................................................................9
6.3. Translator in Maxtor drives .................................................................................................................................10
7. Software restoration of Maxtor HDD .........................................................................................................................10
7.1. Diagnostics of firmware zone malfunctions ........................................................................................................10
7.2. Automatic restoration of module headers ............................................................................................................12
7.3. Translator restoration ...........................................................................................................................................12
8. Surface testing of Maxtor drives.................................................................................................................................12
8.1. Surface testing of firmware zone .........................................................................................................................12
8.2. Logical scanning ..................................................................................................................................................12
8.3. Relocation of defects............................................................................................................................................13
8.4. Drive self-testing..................................................................................................................................................13
9. Auxiliary utility files...................................................................................................................................................14
10. Description of peculiarities in Maxtor drive families ...............................................................................................15
10.1. PROXIMA drive family.....................................................................................................................................15
10.2. RIGEL drive family ...........................................................................................................................................15
10.3. NIKE drive family .............................................................................................................................................16
10.4. ATHENA DSP drive family ..............................................................................................................................17
10.5. ATHENA Poker drive family ............................................................................................................................18
10.6. ROMULUS DSP/Poker drive family.................................................................................................................18
10.7. VULCAN drive family ......................................................................................................................................19
10.8. ARES 64K drive family.....................................................................................................................................19
10.9. N40P drive family..............................................................................................................................................20
10.10. FALCON drive family .....................................................................................................................................21
10.11. CALIPSO drive family ....................................................................................................................................22
11. Data restoration.........................................................................................................................................................23
11.1. Diagnostics during data restoration....................................................................................................................23
11.2. Solution to the translator problem for data recovery .........................................................................................24
1. Purpose
Utilities of PC-3000 software and hardware complex can be used for service maintenance of Maxtor drives.
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;
- removal of data protection password.
We have also reviewed repair methods for electronic boards of the drives as well as causes of specific
malfunctions.
Warning! The success of utilities' usage depends on the level of operator's proficiency. Incorrect application of
algorithms implemented in the utilities may irreversibly damage a drive or prevent restoration of its data.
5. Utility usage
After launching the utility sends a command for reading a drive's ID area and displays a menu for drive family
selection. Drive families are identified in the menu by their factory aliases. For correspondence between family aliases
and models please see section 2.
After drive family selection you'll see a menu for utility start:
Standard mode
Re-read drive ID
Initialization from SA
LDR-file loading
Memory buffer writing
Suppress Reset while utility work
Standard mode starts the utility with complete drive initialization. If the drive is malfunctioning (LDR file is
either not loaded or its loading has not activated the drive firmware) the following error message is output:
Error loading the modules table!
If the DISK(PN=1Fh) module cannot be read the following message will appear:
Error loading configuration module!
Re-read drive ID command updates configuration data in the “MODEL” line. This feature is useful for
diagnostics during drive start.
Initialization from SA command forces partial start of a drive loading firmware from its service data area on
disk. If the drive start succeeds, firmware version should be modified, but that procedure is not automatic. Use the “Re-
read drive ID” command to update the information in the “MODEL” line.
LDR-file loading – accessing that command is recommended without drive initialization in cases, when
firmware data must be restored.
Memory buffer writing command is optional and repeats similar option from the "Work with memory buffer"
menu of the utility. It serves for a more convenient initialization of ATHENA DSP drives, which require for a proper
start loading of a RAM copy from another drive in addition to an LDR file.
Suppress Reset while utility work menu option disables the Reset signal during utility launch and operation.
Resetting is enabled by default.
Standard mode selection in the mode selection menu with subsequent drive initialization brings up the main
menu of the utility:
Logical scanning
Disc firmware zone
Disc ID
Defects table
SELF TEST
Exit
Files of module groups (*.smb) contain all the modules accessible for individual reading plus blank spaces. Those
commands are not used in the methods, which we have developed for restoration of hard drives; however, there is a
certain probability of malfunctions, which might require their use.
SA write test command loads adaptive data and determines correctness of recording to the firmware zone. The
command is implemented for additional drive initialization after loading of an LDR file. Usage of that command is
described in section 7.
Modules repairing command allows restoration of modules with incorrect headers. Usage of that command is
described in section 7.
Translator regeneration command accomplishes creation of translator modules from the factory defects table
(module PN=33h). That command is described in detail in para. 7.3.
Spindle stop command switches a drive to the “sleep” mode. It is used during the Hot Swap procedure.
5.2.3. Disc ID
The option serves for modification of model name and its serial number. These parameters are stored in the
DISK module of the drive firmware (position number 1Fh).
6. Firmware
Firmware of Maxtor drives is subdivided into two parts. The first part of the microcode is stored in masked
ROM inside the processor chip and in Flash ROM. The second part of a drive's firmware is recorded in the firmware
zone. In Maxtor drives it is accessible through logical sectors specifically assigned for that purpose and called “UBA”
(Util Block Addressing, somewhat similar to LBA), automatically converted by the microcode into respective physical
location on disk surface.
PCB firmware consists of two portions: masked ROM in the processor and an external parallel or serial Flash
ROM. Such a scheme has been implemented most likely because masked ROM inside the processor cannot be modified
with sufficient ease. The processor is initialized from the external ROM. If it is missing, the firmware microcode will be
started from ROM inside the processor. A situation is possible, when the microcode inside processor may belong to
another drive family. E.g. CALIPSO drives with disconnected external ROM may be identified as N40P. Maxtor drives
have a “safe mode” jumper. When it is enabled, only firmware stored on the PCB loads but the routine for starting
motors and initialization of firmware portion on disk is skipped. You can identify precisely the version of PCB
firmware. In order to do so enable the “safe mode” jumper and launch the corresponding utility. The “MODEL” line
will show ROM version after the model name.
Drive initialization for an operational condition requires complete replacement of the PCB firmware with the
firmware from the service area on disk. If for any reason the firmware cannot be launched from the service area, its
loading to the drive processor can be forced by starting an LDR file. During the procedure keep in mind that an LDR
file contains just microcode (ROM copy and overlays) but it does not contain the data necessary for drive operation
(tables of defects, adaptive data and other settings). PCB microcode and firmware on disk have different versions. That
difference helps to tell which version is currently being run by the processor. In Poker/Ardent drive families firmware
area contains two programs for drive control: a regular version and a program for factory self test.
Identification of firmware version by labels is complicated with Maxtor drives because manufacturing factories
do not observe strict version numbering rules, which fact leads to quite a lot of incompatible firmware versions with the
same identification codes. Compatibility issues may be caused also by the adaptive parameters for the reading/writing
magnetic heads stored in firmware microcode. However, despite the fact that compatibility cannot be 100% guaranteed,
firmware version can be identified using the following guidelines:
1. Abbreviated values MODEL+HDA+PCBA+UNIQUE. E.g.: 2B020H1110511.
2. Identifying letters, through a comma. E.g.: K,M,B,E.
3. The line in large print over the IDE connector label. E.g.: A4FBA.
Modules map in Maxtor drives contains no names of modules, though some of them still do have names. Such
names are stored in the header of a respective module. Therefore it is impossible to find out the name of a module
without reading its contents. It is possible to introduce unified numbering of modules for various Maxtor drive families,
i.e. the so-called position number (hereinafter PN), that allows convenient identification of specific modules' purpose.
Purposes of the majority of active modules are described in the Table 2.
Copies of the firmware zone are provided for each magnetic head. It is also duplicated using "senior" UBA
locations that are not included into the main map. By default firmware works with all copies since the drive is capable
of operation in a mode using all copies. Reading and writing of module groups serves as a means of accessing a copy of
firmware zone.
The report output by the “Check firmware structure” command (para. 5.2.2.2) contains the following
information:
General information
The section displays selected drive family, minimum and maximum physical cylinders of user's data zone.
DISK configuration module
The module contains drive parameters: number of reading/writing heads and the map of their connections to
the pre-amplifier/commutator chip.
Zone table
Physical location of density zones in a drive.
Data modules
The table with a report on data modules consists of:
- data module number in “#” column;
- PN – position number of the module;
- UBA address of module beginning;
- module length;
- reading flag “Rd”, set to “¥” in case of successful reading or “-” if a module cannot be read;
- “ChkSum” flag set to “¥” in case of successful checksum calculation or “-” in case of calculation error;
- “Id” identification string, beginning with “*” character in case of module containing a table and a line
identifying the table, it begins with “¥” in case of correct data module identification as well as the header read
from the module; if the header contains an error the line will begin with “-” followed by the header actually read
from the module;
- comment that allows to determine the status of modules required for drive operation.
Loadable ROM
The report shows initial UBA, ROM version, identifier, reading status and checksum. Please note that reliable
identification of ROM version is possible using checksum only. It is determined by the fact that the same version
identifier in ROM corresponds to several different actual firmware versions. If checksums of ROM copies in different
drives match, it means that the drives have the same microprogram.
Overlays
The table of report on overlays consists of:
- overlay number in “#” column (a drive has no 18h module);
- UBA address of overlay beginning;
- reading flag “Rd”, set to “¥” in case of successful reading or “-” if a module cannot be read;
- “Id” identification flag set to “¥” in case of identifier match or “-” if the identifier does not match;
- “ChkSum” flag set to “¥” in case of successful checksum calculation or “-” in case of calculation error.
G-List
The section reflects information on the G-List defects table status.
Passwords
Allows reviewing of passwords set in a drive.
- it allows access to firmware zone areas that are not marked in the modules table;
- it allows access to firmware copy using another physical head (or the same head if there is only one present in
a drive).
S.M.A.R.T. attributes can be cleared by recording the module with PN=30h from a drive with «good»
S.M.A.R.T, using the “Writing of modules” command (para. 5.2.2.2.).
Translator is a program that translates physical sectors into logical ones used by an operating system. It is a
general rule for all drives that factory defects are hidden by means of their exclusion from translation. Thus, for
example, if we have a sequence of physical sectors P0,P1,P2,P3, where LBA of physical sector P0 is indicated as L0
and sector P2 is defective, then the sector coordinates will be recorded to the P_LIST in a location inside the zone
specifically devoted to the sectors P0-P3 that we have chosen. The record is made not explicitly as Cyl, Head, Sec, but
in a special notation instead. The counter of defective sectors in the RZTBL table for the zone including the selected
P0-P3 sectors will grow by 1. As a result when an operating system accesses the group of sectors beginning with LBA0
the translator will show the said group as follows:
LBA0 – P0
LBA1 – P1
LBA2 – P3, etc.
Thus we see that sector P2 is excluded from the totality of LBA sectors available to the operating system.
Now let us examine a case, when there is no record indicating that the P2 sector is hidden. It can happen in the
following cases: recording of translator tables from another drive, HotSwap operation or erasure of defects' tables. The
situation will cause sector P2 to appear among the LBA sectors visible for the operating system, but there's more to it!
LBA2 used to be indicated as P3, but now it is shifted to P2! Consequently, all numbers of subsequent sectors will be
shifted by 1. Thus at an attempt to read the sector located after the LBA2 address and containing a directory or a FAT
table the operating system will read not the actual sector containing the directory, but the preceding one containing
erroneous information.
The number of defects in an actual drive may come up to several thousands (or even tens of thousands) sectors.
Therefore actual locations of files, directories and file system tables can be shifted from the expected values by several
hundreds of sectors.
But let us get back to Maxtor. The translator program data are stored in the following modules: U_LIST
(PN=37h), AT_PDL (PN=18h) and RZTBL (PN=78h). A drive forms the translator through an intermediate table with
the PN=33h. The table contains defects in regular notation: cylinder, head, sector. There is an opportunity of compiling
translator tables from that intermediate table using the “Translator regeneration” command. The utility does not show
defects interpreting the translator directly but uses the table instead. Therefore if the translator modules get overwritten
the utility will continue to show the same list of defects as before modification of the translator modules.
Relocation of defects to the G-List table is accomplished using another method. The G-List table does not
exclude sectors from the LBA addressing space. Instead it replaces them using reserved sectors. The reserved space
begins after the highest LBA of a drive. Then the above example will be represented as follows.
L0 – P0
L1 – P1
L2 – reserved sector
L3 – P3, etc.
During the procedure no shift of LBA sectors occurs. Loss of information in the G-List table does not tell on
data restoration in any way. Of course, a situation is possible when a sector hidden by a drive to the G-List could have
contained information critical for functioning of the file system. However, such situation is unlikely and it is
recommended to clear the G-List if it contains any hidden defects, during the process of damaged firmware zone
restoration for data recovery.
Incorrect information recorded to the firmware zone can lead to drive's malfunctions. It may also result from a
problem with electronics or mechanical parts. Diagnostics of such problems is complicated by the fact that
malfunctions of electronics and firmware zone defects can be manifested by the same drive behaviour as incorrect
information in the firmware zone modules.
Firmware zone malfunction may manifest itself as follows:
- The drive is identified correctly but it produces an error for each sector at an attempt to read from disk surface
using LBA (similar situation is possible if a password is set).
- The drive is identified by its factory alias, for example, “Maxtor ATHENA”.
- The drive starts the motor, unparks the heads but does not report on readiness (hangs).
Practically in all of the above cases (except for CALIPSO drive family, see para. 10.9.) factory mode commands
of the drive do not work. In order to switch the drive to a mode, in which factory commands can be started, you'll have
to start it using an LDR file. That can be accomplished using two methods:
1. Drive start without setting the “safe mode” jumper.
That method will work if during the utility launch the drive is identified by its factory alias and the safe mode
jumper is disabled. The essence of that method consists in loading just a part of LDR file modules. The modules at that
must be exactly identical to the original ones in the drive. Step-by-step algorithm:
1. Switch on the power and start the pcmx_dsp.exe or pcmx_pkr.exe utility.
2. In the mode menu select the “LDR-file loading” option.
3. Load an LDR file in the “Modules loader” mode. If the loading procedure succeeds the drive will allow
operations with the firmware zone.
One difference of that method compared to drive switching to safe mode is expressed in the fact that during start
the drive is able to load the defects table and adaptive parameters from the firmware zone. Drive start in safe mode does
not accomplish that. That method will not work if modules having "A" importance are corrupt (see Table 2).
2. Drive start using the “safe mode” jumper setting.
During utility launch in safe mode you'll see the drive's factory alias. The method is recommended in cases, when
the drive "hangs during start" or does not start without the safe mode jumper.
1. Set the “safe mode” jumper (see PCB schemes in section 10).
2. Switch on the power and launch pcmx_dsp.exe or pcmx_pkr.exe utility.
3. If you work with a ROMULUS DSP or Poker hard drive run the “Initialization from SA” command (see para.
5.1.).
4. In the mode menu select the “LDR-file loading” option.
5. Load an LDR file in the “Load ROM and modules”. In case of successful loading the drive will spin up its
motor and report on readiness.
6. In case of ROMULUS DSP hard drives sometimes you have to suppress the Reset signal during utility launch
(see para. 5.1.).
7. Select the “Standard mode” from the mode menu. If during mode entry you see the «Error loading modules
table!» message, it means that an unsuitable LDR file has been loaded, drive hanging has occurred while
loading RAM copy or some problem with electronics/HDA has taken place.
After drive start with the help of an LDR file in order to determine the modules condition you should start the
“Checking of disc FM structure” command (para. 5.2.2.2) and study the report contents carefully using the Table 2. If
the report contains incorrect module headers, their restoration is described in para. 7.2.
Prior to modules repair you should make sure that sectors recording to the firmware area is performed correctly.
In fact drive start using an LDR file firmware initialization is accomplished incompletely leading to errors in its
operation. In order to verify recording correctness you should run the "Test firmware zone recording" command (para.
5.2.2.2). The test consists of two parts: loading of adaptive data from module PN=1Eh and testing of the drive’s ability
to write to firmware zone by recording one sector with randomly selected contents to an unused portion of firmware
zone called “swap1”. If the recording test succeeds the following message is displayed: «Record offset: 0», which
means correctness of recording operations in the firmware zone.
Let us consider the problems which may arise during the test. If the module PN=1Eh is damaged the routine for
loading the adaptive data will abort with an error, which definitely means impossibility of correct recording to the
firmware zone. If a record offset occurs, operations over firmware are also impossible; that may be caused by drive
malfunction during the adaptive data loading stage.
Warning! Save all modules from a drive prior to recording anything to it. That requirement is determined by unstable
drive behavior during recording to its firmware zone. It means that in case of problems with adaptive data one module
can be written over another! That will lead to loss of firmware data, which will be unrecoverable, if the data hasn't been
saved!
The task of translator restoration appears when its tables contain incorrect data or unreadable sectors. In such
situation it is possible to create translator tables on the basis of a pivot defects table (module PN=33h) provided it is
intact.
Translator recalculation is started by the “Translator regeneration” command (para. 5.2.2.2.). The operation
may take quite a long time. Everything depends upon the number of defects in the pivot table. The resulting translator
will not contain the defects relocated in the service zone (therefore the operation is blocked when relocated defects are
present in the firmware zone). All tracks hidden using RZTBL will also be transferred to AT_PDL; theoretically it may
cause a discrepancy between the original and recalculated translator. We haven’t encountered such discrepancies in
practice.
Firmware zone condition can be evaluated using the test provided in the utility: SA surface checking (please
see para. 5.2.2.2). Testing is performed in UBA notation. Discovered defective sectors are added to a report. Only areas
containing groups of modules are tested.
1 Complete list of correspondence between position numbers (PN) and modules is summarized in the Table 2.
Technical support: eng_support @acelab.ru
(8632) 78-50-30, 78-50-40
12 www.acelab.ru
Ɋɋ-3000 £ "MAXTOR: D536DX, D541X, Diamond Max VL40, D540-4D, D531X, Diamond Max Plus 60,
¤ ACELab D541X, Fireball 3, Diamond Max Plus 8, Diamond Max Plus 16, Diamond Max Plus 9"
The “Logical scanning” command starts drive surface test utilizing logical parameters (para. 5.2.1).
Test parameters:
Initial LBA position: 0
Final LBA position: xxxxxxxx
Reversive scanning: No
Number of passes: 3
Perform writing test: No
Verif. instead of reading: Yes
Put defects to: P-LIST
Initial and final LBA position parameters determine the test range.
Reversive scanning defines testing direction. Switching is performed using the [Y] key for "Yes" and [N] for
"No" or [Space]. A drive reads data ahead therefore direct scanning is somewhat faster than reverse.
Number of passes parameter determines the number of complete test passes from the initial to final LBA. Input
range is from 1 to 100.
Writing can be switched on in the Perform writing 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!
Put defects to P-LIST or G-LIST. Switching is accomplished using the [Space] key.
Upon completion of the surface scanning procedure, the table of all discovered logical defects in LBA notation
appears on the screen. Pressing [Enter] key converts 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.
The utility allows hiding defects to the P-List factory defects table as well as to user's G-List table.
P-List defects table can be reviewed using the “View P-List” command (para. 5.2.4). Defects are output from the
pivot defects table (PN=33h) and not restored from the respective translation tables. . It means that if the translation
tables are overwritten with tables from another drive or modified otherwise, the "View P-List" command will still
display the same list of defects as it used to prior to recording and the list will not correspond to the defects actually
relocated in the drive. The same inconsistency is observed when module PN=33h is recorded by copying from another
drive. However, if the utility tools are used for operations with the defects’ tables the pivot table of defects will be
modified correctly.
Some Maxtor drives have relocated defects within the firmware zone. In that case resetting the tables of defects
will be disabled because the utility does not provide for firmware zone recording taking into account the relocated
defects.
G-List defects table can be reviewed using the “View G-List” command (para. 5.2.4).
Defects search is accomplished using the “Logical scanning” command of the utility or with the help of
Defectoscope software (“Import from Defectoscope” command). Discovered defects can be transferred either to P-List
or G-List at user's discretion.
Maxtor drives allow hiding of whole tracks as well as track parts, i.e. several successive sectors added together
as one defect record saving the table space. Grouping of successive defects is performed by the drive automatically.
Maxtor drives automatically relocate defective sectors to G-List, and the “Defects table” - “Move G-List to P-
List” command sequence transfers those defective sectors to P-List, the procedure simultaneously clears G-List. The
operation is performed by the drive itself, the utility just issues the command, therefore if the transfer of defects ends in
an error, it means that the defects stored in G-List cannot be added to P-List.
This version of the utility allows running factory self-testing routine in Maxtor DSP drives; the feature is not
implemented for Poker and Ardent drive families yet. Upon self-testing a drive recalculates its adaptive parameters,
hides defective sectors and resets S.M.A.R.T. attributes to factory defaults.
A drive is switched to self-testing mode by the Start SelfScan command (para. 5.2.5), whereupon, during
subsequent power-on a 30 sec. pause will be made before the drive starts self-testing (drive LED will indicate the
running procedure by blinking at 2Hz frequency). If during those 30 seconds you issue a reset or drive ID reading
command, the drive will enter its operational mode until next power-off/on.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 13
"MAXTOR: D536DX, D541X, Diamond Max VL40, D540-4D, D531X, Diamond Max Plus 60, Ɋɋ-3000 £
"PC-A450AA" "PC-A307AA" "PC-A272AA" "PC-A205AA" ¤ ACELab
Drive LED will be blinking with varied frequency while performing the tests.
The utility can display progress of the self-testing procedure. To accomplish that you should issue the View
SelfScan state command (para. 5.2.5) for an already connected drive with on-going testing procedure. The window will
show current status: test number, cylinder, etc. Please note, that a connected drive does not respond to utility commands
during on-going self-testing process, utility launch in that case may cause self-testing failure.
As a summary we can suggest two methods for indication of self-testing progress with monitoring of a drive
connected or not connected to a PC and powered by an independent supply.
1. Procedure of drive start with status monitoring.
- SELF TEST - Start SelfScan
- Without leaving the utility and with IDE cable connected to the drive, switch its power off and on.
- Start View SelfScan state, then the self-testing progress report will be displayed on-screen.
2. Procedure of self-testing using an independent power supply without a connection to PC.
- SELF TEST - Start SelfScan
- Disconnect the drive and connect it to an independent power supply unit.
- Since PCBs in Maxtor drives have no LEDs you can connect an external LED as shown in figure 1.
Fig. 1. Connection of external LED for monitoring the drive self-testing process.
We have observed different probability of successful self-testing completion with a prior resetting of the defects’
tables and without it. Therefore we advise to clear the tables of defects before running the test.
Successful completion of self-testing will be indicated by the drive LED blinking regularly at 1 Hz, failure and
emergency exit from the testing procedure are indicated by much faster blinking – at approximately 10 Hz. Drive
hanging during self-testing is manifested by absence of changes in its condition for a long (for example, half an hour)
time and lack of LED indication. The LED in such case may be on or off, but it won't blink.
Warning! In some cases when self-testing terminates with a fatal error, firmware zone is considerably damaged
(modules essential for drive operation are missing), therefore you must always backup the firmware zone before
beginning self-testing procedure.
Warning! Self-testing will not start correctly if a drive is started using an LDR file.
Warning! All user data will be destroyed during the self-testing procedure.
MAXTOR
2 LUCENT 1181K 3
LUCENT 1
MS353B3
1 1
2 1
1
1
1. RDS035L03 3. 20 MHz
2. 78L08A 4. M29F102
Jumper Configuration
Master Slave Safe mode
The format of G-List table in that drive family is different from the usual. Therefore the information about
defects displayed by the “View G-List” command will be not quite correct. However, defects will be appended to G-
List correctly. Automatic restoration of the G-list module will also work correctly.
2
DSP
2
D741667APGF
AGERE 1
MS453 1
1 1
1
1
1. RDS035L03
2. 20 MHz
Jumper Configuration
Master Slave Safe mode
1
3 1 SH6770C
1
1
1 1
HY57V161610D
2
DSP
D741864CPGF
LUCENT
2
1. B3185
2. 78L08A
3. M29F102BB
Jumper Configuration
Master Slave Safe mode
One quite frequent peculiarity of drives belonging to the family is demonstrated by their behaviour in case of P-
List malfunctions, when after motor spin-up and removing the heads from parking area a drive turns the spindle motor
off but "forgets" to park the heads. The problem can be identified by a typical sound heard when the motor is turned
off. Such drives should be restored using the method of loading an LDR file in safe mode (see para. 7.1). Then you
should perform diagnostics of problems in the firmware zone, save firmware modules and restore the drive translator
(para. 11.2).
1
3 1 SH6770C
1
1
1 1
48LC1M16A1
2
DSP
D741667APGF
AGERE
2 MS453
1. B3185 3. M29F102BB
2. 78L08A
Jumper Configuration
Master Slave Safe mode
Fig. 5. External view of control board in MAXTOR ATHENA ATA2-PLUS drive family.
Appendix 1 hereto contains a circuit diagram for connection of motor control chip in PCBs of ATHENA DSP
drives.
1
1 SH6770C
1
1
1 1
HY57V
161610DTC-6
1
2
POKER C6
040108200
4370J2
0224S
4849943
1. B3185
2. 78L08A
Jumper Configuration
Master Slave Safe mode
Fig. 6 External view of controller board in MAXTOR ATHENA Poker-based drive family.
10.6. ROMULUS DSP/Poker drive family
Malfunction of one of the heads in drives belonging to that family causes knocking sounds while loading an
LDR file or during calibration at utility launch.
2
DSP
3
D741667DPGF
AGERE 1
MS453 1
1 2 1
1
1
1. RDS035L03 3. 20 MHz
2. A172E
Jumper Configuration
Master Slave Safe mode
040405000
2 D741667CPGF 4
CC-15AE72W
AGERE 1
MS453 1
2 1
3
1
1
1. PHN210T
2. PHN207 5. M29F102BB
3. A171B
Jumper Configuration
Master Slave Safe mode
"L" letter in model name indicates that a fluid dynamic bearing was used, for example, 2F040L0. "J" letter
means that a ball bearing was used, for example, 2F040J0.
With that drive family Maxtor designers began to use two firmware zones with similar structure but totally
different purposes. The main firmware zone is used during normal drive operation. It contains all the modules with
correct data required for drive operation.
Table of correspondence between starting modes and firmware versions in ARES 64K drives.
User mode of operation ROM loader mode Self Test mode
VAM51JJ0 VAM52JaZ VBM51J80
1
3 1 SH6770C
1
1
1 1
HY57V161610D
2
Poker
040111600
LUCENT
2
1. B3185 3. M29F102BB
2. 78L08A
Jumper Configuration
Master Slave Safe mode
Fig. 9. External view of controller board in MAXTOR ARES 64K drive family.
In this drive family ST25P10V6 external Flash ROM with serial access is used.
Quite numerous existing ROM versions complicate the issue of their compatibility making it difficult to pick a
matching board. ROM chip can be soldered to a new board since it does not have too many pins so the procedure can
be performed fairly quickly. Such variety of versions results from the fact that program microcode, namely, overlay 6
and ROM chip on PCB contain built-in adaptive parameters for the reading/writing heads. When modified heads are
installed during the manufacturing process, the whole firmware version has to be changed. That produces numerous
versions and as a result the microcode in the masked ROM of the drive processor ceases to match those versions.
Consequently it has to be supplemented with external ROM containing the necessary modifications to the adaptive data
and firmware version. That situation also influences drive starting with the help of an LDR file. The utility may start a
drive using another firmware version, but the adaptive data of that version may not match the drive. Usually it is
practically impossible to read the firmware if the adaptive data built-in into the microcode does not match the drive,
although running a loader file with suitable adaptive data makes everything work fine. Compatibility of adaptive data
can be controlled using the ROM version on PCB output by the drive in “safe mode”.
This family is characterized by peculiar P-List corruption. Besides the header one or several sectors of P-List
become BAD. After header restoration and recalculation of checksum the drive is still unable to start and, moreover, it
is impossible to make it record anything else to its firmware zone.
1 3
2
2125G
W981616BH-6
Ardent C5-C1
040110100
ARDENT-C5C1
-790UK
023S
4963143
1. ST25P10V6
2. SH6782B
3. FDS9431A
Jumper Configuration
Master Slave Safe mode
Fig. 10. External view of controller board in MAXTOR N40P drive family.
LUCENT
MS353B3
2 2
3
MAXTOR
LUCENT 1181K
1. 2DPFS20V 3. M29F102BB
2. FDS9431A 4. 20 MHz
Jumper Configuration
Master Slave Safe mode
Fig. 11. External view of controller board in MAXTOR FALCON drive family.
Just like in N40P drive family here external Flash ROM with serial access is used.
For this family a specific malfunction is typical, when one of magnetic heads goes out of order. As a result such
drive is identified as Maxtor CALIPSO, but allows reading/writing of firmware zone without an LDR file and all the
modules remain intact. The said effect is caused by the fact that during start the drive does not find one of the heads
included into its table. Therefore the firmware zone mapped for a different number of heads cannot be correctly
processed by the drive control microcode. Such drives produce slight knocking sound if a calibration command is
issued!
The following problem is possible with drives from that family: incorrect recording during an attempt to restore
a module will erase some modules having A or B importance. Consequently the drive’s firmware during the next start
will be unable to load the essential modules from the main firmware zone and it will have to switch to the alternative
zone. Therefore the modules prove to be intact after restart, but those are in fact absolutely different modules. That
condition cannot be repaired using the current version of the utility.
The “safe mode” jumper position is yet unknown for the Serial ATA modification of CALIPSO drive family.
That family uses two formats of the G-List table of defects. The utility cannot recognize table format
automatically and thus it is set up for the newest format. The older format will be displayed incorrectly. In order to view
G-List in the older format you should enter the utility having selected, for example, N40P.
LUCENT
MS353B3
2 2
MAXTOR
LUCENT 1181K
4 3
1. 2DPFS20V 3. 25P10V6
2. RDS035L03 4. 20 MHz
Jumper Configuration
Master Slave Safe mode
Fig. 12. External view of controller board in MAXTOR CALIPSO drive family.
In very rare cases a drive may not start or it may hang at power-up when its G-List contains incorrect information
under a correct header and valid checksum. You can view the G-List with an LDR file loaded. An attempt to reset (the
record to the firmware zone should be correct) G-List in that mode will not achieve a proper result as the replacement
LBA will be defined as –1. Recording a clear G-List copied from another drive of that family with the same capacity
represents a more accurate method.
There is a rather frequent situation when translator modules have correct headers and checksums and all other
essential modules are in order, but the drive still does not function using its logical parameters. At present two reasons
for such condition are known:
The first and quite rare cause occurs in CALIPSO drives when one of drive heads gets physically disconnected – the
drive translator refuses to load. That happens because the RZTBL (PN=78h) module contains the number of heads.
Diagnostics of that malfunction is described in more detail in para. 10.11.
The second variant of that situation is encountered practically in all Maxtor drives supported by the PC-3000
complex. It results from occasional recording of random or pseudo-random data to the translator table fields (data from
one module can be recorded to another). Module headers and checksums at that may remain correct. Automatic
restoration of modules in such a situation will not help restore the drive.
In order to perform diagnostics in that situation you should record to the malfunctioning drive translator modules
(PN=37h, PN=18h and PN=78h) copied from an operational drive with the same capacity. Prior to the operation save
all modules from firmware zone, especially module 33 and ensure that the firmware zone has no relocated defects. The
suggested method of diagnostics is not applicable if the firmware zone contains hidden defects. If after recording of the
translator modules the drive starts normally and can be accessed using its logical parameters, it means that the problem
resulted exactly from invalid data in the modules.
If the module PN=33 is intact (the utility will output a list of defects upon P-List query) you can perform the
“Translator recalculation” procedure (see para. 5.2.2.2 and para. 7.3).
CT
u503A u503B
8 MOTA
7 1 6
5 3
2
CT
4
A
MOTB
u504A u504B B
8 C
7 1 6
5 3
SPINDLE MOTOR
2
4
MOTC
u505A u505B
8 SPSNS
7 1 6
5 3
R517
R518
2
4 R519
5V
R520
Q501
2
1 25 C6
$PIN0 $PIN24 3.3V
2 $PIN1 $PIN25 26
3 $PIN2 $PIN26 27 u302 (48) IRFD110 3.3V
4 $PIN3 $PIN27 28 1 (BSP 100)
5 $PIN4 $PIN28 29
6 30 R3
$PIN5 $PIN29 U302(25)
3
7 31
A 8
$PIN6
$PIN7
$PIN30
$PIN31 32 8 7 6 5 A
9 $PIN8 $PIN32 33 33mkFx 16V C506
10 34 R2 +
$PIN9 $PIN33 R503 C01
11 $PIN10 $PIN34 35
R515 12 36 2 4
$PIN11 $PIN35
DSP (57)
DSP (148)
13 $PIN12 $PIN36 37
14 38 C5 C3
$PIN13 $PIN37 1 3
15 $PIN14 $PIN38 39
C512 16 40 7 8
$PIN15 $PIN39
17 $PIN16 $PIN40 41
R305 18 42 REGULATOR 3.3V IRF7101
$PIN17 $PIN41 u506A
19 $PIN18 $PIN42 43
20 $PIN19 $PIN43 44 2 (W241)
21 $PIN20 $PIN44 45
22 46 C2
$PIN21 $PIN45 1
23 $PIN22 $PIN46 47 12V
24 48 C1
$PIN23 $PIN47 C102 + 15 mkFx 25V
U500
DSP (119)
DSP (123)
DSP (121)
u501A 7 8 7 8
DSP (98) u502A
DSP (103)
2 2
R513
1 1
J4 RADIX
1 2 34 5 5 6 5 6
u501B u502B
8V
vr200 4 4
VCM- VCM+
3 3
12V 8 IN OUT 1 J2(9)
2 C10
C203 COM R207 WDN L1
3 COM
6 COM
7 COM
78L08A 1 2
J2
Title
REGULATOR 8V MAXTOR ATHENA ATA2-PLUS motors controller
A
A
R
ROM
R512 KT C C FCOMM 8 7 6 5
1Om Voice Coil 25P10V6
KT
R511
1Om
Motor C209 R
Ardent (4) Ardent (8) 1 S Vcc 8
+3.3V
1Om 1Om 1Om 1Om C401
Ardent (212)
R510 2 7
VCM- Ardent (128) Q HOLD
1Om U401
R508 R504 VCMI 3 6
VCM+ +3.3V W C Ardent (130)
1Om
C210 R
R06 4 5 1 2 3 4
GND D Ardent (138)
1Om
U401
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
SPINDLE MOTOR +1.7V
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
49 32 c
Ardent (206)
49 32
Ardent (87)
Ardent (67)
Ardent (29)
Ardent (26)
Ardent (7)
R
Ardent (155)
Ardent (144)
Ardent (137)
Ardent (145)
Ardent (171)
Ardent (174)
50 50 31 31
R
51 30 C
C508 51 30 +12V
52 52 29 29
C
BUX 53 28 C C C C C C C C C C C C
53 28
54
SMOOTH 27
MOT MOT MOT CT +12V 54 L7250E 1.0 27
8 7 6 5
C B A +12V 55 55 26 26
R
56 56 25 25
R C
57 24 C S500 Q400 IR230M
57 24
58 58 23 23
+1.7V
59 22 C505
59 22
Shock Sensor
R229 R230 R231 60 21
60 21 Ardent (5)
1 2 3 4 5,6,7,8
61 61 20 20
A C Q400 A
62 62 19 19
Ardent (170) 4
63 18 R 2k
63 18 Ardent (211)
Control Line C
2 1,2,3
64 64 17 17
+3.3V
10
11
12
13
14
15
16
1
9
C501 C507
C
10
11
12
13
14
15
16
8 7 6 5 Q501
1
9
REGULATOR +1.7V C
+5V
1 2 3
Q500 1
C R
+12V 3 2 +5V
C506 Q501
1 2 3 4 R513 R
1Om 1Om R516 REGULATOR +3.3V
C
+3.3V
C511
Q500 +3.3V
Ardent (114)
Ardent (184)
Ardent (157)
Control Line
Ardent (150)
Ardent (102)
Ardent (166)
Ardent (190)
Ardent (203)
Ardent (126)
Ardent (154)
Ardent (12)
Ardent (58)
Ardent (44)
Ardent (89)
Ardent (71)
Ardent (27)
Ardent (79)
5 4 C519
R 1K
6 3
+5V C C C C C C C C C C C C C C C C
C513 C
7 2
R 8.2k
L500
IBM
Contents
1. Structure of drive families.............................................................................................................................................2
2. Utility command menu..................................................................................................................................................2
2.1. Launching the utility ..............................................................................................................................................2
2.2. Utility usage ...........................................................................................................................................................3
2.2.1. Servo test, surface scanning ............................................................................................................................3
2.2.2. Firmware data .................................................................................................................................................3
2.2.2.1. Work with memory ..................................................................................................................................4
2.2.2.2. Work with firmware zone ........................................................................................................................4
2.2.2.3. “Modify configuration” command ...........................................................................................................7
2.2.2.4. “Run an LDR file” command...................................................................................................................8
2.2.2.5. Translator recalculation............................................................................................................................8
2.2.2.6. Spindle stop..............................................................................................................................................8
2.2.2.7. Enable write cache ...................................................................................................................................8
2.2.3. Drive ID ..........................................................................................................................................................9
2.2.4. Formatting.......................................................................................................................................................9
2.2.5. Logical scanning .............................................................................................................................................9
2.2.6. S.M.A.R.T. table .............................................................................................................................................9
2.2.7. Defects table..................................................................................................................................................10
2.2.8. Automatic mode............................................................................................................................................10
2.2.9. SELFSCAN...................................................................................................................................................10
3. Drive firmware............................................................................................................................................................12
3.1. Structure of IBM HDD firmware.........................................................................................................................12
3.2. Compatibility of electronics printed circuit boards..............................................................................................13
3.3. Description of structure and methods of firmware zone access in case of malfunctions.....................................13
3.4. Critical modules for drive data.............................................................................................................................16
4. Description of IBM drive families ..............................................................................................................................17
4.1. Construction peculiarities of 22GXP(DJNA7), 34GXP(DPTA7), and 37GP(DPTA5) drive families ...............17
4.2. Construction peculiarities of 40GV(DTLA5), 75GXP(DTLA7), 60GXP(AVER), and 120GXP(AVVA) drive
families........................................................................................................................................................................18
4.3. Software repair.....................................................................................................................................................20
4.3.1. Identification and relocation of defects in user's area ...................................................................................20
4.3.2. Malfunctions of “Open modules' table cannot be read!” type ......................................................................20
4.4. Peculiarities of software restoration.....................................................................................................................21
5. Auxiliary utility files for IBM drives ..........................................................................................................................21
6. Malfunctions of electronics boards in IBM drives......................................................................................................22
7. Electric circuit diagram...............................................................................................................................................22
7.1. Elements layout....................................................................................................................................................22
7.2. Electric circuit......................................................................................................................................................23
At the start the utility offers the choice between two available initialization modes: “Standard” and “By
Default”. When started in the standard mode the utility reads certain parameters from the drive and initializes its
internal structures accordingly. A launch in the default mode forces the utility to act as though the drive does not
respond to its queries; however, the utility skips the delay allocated for awaiting response. Actually it does not access
the drive in that mode. That may be useful in cases of damaged drive’s firmware, when a drive does not respond to
access attempts or fails beginning to knock.
Let us review the “Standard” mode of utility launch in detail (the “By Default” launch respectively will be
accompanied by all the error messages mentioned below and pertaining to collection of information about the drive).
The utility reads drive ID during launch in order to determine its logical parameters. If a drive returns an error
the following message will be output:
Unidentified logical drive parameters
Default values used – “Final LBA” = 1000
At that the information about model name returned in the drive ID will appear in the “MODEL:” top line of the utility
window.
Then you'll be prompted to select a model in order to define the number of physically present heads for further work.
After that the utility will be adjusted to the connected drive during the following sequence:
1. reading of NV-RAM to identify some internal drive parameters. In case of an error the following message
appears: “Error reading NV-RAM. Using default parameters”.
2. reading of modules table (“USAG”). In case of an error the following message appears: “Modules table
cannot be read.Do continue?”
3. reading of the so-called "open modules table" (a synthetic table returned by a drive in case of its correct
initialization). In case of an error the following message appears: “Open modules table cannot be read”.
4. reading of zone allocation module (“ZONE”). In case of an error the following message appears: “Error
reading zone allocation module. Default zone allocation used”. If a module has been read successfully, the number of
drive heads will be adjusted accordingly. If the user's choice (selected model) does not match the estimated number the
smallest figure is assumed and the following message appears: “Model adjusted according to the number of physically
present heads. Press [Enter]”.
Please see further possible causes of malfunctions resulting in the above error messages as well as methods of their
elimination.
Servo test and Surface scanning, unlike utilities for other drive families do not accomplish hiding and relocation of
defects since this version of utilities has no automatic algorithm for hiding corrupted areas. Presence of those menu
items in the utility is determined by the task of telling heads that have problems from those that have none. Thus it is
not recommended to use those commands if a drive has just insignificant damage. After servo test the drive will be
unable to read from the surface in LBA mode, therefore subsequent factory formatting is required.
Spindle stop
Enable write cache1
1 This menu item is available only in utilities for DTLA, AVER, and AVVA drive models.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
4 www.acelab.ru
Ɋɋ-3000 £
¤ ACELab "IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP
Selection of the “Factory copy” mode provides access to modules recorded at the manufacturing factory to a
separate track unused by the drive.
WARNING! Only modules listed in “USAG” will be accessible in that mode. Besides, the SRVM module present
in that copy will differ from its actually operating counterpart as regards its adaptive part. Apparently the
difference is caused by final drive calibration performed after recording of the “factory copy”.
Load USAG command allows loading to the utility's memory of a selected modules’ directory without
recording it to a disk. That feature is useful while estimating the condition of a drive with corrupt “USAG” module.
Re-read module tables command loads USAG and a table of open modules. That feature may be useful for
utility readjustment for changes introduced to the firmware zone by user or a launched LDR file (no need to leave the
utility and start it again in cases when firmware zone is modified).
Cleaning of logs (ELG1, EVLG)command allows to clear a drive's error log (in 60GXP and 120GXP models
EVLG event log is also cleared). The feature is useful in cases of zero drive head overcommutation. It is necessary to
perform Clear SMART after finishing of this operation.
Clear FLYH command (derived from Fly Head) allows clearing the mechanical hits log in a drive. The log is
present in all drives described in this manual from 120 GXP (IC35AVVA) to earlier models.
Restore firmware zone command attempts to restore unreadable areas in drive's firmware zone. That menu
item is necessitated by the fact that firmware zone in IBM drives is scattered, i.e. there are areas between the modules,
which are not included into the module tables. Such areas mostly are either not utilized by the drive altogether or
contain SELFSCAN modules. At the same time a drive reads the firmware track to RAM completely during
initialization. Consequently, an attempt of initialization will end in error, if the track contains unreadable areas. Besides,
in cases of data restoration, when the most of own drive service data must be restored, there might arise a situation
when a part of some module essential for such data cannot be read, for example, in the final part containing no
information. In that case restoration will allow obtaining the required module with empty space instead of its previously
inaccessible area. And in some cases the actual data from the area will be restored, too. That menu item processes the
whole firmware in a drive, which is slower than reading modules in "IRE" mode (please, see "Ignore reading error"),
but its advantage is in the ability to attempt reading of an inaccessible sector using physical parameters during
restoration (at user's option). One more application aspect of that operation regards overcommutation of a drive's
system head (please see details in the "Modify configuration" section).
That menu item brings up a dialog window, where you can select drive heads for restoration, operation type
(restoration, clearing or extensive clearing), and number of retries using logical and physical parameters. If you select
"clear" or “extensive clear” operation type or 0 of retries, the firmware data area will be filled with 77h code. Selection
of the “extensive clear” menu item forces clearing in the style adopted in 1.07 version of the utilities. It is slightly safer
when a drive is damaged, but takes more time than plain clear operation. However, the statistics proves that it is
frequently necessary in order to restore the readability of firmware area. Thus we recommend using the “extensive
clear” option only in cases, when selection of common clearing procedure had no desired effect.
WARNING! Performing of this part can be potentially dangerous for HDD! If you have choosen Recovery and
HDD have a problem with heads the execution of this command can caused the damaging of service area or incorrect
writing into the correct sectors of service area. Moreover if you have choosen the Cleaning or Extended cleaning, the
microprogram can be erased. Therefore before performing of this operation you should save the maximum of
modules from all disc surfaces of HDD. For this can be useful paragraphs Load USAG (load into the utility table of
modules from the file ~USAG.rpm from compatible HDD) and Ignore reading error (allows while reading to get
maximum information of module, even if it has unreadable areas ). Remember that microprogram has great amount of
special information about this HDD and simple substitution of it by another HDD can caused inability to work of
repairing drive.
Create an LDR file menu item allows saving drive's firmware to a file in IBM LDR format. After selection of
that menu item you'll be prompted to enter a name for the LDR file. Since the file size is limited, tables of defects
(PSHT, RDMT) are saved in a separate file in LDR format under the same name but with ".dld" extension (i.e. in order
to restore original modules using the file you should rename it to *.ldr). Besides, another file with the same name and
".ldl" extension is created containing information about the drive and a list of modules recorded to the LDR file. If any
modules cannot be read, they will be skipped with subsequent listing of such cases in a report after the operation is
complete.
WARNING! The loader thus generated will differ from the original one since it will contain modules specific for
the individual drive and a complete NV-RAM block. If you wish to use the loader for firmware updating in
another drive you should copy the “native” SRVM module and NV-RAM of that drive after using the loader.
Security subsystem menu item allows viewing information about user passwords and their resetting, i.e.
removal of passwords opening access to drive's data. The "Setup" item serves for modification of password module
location in a drive's memory. The address is presumably the same for the whole drive family, though it is likely that it
may differ in some firmware version.
Beginning with 40GV drive family some firmware versions employ an encryption mechanism for the
password module. Therefore the password reviewing routine will display an encrypted block of security module, which
cannot be used as password text.
Besides, beginning with 60GXP drive family password-protected drives block factory mode commands.
Therefore the algorithm of password removal becomes somewhat more complicated. During the process you'll have to
short-circuit data pins of NV-RAM (No. 5 and 6) to ensure drive's report on readiness without initialization of its
security subsystem. The said procedure is implemented in Wizard style, which allows to skip its detailed description
here.
likely that after their recording from another drive you may need to repeat the algorithm procedure again. Here belong
modules ZONE, SRVM, MLBA, and CNSL. A situation is possible, when none of modules can be read (when the
system head is damaged). In that case the LDR file would contain only corrected NV-RAM. Then you should perform
steps from 2 through 5, record to the drive corresponding firmware from a database or as modules, and switch power
supply to the drive off and on. Then perform the complete overcommutation procedure again from the first step.
“Head map change” command allows modification of heads mapping only in NV-RAM without readjustment
of other drive structures. Thus it is possible to define heads mapping filled, for example, with just one number using the
dialog box produced by the command. That may be useful for recovery of drives with corrupted sectors in firmware
area.
“Switch SA access” command inverts the high bit in the lower byte identifying firmware version in NV-RAM.
The operation grants access to drive modules in cases, when firmware area is corrupted so that during regular start such
drives either hang or start knocking with the heads. Previously for the same purpose it was recommended to find NV-
RAM of a similar, though not the same NV-RAM version containing heads’ map identical to the current NV-RAM.
The command functions as a trigger, i.e. running it twice successively will produce the original NV-RAM.
Isolate zones” command accomplishes isolation of zones in the beginning of a drive only. Its selection brings
up a dialog window, where you'll have to input the number of the first operational zone of the drive. Previously isolated
zones will be skipped. After successful performance of that operation you'll need to set the correct MaxLBA value
separately using the SetMaxLBA command in the PC3000AT utility. The new MaxLBA can be obtained with either of
two methods:
- calculate the number to deduct from the current MaxLBA taking into account the isolated zones;
- perform logical scanning and assume as new MaxLBA the value followed by continuous IDNF error zone.
Activation of drive zones is performed separately by means of recording a respective ZONE module in the "Write
modules" dialog; then you'll have to restore correct MaxLBA in the PC3000AT utility. The utility will display the
default MaxLBA value in the respective dialog window. Thus you may just confirm the value displayed by the utility
without any modifications.
WARNING! The first 6 characters in P - Code should never be changed, i.e. TX2DA50A can be replaced with
TX2DA59A, but not TX2DA69A.
disabling the write-cache. Technically you could simply clear G-List using the current utility version, but we believed
that you might wish to preserve the original G-List of the drive sent for repair in order to facilitate a more complete user
data recovery.
2.2.3. Drive ID
Drive ID command allows to modify the information returned by a drive in response to drive ID request (drive
ID is read during PC loading procedure performed by system BIOS) and compare identification records from the
firmware zone and the drive labels.
2.2.4. Formatting
Formatting command performs translator recalculation and quick LBA surface overwriting using random code
from the sector buffer. The procedure ends with an error if it encounters a seriously damaged area. In order to perform
the formatting procedure you should enter the initial value and the number of LBA sectors in the range to be formatted.
Besides, you can define the utility behavior in case of errors. The following variants are possible:
- stop formatting when an error is encountered;
- skip several sectors (their number is entered in a dialog window by the user) when an error is encountered and
continue to a previously defined limit.
The need for the second mode is predetermined by the fact that 60GXP and newer models require completion of
formatting at the last accessible LBA from the user's data zone for normal subsequent work with such data.
Upon completion of formatting a report will be output listing zones skipped because of errors. Then logical
scanning of those zones with writing on must be performed.
Besides, that menu item allows to detect zones with considerably damaged servo fields, which can be hidden
then into "cylinder table" (please see "defects table”).
WARNING! Because of an error in firmware of IBM drives the formatting command leaves some LBA at disk
end unformatted. For safety reasons we did not modify the utility algorithm though it could enable the utility to
define block range greater than the one entered by the user. Thus after formatting you will need to add the final
range of a drive (2-3 tracks per head) using logical parameters.
WARNING! The command forces formatting of sectors in accordance with P-List, but actual recording is
performed over the whole disk surface with the exception of cylinders listed in the SRVM table, thus formatting
errors (corrupted servo fields, circular scratches, etc.) cannot be excluded by appending those defects to P-List.
As a last resort the corrupted area can only be isolated from the user data space by running the formatting
procedure manually and beginning with a location outside the corrupted area after the defects are added to P-
List. In such cases it is recommended to append to P-List the preceding and the following track in addition to
the one with actually damaged formatting.
S.M.A.R.T. table menu item allows to view the values of S.M.A.R.T. parameters, load them from a model
module, reset S.M.A.R.T. values1, and control thermal mode of head and disk assembly (HDA). You may also monitor
the changes of temperature in the process of random positioning. The "latency period" parameter controls the delay
between positioning to random LBA.
1 Information on SMART reset command has been kindly provided by Lev Koriagin (hdd3k@cef.spbstu.ru).
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 9
Ɋɋ-3000 £
"IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP ¤ ACELab
Automatic mode command allows running test sequences (formatting, translator recalculation, scanning using
physical parameters, logical scanning and servo test) in arbitrary order with output of results. Automatic operation with
IBM drives does not differ from work with other drive types (see, for example, description for Fujitsu HDDs).
2.2.9. SELFSCAN
The SELFSCAN menu contains elements for control and status review of the so-called “SELFSCAN” routine.
SELFSCAN is a part of factory firmware stored in a drive and designed for drive self-testing and self-adjustment. In
IBM drives SELFSCAN performs adjustment of adaptive drive parameters and multi-pass surface scanning of the disks
with defects relocation. At that during the first pass the drive scans its firmware zone, during the second pass it scans
the user's data area and adds defects to the cylinder table, the third pass is used for scanning with defects entry into P-
List.
SELFSCAN menu consists of the following options:
Start SELFSCAN
Stop SELFSCAN
View state
View result
Read SELFSCAN module
Write SELFSCAN module
View MFG parameters
View HLRC data
View SRST dump table parameters
Read SELFSCAN log
Repair SELFSCAN module
Start SELFSCAN menu item serves for initialization of the SELFSCAN routine. After the initialization you
should connect the drive to an independent power supply and wait for the procedure completion. While waiting it is
possible to view SELFSCAN state – i.e. drive registers – in order to estimate information on the progress of
SELFSCAN.
WARNING! The command starting the SELFSCAN routine will automatically clear P-List and G-List, ELG1
and EVLG logs and reset SMART parameters.
WARNING! It is essentially important that you do not disconnect the power to the drive throughout the whole
procedure of SELFSCAN. If the SELFSCAN procedure is interrupted by a power shutoff, after the next power-
on SELFSCAN will restart with incorrect parameters since some of them are stored by the drive in RAM.
Therefore you should abort the incorrectly started SELFSCAN procedure using the Stop SELFSCAN command.
Then you can restart SELFSCAN.
Stop SELFSCAN menu item serves for termination of SELFSCAN procedure. Its selection brings up a wizard-
style sequence of windows guiding through the actions required to stop SELFSCAN.
View state menu item serves for reviewing the current status of SELFSCAN procedure. Its selection brings up a
window reflecting the contents of IDE registers, thus it allows identification of current SELFSCAN stage and surface
scanning position. SELFSCAN completion is manifested by the presence of a specific group of values in the “1x3” and
“1x4” drive registers. For DJNA and DPTA models it is “1x3” = 0x40, “1x4” = 0x11. For DTLA and newer models it
is “1x3” = 0x62, “1x4” = 0x11.
View result menu item allows checking the key word or error code after SELFSCAN completion.
Attention! That operation becomes available ONLY UPON COMPLEION of the SELFSCAN procedure.
The following key word variants are possible:
x “COMPFIN1”, “COMPLETE” – SELFSCAN completed successfully
x “ABORTED!” – SELFSCAN completed with an error
x “SELFSCAN” – SELFSCAN did not complete, it was terminated by the utility.
If SELFSCAN ends with an error the drive has to be restored manually using the formatting procedure, please
find extensively damaged areas and add them to the cylinder table, then perform standard procedure of defects search
(please see section 4.3.1). You can see some of SELFSCAN error codes:
Code Description
00 00 SELFSCAN completed successfully
01 01 SELFSCAN detected a defective head
02 02 overflow of track defects’ table
06 02 P-List overflow
Read SELFSCAN module menu item allows reading SELFSCAN module from a drive to a file.
WARNING! Together with the SELFSCAN module you should also copy the MFGP module containing
SELFSCAN parameters (available as "~@@01.rpm" module for drive families older than AVER, please see
Table 5 and a footnote thereto). SELFSCAN can be subsequently started normally only if a valid pair of MFGP
and SELFSCAN modules is available.
WARNING! Current version of the utility does not save the SELFSCAN module to the firmware database and
does not read it after selection of the "read modules" menu item, therefore the module should be saved
separately. Please note, besides, that the body of SELFSCAN module may contain empty sections that prevent
its reading but do not tell on its functionality. Correction of such situation is achieved through the Repair
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 11
Ɋɋ-3000 £
"IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP ¤ ACELab
SELFSCAN module menu item. When it is invoked, the utility reads a SELFSCAN module ignoring reading
errors and records it back. After that action you'll be able both to read the SELFSCAN module and attempt to
start it.
Write SELFSCAN module menu item serves for recording of a SELFSCAN module to a drive.
WARNING! Record to a drive SELFSCAN module belonging only to a corresponding firmware version AND A
CORRESPONDING DRIVE MODEL! Recording an unsuitable SELFSCAN module to a drive may lead to its
destruction (heads “knocking away”).
WARNING! While recording a SELFSCAN module keep in mind that its proper functioning depends on the
presence of the corresponding MFGP module containing SELFSCAN parameters. The “corresponding” module
here means that it must be copied from the same drive or, at least, from an identical model WITH THE SAME
NUMBER OF HEADS!
WARNING! In DTLA and newer drives starting SELFSCAN procedure when isolated heads are present will
cause an error since the module contains a record with a strictly defined number of heads. Therefore starting
the module requires copying the MFGP and SELFSCAN modules from a corresponding model with smaller
capacity.
View MFG parameters menu item will display a report on the current parameters of SELFSCAN (MFG
parameters).
View HLRC data menu item will display an interpretation for the factory report on drive test (HLR1 / HLR2
modules). It contains aggregated data about heads' status based on various tests. Probably, it may be modified by the
SELFSCAN routine. Those reports appeared beginning with the 60GXP (AVER) drive series.
View SRST dump table parameters menu item outputs a summary report on the tests performed by
SELFSCAN and compiled by the drive itself on the basis of its operation log.
Read SELFSCAN log menu item allows reading the SELFSCAN progress log as a binary file. Its interpretation
will be implemented in the utility later or we shall create a separate utility for its analysis.
Repair SELFSCAN module menu item is applicable when a SELFSCAN module contains empty buffer sections,
which do not influence the code itself or module data. If the SELFSCAN procedure does not start or the SELFSCAN
module cannot be read, please try this option prior to overwriting the "native" module, attempt to read the SELFSCAN
module and analyze its contents.
WARNING! Due to microprogram specifics SELFSCAN does not record all the defects. Therefore after
SELFSCAN completion you should perform formatting with subsequent standard defects search procedure
(please see section 4.3.1.).
3. Drive firmware
Firmware is stored in masked ROM, which cannot be modified1. The whole modernization of firmware is performed
using the pair of NV-RAM + Disk F/W. Therefore IBM experts introduced the following rule for identification of new
versions: only firmware version NUMBER is changed while the firmware version CODE remains the same. At that
only the second pair of characters in the number is changed. For example, firmware version number before
modification might have been A46A. After update the version will change to A4xx, where xx stand for another two
characters.
Attention! Replacement with firmware from another drive family is not allowed.
Thus the sets (ROM+NV-RAM+Disk F/W) will be compatible if they conform to the following conditions:
- firmware version CODE is the same for ROM, NV-RAM, and Disk F/W;
- P - Codes in NV-RAM and Disk F/W match;
- firmware version NUMBER stored in ROM may differ from the number in NV-RAM and Disk F/W in the
last pair of characters only.
Compatibility of PCBs can be conveniently identified using the label at IDE connector2 (see Fig. 3.1). If the
first symbols in the first two lines match, electronic parts are mostly compatible and are completely interchangeable.
Precise identification of compatibility can be performed using the information from ROM or NV-RAM3.
07N6544
H31718_
L5Y106
HBM5
1 In drives from sample testing shipments firmware is not stored in masked ROM; instead it is loaded from serial Flash
ROM.
2 The code from IDE connector label is also recorded in PIDM "open" module.
3 Since NV-RAM may become corrupt or overwritten incorrectly it is safer to rely on information stored in ROM.
additional modules used by the utilities distributed by the manufacturer for diagnostics of malfunctions. A large part of
those additional modules is not necessary for drive functioning. Some spaces are just allocated for modules, but contain
nothing, producing an error at an attempt to read such space. All the main functional parts are located in a protected
firmware zone described in the USAG module.
The data in firmware zone can be subdivided into four categories:
- RSVD module, present in none of the tables containing modules; it marks the beginning of a service track.
- Modules listed in the USAG table. All the modules are critical for drive operation.
- Records that are not included into USAG table but participate in factory self-testing.
- A part of open firmware data, which does not intersect with the group of modules from USAG (the table of
open modules contains, apart from the rest, references to a large number of USAG modules required for functioning of
the manufacturer's testing utilities).
After the “Check firmware structure” command is issued, both the closed and open parts of firmware are read.
Besides, the "spaces" in the main and additional service tracks are checked (a "space" is a service track portion, which
is not occupied by any module from the lists). The "RD" label indicates, whether a module could be read. “RD: ”
appears, if the module has been read, otherwise you'll see “RD: -”. The “ID” label reflects whether a module identifier
in the table of modules matches its identifier contained inside the actual module body. We should note that the table of
"open modules" contains, apart from the rest, aliases of modules (for example, the main copy of the RDMT module in
the table of "open" modules in named RDM1, and a copy thereof is called RDM2).
The command also outputs the table of zone allocation and some other parameters. The purposes of some
firmware modules are listed in tables 4 and 5.
1 The MFGP module appeared in the “open modules table” beginning with AVER drive family only. For earlier models
it is available as a “space” module “~@@01.rpm” in the “open modules table”.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
14 www.acelab.ru
Ɋɋ-3000 £
¤ ACELab "IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP
some modules in a drive cannot be read, such problem can easily be identified after looking through a report on
firmware zone structure.
If a drive switches to "endless knocking" after an attempt to read firmware data, you can proceed as follows:
disconnect the spindle motor control cable between the PCB and HDA and wait until the drive reports on
readiness. Here we should note that the said procedure is inapplicable for 120GXP drives, since they do not report on
readiness without a HDA.
In that case you'll have to use another method:
1. having switched the drive off first, short-circuit the 5th and the 6th pins of NV-RAM, then switch the
drive's power supply on with the short-circuit between the said pins. After a few seconds the drive should report on
readiness. Then remove the short-circuit bridge.
2. select the “Switch SA access” option in the menu “Work with firmware zone / Modify configuration”
After that the drive will be correctly initialized from NV-RAM but having read USAG with a different version it will
terminate further loading. However, its firmware zone will be accessible for analysis.
Then we should perform diagnostics of firmware zone (DISK F/W). For that purpose we shall read modules from the
drive one by one using the "Firmware", "Work with firmware zone", "Read modules" menu. The module causing
knocking sounds during the procedure is damaged.
Besides, we should mention the so-called Safe Mode of IBM drives. A drive is switched to that mode by a special
jumper configuration (please see section 4). The drive allows reading and recording NV-RAM in that mode, but rejects
commands for work with disk surface. Consequently the Safe Mode can be used as an alternative to the method of
"short-circuit" in order to modify NV-RAM. The Safe Mode interacts differently with the firmware zone in different
drive families.
while addressing firmware zone firmware overlays are read and started, performing complete
22GXP, 34GXP,
drive initialization. Thus, if firmware zone is corrupt, the drive may enter the "endless
37GP
knocking" mode
40GV and newer attempts to access firmware zone are ignored.
Thus Safe Mode cannot be used for testing and restoration of corrupt data in firmware zone.
While working with firmware zone you should keep in mind information from the following sections of this
manual:
- Work with ROM (please see review of a report on ROM and NV-RAM)
- Work with firmware zone
You may use the following scheme as a general guideline for discovery of possible malfunctions:
Check:
Yes The spindle No
- NV-RAM
spins up - PCB
- motor
While checking NV-RAM you should pay attention to the following aspects:
- Identifier must be “E2PR”
- Firmware version number must match ROM version (please see the section on viewing a report about ROM and NV-
RAM)
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 15
Ɋɋ-3000 £
"IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP ¤ ACELab
Firmware version code must match the ROM code (please see the section on viewing a report about ROM and NV-
RAM)
Mapping of drive heads must correspond to the one typical of that drive family, if the drive hasn't been previously
repaired with overcommutation of heads – or it should at least have a certain sense. For example, it may never contain
references to non-existent points of connection to the commutator (for instance, for the 33rd head).
Besides you should keep in mind that NV-RAM contains a checksum and if NV-RAM gets corrupt the drive will
terminate loading procedure having discovered a checksum mismatch. In that case you can record from a database to
the drive NV-RAM having corresponding type and version. In cases when NV-RAM structural corruption has caused
malfunctioning of the device, the drive will spin up the spindle and attempt to load firmware from disks' surface as soon
as its power supply is turned on.
Checking of firmware modules is accomplished through the menu items "Firmware / Check firmware structure”. If a
part of any module is unreadable, the testing report will reflect inaccessibility of a respective module. In such cases you
should overwrite corrupt modules using database as the source of modules collected from a corresponding drive type
with a matching firmware version using the guidelines on modules critical for user's data and the drive itself and
described in this manual. You should bear in mind that firmware modules in IBM drives have no checksum, which
makes identification of corrupt modules somewhat more complicated.
It is worthwhile to review individually the cases of damage to the “RSVD” module when the “RSVD” marker
is present in it, but the module body is filled with “garbage”. In such cases a drive behaves as though its heads are
malfunctioning, making it impossible to restore its functionality using regular methods. Let us describe the case and the
procedure for drive repair.
Problem: the drive cannot find the firmware, it produces typical sounds, the drive cannot write anything, i.e. behaves
as though recording is disabled for all its heads and:
1) a part of firmware got corrupted
2) all of the firmware got corrupted
3) reading has become disabled for all the heads
Cause: logical corruption of the RSVD module, when the RSVD marker is present in its due place, but the remaining
information is invalid.
Recovery procedure:
x Set the Safe Mode jumpers (or disconnect the motor controller cable for DJNA, DPTA) and create an
alternative loader with heads mapping where another head is substituted into the position for the zero head.
You could try to use head 1. Return the jumpers to the regular position, switch the power on and wait until the
drive reports on readiness. It would be useful to inspect NV-RAM, too (just in case).
x Run the loader to switch the order of heads’ assignment.
x The drive should report on readiness, but you will see a message telling that the modules’ table could not be
read.
x Clear the drive using all the heads.
x Switch the drive power off and on and clear the firmware zone again.
x Record the native NV-RAM, clear the firmware zone.
x Switch the drive power off and on and clear the firmware zone again.
¾Record NV-RAM, the CORRECT RSVD, USAG
¾Record the remaining modules
¾Run the loader with modules (not the one switching heads mapping, but the loader containing modules to be
recorded). This action will additionally ensure normal recording of the modules.
x Record PSHT, RDMT
x Switch the drive power off and on
¾Clear the firmware zone.
¾Record RSVD, USAG
¾Record the remaining modules
¾Run the loader containing modules.
x Record PSHT, RDMT
WARNING! The listed actions marked by an arrow are to be performed at once, without a prior switching of the power
off/on or restarting the utility.
The following are modules essential for drive data in IBM HDDs: PSHT, RDMT, SRVM, ZONE, CNSL,
MLBA (please see Table 2). Besides, you should remember about the requirement of conformity to the heads mapping
in NV-RAM.
90G0653
1
1
N37951H4-
923B-130
90G1267
5100HP
M51181650-
2 3
50TK
Jumper Configuration
Master Slave Safe mode
Figure 4.1. External view of controller board in the DJNA drive family.
Table 1 demonstrates the model composition of drive families. Junior model in the family contains 4 heads.
The maximum number of disks for those drive families is 5.
Two ROM chips are present on the PCB:
- Masked ROM integrated with the processor. It contains the executable processor code and default setup
values.
- Flash ROM with serial access - NV-RAM. It contains setup parameters for access to the drive's firmware
zone. Its type is S93C56, size – 256 bytes.
In case of processor malfunction the PCB is unable to report on readiness without HDA. At the utility launch
you'll see a message "Error reading NV-RAM". If the processor is functioning the PCB will always report on readiness
without a HDA (only DRDY and DSC LEDs in status register will be illuminated) independently from NV-RAM
contents.
If firmware modules could not be read, you'll see the following messages: "Modules table cannot be read.
Continue?" and "Error reading zone allocation module. Default zone allocation used". If the drive unparks its heads
during the procedure and you do not hear knocking sounds the error is most likely in the firmware data. In that case you
can perform the "Check firmware structure" command and see, which modules have been damaged.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 17
Ɋɋ-3000 £
"IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP ¤ ACELab
If modules can be read, but contain incorrect information, you can overwrite them using the "Write modules"
command from the menu for work with firmware zone.
PCBs have several firmware versions located in masked ROM inside the processor. Matching firmware
versions are compatible. Besides, two last characters in the firmware version and ROM version number may be
different (please see section 3.1 “Structure of IBM HDD firmware”). Installation of PCB from one drive family to a
HDA from another is impossible in principle because masked ROM and different chips are used for reading/writing and
motor control. If there is a need to transfer a PCB from a drive with a different number of heads but containing the
same processor ROM version you should eliminate the difference, i.e. NV-RAM contents. It is possible to read /write to
NV-RAM on a separate board without a connected HDA. For that purpose it would be sufficient to disconnect the cable
to spindle motor and wait until the PCB reports on readiness.
If one or more magnetic heads are malfunctioning, the drive enters a continuous cycle, during which it keeps
knocking the magnetic-head assembly against the limiting stop. If the heads are functioning and the problem is caused
by incorrect firmware data the drive will report on readiness quite quickly after the knocking sounds.
IBM36 IREL
AMSRC04 03
TQA7BB.6C
06K2869 PQ
2
90G2232
007AT00
N37980F8-
3000HP
1. 33.3 ɆȽɰ
2. NV-RAM S93C66
Jumper Configuration
Master Slave Safe mode
Figure 4.2. External view of controller board in the DTLA-7 drive family.
1. NV-RAM S93C66
Jumper Configuration
Master Slave Safe mode
Figure 4.3. External view of controller board in the DTLA-5, AVER, and AVVA drive families.
Table 1 demonstrates the model composition of drive families. Junior model in the family contains 2 heads
(sometimes you may encounter factory-refurbished drives with 1 head). The maximum number of disks for those drive
families is 5. In those models glass disks are used since the accuracy of smooth surface production is higher for glass
than for aluminum.
Two or three ROM chips are present on the PCB:
- Masked ROM integrated with the processor. It contains the executable processor code and default setup
values.
- Flash ROM with serial access - NV-RAM. It contains setup parameters for access to the drive's firmware
zone. Its type is S93C56, size – 512 bytes.
- The third ROM chip is not always present on a PCB. Those Flash ROM chips were used in sample testing
shipments of drives with firmware recorded in serial Flash ROM instead of a masked ROM, which fact allowed
correction of errors in ROM code. The socket for that chip is located near NV-RAM. Its size is 1 Mbit, type -
25FV101T.
Unlike the previous drive families incorrect information in NV-RAM may result in PCB "hanging" preventing
it from reporting on readiness. In such case you may use the methods listed in section 3.3 “Description of structure and
methods of firmware zone access in case of malfunctions” in order to bring the drive out from the "endless knocking"
state and make it report on readiness. After the drive reports on readiness you must record correct NV-RAM to it. It is
recommended to perform that operation having first launched the utility without a drive so as to exclude sending of
additional commands, for example, drive ID request and software reset.
A drive with corrupt modules behaves similar to drives from the previously described families.
The drive families in question use heads' parking not on disks, as it used to be, but at the external edge of the
disks – on a special polymer stand. Sometimes such method causes complete notching of disks in cases when a head
either gets bent during its entrance/exit or when it hits under the parking stand guide. Heads also quite frequently get
"stuck" remaining on disks.
If a drive demonstrates defects that disappear during the recording process, it is convenient to repair it using
"factory formatting". It replaces the process of overwriting the whole drive space and it is performed with the maximum
speed possible since no data or control commands are sent from/to the drive. The duration of a complete factory format
cycle is 25 minutes for 40Gb AVER drive.
As a matter of fact, such situations when corrupt sectors appear result most frequently from lack of contact
between the PCB and HDA connector. The case is that the contact between electronic circuitry and the PCB is
accomplished through a pin connector under the board located near the power connector. However, PCBs mounting is
quite unreliable in those drives, as a result mechanical influences or thermal deformations cause perforation of tin
contact pads under the contact pins, which thus cease to provide adequate connection. Therefore prior to the repair it is
necessary to caulk the contact pads by soldering.
This manual is supplemented with a part of a drive's circuit diagram showing the portion controlling the
spindle motor rotation and the voice coil together with a scheme of parts location and their labeling.
Mechanisms of software relocation of defective sectors provided in the utility allow to hide defects in G-List
using the "autoassign" method and also perform manual editing of G-List (RDMT) and “cylinder table” (SRVM).
Please refer to "Defects table" section for details on respective features.
In case of insignificant damages the algorithm of defects relocation is quite simple:
In case of insufficient contact in the connector refer to section 6 “Malfunctions of electronics boards in IBM drives.” in
this manual for diagnostics of that malfunction and a description of the main electronic circuitry defects.
1. Perform factory format. If it completes normally (without errors), there is no serious damage.
2. Perform logical scanning and relocate defects to G-List. Testing using physical parameters presently does not
add defects automatically to relevant tables.
3. Perform translator recalculation if any defects have been discovered. During the process defects from G-List
will be moved to P-List and G-List will be cleared. We should note that candidate defects will not be transferred from
G-List to P-List due to specific operation of the transfer feature algorithm implemented in the drive itself. It is
explained in particular by the fact that a drive views candidate defects just as areas with unstable access. If you still
wish to transfer candidate defects to P-List enter the RDMT editor (menu “Defects table./ Editors”) and respond
"Transfer" to the question regarding action to perform with candidate defects – and save the table immediately.
Translator recalculation will be carried out automatically after that.
4. Perform logical scanning once again. If any defects are discovered, return to step 3.
Factory formatting, apart from its other features, allows to localize considerably damaged servo fields that may
subsequently be hidden to the "cylinder table”. Specific manner of firmware operation after modification of "cylinder
table" requires to clear ɨɱɢɫɬɤɢ P-List and G-List since such modification invalidates the defects listed in those tables.
Besides, defects that have not been eliminated using the "autoassign" mechanism can be added to G-List
(RDMT) manually using an internal editor. Specific character of that operation requires to perform translator
recalculation started automatically by the utility after editing.
It is also to load a list of defects created by "defectoscope" software. For details refer to section 2.2.7 "Defects
table”.
The table of open modules is a synthetic one, i.e. it does not exist as an actual integral block of data on disk surface.
The table of open modules is generated from the OVR4 overlay (OVR1 module contains several overlays, including
OVR4) based on drive geometry. The table itself is returned by the drive in response to a special command that does
not belong to the group of factory commands. Consequently, the impossibility to obtain the table from a drive results
from its incomplete initialization. The situation may arise for a number of reasons.
1. Unreadability of RSVD.
2. Unreadability of a module from USAG.
3. “Garbage” in a USAG module.
4. Unreadability of a sector (space) between modules.
5. Corruption of NV-RAM image on disk surface (beginning of WRT0 module).
6. Incompatibility between firmware modules that resulted from incorrect firmware update or incorrect repair.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
20 www.acelab.ru
Ɋɋ-3000 £
¤ ACELab "IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP
When firmware data gets corrupt a drive frequently enters the state of endless knocking with its heads against
the limiting stop, endless waiting, etc., i.e. conditions making software repair impossible. In those cases it is necessary
to prevent the drive's attempt of loading firmware data from disks' surface, still preserving access to firmware zone. It is
necessary to modify NV-RAM header, namely firmware version number, to achieve that goal. However, it requires at
least the ability to read/write to NV-RAM. Different models of IBM drives differ from each other as regards the
methods of accomplishment of that task. The methods and description of NV-RAM header modification are in the
section 3.3. "Description of structure and methods of firmware zone access in case of malfunctions". Here we show the
table of applicability for the described methods as regards different drive.
Disconnection of spindle Short-circuit of NV-RAM
Model/method Safe Mode1
control cable pins
22GXP(DJNA7),
34GXP(DPTA7), + + +
37GP(DPTA5)
40GV(DTLA5),
+ + +
75GXP(DTLA7)
60GXP(AVER),
- + +
120GXP(AVVA)
1 In Safe Mode only reading/writing to NV-RAM is possible, work with surface is prohibited.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 21
Ɋɋ-3000 £
"IBM" 22GXP, 34GXP, 37GP, 40GV, 75GXP, 60GXP, 120GXP ¤ ACELab
*.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 modules. During the reading procedure they are
copied to the directory “IBMxxMOD”, where xx represents drive family identifier; (*.bad – modules that have been
read with an error)
*.log files can be viewed as regular text files; *.bin files can be viewed as binary files using a hex editor.
C1
R13 C65
C28
C45
R49
C9
C31
R10
R42
C64
C63
C52
C67
C78 Q2 C53 C62
R45
R39
90G2018
R12 C51 R50
C8 C66
R38
C49
C60 C35
C26 C33 R41
C7 R24 R53 R37
R23 R52 C32
R11
R51 C30 C36
C59
R1 R48
C25 C23
R47
C24 R40
C48
C22 R30
C6
R29
D1
R82 C21 C56
R56
C54
R27
R28
R8
C39
C46
Q1 R46 C11
R21 C27
U6 R4
ɋ5
C47
C56
R20 R18
D2
C29 C57
C2 R50 1
C42
U9
C43
C44
R17
R26
C41
L1 R25 J3
C20
R6 R7 C19
R5 R31
C88 R16 IBM36 IREL
C70
C18 C40
R36
AMSRC04 03 R19
Q3 C17 TQA7BB.6C C37
R9 06K2869 PQ
R3 C12 C69
R2
R22
C34
C36
R35
C10
R14
R25
LS1
1
2 C54 C55 C48
3
4
D1
3 SPINDLE MOTOR
2 C27
D D
1
C39
D2
C58 3
2
1
C29
12v
R40
64
63
62
61
60
59
58
57
56
55
54
53
52
51
50
49
C59 U1
VCM1
P64
P63
P62
P61
P60
P59
P58
P57
P56
P55
P54
P53
P52
P51
P50
P49
1 P1 P48 48 VCM2
C 2 P2 P47 47 C
C57 3 46
P3 P46
4 P4 P45 45
5 44 12v
C11 P5 P44 C50
6 P6 P43 43
7 P7 P42 42
R1 8 41
P8 P41 R42
9 P9 P40 40
C38 10 39
P10 P39 C49
11 P11 P38 38
R48 12 37
C60 P12 P37 C51 R45
13 P13 P36 36
14 P14 90G2018 P35 35
R50 C52
15 P15 P34 34
16 P16 P33 33
C62 R39
P17
P18
P19
P20
P21
P22
P23
P24
P25
P26
P27
P28
P29
P30
P31
P32 C33 C36
B B
C63
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
C53
c109
R49 C64 C67
R10
C65 C66
m37(106)
5v U9
D1758
m37(101)
ibm36(18) R37
1
5v
m37(102)
m37(103)
A A
Western Digital
Classification of WD drive families
Western Digital is the oldest manufacturer of hard disk drives and their components. Thus, WD belongs to the
leading companies developing and manufacturing system controllers, which it uses in its HDDs. Therefore it is
customary to subdivide the generations of WD HDD models according to their architecture (Arch.), which depends first
of all upon the circuitry solutions used in the system controller.
1. Nomenclature of products
A drive’s family and capacity can be identified by its name. The first generation of WD IDE drives was called
Centaur and consisted of 4 drive families. The models of the first four families were labeled as follows:
WD 9 5 04 4 A
Form factor: Peculiarities: Seek time: Interface type:
Western Digital 3,5" 3 - type 1 Capacity, x10, Mb 8 - 70 ms A - AT
5 – type 2 4 - 28 ms X - XT
E.g.: WD93048A, WD95044A
The second generation of WD HDDs consisted of more than 50 families identified as follows:
WD A C 3 3100
Interface type: B - Tadbit 2.5"
Western Digital A - ATA C - Caviar The number of Capacity, Mb
C - PCMCI D - Portfolio 3.0' disks in the head-
Ph - Portable IDE E - Enterprise 3.5" and-disk assembly
ɇɟɬ - SCSI L - Lite 2.5"
U - Ultra Lite 1.8"
E.g.: WDAC2120, WDAC35100A, WDE4360, PhD2100, WDCU140
Beginning with the 20.5 GB model in WD205AA drive family the labeling of models was changed to the one used
nowadays:
WD 2000 B B - 32 AA A0
1 2 3 4 5 6 7
1. WD
Western Digital
2. Capacity
200,0 GB (up to 999,9 GB maximum)
3. Rotational speed of the disks
letters A-E are assigned to EIDE
A - 5400 rpm (WD Caviar 5400)
B - 7200 rpm (WD Caviar 7200)
C - 10'000 rpm
D - 4500 rpm (WD Spartan)
E - 5400 rpm (WD Protege)
letters F-Z are assigned to SCSI and specialized HDDs
F - 10'000 rpm, 2 Mb cache
G - 10'000 rpm, 8 Ɇɛɬ cache
H - 10'000 rpm, 4 Ɇɛɬ cache
J - 7200 rpm, 8 Ɇɛɬ cache
K - 7200 rpm (Performance)
L - 7200 rpm (Fluid Bearing Motor)
M - 5400 rpm (Fluid Bearing Motor)
N - 5400 rpm (WD Protégé - Fluid Bearing Motor)
purposes. The number used to be indicated on microprocessor package or on a paper label over the ROM chip (if
external ROM is used), it consists of three parts:
62-xxxxxx-yyy, where:
62 – indicates that the device belongs to magnetic hard disk storage type,
xxxxxx – six-digit number indicating the drive family,
yyy – three-digit number indicating firmware version.
E.g.: ROM number 62-602208-064 corresponds to the WDAC 33100 drive family.
Please see the table of correspondences below:
Table 2.1.
HDD architecture HDD family Family number Testing utility
WD 450AA 62-001003-xxx pca450aa.exe
WD 307AA Blank pca307aa.exe
Arch-V
WD 272AA Blank pca272aa.exe
WD 205AA 62-602234-xxx pca205aa.exe
WDAC 313000A 62-602233-xxx pca31300.exe
WDAC 310100A 62-602230-xxx pca31010.exe
Arch-IV
WDAC 38400A 62-602225-xxx pca38400.exe
WDAC 36400A 62-602220-xxx pca36400.exe
Arch-III WDAC 35100A 62-602221-xxx pca35100.exe
WDAC 34000A 62-602210-xxx pca34000.exe
WDAC 33100A 62-602208-xxx, pca33100.exe
62-602222-xxx
WDAC 32500A 62-602214-xxx, pca32500.exe
62-602215-xxx,
62-602203-xxx
Arch-II WDAC 31600A 62-602111-xxx pca31600.exe
WDAC 21200A 62-602202-xxx, pca21200.exe
62-602209-xxx
WDAC 2850A 62-602110-xxx, pcac2850.exe
62-602200-xxx
WDAC 2700A 62-602107-xxx pcac2700.exe
WDAC 31200A 62-602108-xxx pca31200.exe
WDAC 31000A 62-602101-xxx pca31000.exe
WDAC 2540A 62-602104-xxx pcac2540.exe
WDAC 2420A 62-602103-xxx, pcac2420.exe
62-602084-xxx
Arch-I
WDAC 2340A 62-602082-xxx, pcac2340.exe
62-602083-xxx,
62-602091-xxx
WDAL 2170A 62-602085-xxx pcal2170.exe
WDCU 140A pccu140.exe
WDAC 2200A 62-600059-xxx pcac2200.exe
Arch-0 WDAC 2120A 62-600060-xxx pcac2120.exe
WDAC 280A 62-600031-xxx pcac280.exe
Centaur Family WD9xxxxA - pcwd9x.exe
Beginning with Arch-V generation WD discontinued marking the ROM chip with an identification code
(although those marks was preserved in some Arch-V drive families, please see Table 2.1). It complicated drive family
identification and really impeded identifying the firmware version necessary to ensure compatibility between the
electronics board and a head-and-disk assembly or interchangeability between different boards. Most likely it resulted
from the fact that WD began using FLASH ROM instead of 27ɋɯɯɯɯ one-time-programmable chips, recording
firmware to ROM after board assembly.
3. Conclusion
Attention: A corresponding utility must be selected correctly for HDD testing. Otherwise you may irreversibly
damage the drive. If there is no individual utility for a specific model, such drive can be tested with universal
utilities of the complex only.
You can use the ac_ident.exe utility in order to identify the family of a drive (up to Arch-V). It will display the
drive family (which can be used for selection of a corresponding testing utility, please see Table 2.1), the number of
physical cylinders and heads in the drive.
1
The pcwd_cb2.exe offers a limited number of features.
Contents
1. Purpose..........................................................................................................................................................................2
2. Basic options for the repair of WD Caviar Arch-V drives ...........................................................................................2
3. Preparing for work ........................................................................................................................................................2
4. Utility usage ..................................................................................................................................................................3
4.1. Standard mode .......................................................................................................................................................3
4.1.1. Servo test........................................................................................................................................................... 3
4.1.2. Surface test........................................................................................................................................................ 3
4.1.3. Disc Firmware zone .......................................................................................................................................... 3
4.1.4. Drive description............................................................................................................................................... 6
4.1.5. Formatting......................................................................................................................................................... 6
4.1.6. Logical structure scanning ................................................................................................................................ 6
4.1.7. S.M.A.R.T. table ............................................................................................................................................... 6
4.1.8. Defects table...................................................................................................................................................... 6
4.1.9. Automatic mode................................................................................................................................................ 7
4.2. SAFE MODE .........................................................................................................................................................7
4.2.1. Alternative SAFE MODE ................................................................................................................................. 7
5. Brief technical description of WD450AA, WD307AA, WD272AA, and WD205AA drive families .........................8
5.1. The structure of HDD firmware.............................................................................................................................9
5.2. Compatibility between electronics boards .............................................................................................................9
5.3. The structure of loadable firmware portion (DISK F/W) ....................................................................................10
5.3.1. Critical modules for drive data........................................................................................................................ 11
5.4. Modification of configuration..............................................................................................................................11
6. Software restoration of a drive....................................................................................................................................11
7. Restoration of firmware modules................................................................................................................................12
7.1. HDD translator recalculation ...............................................................................................................................13
8. Flash ROM recording .................................................................................................................................................13
8.1. Creation of an external loader file........................................................................................................................13
1. Purpose
The utilities are designed for restoration of 3" Caviar Arch-V drives manufactured by Western Digital, drive
families: WD450AA, WD307AA, WD272AA, WD205AA (please see Table1.1.). You can use the ac_ident.exe utility
for a more precise identification of models within drive families.
Table 1.1.
Utility Supported models – Capacity Number Heads MDL Family number1
(family) of disks
1 - the number is printed on the ROM chip label; xxx – stands for the version of microprocessor firmware in this drive
family.
2 Reduced recording density.
is present, the standard external PC power supply should be used with manual switching of power on/off according to
messages displayed on the screen.
3. Current directory must contain the utility executables (*.exe) and resource files (*.rsc).
4. Switch on the power supply to the drive being tested. If the PC-3K PWR adapter is present power supply is
controlled via PC keyboard (please see description for shell.com software command shell).
5. Start a respective utility using the shell.com command shell.
Attention! Utility tests have lots of options. It is recommended that novice users begin working with default test
options.
4. Utility usage
After utility start the following mode selection menu appears on the screen:
Standard mode
SAFE MODE
The standard mode is the regular mode of utility operation provided that the drive can be initialized.
SAFE MODE serves for working individually with the printed circuit board (PCB) containing the electronic
components without a head-and-disk assembly (HDA). The drive switches to SAFE MODE if three jumpers are enabled
together: CS, SLAVE and MASTER.
When the utility starts in the Standard mode it checks if the drive belongs to the corresponding drive family. In
case of a mismatch the following message appears: CONNECTED DRIVE NOT SUPPORTED BY THE UTILITY
with a subsequent offer of exit from the utility. If the utility corresponds to the type of the connected drive it lists the
drives which constitute the corresponding family. The cursor automatically moves to the name of the connected drive
model, but the choice can be changed if necessary. Pressing [Enter] will bring up the main menu of operation modes:
Servo test
Surface test
Disc Firmware zone
Drive description
Formatting
Logical structure scanning
S.M.A.R.T. table
Defects table
Automatic mode
Exit
Servo test – testing is performed using physical parameters in ABA format (absolute block addressing). The test routine
does not differ in any way from that for the previous drive families; please see details in the description for WD Arch.4
“PC-A313000, PC-A310100, PC-A38400, PC-A36400”.
Surface test allows to estimate the quality of magnetic surfaces, the state of magnetic-head assembly (MHA) and its
switch circuit, to detect and relocate all defective tracks and sectors. The test routine does not differ in any way from
that for the previous drive families, please see details in the description for WD Arch.4 “PC-A313000, PC-A310100,
PC-A38400, PC-A36400”.
Read modules - this operation allows reading of HDD firmware stored in the modules directory within the disk
service area. The read modules are placed then into the WD5_MOD subdirectory. The name of each read module file is
generated as follows.:
~idxx.rpm, where:
xx is the module identifier, e.g.: ~id20.rpm is the module of the 20h translator table.
Before the operation a list of modules available for reading appears on the screen, you will need to select either a
specific module in it or “ALL MODULES” item. In the latter case all the firmware modules will be read to the
WD5_MOD subdirectory. If the subdirectory already contains modules with the same names, repeated reading will
overwrite them without notification.
WARNING! Not all the modules present in the firmware area are indicated in the modules directory; instead it
contains just modules required for HDD operation. Thus, for example, several auxiliary modules - Selfscan,
Selfscan results, etc. may be not included into the modules directory. Therefore it is recommended to use
firmware image reading method in order to save the firmware completely (please see the paragraph on firmware
data read/write).
Write modules – this operation allows recording a firmware module (or modules) to the firmware zone of the
drive. Prior to the procedure you will see a list of all modules, which are available for writing in the WD5_MOD
subdirectory. The user has to select a certain module or the “ALL MODULES” option. In the latter case all the modules
from the WD5_MOD subdirectory will be written to the firmware zone. Module(s) checksum recalculation and
correction takes place before recording.
WARNING! The utility does not check the module structure before writing, therefore you should be extremely
attentive, otherwise you may irreversibly damage the drive.
Security subsystem1 menu option contains commands, which allow reviewing and resetting master and user
passwords in a hard drive.
Drive description - – brings the drive’s disk description on the screen. All non-displayable ASCII characters are
replaced with spaces. Drive’s description: logical structure parameters and serial number can be corrected. When it is
necessary to correct model name you should first set MODEL FROM ROM parameter to NO by pressing [Space].
Press [Enter] to enter the parameter or to move to editing the next one; press [Esc] if you do not want to rewrite the
drive description area.
4.1.5. Formatting
Formatting – starts the low-level formatting procedure. During formatting the drive skips defective sectors and
defective tracks reading their numbers from the defects table (if the method using one or another table has been
selected). The formatting procedure cannot be interrupted because when it finishes a translator recalculation and
recording are performed. If format ends in error it means presence of corrupt servo information or incorrectly compiled
defects table. Even if formatting ends in error, the translator is recalculated and recorded, though not all the surface of
the drive will be formatted. Before the start of formatting you have to select the defects table mode or formatting
without defects table data. Formatting takes approximately 40 minutes, but it depends on the model, condition of
magnetic disks and can grow considerably with defective surfaces.
S.M.A.R.T. table – allows viewing S.M.A.R.T. parameters of a drive. You can read in detail about S.M.A.R.T. in the
PC-3000AT tester description.
Defects table – allows to view, add, clear defects table or perform defects grouping:
View defects table. This command displays the table of relocated defects in a drive. Viewing defects’ tables
helps estimate the quality and status of the magnetic disks used in the drive.
Add LBA defect. This command adds a logical defect in LBA notation. After addition all entered logical
structure defects are translated into physical location 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.
Import logical defects table. This command allows to add values from a *.dft file to the defects table (P or G-
List at your option). Such a file may be prepared, 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.
Clear defects table. After execution of that command the respective defects table will be reset – the number of
defective sectors become equal to 0. The user has to select which table should be cleared.
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 reset 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.
Group to tracks. This menu item allows to group into defective tracks those defective sectors, which already
are entered into the tables of defects. When you enter the mode you will see the message: LIMIT OF GROUPING
INTO TRACKS. Then you have to enter the limit value above which sector defects should be grouped into defective
tracks in both P-List and G-List tables. The input range is from 1 to 50.
Automatic mode allows scanning the drive automatically without operator intervention. When this mode is selected two
lists appear on the screen: TASKS LIST and AVAILABLE TASKS. Before testing starts a test program must be
created or a previously created one loaded.
Attention! The work in the automatic mode does not differ in any way from that for the previous drive families,
please see details in the description for WD Arch.4 “PC-A313000, PC-A310100, PC-A38400, PC-A36400”.
Exit – exits from the utility.
The mode provides access to a limited number of drive features. The safe mode is meant for testing the printed circuit
boards (PCB) separately from the HDA. However, after switching a drive into safe mode you may leave a PCB on its
HDA. In order to enable the safe mode you should set three jumpers at once: CS, SLAVE, MASTER and switch on the
power. The drive at that does not process bits D6 (DRDY) and D4 (DSC) in the status register. The following menu
appears after selection of that mode:
Work with ROM
PCB testing
Work with ROM menu option allows access to recording, reading and viewing of a drive’s ROM:
Viewing ROM information command displays on-screen firmware version, the version of the links’ table and a
list of modules supported in that drive family:
Copyright 1996-99
ROM version : WDC 05.09 B
ROM revision : 1F
Links table version: 05.56
Supported models
WDC WD51AA
WDC WD102AA
WDC WD153AA
WDC WD205AA
WDC WD255AA
WDC WD307AA
Reading ROM command accomplishes reading of ROM contents to a file with *.bin extension. If you select
that operation you should enter the file name without an extension. The read-in file will be placed in the current
PC3000 subdirectory.
Writing ROM1 command accomplishes recording of drive ROM from a file. During the procedure you should
first select the wd_aa.lmc loader file (or compatible), then select a *.bin file to be recorded, it has to be in the PC3000
subdirectory. When the file is selected, the actual recording process begins. The method of recording ROM is described
in more detail in section 8.
PCB test command allows checking several components of a drive’s electronics board, namely, it can sector
buffer test and initiate internal self diagnostic. Please see details of those modes in the description to the PC-3000AT
tester.
The WD3xxxAA drive family has one more mechanism for switching a drive into Safe Mode, i.e. by default.
If you remove the PCB from its HDA without installed jumpers and leave it for 3 minutes with power on, then the
board will report on readiness when that period expires. If you launch after that the universal PC-3000AT utility, the
board will be identified as the top-of-the-line model in the family. That will enable you to check the board electronics
by testing the sector buffer and running the drive’s self-testing routine, those tests are available in the controller testing
mode of the PC-3000AT tester. You can also view drive ID in that mode. It is helpful, when you do not know exactly
the family, to which a PCB belongs. By reviewing the drive ID description you can identify the family and ROM
firmware version.
1
M27C1024-
35C1 CL-SH3367-
WD70C12 62-001003 DH-B3
-065
4
WDC © 1999
MASTER
SLAVE 1. 25.00 MHz
CS 2. US1010-3,3
1
3. L6262 2.6
2
3 4. 78M08A
CS
CS
SLAVE
SLAVE
SLAVE
MASTER
MASTER
MASTER
MASTER
SLAVE
CS
Pic. 5.1.1. External view of the electronics board in WD405AA drive family.
1
WDC99
62-602234 CL-SH3367-
-080 HC -B2
WD70C10-SW
4
WDC © 1999
MASTER
SLAVE 1. 25.00 MHz
CS 2. US1010-3,3
1
3. L6262 2.6
2 4. 78M08A
3
CS
CS
SLAVE
SLAVE
SLAVE
MASTER
MASTER
MASTER
MASTER
SLAVE
CS
Pic. 5.1.2. External view of the electronics board in WD205AA drive family.
Firmware of WD HDDs consists of a microprogram stored in ROM, a configuring links table also located in
ROM, a loadable firmware portion and data in the service area of a drive (DISK Firmware). The firmware is
characterized by its revision number (F/W Rev.), which defines its development and compatibility.
Firmware part Version, example Location
Microprogram 82.18A ROM
Links table 10.07 ROM
Loadable firmware version, tables 82.18A Firmware zone, (cylinders -1 to -14)
You can find out the microcode version and the version of ROM links table using the Viewing ROM information
command in Safe Mode. The version of loadable firmware portion (DISK F/W) can be displayed by running the Disc
Firmware structure test menu item in the basic utility mode. The version indicated in the modules’ directory will be the
version for DISK F/W.
Version number output by the drive in the “firmware version" line after the Identify DRV (ECh) command, i.e.
when the drive ID is viewed, is an aggregative value and contains the information from all three parts of HDD
firmware, e.g.:
ROM firmware: 82.18A
ROM links table: 10.07
DISK F/W: 16.14A
As a result the compiled version of HDD firmware will look like: 82.10A16. As it can be seen in this example, the
version number was formed using the first bytes from the respective versions of the parts of HDD firmware. The letter
is borrowed from the version of ROM microcode. If you read microprogram version in Safe Mode, the DISK F/W part
of the version will be missing, because all operations with disk firmware portion are disabled in that mode.
As with previous WD drive families the manufacturer indicates the firmware recorded to a 27ɋ1024 ROM
chip with a special label bearing version number according to internal factory classification:
62-xxxxxx-yyy, where:
62 – indicates that the device belongs to HDD storage type;
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 9
Western Digital "Caviar" Arch-V Ɋɋ-3000 £
"PC-A450AA" "PC-A307AA" "PC-A272AA" "PC-A205AA" ¤ ACELab
xxxxxx – family number (it may have different values even within one family);
yyy – firmware version number in that family.
Thus, for example, for a WD64AA drive (WD205AA family) firmware version is 62-602234-080, while for a
WD153AA drive (WD450AA family) firmware version will be 62-001003-065. Such classification is very convenient
and allows error-free selection of replacement boards – if the ROM numbers match it means that the boards are
completely interchangeable.
However, in WD272AA and WD307AA drive families the manufacturer started using Flash ROM with a
circular label on the chip, but it does not bear any numbers, therefore firmware version can be identified only after
reading ROM contents or by running the Viewing ROM information command in Safe Mode.
WD drives have 14 service cylinders (from –14 through –1) used for storage of firmware recorded in two
copies over sides 0 and 1. However only first 4 cylinders (-1 through -4) are actually used for recording of the firmware
modules. Firmware data are stored in the form of individual modules, which form together HDD control and operating
system. Navigation between the modules is performed in accordance with the modules’ directory containing the address
of each module, its identifier and length. Each module, in its turn, has a standard header containing its date, checksum,
identifier, version number and module length expressed in sectors. Please see the main DISK F/W modules in the
summary table below.
4E ? Reserved
61 Loadable portion of firmware code, the part which performs overwriting of Flash ROM
FF Selfscan module
At power-up a drive configures itself as a specific model of its family during initialization. The FLT/SE signal
produced by the commutator pre-amplifier chip is used for that purpose. After spin-up of the spindle motor the drive
microprocessor sequentially checks all heads beginning with the zero one. When a missing head is detected, the
FLT/SE signal is sent to the microprocessor. Thus the drive determines precisely the number of heads and configures
itself as a corresponding model. The signal for heads’ switching is sent by the microprocessor in a serial code.
Developers of the utility have not yet discovered a method for software isolation of defective surfaces; so there
is just one way to decrease the capacity of a drive – i.e. disabling the disk sides “from the top”. In order to disable a
malfunctioning side you’ll have to open the HDA and disconnect the conductors from the magneto-resistive heads of
the defective sides and all sides above the ones being disabled. Keep in mind the location of magnetic surfaces during
that procedure.
Depending upon the state of the drive being repaired, certain operations might be necessary for its restoration.
For example, if at power-up a drive does not spin up the spindle motor or spins it up and stops, then such a defect most
likely has to deal with the electronics board and requires its repair. If a drive starts to spin up the spindle motor and
monotonously knocks with its positioner against locking plate instead of recalibration, then such a defect demonstrates
malfunctions of the drive’s servo system and can be caused by one of the following:
- electronic controller board and the sealed HDA belong to different drive families and are incompatible;
- malfunction of commutator pre-amplifier chip of the Head Assembly (HA) inside the HDA;
- malfunction of the HA itself;
- seriously corrupt servo data or a shift of magnetic disks pack after a shock (increased noise of spindle motor
rotation usually and case vibration show that the drive has been hit).
In all of the above cases except for the first one software restoration of the 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 firmware data from the disk. That kind of defect may arise from:
- data reading/translation channel malfunction;
- servo modules corruption;
- incompatibility between the disk firmware version and the firmware code recorded in the control board
ROM.
In such case ensure that the control board is functional (the best method is swapping of the boards), the ROM and HDA
versions are compatible, and begin the hardware data restoration from step 1.
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 started from step 2.
a). Perform the command “DISC FIRMWARE STRUCTURE TEST” and identify corrupted modules. If just
some modules are damaged while others remain normal, you can overwrite the defective modules using the
method described in section 7.
b). If the majority of modules are corrupted in a drive select the “DISC FIRMWARE ZONE” menu option and
run the “DISC FIRMWARE SURFACE TEST” command. Make sure that there are no errors on cylinders: -5 ..
-1, heads: 0-1. If errors occur, perform DISC FIRMWARE ZONE FORMATTING;
c). Select the menu items: “DISC FIRMWARE DATA READ/WRITE”, “WRITE FW TO THE DISC” and write
the data to the drive being restored according to the version of the drive processor microcode. After successful
recording the firmware is restarted;
d). Correct the logical parameters, if necessary.
2. Clear PLIST and GLIST defects tables and reset SMART.
3. Run SERVO TEST. Ensure that the CLEAR TRANSLATOR option is enabled. During testing a block-by-block surface
formatting is performed, the testing procedure measures the time of decoding for all the servo fields in the current block
and the obtained value is shown on a respective diagram.
When the test is complete the table containing the number of the defective sectors in ABA notation appears on
the screen. Pressing the [Enter] key converts all block numbers in ABA notation into physical PCHS notation and
displays a table of defective tracks. Pressing [Enter] appends all defective tracks to P-List.
4. Run SURFACE TEST. The test is performed using physical parameters in ABA format. It is allowed to switch off
writing and perform verification instead of reading to make the test run faster. After testing procedure a table
containing defective ABA numbers appears on the screen. Pressing [Enter] converts all the ABA-represented blocks
into physical PCHS notation and a table with defective sectors and tracks appears on the screen. Pressing [Enter]
appends all defective sectors and tracks to P-List.
5. Using the results of tests 3 and 4 make a conclusion concerning the necessity of defective surfaces isolation (see
section 5.4.). After turning off defective sides it is necessary to continue the drive restoration beginning with step 2.
6. Perform low-level formatting using PLIST, which should complete successfully. If formatting ended in an error, you
have to repeat steps 3, and 4 or, if the drive was reconfigured, correct its logical parameters (cyl, head, sec) in
accordance with the new model parameters.
7. Perform LOGICAL STRUCTURE SCANNING procedure, which is executed in LBA format. After completion of
surface scanning procedure a table of all detected logical defects in LBA notation will be output on the screen. Pressing
[Enter] converts all logical defects into physical addresses and adds them to the P-LIST or G-LIST defects table at
user’s option.
8. Perform low-level format using P and G-List.
9. Write serial number into the drive ID area, if necessary.
10. Perform COMPLEX TEST with the PC-3000AT tester. If errors are detected repeat steps 3-6 or run the
UNIVERSAL DEFECTS RELOCATION procedure.
11. Run the PC-3000AT tester COMPLEX TEST and make sure that the drive is functional.
Some of the modules are critical for data protection and should not be overwritten if you wish to preserve the
user's data, for example, the 20h - 25h translator modules, 46h - 49h modules containing adaptive parameters.
Other modules are not so essential and they can be overwritten, however, it’s better to copy normal modules from the
same HDD model with an identical firmware version.
Anyway, prior to starting the drive restoration it is necessary to save all the modules and the ROM
firmware to have an opportunity to reverse the changes.
Translator restoration can be invoked as follows: Disc Firmware zone, Translator operations, Regenerate
Translator. Upon entering the mode you will be offered to select the basic tables to be used for the recalculation:
Take into account PLIST and G-LIST
Take into account Use PLIST
Take into account Use G-LIST
Do not take into account neither PLIST nor G-LIST
Factory testing of a drive appends defects to the P-List table (primary) only; the G-List (Grown) table remains empty. It
is filled in the process of drive operation by the device itself in the Data Lifeguard and Assign modes. Thus, translator
of a drive arriving from a factory is recalculated using P-List only. Therefore if you restore a drive with corrupted 20h
and 25h modules, the procedure should be performed using P-List only, in that case access to user data will be restored.
In order to produce an external loader file copy the ~id61.rpm module from an operational drive with a Flash ROM
chip of the required type. Rename the file so that it receives the Loader Micro Code (lmc) extension.
1 Flash ROM chips are marked: 28xxx, 29xxx, 49xxx. 27xxx chips do not belong to Flash type.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 13
Ɋɋ-3000 £ Western Digital "Spartan", "Protege", "Caviar" Generation electronics Arch-V, Arch-VI
¤ ACELab "PCWD_DA", "PCWD_EB", "PCWD_ABJ", "PCWD_CB2"
Contents
1. Purpose..........................................................................................................................................................................2
2. Basic options for the repair of WD Arch-V drives .......................................................................................................2
3. Preparing for work ........................................................................................................................................................3
4. Utility usage ..................................................................................................................................................................3
4.1. Standard mode .......................................................................................................................................................3
4.1.1. Disc Firmware zone .......................................................................................................................................... 3
4.1.2. Drive description............................................................................................................................................... 6
4.1.3. Formatting......................................................................................................................................................... 6
4.1.4. Logical structure scanning ................................................................................................................................ 6
4.1.5. S.M.A.R.T. table ............................................................................................................................................... 6
4.1.6. Defects table...................................................................................................................................................... 7
4.1.7. Automatic mode................................................................................................................................................ 7
4.2. SAFE MODE .........................................................................................................................................................7
5. Brief technical description of Spartan, Caviar, Protege Arch-V, and Caviar Arch VI drive families. .........................8
5.1. The structure of HDD firmware...........................................................................................................................10
5.2. Compatibility between electronics boards ...........................................................................................................10
5.2.1. HA compatibility (knocking sounds at power-up).......................................................................................... 11
5.3. The structure of loadable firmware portion (DISK F/W) ....................................................................................11
5.3.1. Critical modules for drive data........................................................................................................................ 13
5.4. Data structure in Flash ROM in WD Caviar and Protege drive families .............................................................13
5.5. Modification of drive configuration, software heads deactivation ......................................................................13
6. Software restoration of a drive....................................................................................................................................14
7. Restoration of firmware modules................................................................................................................................15
7.1. HDD translator recalculation ...............................................................................................................................15
8. Flash ROM recording .................................................................................................................................................16
8.1. Creation of an external loader file........................................................................................................................16
9. Electric circuit.............................................................................................................................................................16
9.1. Reference voltage sources....................................................................................................................................16
9.2. Control circuit of spindle motor and positioner ...................................................................................................17
9.3. Data reading channel............................................................................................................................................17
1. Purpose
The utilities are designed for restoration of 3" Spartan, Caviar, Protege Arch-V and Caviar Arch VI drives
manufactured by Western Digital, drive families: WDxxxDA, WDxxxAB, WDxxxBB, WDxxxEB, and WDxxxJB
(please see Table 1.1.).
Table 1.1.
Utility Arch. Supported models – Number Heads Speed, Utility
(family) capacity of disks RPM
WD2000BB/JB - 200 GB 3 6
WDxxxBB/JB, Caviar
WD1800BB/JB - 180 GB 3 6
(WD2000BB series) VI 7200 pcwd_cb2.exe1
WD1600BB/JB - 160 GB 3 6
WD1200BB/JB - 120 GB 2 4
WD800BB/JB - 80 GB 1 2
WDxxxBB/JB, Caviar
V WD600BB/JB - 60 GB 1 2 7200 pcwd_abj.exe
(WD800BB series)
WD400BB/JB - 40 GB 1 1
WD1200BB/JB - 120 GB 3 6
WD1000BB/JB - 100 GB 3 5
WDxxxBB, Caviar
WD800BB - 80 GB 2 4
(WD1200BB series) V 7200 pcwd_abj.exe
WD600BB - 60 GB 2 3
WD400BB - 40 GB 1 2
WD200BB - 20 GB 1 1
WD400BB - 40 GB 1 2
WDxxxBB, Caviar
V WD300BB - 30 GB 1 2 7200 pcwd_abj.exe
(WD400BB series)
WD200BB - 20 GB 1 1
WD400EB - 40 GB 1 2
WDxxxEB, Protégé
V WD300EB - 30 GB 1 2 5400 pcwd_eb.exe
(WD400EB series)
WD200EB - 20 GB 1 1
WD1200AB - 120 GB 3 6
WD1000AB - 100 GB 3 5
WDxxxAB, Caviar
WD800AB - 80 GB 2 4
(WD1200AB series) V 5400 pcwd_abj.exe
WD600AB - 60 GB 2 3
WD400AB - 40 GB 1 2
WD200AB - 20 GB 1 1
WD153DA - 15.3 GB 1 2
WDxxxDA, Spartan V 4500 pcwd_da.exe
WD75DA - 7.5 GB 1 1
4. Utility usage
After utility start the following mode selection menu appears on the screen:
Standard mode
SAFE MODE
The Standard mode is the regular mode of utility operation provided that the drive can be initialized.
SAFE MODE serves for working individually with the printed circuit board (PCB) containing the electronic
components without a head-and-disk assembly (HDA). The drive switches to SAFE MODE if three jumpers are enabled
together: CS, SLAVE and MASTER.
In the Standard mode the utility does not check the family of the connected drive during launch (unlike earlier
versions of utilities for WD drives). Instead it displays an entry menu: Spartan, Protege or Caviar (depending upon the
launched utility). Users have to check personally the model of the connected drive. Pressing [Enter] will force reading
of the configuration modules and bring up the main menu of operation modes:
Disc Firmware zone
Drive description
Formatting
Logical structure scanning
S.M.A.R.T. table
Defects table
Automatic mode
Exit
Firmware zone – allows to format and test the service area of a drive, to view and check the firmware structure, to
rewrite the firmware completely and reconfigure the drive. Selection of that mode will bring up the following menu:
Viewing ROM information command displays on-screen firmware version, ROM revision (which might serve
as a family code), the version of the links’ table and a list of supported models together with information about heads
mapping:
Copyright 2001 WDC
ROM version : 06.40 G
ROM revision : 33
Links table version : 04.27
Supported models
WDC WD200BB
WDC WD400BB
WDC WD600BB
WDC WD800BB
WDC WD1000BB
WDC WD1200BB
Heads assignment data
Heads assignment : default
The data is valuable for estimation of compatibility between different ROM versions during selection of PCBs for
replacement.
Changing heads map in ROM1 command accomplishes software disabling or enabling of previously disabled
drive heads. When that mode is selected the cursor is positioned over the current variant of heads assignment: by
mapping or default, the variants are switched by pressing the [Space] key.
Selection of By default heads assignment means that HDD heads mapping will be formed according to the
results received after physical polling of the heads connected to pre-amplifier/commutator during the initialization
stage. Selection of assignment by mapping allows disabling of the internal map used for physical heads polling. In such
case a drive will not rely on the data about physically connected heads using instead the heads mapping data in ROM.
Then you must indicate the Full heads amount – i.e. the value of their maximum number allowed for that drive
family (usually 6). Then you can proceed and disable or enable drive heads using [Space]; pressing [Enter] will shift
the highlighted rectangle to the next head. After completion of the current operation you will see an offer to record thus
generated ROM to a file or write the modified heads mapping directly to the drive’s Flash ROM. Please see details
about the mechanism of ROM recording in the paragraph devoted to the Write ROM command.
If you define the flag “by mapping” for a HDD, which used By default heads mapping before that, then the
Full heads amount and Active heads values will equal 0, all heads become configured as disabled. In that case you
should set the value “Full heads amount” = 6 (as the maximum allowed in the drive family) and enable the suggested
heads, e.g. 0 and 1 for a model with 2 heads. If the drive starts knocking after that, it means that the heads have been
enabled incorrectly and you should attempt to select two other heads, e.g. 1 and 2, in Safe Mode.
Read ROM command accomplishes reading of ROM contents to a file with *.bin extension. If you select that
operation you should enter the file name without an extension. The read-in file will be placed in the current PC3000
subdirectory.
Write ROM2 command accomplishes recording of drive ROM from a file. During the procedure you should
first select the loader - module 61h or an external *.lmc module, then select a *.bin file to be recorded (it has to be in
the PC3000 subdirectory). When the file is selected, the actual recording process begins. The method of recording
ROM is described in more detail in section 8.
First of all, the utility lists the modules’ directory with a version actually representing the version of HDD
firmware portion recorded on disk surface (Disk F/W). Two new data tables have been also added into the report: DCM
Info and VER Info1. In fact they are logs containing certain ASCII information output by the utility. The DCM Info
table is stored in module ɋ5h, table VER Info is stored in module 4Eh:
DCM Info – the purpose of that table is not quite clear yet; it is likely to be useful in future during selection of
matching “donor" drives for replacement of heads assembly (HA) for data recovery. Please see details in section 5.2.1
VER Info table contains the versions of ROM, links table, and Disk F/W. That information is useful for
selection of matching PCB.
ATTENTION! The information in DCM Info and VER Info in the ɋ5h and 4Eh modules is optional; it is
generated in logs. Therefore absence of data or garbage in those tables does not indicate a drive’s malfunction.
Disc Firmware data read/write. The command accomplishes reading or recording of firmware data image
(tracks from -1 through -8 excluding track -7) from (to) an *.rsc resource file. The utility reads the number of sectors in
the firmware zone from the zone allocation table. If the table cannot be read, the operator will have to enter manually
the number of sectors per track for the firmware zone of that HDD model at utility launch.
Running the command is identical to the same procedure for the preceding drive families; please see the details
for the Disc Firmware data read/write command in the description for WD Arch.4 “PC-A313000, PC-A310100, PC-
A38400, PC-A36400”.
WARNING! Please note that the firmware zone occupies cylinders from -1 to -32, but the utility saves just
cylinders from -1 through -8 (except for cyl. -7), since we believe that it should be sufficient. That peculiarity
saves the space occupied by a resource file and the time required for reading. However, there may be certain
HDD modifications, for which not all of the firmware data will be read and recorded.
Read modules - this operation allows reading of HDD firmware stored in the modules directory within the disk
service area. The read modules are placed then into the WDxxxMOD subdirectory, where xxx:
DA_ - for WD Spartan
EB_ - for WD Protégé
ABJ - for WD Caviar
The name of each read module file is generated as follows: ~idxx.rpm, where:
xx the module identifier, e.g.: ~id20.rpm is the module of the 20h translator table.
Before the operation a list of modules available for reading appears on the screen, you will need to select either a
specific module in it or “ALL MODULES” item. In the latter case all the firmware modules will be read to the
WDxxxMOD subdirectory. If the subdirectory already contains modules with the same names, repeated reading will
overwrite them without notification.
WARNING! Not all the modules present in the firmware area are indicated in the modules directory; instead it
contains just modules required for HDD operation. Thus, for example, several auxiliary modules - Selfscan,
Selfscan results, etc. may be not included into the modules directory. Therefore it is recommended to use
firmware image reading method in order to save the firmware completely (please see the paragraph on firmware
data reading/writing).
Write modules – this operation allows recording of a firmware module (or modules) to the service area of the
drive. Prior to the procedure you will see a list of all modules in the WDɯɯɯMOD subdirectory available for writing.
The user has to select a certain module or the “ALL MODULES” option. In the latter case all the modules from the
WDɯɯɯMOD subdirectory will be written to the firmware zone. Module(s) checksum recalculation and correction takes
place before recording.
WARNING! The utility does not check the module structure before writing, therefore you should be extremely
attentive, otherwise you may irreversibly damage the drive.
Erase firmware area command fills all sectors in the service area with code 7777h using heads 0 and 1. All
information in that zone will be deleted. Before the operation you should enter the initial and ending cylinders, default
values are read from the zone allocation table (-32 .. -1).
The need for that operation arises when service area contains “garbage” preventing normal drive operation.
WARNING! All information within the firmware zone will be erased during area clearing. Therefore you should
save firmware data as modules and firmware zone image prior to the operation.
1 DCM Info and VER Info tables are missing in the WD Spartan drive family.
Technical support: eng_support@acelab.ru
(8632) 78-50-30, 78-50-40
www.acelab.ru 5
Western Digital "Spartan", "Protege", "Caviar" Generation electronics Arch-V, Arch-VI Ɋɋ-3000 £
"PCWD_DA", "PCWD_EB", "PCWD_ABJ", "PCWD_CB2" ¤ ACELab
Change servo area SPT command helps define the number of sectors per track for operations with service area
(from cyl. -32 through cyl. -1). The default value is read from the zone allocation table, the allowed maximum is limited
by the default 1361 cyl. value.
The SPT value has to be modified in cases when the command for reading zone allocation data returns invalid
information (negative values, garbage or error). In such cases you have to explicitly provide to the utility the number of
sectors per tract to use. The number of sectors in firmware zone can be identified by running the Disc Firmware surface
test. Sector numbers in that test grow sequentially beginning with 1. The maximum cylinder number will be the one
producing constant errors on all cylinders of firmware zone.
Security subsystem menu option contains commands, which allow reviewing and resetting master and user
passwords in a hard drive.
Drive description – brings the drive’s disk description on the screen. All non-displayable ASCII characters are replaced
with spaces. Drive’s description, i.e. logical structure parameters and serial number can be corrected. When it is
necessary to correct the model name you should first set MODEL FROM ROM parameter to NO by pressing [Space].
Press [Enter] to enter the parameter or to proceed to editing the next one; press [Esc] if you do not want to rewrite the
drive description area.
4.1.3. Formatting
Formatting – starts the low-level formatting procedure. During formatting the drive skips defective sectors and
defective tracks reading their numbers from the defects table (if the method using one or another table has been
selected). The formatting procedure cannot be interrupted because after its completion translator recalculation and
recording are performed. If format ends in error it means presence of corrupt servo information or incorrectly compiled
defects table. Even if formatting ends in error, the translator is recalculated and recorded, though not all the surface of
the drive will be formatted. Before the start of formatting you have to select the defects table mode or formatting
without defects table data. Formatting takes approximately 40 minutes, but it depends on the model, condition of
magnetic disks and can grow considerably with defective surfaces.
Logical structure scanning – starts the defects detection procedure utilizing logical parameters in LBA. The test routine
does not differ in any way from that for the previous drive families, please see details in the description for WD Arch.4
“PC-A313000, PC-A310100, PC-A38400, PC-A36400”.
S.M.A.R.T. table – allows viewing S.M.A.R.T. parameters of a drive. You can read in detail about S.M.A.R.T. in the
PC-3000AT tester description.
Defects table – allows to view, add, clear defects table or perform defects grouping:
View defects table. This command displays the table of relocated defects in a drive. Viewing defects’ tables
helps estimate the quality and status of the magnetic disks used in a drive. At the manufacturing factory defects are
added to P-List only; thus presence of records in the G-List means new defects.
Add physical track. Allows to enter physical defective tracks manually.
Import logical defects table. This command allows to add values from a *.dft file to the G-List table of defects.
Such a file may be prepared, for instance, by Defectoscope 2.10 software or any other program. The *.dft file structure
is described in the supplement to the Defectoscope utility. After adding the defects formatting must be performed.
Clear defects table. After execution of that command the respective defects table will be reset – the number of
defective sectors becomes equal to 0. The user has to select which table should be cleared.
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 reset 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 of Relocated Sector Count.
Group to tracks. This menu item allows to group into defective tracks those defective sectors, which already
are entered into the tables of defects. When you enter the mode you will see the message: LIMIT OF GROUPING
INTO TRACKS. Then you have to enter the limit value above which sector defects should be grouped into defective
tracks in both P-List and G-List tables. The input range is from 1 to 50.
The mode provides access to a limited number of drive features. The safe mode is meant for testing the printed circuit
boards (PCB) separately from their HDAs. However, after switching a drive into safe mode you may leave a PCB on its
HDA. In order to enable the safe mode you should set three jumpers at once: CS, SLAVE, MASTER and switch on the
power. The drive at that does not process bits D6 (DRDY) and D4 (DSC) in the status register. The following menu
appears after selection of that mode:
Work with ROM
PCB testing
Work with ROM menu option allows access to recording, reading and viewing of a drive’s ROM:
Viewing ROM information command displays on-screen firmware version, the version of the links’ table, the
list of models supported in that drive family and heads mapping:
Copyright 2001 WDC
ROM version : 06.40 G
ROM revision : 33
Links table version : 04.27
Supported models
WDC WD200BB
WDC WD400BB
WDC WD600BB
WDC WD800BB
WDC WD1000BB
WDC WD1200BB
U5
WD70C12-SW M29F102BB
U2
WDC © 2000
U4
MASTER 1
SLAVE U6
CS U3
1 U1 1. US1235
2. L6262 2.6
CS
CS
MASTER
SLAVE
SLAVE
MASTER
MASTER
MASTER
SLAVE
CS
Fig. 5.1. External view of the electronics board in Spartan drive family.
U4
U2
M29F102BB
U5
WD70C23-GP
D7
L6
1 U6 U8
MASTER
SLAVE U7
CS
1 U1 1. IRU1239SC
3 2. ST755
3. 50G64741
Q4 4. L6278 AC
CS
SLAVE
SLAVE
MASTER
MASTER
MASTER
MASTER
SLAVE
CS
Fig. 5.2. External view of the electronics board in Protege drive family.
U4
U2
M29F102BB
U5
WD70C23-GP
L6
D7
U6 U8
1
MASTER
SLAVE U7
CS
1 3 U1 1. IRU1329
2. ST755
3. 50G66474
Q4 4. L6278 1.2
CS
CS
SLAVE
SLAVE
SLAVE
MASTER
MASTER
MASTER
MASTER
SLAVE
CS
Fig. 5.3. External view of the electronics board in Caviar Arch. V drive family.
U4
U9
Q3 L7
U5
D7
WD70C22-GP
U12
U6
1
MASTER
SLAVE U7
CS 1. IRU1239SC
1 3 2. 26P10AV
3. 88C5540-LFE
4. L6282 3.2E
U1
5. 349T
6. 25 MHz
Standard Configuration Settings
Master only Master with Slave Slave Safe Mode
1 1 1 1
CS
SLAVE
CS
CS
MASTER
SLAVE
SLAVE
MASTER
MASTER
MASTER
SLAVE
CS
Fig. 5.4. External view of the electronics board in Caviar Arch. VI drive family.
Firmware of WD HDDs consists of a microprogram stored in ROM, a configuring links table also located in
ROM, a loadable firmware portion and data in the service area of a drive (DISK Firmware). The firmware is
characterized by its revision number (F/W Rev.), which defines its development and compatibility.
Firmware part Version, example Location
Microprogram 06.40G ROM
Links table 04.27 ROM
Loadable firmware version, tables 06.C0G Firmware zone, (cylinders -1 to -32)
You can find out the microcode version and the version of ROM links table using the Viewing ROM information
command. The version of loadable firmware portion (DISK F/W) can be displayed by running the Disc firmware
structure test menu item in the standard utility mode. The version indicated in the modules’ directory will be the
version of DISK F/W.
Version number output by the drive in the “firmware version" line after the Identify DRV (ECh) command, i.e.
when the drive ID is viewed, is an aggregative value and contains the information from all three parts of HDD
firmware, e.g.:
ROM firmware: 06.40G
ROM links table: 04.27
DISK F/W: 06.C0G
As a result the compiled version of HDD firmware will look like: 06.04G06. As it can be seen in this example, the
version number was formed using the first bytes from the respective versions of the HDD firmware parts. The letter is
borrowed from the version of ROM microcode. If you read microprogram version in Safe Mode, the DISK F/W part of
the version will be missing, because all operations with disk firmware portion are disabled in that mode.
Unlike the previous families of WD HDDs, in the Spartan, Caviar, and Protege the manufacturer discontinued
indication of firmware code on the ROM chip label. That complicates selection of replacement PCBs considerably.
Moreover, WD does not adhere to strict classification of Caviar and Protege trademarks and frequently totally identical
and compatible HDDs are named differently. One should also pay attention to the construction peculiarities of head-
and-disk assemblies and, consequently, of their PCBs. We mean the location of the mounting hole on a PCB near the
spindle motor connector. In several PCBs it is located along the centerline of the connector while in some PCBs it is
shifted away from that line, please see Fig.5.1-5.4.
We can offer the following compatibility criteria useful for electronics boards in WD HDDs. First of all, here
belongs the family code indicated in the MDL line over HDA label (see WD classification) and in Table 5.2.1.
Table 5.2.1 several drive family codes of WD HDDs
WD Spartan WD Protégé WD Caviar Arch. V WD Caviar Arch. VI
WD75DA-xxAWxx WD300EB-xxCPxx WD1200BB-xxCAxx WD1200JB-xxEVxx
WD400EB-xxCPxx WD600AB-xxCBxx WD1200JB-xxFUxx
WD800BB-xxCJxx
WD1200JB-xxCRxx
WD200BB-xxCVxx
WD1200BB-xxDAxx
WD400BB-xxDExx
WD200BB-xxDGxx
WD1200BB-xxKAxx
Secondly, you should note the version of firmware in ROM and the number of links’ table. Those numbers can be
identified by switching the PCB to Safe Mode and running the Viewing ROM information command. In the third place
note the mapping of HDD heads. It is also displayed together with reviewed ROM data showing the disabled and active
heads. There is very high probability that knocking sounds will be produced by “non-native” HDAs when used with
totally identical PCBs having compatible firmware versions just because different heads are indicated as enabled in
those boards. Please see details about the mechanism of heads selection during initialization in section 5.5.
The need for Head assembly (HA) replacement appears when it becomes damaged, i.e. when pre-
amplifier/commutator goes out of order or, more frequently, in case of MR heads’ malfunctions. In such situations a
drive after power-up produces knocking sounds hitting its positioner against the limiting stop. A HDD can be repaired
in case of such malfunction (if the defective MR head does not scratch disks) using software access to disable the
defective head. Of course, the drive’s capacity will decrease, but the HDD will become totally operational. If HDD
repair is of minor importance but valuable user data from that HDD have to be recovered, there is only one way
remaining – it is replacement of damaged HA with a known-good one taken from an operational HDD of the same
model.
Beginning with Arch. V (Spartan, Caviar, and Protege) WD drives demonstrate total disorder as regards
interchangeability of HA. Similar models (with identical MDL lines) may use different number of heads or their
different positions. According to our observational studies, the DCM line (see Fig. 5.2.1.) on HDA label contains
information valuable for compatibility. At least, the letters next to last in DCM of both drives should match if the same
preamplifier-commutators are used in HA (e.g. Fig. 5.2.1, number 2). We recommend using as “donors” drives with a
matching MDL line, matching 2-3 last letters/figures in DCM and with closest dates of manufacture.
S/N: WMAATC607218
MDL : WD300EB-75CPF0
DATE: 03 MAY 2003
DCM : DSBBNV2A
Fig. 5.2.1 Label of WD drives (preamplifier type denoted by figure 2 in DCM).
The utility outputs the DCM information line while reviewing firmware zone structure (see section 4.1.1.2.) displaying
DCM line decoded for a specific drive; however its purpose and applicability for “donor” selection are yet not clear,
probably, that information will be of use in future.
WD drives have 32 service cylinders (from –32 to –1) used for storage of firmware recorded in two copies
over sides 0 and 1. However only first 8 cylinders (-1 through -8) are actually used for recording of the firmware
modules. Firmware data are stored in the form of individual modules, which constitute together HDD control and
operating system. Navigation between the modules is performed in accordance with the modules’ directory containing
the address of each module, its identifier and length. Each module, in its turn, has a standard header containing its date,
checksum, identifier, version number and module length expressed in sectors. Please see the main DISK F/W modules
in the summary table below.
Table 5.3.1 Functional purpose of modules
Module Purpose
ID, hex
01 Loadable portion of firmware code
02 Loadable portion of firmware code
10 Loadable portion of firmware code
11 Loadable portion of firmware code
12 Loadable portion of firmware code
14 Loadable portion of firmware code
17 ? 2 sect. table (usually empty)
18 ? 2 sect. table (usually empty)
19 Loadable portion of firmware code
20 Translator
21 Translator
22 Translator
23 Translator
25 Translator
26 Module containing SMART parameters
29 Module containing SMART parameters
2A SMART log
2B SMART log
2C SMART log
2D Module containing SMART parameters
2E Initial table of SMART parameters, it is not used during drive operation and serves as a model
2F SMART/RESERV log
36 Loadable portion of firmware code
41 (~dir) Modules directory (the table of modules location within firmware zone)
42 Configuration table (HDD ID)
43 P-LIST defects table
44 G-LIST defects table
46 ? Adaptive parameters
48 ? Adaptive parameters
49 ? Adaptive parameters
4A ? Adaptive parameters
4B ? Adaptive parameters
4C ? Adaptive parameters
4D ? Adaptive parameters
4E Log (versions of: ROM firmware, links table in ROM, DISK F/W, lots of other info), frequently empty
59 4 sector table, purpose?
5A Table or log, occupies 1 sect., purpose?
5B Table or log, occupies 1 sect., purpose?
61 Loadable portion of firmware code, the part which performs overwriting of Flash ROM
7x Tables, 2 sector each, purpose?
BF Bit table, 2 sect., purpose?
C4 Calibrator module
ɋ5 Calibrator log
Ex Reserved?
Fx Reserved?
FF Selfscan module
The translator modules (20h – 25h) and modules containing adaptive parameters (46h-4Dh) are traditionally
essential for data integrity in drives belonging to Spartan, Caviar, Protege families, there may be other important
modules, but we haven’t identified any so far. Besides, yet unknown remains the degree of importance for the modules
containing adaptive parameters and the opportunities for their replacement if the original modules become corrupted.
If the translator modules get corrupted you can perform their recalculation based on the P and (or) G-List
defects tables and overwrite them. The procedure is performed by the Regenerate Translator command (please see
details on restoration of damaged modules in chapter 7).
5.4. Data structure in Flash ROM in WD Caviar and Protege drive families
The structure of parallel Flash ROM in those drives differs from earlier families. First of all, it is manifested in
the presence of heads’ table (there is no such table in earlier drive families, like WD-Spartan, WDxxxAA,).
Table 5.5.1 describes the structure of parallel Flash ROM contents, newer families are based on serial Flash
ROM chips using a different data structure.
Table 5.5.1
Address Length Purpose
0h 512 bytes Interrupt vectors
200 h … Microprocessor control firmware code
… …
1EBxx h 15 bytes Copyright 2001 WDC
1EBxx h 3 bytes WDC (keyword, followed by ROM firmware version)
+3 h 7 bytes ROM firmware version, ASCII
+A h 1 byte ROM revision (HDD family code)
+B h 120 bytes Supported HDD models (6 records, 20 bytes each, ASCII)
+83 h … Links table (configuring jump table)
… 5 bytes Links table version, ASCII (the last element of the links table)
1FFD0 h 31 bytes Table of active heads
+2 h 1 byte Heads table flag (00-assignment according to heads table, 01- according to MHA
polling)
+3h 1 byte Maximum possible number of heads for the drive family, usually 6
+4h 1 byte The number of active (enabled) heads
+5h 1 byte Bit map of active (enabled) heads
+ 31 h 1 byte Checksum byte for the heads’ table
… …
ROM data consists of executable microprocessor code and various tables including jump tables. However, those
portions do not have fixed constant addresses; their locations are floating depending upon ROM version, and that
circumstance complicates indexing of data tables. Therefore they are searched using keywords and offsets.
At power-up a drive configures itself as a specific model of its family during initialization. The FLT/SE signal
produced by the commutator pre-amplifier chip and MR heads polling are used for that purpose After spin-up of the
spindle motor the drive microprocessor sequentially checks all heads beginning with the zero one. When a missing head
is detected, the FLT/SE signal is sent to the microprocessor. Thus the drive determines precisely the number of heads
and configures itself as a corresponding model.
Beginning with Protege and Caviar drive families the manufacturer changed the algorithm of adjustment for
MHA type. ROM (beginning with address 1FFD0h) has been supplemented with heads mapping containing records of
their total number and enabled heads. The map contains a byte, which serves as a flag switching the method to be used
by microprocessor for identification of the total number of heads and the enabled ones – MHA polling or heads
mapping in ROM. During drive initialization its microprocessor reads the heads mapping byte after MR heads polling.
If the flag is not set, the processor uses information about drive heads received after MHA polling; if the byte is set, it
uses respectively the heads mapping in ROM. Then the drive configures itself as a specific HDD model and reads
firmware data.
The mechanism can be utilized to disable or enable previously disabled heads using software access.
Manufacturing factories frequently ship drives with some magnetic heads already disabled, they can be enabled using
software access and turn out to be absolutely operational! The need to use software access in order to disable/enable
drive heads arises when they become damaged or when you have to adapt a PCB to a HDA containing thus disabled
heads.
WARNING! If you define the flag “by mapping” for a HDD, which used default heads mapping before that, then
the Total number of heads and Active heads values will equal 0, thus all heads become configured as disabled.
In that case you should set the value “Full heads amount” = 6 (as the maximum allowed in the drive family)
and enable the suggested heads, e.g. 0 and 1 for a model with 2 heads. If the drive starts knocking after that, it means
that the heads have been enabled incorrectly and you should attempt to select two other heads, e.g. 1 and 2 or 2 and 3.
You can also try to enable heads one by one and thus determine all operational heads.
WARNING! If a drive starts knocking after modification of heads mapping, you have done something wrong. In
that case you should switch the PCB to Safe Mode and record the original ROM (saved prior to mapping
modification). Always save the native ROM before making changes to heads mapping.
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,
or it takes too long to report on readiness, then it means that the drive cannot read firmware data from disk. That kind of
defect may arise from:
- data reading/conversion channel malfunction;
- firmware modules corruption;
- incompatibility between the disk firmware version and the firmware code recorded in the control board
ROM.
In such case ensure that the control board is functional (the best method is swapping of the boards), the ROM and HDA
versions are compatible, and begin the hardware data restoration from step 1.
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 started from step 2.
1. Restore firmware data (F/W). The F/W restoration procedure is as follows:
a). Perform “DISC FIRMWARE STRUCTURE TEST” and identify corrupted modules. If just some modules
are damaged while others remain normal, you can overwrite the defective modules using the method described
in section 7.
b). If the majority of modules are corrupted in a drive select the “DISC FIRMWARE ZONE” menu option and
run the “DISC FIRMWARE SURFACE TEST” command. Make sure that there is no considerable damage in
firmware zone. If necessary, CLEAR FIRMWARE ZONE but prior to that procedure save modules, which can
be copied and firmware area image, see section 4.1.1.2.
c). Select the menu items: “DISC FIRMWARE DATA READ/WRITE”, “WRITE FW TO THE DISK” and write
the firmware data to the drive being restored, observe its compatibility with the version of the drive processor
microcode. After successful recording the firmware is restarted.
d). Correct the logical parameters, if necessary.
2. Clear the GLIST defects table and reset SMART. You will have to reset the P-LIST table if you have disabled HDD
heads, if external firmware has been recorded to the drive or if P-LIST has been copied from another drive.
3. Perform low-level formatting using P-LIST, which should complete successfully. If formatting ends in an error one
of drive surfaces may have corrupt servo information. You can attempt to use grouping into tracks (defective tracks
block corrupted servo fields) or isolate the side containing too many defects.
4. Perform LOGICAL STRUCTURE SCANNING procedure, which is executed in LBA format. After completion of
surface scanning procedure a table of all detected logical defects in LBA notation will be output on the screen. Pressing
[Enter] converts all logical defects into physical addresses and adds them to the G-LIST defects table.
5. Using the results of tests 3 and 4 make a conclusion concerning the necessity of defective surfaces isolation (see
section 5.5.). After turning off defective sides it is necessary to continue the drive restoration beginning with step 2.
6. Perform low-level format using P and G-List.
7. Write serial number into the drive ID area, if necessary.
8. Perform COMPLEX TEST with the PC-3000AT tester. If errors are detected repeat steps 3-6 or run the UNIVERSAL
DEFECTS RELOCATION procedure.
9. Run the PC-3000AT tester COMPLEX TEST and make sure that the drive is operational.
Translator restoration can be invoked as follows: Disc Firmware zone, Disc Firmware zone, Regenerate,
Translator. Upon entering the mode you will be offered to select the basic tables to be used for the recalculation:
Take into account PLIST and G-LIST
Take into account Use PLIST
Take into account Use G-LIST
Do not take into account neither PLIST nor G-LIST
Factory testing of a drive appends defects to the P-List table (primary) only; the G-List (Grown) table remains empty. It
is filled in the process of drive operation by the device itself in the Data Lifeguard and Assign modes. Thus, translator
of a drive arriving from a factory is recalculated using P-List only. Therefore if you restore a drive with corrupted 20h
and 25h modules, the procedure should be performed using P-List only, in that case access to user data will be restored.
In order to produce an external loader file copy the ~id61.rpm module from an operational drive with a Flash
ROM chip of the required type. Rename the file so that it receives the Loader Micro Code (lmc) extension.
The standard package contains several loaders to be selected in accordance with the families of drives being
repaired, see the table:
Family Original file Renamed loader file
WD Caviar Arch. VI, Serial ROM ? none
WD Caviar Arch. V ~id61.rpm Caviar
WD Protege ~id61.rpm Protege
WD Spartan ~id61.rpm Spartan
9. Electric circuit
WD Spartan, Protege, Caviar Arch. V and Caviar Arch. VI drives use different electronics boards (see Fig.5.1 - 5.4)
and electric circuits, but labels of elements on PCBs match in most cases. That helps to use the basic electric circuit
even in those cases, when it does not fully match the PCB of a HDD.
Checking all voltage generating devices (see electric circuits: WDxxxBB/JB R/W Channel, SPINDLE
MOTOR Control and WDxxxBB/JB L6278 1.2) is the first thing to do for diagnostics of malfunctions in the
electronics board of a HDD. WD Spartan, Protege, and Caviar drives use six voltages, they are: +12V, +5V (from the
PC power supply), +3.3V, +2.6V (generated by the U6 IRU1329SC stabilizer), +1.8V (generated by the U7 chip when
Technical support: pc-3000support@acelab.ru
(8632) 78-50-30, 78-50-40
16 www.acelab.ru
Ɋɋ-3000 £ Western Digital "Spartan", "Protege", "Caviar" Generation electronics Arch-V, Arch-VI
¤ ACELab "PCWD_DA", "PCWD_EB", "PCWD_ABJ", "PCWD_CB2"
an external power control on Q4 is employed) and a -5V source that supplies power to the preamplifier-commutator
(generated using the U8 chip of the DC-DC ST755 converter). In Caviar Arch. VI drives -5V negative voltage
generator is based upon the FG2M chip and Q3 power switch (see electric circuit WDxxxBB/JB Serial ROM,
Converter DC-DC -5V). It is essential to check +5V and -5V supply voltages directly over the J1 pocket-plate MHA
connector, pins 4 and 2 respectively (see electric circuit WDxxxBB/JB R/W Channel, SPINDLE MOTOR Control). A
malfunction may be manifested in divergence or absence of supply or reference voltages because of defective
stabilizers, power switches or their control schemes. You should also check the L2, L4, L5, and L6 filter inductors
since supply voltages may disappear when they are broken.
Use digital millivoltmeter and an oscilloscope for measurements of supply and reference voltages. The
voltmeter is useful for checking voltage values, oscilloscope checks pulses.
3
U12 +3.3V
JP2(1)
C IRF9240
WD70c22(101) 1 S Vcc 8
JP2(7)
2 Q HOLD 7 JP2(9)
1 2
WD70c22(104) WD70c22(108)
3 W C 6 JP2(4)
WD70c22(105) WD70c22(103) 3 2 1
JP2(8) 4 GND D 5 JP2(3)
WD70c22(102) FG2M
+5V
4 5
M25P10(SROM) C 4.7mkf
R 100om
+5V
C R25 C79 2
R Q3
1
R24 0om R21 C109
E36
IRF9240
3
A D2
Plug to HDA A
R
J1(2)
FG2M 5
C47 2.2mkF -5V
3 L L
FB Vin
SW 1
4 Sens
R GND
R R R R R124 R125 R R
C2
1om 1om 1om 1om 1om 1om 1om 1om
Title
WDxxxxBB/JB Serial ROM, Converter DC-DC -5V
Size Document Number Rev
A ACE Lab. PC-3000 Documentation 1
C
R (10k)
plug to HDA
-5V R 80 (0.5) C72 C33
J1(2)
19 R
D7 6 3
GND SS
R77(2om) R(1om) R(1om) L6
C80 R6
C R79
17 7 LX Vref 2
R1
Voice Coil
+5V 8 Vcc SHDN 1
R R R
33
32
31
30
29
28
27
26
25
24
23
33
32
31
30
29
28
27
26
25
24
23
34 34 22 22 +5V
C5 R28
35 35 21 21
WD70C23(56)
A J6
36 36 U1 20 20
E90 A
37 37 19 19 +12V SHUT-DOWN control(Vcc=ON,GND=OFF)
38 18
2 38 L6278 1.2 18
39 39 17 17 WD70C23-GP(80)
40 40 16 16 WD70C23-GP(84)
3
41 41 15 15 +3.3V
42 42 14 14 WD70C23-GP(89)
4
43 43 13 13 C5
44 44 12 12
R16 R15 R14
10
11
1
9
1
10
11
1
9
SPINDLE MOTOR C12 C6
C
D1
R23(10 kOM)
+12V
C9 C13
3.3V
Title
WD70C23-GP(82) WD70C23-GP(81) WD70C23-GP(83) WDxxxxBB/JB L6278 1.2
Size Document Number Rev
B ACE Lab. PC-3000 Documentation 1
U2 M29F102BB U4 K4S1616220
WD70C23(119) 1 A9 Vss 40
1 1 50 50
WD70C23(120) 2 A10 A8 39 WD70C23(98)
WD70C23(139) 2 2 49 49 WD70C23(147)
WD70C23(121) 3 A11 A7 38 WD70C23(99)
WD70C23(140) 3 3 48 48 WD70C23(149)
WD70C23(122) 4 A12 A6 37 WD70C23(100)
4 4 47 47
WD70C23(124) 5 A13 A5 36 WD70C23(101)
WD70C23(141) 5 5 46 46 WD70C23(150)
WD70C23(125) 6 A14 A4 35 WD70C23(103) L5
WD70C23(142) 6 6 45 45 WD70C23(151)
WD70C23(126) 7 A15 A3 34 WD70C23(104)
+3.3V 7 7 44 44
WD70C23(127) 8 NC A2 33 WD70C23(105)
WD70C23(143) 8 8 43 43 WD70C23(152)
WD70C23(128) 9 W A1 32 WD70C23(106)
WD70C23(144) 9 9 42 42 WD70C23(154)
+5V 10 Vcc A0 31 WD70C23(107)
R29 (10k) 10 41
E1 10 41 E
+3.3V 11 RP G 30 WD70C23(108)
WD70C23(145) 11 11 40 40 WD70C23(155)
WD70C23(129) 12 E DQ0 29 WD70C23(110)
WD70C23(146) 12 12 39 39 WD70C23(156)
WD70C23(130) 13 DQ15 DQ1 28 WD70C23(111)
A 13 13 38 38 A
WD70C23(131) 14 DQ14 DQ2 27 WD70C23(112)
E 14 14 37 37 E
WD70C23(132) 15 DQ13 DQ3 26 WD70C23(113)
WD70C23(168) 15 15 36 36
WD70C23(133) 16 DQ12 DQ4 25 WD70C23(114)
16 35 R36
WD70C23(169) 16 35 WD70C23(157)
WD70C23(135) 17 DQ11 DQ5 24 WD70C23(115) WD70C23(176)
WD70C23(170) 17 17 34 34
WD70C23(136) 18 DQ10 DQ6 23 WD70C23(116)
E 18 18 33 33 E
WD70C23(137) 19 DQ9 DQ7 22 WD70C23(117)
WD70C23(171) 19 19 32 32 WD70C23(160)
20 21 R17 (10k)
WD70C23(138) DQ8 Vss
WD70C23(172) 20 20 31 31 WD70C23(162)
C16 21 30
WD70C23(173) 21 30 WD70C23(163)
WD70C23(174) 22 22 29 29 WD70C23(164)
WD70C23(175) 23 23 28 28 WD70C23(165)
E 24 24 27 27 WD70C23(166)
25 25 26 26
Title
WDxxxxBB/JB ROM, RAM
Size Document Number Rev
A4 ACE Lab. PC-3000 Documentation 2
WD70C23(62)
C47 WD70C23(63) WD70C23(66)
J1
WD70C23(61)
R (10k) C64
WD70C23(57)
WD70C23(59)
WD70C23(58)
WD70C23(67)
19 plug to HDA C63
R 80 (0.5) C C33 WD70C23(68)
R (1.0) R(1.0)
-5V
WD70C23(64)
J1(2)
R1
17
C61 C71 U8 ST755 C68
C
R C
Voice Coil 5 4
C53
R R65 Vo CC
R C28 C26
R WD70C23(55)
plug to HDA D7 6 GND SS 3
L6 R
60
59
58
57
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
C80 R6
plug to HDA C48
7 2
60
59
58
57
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
LX Vref
61 61 40 40
J1(20)
C C E 62 39
D2 J1(18) 62 39 WD70C23(69)
8 Vcc SHDN 1
+12V +5V
63 63 38 38
C13 C9 J1(14) WD70C23(70)
36
35
34
33
32
31
30
29
28
27
26
25
C57 64 37
C86 64 37 WD70C23(71)
Converter
36
35
34
33
32
31
30
29
28
27
26
25
37 24 65 36
37 24 +5V DC-DC -5V 65 36 C45
38 38 23 23 E 66 66 35 35
39 22 R9 C 67 34
40
39
40 U1
22
21 21
E
+12V
68
67
68
U7 34
33 33
WD70C23(73)
WD70C23(72)
SHUT-DOWN control(Vcc=ON,GND=OFF) C35
41 41 20 20 69 69 32 32
WD70C23(74)
42 42 L6278AC 19 19
R39 WD70C23(80)
R28 (470)
plug to HDA C36
70 70
50G6474 IBMBM 1.1 31 31 WD70C23(75)
R14 WD70C23(56)
43 43 18 18 WD70C23(84) 71 71 30 30
C44
J1(1) E5
44 44 17 17 72 72 29 29
WD70C23(76)
R15 45 16 73 28
45 16 WD70C23(89) J1(3) L4 E 73 28 WD70C23(77)
46 46 15 15 E 74 74 27 27 WD70C23(78)
R16 C5 J1(4) +5V
47 47 14 14 3.3V VOLTAGE REGULATOR C58 + 100mkf E 75 75 26 26
48 13 U6 IRU1329SC 76 25 C43
48 3 J1(10) 76 25
121
10
11
1
77 77 24 24
C6 WD70C23(79)
10
11
12
1
78 23
A J1(7)
79
78 23
22
C42 A
J1(5) 79 22
1.24V
GND
1.2V
3.3V
2.6V
Vdd
Vcc
C8 80 21
80 21 WD70C23(93)
10
11
12
13
14
15
16
17
18
19
20
1
9
C12 R10 R2 (0)
+3.3V Y1
1
10
11
12
13
14
15
16
17
18
19
20
R23(10k)
9
4 3
+5V +12V
5 2
R24
6 1
J6 1 2 3 4 WD70C23 (82) (81) WD70C23(83) C
L2
+3.3V
+ C50 100mkf
C17 C18 C C C C
Q4
SPINDLE MOTOR
1
+2.6V +1.8V
3 2
+3.3V
+2.6V C76
REGULATOR +1.8V C66 C65
WD70C23(153) WD70C23(2) WD70C23(43) WD70C23(88) WD70C23(118) WD70C23(134) WD70C23(25) WD70C23(102) WD70C23(65) WD70C23(94) WD70C23(161)
Q4 2
C19 C20 C22 C52 C55 C56 C31 C34 C40 C C49
1 2 3
U6
IRU1329C
Title
1 2 3 4 5 6 7 WDxxxxBB/JB R/W Channel, SPINDLE MOTOR Control
Size Document Number Rev
ACE Lab. PC-3000 Documentation 1
A
Ɋɋ-3000 £
¤ ACELab Fujitsu MPF-AT, MPG
Contents
1. Introduction.....................................................................................................................................................................2
2. Structure of drive families...............................................................................................................................................2
3. Basic options for repair of Fujitsu drives........................................................................................................................2
4. Preparation for work. ......................................................................................................................................................2
5. Utility usage. ...................................................................................................................................................................3
5.1. Servo test................................................................................................................................................................3
5.2. Surface scanning. ...................................................................................................................................................4
5.3. Disk firmware zone................................................................................................................................................5
5.4. Drive ID. ................................................................................................................................................................8
5.5. Formatting..............................................................................................................................................................8
5.6. Logical scanning. ...................................................................................................................................................8
5.7. S.M.A.R.T. table ....................................................................................................................................................9
5.8. Defects table...........................................................................................................................................................9
5.9. Automatic mode...................................................................................................................................................10
6. Brief technical description of ARM7-based families of Fujitsu drives.........................................................................10
6.1. MPF3xxxAT family.............................................................................................................................................10
6.1.1. Disk space organization in MPF3xxxAT family drives................................................................................10
6.1.2. Modification of drive configuration..............................................................................................................12
6.2. MPG3xxxAT/H/E family.....................................................................................................................................13
6.2.1. Disk space organization in MPG3xxxAT/H/E family drives........................................................................13
6.2.2. Modification of drive configuration..............................................................................................................15
7. Repair of ARM7-based Fujitsu drives. .........................................................................................................................16
7.1. Hardware repair. ..................................................................................................................................................16
7.1.1. Structure chart...............................................................................................................................................16
7.1.2. Initialization. .................................................................................................................................................17
7.1.3. Microcircuitry malfunctions..........................................................................................................................17
7.2. Software repair.....................................................................................................................................................18
7.2.1. Drive restoration algorithm. ..........................................................................................................................18
7.2.2. Tests' duration. ..............................................................................................................................................19
8. Special utility files for Fujitsu drives. ...........................................................................................................................19
9. Restoration of hardware modules in the MPF-AT and MPG families..........................................................................20
10. ROM data structure in MPF-AT and MPG drive families..........................................................................................20
10.1. Mutex byte in ROM. ..........................................................................................................................................21
11. On compatibility between ROM firmware and HDA service data in MPF-AT and MPG drive families (boards
compatibility)....................................................................................................................................................................21
12. Data saving peculiarity in MPF-AT and MPG drive families. ...................................................................................22
13. Password disabling. ....................................................................................................................................................23
14. Patching the module ID=3Dh in non-standard models of MPF-AT, and MPG drive families...................................23
14.1. Fujitsu MPF-AT (PB15). ...................................................................................................................................24
14.2. Fujitsu MPG-AT E (PB16E)..............................................................................................................................24
14.3. Fujitsu MPG-AT (PB16)....................................................................................................................................24
14.4. Fujitsu MPG-AH (PB16 AH), Fujitsu MPG AHE (PB16 AH E)......................................................................24
15. ROM reading/writing to PCB without a HDA (kernel - mode)..................................................................................25
16. Translator recalculation. .............................................................................................................................................25
17. Work with adaptive data. ............................................................................................................................................25
18. Addition of the new firmware ROM into the file Fujitsu.ini. .....................................................................................26
19. Pcb circuit. ..................................................................................................................................................................27
1. Introduction.
This manual contains descriptions of 3" family drives manufactured by Fujitsu Co, Ltd. and based on 32-bit
ARM7 processor of the Advanced Risk Machines (ARM) integrated together with drive electronic components by
Cirrus Logic as well as methods of their repair. It also covers methods of software restoration using PC-3000 complex.
This architecture differs mostly from the previous one based on MB9000 microprocessor by its use of loaded
firmware code. A portion of control code is stored in the control board ROM while another portion is recorded in
firmware zone of module 3Dh and loaded to RAM during initialization. Therefore a mode of direct service data loading
to drive RAM is provided for in the utilities.
1
Recorded in service zone of module 3Dh on disk;
5. Utility usage.
After utility start the following mode selection menu appears on the screen:
Standard mode
Kernel - mode
The standard mode is the regular mode of utility operation provided ROM can be read.
Kernel - mode is designed for writing/reading of FLASH ROM in cases, when ROM cannot be read, when ROM
firmware version does not correspond to service data version of the head-and-disk assembly or when ROM firmware
contains adaptive data that is not native for the drive. Kernel mode operation is further described in detail in a chapter
under the same title. (See part 15).
If the standard mode is selected, the utility reads drive ROM header, determines firmware version and adjusts itself
according to ROM configuration tables (table of modules, table of zone distribution, etc.). If ROM cannot be read the
following message is output:
Error reading ROM
You'll be offered to press [Enter] – and setup the utility using a file (containing previously read ROM data). You'll have
to indicate a file containing ROM firmware with a corresponding version1. Otherwise you should press [Esc] – and start
operating the utility with default parameters. If the ROM has been read but is not recognized by the utility, the
following message appears:
Unknown drive ROM firmware discovered (F/W=xxɯɯ)2.
Using default parameters.
You'll be offered to press [Esc] to leave or [Enter] to continue (in that case the utility may operate erroneously). Then a
list of basic family models will appear. After model selection and pressing [Enter] the program reads the drive's
configuration tables and verifies their conformity to physical parameters of the selected drive. If they match the
program will bring up the main operating modes menu:
Servo test
Surface scanning
Disk firmware zone
Drive ID
Formatting
Logical scanning
S.M.A.R.T. table
Defects table
Automatic mode
Exit
If there is no match, the following message appears:
Model adjusted according to the number of physically present heads.
It indicates that the basic model configuration has been changed.
1
ROM version number can be seen on HDA label, see Chapter 11
2
if: ɯɯɯɯ=FFFF, ROM has been read but it could not be recognized;
ɯɯɯɯ=0000, ROM could not be read.
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 PL table and defective tracks – to the TS1 table. If there is no need to hide the
defects, please press [Esc].
During servo test surfaces are formatted track-by-track. That is "physical" formatting unlike logical format
procedure (accomplished, for instance, during factory formatting), therefore in order to perform further drive testing,
i.e. to carry out subsequent scanning of surfaces for physical parameters compliance, you'll have to run servo test from
the beginning to the end of the user data zone on every surface. And vice versa, for testing of the drive's logical
parameters you'll have to accomplish factory formatting without errors.
1
- In the MPF3xxxAT family defective tracks are recorded to the CS table and hidden as cylinder defects.
1
There is firmware update software (see http://www.fel.fujitsu.com/home/drivers.asp?L=en&CID=1).
Disk service data check. Selection of this command brings the following list of basic modules on screen:
SN (Serial number) module – contains the drive's serial number;
HS (Head Select) module – contains the total number of heads and numbers of the used ones;
TS (Track Skip, for MPG-AT/H/E) module – drive's table of defective tracks;
CS (Cylinder Skip, for MPF-AT) module – drive's table of defective cylinders;
PL (Primary List) module – drive's table of defective sectors;
FI (Factory Information) module – contains information on production cycle. Of all the data the utility displays just
the date of drive manufacture.
CI (Components Information) module – contains information about HDA components: magnetic discs (MEDIA),
heads (HEADS), preamplifier/commutator microcircuit (HD-IC), spindle motor (DCM);
ZP (Zones Plan) module – contains information on allocation of zones;
SM (Security Master) module – contains information about master password;
SU (Security User) module – contains information about user password.
Following the list of basic modules a list of FIRMWARE MODULES is output as follows:
# ID Name Length Output Identification
where:
# - module number;
ID – module descriptor;
Name – module key name;
Length – module length in sectors;
Output – result of module reading;
Identification – result of module header comparison.
Resource – is a place of pickup the module: HDA from service zone and ROM from the RAM of the pcb. At
correct initialization of HDD the modules from service zone is copying in RAM of pcb. If the HDD has reading of
service information problems (errors in HDA strikes) the value in the strike ROM will show errors (modules errors in
RAM), except the modules which are loaded in RAM by defaults from ROM.
Drive service data writing/reading. This command records all the necessary data into the disk service zone. It
is necessary to re-write the service data if it is corrupt or if drive’s electronic circuit board was replaced during repair
(or ROM program was changed) and the version of microprocessor control program of the new board is incompatible
with the resident HDA microprogram. In order to write the service data you should select the menu option “WRITE
FIRMWARE FROM DATABASE TO DISK”, ROM version and appropriate service data version. You'll be offered to
write to drive’s RAM or to disk service zone. In order to accomplish a flawless writing the service data should first be
written to RAM, and only then to disk. Upon completion of writing to the disk it is necessary to switch off/on drive
power supply, clean the PL and TS (CS) tables of defects and switch off/on the drive power supply again. In case
you use PC-3K PWR adapter the whole switching procedure is performed automatically.
Attention! The utility checks whether the service data matches the version of ROM being recorded to. In case
of mismatch a notification will appear with an offer to write compatible modules only. In such case even after
successful writing completion an error message will appear on screen.
This utility enables the user to create and supplement a firmware database. In order to add a new firmware version to
the database you'll have to connect a good drive with that firmware and select the («ADD FIRMWARE TO
DATABASE») option; then the processor firmware version and model name should be input, for example: 82-80C2
MPG310AT. If firmware has been added with errors it can be deleted using the option «REMOVE FIRMWARE
FROM THE DATABASE».
Attention! If the utility recognizes the ROM1 it works with the list of modules taken from the drive ROM
during subsequent service data writing and reading. But it is possible that some of the modules have not been recorded
by the manufacturer on an absolutely functional disk. In that case the utility will notify about module absence and offer
to stop the writing/reading operation or to continue. If it is known a priori that the drive being read is good then the
operation may be continued, for it will be accomplished correctly. Such peculiarity of work is caused by certain
confusion at the manufacturing plant. For example, the ROM modules' list contains module ID=00h, however, there is
no such module in actual drives, therefore utilities block it.
Modules reading – the operation allows reading the drive hardware data in the order of its storage in HDD service
zone. Read modules are placed in a respective subdirectory (see Table 5.3.1):
1
If the utility could not recognize the drive ROM all the operations are performed with a reduced set of default
modules.
Table 5.3.1
Family Utility name Subdirectory for work with modules
MPG3xxxAT/E Pcfujmpg FUJMODGA
MPG3xxxAH/E Pcfjmpgh FUJMODGH
MPF3xxxAT Pcfujmpf FUJMODF
TAU, MPA-MPE, All Arh. MB9000 utilities FUJ_MOD
MPF3xxxAH
The name for every read file is generated as follows:
~PR ID NAME.rpm, where:
~ - the symbol identifying a firmware module;
PR – module type, 01 - module from the disc, 02 – module from RAM, Hex byte;
ID – module’s descriptor, Hex byte;
NAME – file name, it can contain from 2 to 3 ASCII symbols.
For example: ~010csm.rpm – means master password module SM read from disc; ~0204hs.rpm – HS module (heads
selection) read from RAM.
Prior to execution of modules reading operation a list of modules available for reading appears on screen, where you
should pick up any specific module or the «ALL MODULES» option using the [SPACE] key. In the latter case all the
service data modules are read into respective subdirectories (see table 5.3.1). If a subdirectory already contains modules
with the same names, the reading procedure will overwrite them without warning.
Modules writing – the operation allows to write a service data module (or modules) to the drive's service zone
or RAM. Prior to execution of this operation a list of modules in the modules work subdirectory (see Table 5.3.1)
available for writing appears on the screen, where you should pick up any specific module or the «ALL MODULES»
option using the [SPACE] key. In the latter case the utility offers to select writing modules to disk or to RAM, where all
the modules located in a respective subdirectory will be subsequently written.
Attention! During the writing process the utility doesn’t check module’s structure, therefore it is necessary to
exercise extreme caution while using this operation otherwise the disk can become irreversibly damaged.
Translator recalculation – that menu option is meant for restoration of static translator part (DM module) on
the basis of the PL table. Complete translator restoration also requires to provide for accuracy of its dynamic part (TS
module).
Safety subsystem – allows viewing set passwords and resetting them without corrupting user’s data if needed.
Log cleanup – it allows to perform the cleanup of modules containing the list of errors which HDD have
found during the work. These modules are 27h, 28h, 2Dh (FA), 31h(RE), 32h(WE), 70h and for the families MPG-
AT/AH additional modules 51h ɢ 52h.
Heads deactivation performs software deactivation of defective drive heads, inverse operation is also possible.
Prior to switching-off make sure that there are no records about heads being deactivated in the defects table, otherwise
the defects table should be reset first. When the heads deactivation mode is selected the table of used heads appears on
screen and you are prompted to switch the defective heads off or to switch operable ones on. After entering this mode
the blinking cursor appears at the first head. Press the [Space] key to switch the head off/on, and [Enter] - to move to
the next one. Press [Esc] to cancel this mode. Any head can be switched off, unless a restriction exists in the family.
Attention! After software heads de/activation it is necessary to switch off/on drive power supply and reboot the
utility! In case of software heads de/activation drives automatically change model name after reboot, with the exception
of nonstandard models (please see Chapter 14).
Spindle stop commands to stop the drive spindle. This mode is used during performance of HOT SWAP
boards replacement and might be used in the process of user’s data recovery.
Work with adaptive data offers two modes – "adaptives transfer" and "adaptives matching".
Adaptives transfer menu option serves for copying the adaptive data from one file to another. No actions are
performed with the connected drive. The pop-up window allows to select the type and name for source adaptive data
file and the destination file. The file type is determined by the location of adaptive data block in it. There are two
defined file types: "ROM file" and "module file". In case of work with ROM file the adaptives are located at offset
FDE0h. In case of work with the module 20h the adaptives are located at file beginning. After input of all the necessary
parameters the utility will perform actual transfer of 512 bytes of the adaptive data from one file to the other.
Adaptives matching menu option is designed to search for adaptive data matching the current drive in the
existing file set. In order to work with a drive you'll have to find a firmware that would quite promptly (in less than 1
min.) set the drive on readiness without knocking sounds. Files with adaptive data should be located in the ADP_DIR
subdirectory of the utility directory. In the process of work the utility will sequentially load adaptives from source files
to drive RAM and attempt to read module 20h from disk surface. If reading operation is successful the report will
include the name of the file containing adaptives that allow to read module 20h and the name of the file to which the
20h module has actually been read. You can break the matching process at any time by pressing [ESC]. In such case, as
with completion of matching all the source files, you'll see a brief report (containing a list of successful operations only)
on performed works. A complete report that allows to find out, which files have been processed but did not match,
names of matching adaptive data files and downloaded 20h modules can be found in the file ADP_DIR\adp_find.log.
5.5. Formatting.
Formatting option starts the native format procedure (Low-Level Format). Prior to the formatting procedure the drive
will erase the translator tables, check the defects tables for quantity and accuracy and start the actual formatting
process, when the drive skips defective sectors and defective tracks, the numbers of which it reads from the defects
table. The formatting procedure cannot be interrupted since after its completion a recalculation and translator recording
takes place. If format ends in error it means presence of corrupt servo information or incorrectly compiled defects table
(illegal values or values exceeding limits), in such case the drive's translator will not be recalculated, which will render
impossible its work using the logical parameters. Therefore it is recommended to save in a temporary file the service
data prior to formatting start to allow its subsequent restoration. Formatting takes approximately 20 minutes, but it
depends on the model, condition of magnetic disks and can increase considerably for defective surfaces.
Formatting error can appear immediately after the formatting procedure begins in case of incorrect PL and TS
(CS) tables' contents. For instance, that happens if some heads were switched off in the process while the PL and TS
defects tables contain left-over notes about defects for deactivated heads. That will be indicated in PL and TS tables by
the difference between the total number of defective sectors and their total amount for the remaining heads. In that case,
it is necessary to reset the tables of defects.
You should remember to group defective sectors into tracks. The following threshold values are allowed for MPG
drives:
- the number of P-LIST records does not exceed 5200;
- the number of defective sectors in one track does not exceed 63;
- consecutive chain of track defects in TS does not exceed 128 cylinders.
If an error occurs the contents of drive's registers is output on the screen. In some cases the information can be
useful, thus the 04h (ABRT) formatting error indicates incorrectly created PL, TS (CS) tables of defects, for example,
containing more than 63 defects per track. In that case the registers 1F4 and 1F5 will contain the defective cylinder
number and 1F6 – head number. Formatting error 18h means corruption of servo information; registers 1F3 - 1F6
contain LBA, where a corrupt servo field has been discovered. The information can be used for drive capacity
restriction from the end.
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 from 1 to 10.
Critical time – determines latency time of performing the operations read (or write). If this period is exceeded
the sector is considered defects. The limitation of inputs are 10ms up to 999 ms, by defaults parameters it is indicated
100 ms. The reducing of critical time should be performed very carefully. Too small value of critical time (depends of
the model of HDD, concrete model of pc where the test is performing) can caused the faulse error. Moreover,
periodically the HDD is performing termocalibration and this can be considered as error.
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.
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 PL table. After that the formatting
procedure should be performed.
The test setup menu contains recommended parameters by default.
The records demonstrate that the defect is a scratch, but the table contains no records on cylinder no. 746, where sector
46 supposedly should be defective. It is recommended to add such defects to the table. Formatting is required after
adding defects to the table.
Add physical track (cylinder). The operation allows to enter physical defective tracks (cylinder for MPF-AT)
manually.
Group into tracks (cylinders). This menu item allows to group into defective tracks those defective sectors,
which already are entered into the PL defects table. When you enter the mode the message: LIMIT OF GROUPING
INTO TRACKS appears, and you are prompted to input the threshold value above which sector defects are to be
grouped into defective tracks (cylinders) and added to the TS (CS) table.
Group tracks into cylinders- it allows to regroup track defects into cylinders (only for the family MPG-
AT/AH). In this connection all tracks defects which are in the table TS must be automatically copied by all heads of
defective track. Such operation allows to hide defects better.
Import of logical defects table. This command allows to add values from a *.bad file to the defects table. Such
file can be prepared, for instance, by PC-DEFECTOSCOPE software. The pcdefect.bad file structure is described in the
manual for the PC-DEFECTOSCOPE utility. After adding the defects formatting procedure must be performed (please
see Chapter 5.5).
Clear defects table. You'll be offered to reset the defects table(s). After the execution of this command the
selected defects table(s) is cleaned-up – the number of defective sectors is made equal to zero. In case of TS (CS) table
erasing it is necessary to switch off/on the drive power supply to force reloading of dynamic tables; if you use PC-3K
PWR adapter the operation is performed automatically.
1
- full capacity available in LBA mode only.
CA21246
-B76X
28F1101T
HA13626
PFT
1 3
W981616AH
1. 20.0 MHz
2. BA3946
3. TA7BM08F
Jumper Configuration
Master Slave Cable Select Slave Present
2 4 6 8 2 4 6 8 2 4 6 8 2 4 6 8
1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9
Fig.6.1.2. External view of MPF3xxxxAT control board.
Translation from LCHS or LBA into actual physical representation is achieved in the same manner as in the MPE
drive family. One distinctive feature is the initial cylinder in the user's data zone. The said zone in the MPF3xxxxAT
family starts from cylinder 0, which corresponds directly to the logical zero cylinder.
H3
H2
H1
H0
Reconfiguration can be performed from the top downwards by switching off defective surfaces and magnetic
disks. Besides, not only top surfaces can be switched off but also those in the middle of the package. Junior models are
thus created from the top ones. In case of configuration modification the model name, logical drive parameters and
translator’s operation are set up automatically. Monosurface model is an exception, and requires updating of module
ID=3Dh. Upon completion of configuration modification it is necessary to switch the drive power supply off/on in
order to initialize such drive with new parameters, and reload the utility, selecting a basic model at utility start.
The firmware zone is inaccessible in an apparent form and is represented by modules, available through their
identification numbers (ID). Those modules contain essential configuration tables of the drive, and unlike previous
drive families, also resident microcode for the controlling microprocessor in the module identified as 3Dh.
During initialization the module is loaded to HDD RAM, and along with ROM it forms the drive controlling
microprogram. Module 3Dh is registered as ROM (it has a corresponding header), and an absolute version match
between that module and ROM firmware is an essential condition. If module 3Dh has not been loaded into RAM the
drive cannot be operated, besides, the commands of modules writing/reading in the disk service zone do not work. In
such case it is necessary to load hardware data into drive RAM first, and then write the data to the drive hardware zone.
Modules are handled through their road map located in the ROM microcircuit on the control board. In case if the
ROM version has not been recognized (modules road map has not been found) then operations with hardware zone are
performed by default in accordance with the following table:
Capacity of the PL sector defects table is 5243 defects as sum total for all surfaces. Capacity of the TS cylinder
defects table is 3319 defects as sum total for all surfaces.
As it has been stated above, unlike the previous Arh. MB9000 families the firmware contained in ROM on the
control board of the Arh. ARM7 HDD family is insufficient for drive operation. A part of microprocessor code
necessary for drive operation, is located in the drive service zone, and loaded during initialization into RAM for
subsequent use of the code. Therefore, if drive hardware data is corrupt, performance of a writing procedure requires
loading of hardware data into RAM first with its further writing onto the drive. Please see Chapter 11 of this manual
for details on microcode compatibility.
External view of MPGxxxxAT/H/E control board is shown in Fig. 6.2.5.
1
1
2
1. HA13627
2. DI758
3. LE28F1101T-40
Jumper Configuration
Master Slave Cable Select Slave Present
2 4 6 8 2 4 6 8 2 4 6 8 2 4 6 8
1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9
Fig.6.2.5. External view of MPG3xxxAT/H/E control board.
Table 6.2.2.
Family Model Number of surfaces
MPG3307AT 4
MPG3153AT 3
PB16
MPG3153AT 2
MPG3153AT 1
MPG3409AT 4
MPG3102AT 3
PB16E
MPG3204AT 2
MPG3102AT 1
MPG3204AH 4
MPG3102AH 3
PB16H
MPG3102AH 2
MPG3102AH 1
MPF3409AT 4
MPF3307AT 3
PB16HE
MPF3204AT 2
MPF3102AT 1
H3
H2
H1
H0
Flach ROM
RDC
64K x 16 bits
CL-SH3515
ATA HDC
Series Termination SH7661 Head IC SVC
I/F SR1756 HA13627
- PIO Mode-4
- Multiword DMA Mode-2 R/W SPM/VCM
- Ultra DMA Mode-2 (66.6 MB/s) control
- Ultra DMA Mode-2 (100 MB/s) Buffer Bandwidth = 160.0 MB/s
Data Buffer
256K x 16 bits
or
1024K x 16 bits
7.1.2. Initialization.
The drive initializes itself at power-up:
1. Power-up.
2. Self-diagnostics 1:
- data bus and MPU address test;
- writing/reading test of microcircuit registers via internal data bus;
- internal RAM writing/reading test.
3. Spindle motor start-up.
4. Self-diagnostics 2:
- buffer RAM writing/reading test.
5. Stabilizing the spindle motor rotation speed.
6. Heads release from latch (magnetic heads' unparking).
7. Service data reading.
8. Recalibration start.
9. Setting itself in readiness mode (ATA command waiting).
HA13627 microcircuit is used in MPG families and frequently enough suffers from the substrate separation defect and
local overheating of the crystal. With such malfunction the drive spins up normally, sets on readiness, operates, and
after a while the spindle motor stops. (it’s a defect similar to TDA5247HT microcircuit of the Quantum drives).
3. Integrated chipset (CL-SH8669 in MPF-AT and CL-SH8671 in MPG family), contains the ARM7TDMI processor,
CL-SH3515 reading/writing channel (the microcircuit was used separately in MPF-AH drives) and CL-SH7661
interface controller. This circuit is the weak spot of MPF-AT and (especially) MPG drives, it causes 90% of troubles
with those drives. The malfunction becomes apparent after circuitry heating (especially in summer period) during
writing cycles. As a rule in such cases a drive corrupts its own firmware modules. One can indirectly judge about the
microcircuit operability by activity in data bus lines, connected to ROM and buffer RAM chip. If there is none you
should check the presence of power voltage and clock generation or a steady "RESET" signal. Complete check of
integrated chipset requires drive testing in PC-3000AT in cyclic mode with writing set on for at least 3 full passes. If a
drive malfunctions, hangs (does not report readiness), erases firmware modules, then the circuit is defective. In some
cases this can be corrected by microcircuit unsoldering, solder alloy replacement on board pads and the circuit, flushing
the residue of old fusing agent and subsequent soldering the microcircuit back with obligatory flushing.
- reset SMART.
3. Run SERVO TEST. During testing a track-by-track surface formatting is performed, the testing procedure measures
the time of decoding for all the servo fields on the current track and the obtained value is shown on a respective
diagram. When the test is complete the table containing the number of the defective sectors appears on the screen.
Pressing the [Enter] key will write all the defective sectors into the PL-table, and defective tracks into the TS (CS)
table. Servo test shouldn’t be interrupted and must be accomplished from the beginning to the end.
4. Run SURFACE SCANNING. The test checks physical parameters. When the surface test procedure is complete a
table containing the number of defective sectors appears on the screen. Pressing the [Enter] key will write all the
defective sectors into the PL-table, and defective tracks into the TS (CS) table.
5. To perform the group of tracks into the cylinders (only for the family MPG-AT/AH).
6. On completion of the tests 3 and 4 according to their results make a conclusion about the necessity of switching
some surfaces off. For example, you can switch off the surfaces with extensive servo corruption, or surfaces containing
maximal number of defects. After surfaces deactivation it is necessary to switch the drive power supply off/on and
restart the program, having selected a new model at utility start, and proceed with hardware restoration from step 2.
7. Perform low-level (factory) format procedure, which should be accomplished successfully. If formatting ends in
error you should repeat steps 3, 4, and 5.
8. Run LOGICAL SCANNING procedure performed in LBA format. It is possible to switch writing off and perform
verification instead of reading to speed up testing considerably, see Chapter 5. When the surface scanning procedure is
over the table of all discovered logical defects in LBA notation appears on screen. Pressing the [Enter] key translates
logical defects into physical and displays them on screen; second pressing [Enter] key appends all the defects to the PL
table. After that step 8 should be performed. If the logical scanning didn’t detect any errors, then proceed with step 9.
9. Perform low-level (factory) format procedure, which should be accomplished successfully.
10. Record serial number to drive ID if necessary.
11. Run PC-3000AT COMPLEX TEST. If an error is discovered, repeat steps 7 and 8.
12. Run PC-3000AT COMPLEX TEST and make sure the drive is fully functional.
1
- average testing duration is indicated, it can increase considerably if defects are numerous.
2
- with default test setup parameters.
*.rpm – technological files of the drives' resident firmware modules. During the reading procedure they are
copied to their respective directory (see Table 5.3.1).
*.log files can be viewed as regular text files; *.bin files can be viewed as binary files.
1
Module 60h is not used in several models, so it can be left without re-writing.
1
- adaptives are recorded both to ROM and service data module 20h on disk.
C:\
PC-3000
ROM
DATA
MPG
PB16
PB16E MPG3102A.001
FUJMODGA
PB16H
pcfujmpg.rsc
PB16AHE
rom.bin
readme.txt
MPG3102A.002
MPG3204A.001
14.4. Fujitsu MPG-AH (PB16 AH), Fujitsu MPG AHE (PB16 AH E).
Unfortunately we haven’t tested them in the absence of such drives.
Note:
At this point we correct just the number returned by a drive as its maximum capacity value. The model’s name
(for example, MPG3204AT) remains unchanged (incorrect). Actually the number in the model name is stored in the
ID=3D module as a line recorded in several places, that are varied for different hardware, and their exact identification
is not possible yet - thus modification may pose a threat of code damage. Theoretically, if someone wants to take a
chance, one should look for the last 3 figures of identifier (for example, 204).
Adaptives matching
Adaptives transfer option serves for copying adaptive data from one file to another. No actions are performed with
the connected drive.
Utility pop-up window allows to select the type and name for source adaptive data file and the destination file.
The file type is determined by the location of adaptive data block in it. There are two defined file types: "ROM file" and
"module file". In case of work with a ROM file the adaptives are located at offset FDE0h. In case of work with the
module 20h the adaptives are located at file beginning. After input of all the necessary parameters the utility will
perform actual transfer of 512 bytes of the adaptive data from one file to the other.
Adaptives matching1 is designed to search for adaptive data matching for the current drive using the existing file
set and read the drive's module 20h with its "native" adaptive data.
Attention! The operation is automatic but a situation is possible when a drive may be damaged during
work with a loaded adaptives' block because of heads bouncing.
In order to work with a drive you'll have to find a firmware version that would quite promptly (in less than 1
min.) set the drive on readiness without knocking sounds. Of course, reporting on readiness does not mean that
anything can be read from such drive. It would be enough if at power-up it sets itself on readiness quickly (without
additional self-damage caused by intensive "knocking"), even without loading hardware data from disks. Files with
adaptive data should be located in the ADP_DIR subdirectory of the utility directory. There are three sources for
matching: ROM files (*.bin), files with module 20h (*.rpm), and adaptive data files (*.adp). *.adp files represent the
most space-saving variant of adaptives storage since the contain nothing more2. In the process of work the utility will
sequentially load adaptives from source files to drive RAM and attempt to read module 20h from disk surface. If
reading operation is successful the report will include the name of the file containing adaptives that allow to read
module 20h and the name of the file to which the 20h module has actually been read. You can break the matching
process at any time by pressing [ESC]. In such case, as with completion of matching all the source files, you'll see a
brief report (containing a list of successful operations only) on performed works. A complete report that allows to find
out, which files have been processed but did not match, names of matching adaptive data files and downloaded 20h
modules can be found in the file ADP_DIR\adp_find.log.
18. Addition of the new firmware ROM into the file Fujitsu.ini.
The utilities for the HDD Fujitsu families MPF-AT and MPG – AT/E/AH allows user to add new firmware
ROM, which he can find. A part of the firmware wired-in the utility body and another part is loading after the
initialization it from the module Fujitsu.ini. The addition of the unknown firmware into the utility allows to work
correctly with the modules of the HDD, which have such firmware. Otherwise the work will be by defaults parameters
and some inaccuracy in the head of modules, the length and the quantity of it is possible. To set the work of the utility
it is necessary to indicate the shift to the modules table in ROM.
The file of the settings of Fujitsu.ini editing:
[PB15_DIR] – section for MPF AT (PB15)
[PB16_DIR] - section for MPG AT (PB16) ɢ MPG AT-E (PB16E)
[PB16H_DIR] - section for MPG AH (PB16H) ɢ MPG AH-E (PB16HE)
Commentary – is a string which is beginning with symbol ";" .
The format of writing:
$xxxxxxxx=$yyyyyyyy ;zzzzzzzz
xxxxxxxx – full version of the firmware: F/W (4 byte from the shift 0x20 into ROM), for example: 000020: 80 B5 B6
03 – for the firmware F/W HDA : A9-80B5.
yyyyyyyy - hexadecimal shift of the modules table in ROM
zzzzzzzz - commentary
Example:
[PB16_DIR]
1
- The function requires presence of PC-3K PWR power supply controller.
2
- If adaptives have to be transferred from an “adp”-file to ROM file or a module 20h file (see paragraph “Adaptives
transfer”) rename an *.adp file to *.rpm and select in the corresponding menu "module" source type.
$20070204=$0001D480 ;x00-2007
Researching of the modules table in new ROM should be perform by signature.
MPF AT : 01 00 4E 00 00 00
MPG AT : 01 00 51 00 00 00
MPG AH : 01 00 51 00 00 00
To view which firmware are switched on now you can by option:
Service info / Work with ROM / supported firmware.