Change configuration parameters option serves for control of cache parameters. ECC control and defects relocation in standard mode of operation. Please see details in section 9.3 5.4.3.2 Software heads deactivation Software heads deactivation means switching heads off by means of editing firmware zone and allows to adjust drive's firmware for work with a different number of magnetic heads without modification of existing adaptive data for still operational head/surfaces 543. 3 Zone removal Zone removal means exclusion of zones from logical translation please see details in Section 6.7 5.4. 4 Load ldr file to drive ram Load LDR file to drive raM command offers to input an LDR file for its subsequent loading to drive. Then the loading procedure follows with a drive restart. The selected file should correspond to the connected drive's family 5.4.5. Spindle stop Spindle stop commands to switch the drive to an energy-saving mode when the drive parl its heads and stops the motor (required for hot swap operations 5.5.DriⅤeID Drive ID option serves for modification of logical parameters, model name and its serial number 5.6 Logical scanning Logical scanning is a drive surface test utilizing logical parameters. This command is scribed in detail in section 8.2 5.7.SM.ARTtable S M.A.R. T table represents a set of commands for review and modification of S.M.A.R.T data 5.7.1 Views.M.ARttable View S.M.A.R.T table command outputs a report containing a table of values for S M.ARTattributes 5.7.2 Load S M. A RT(external module) Load S.M.A. R T(external module)command will requests a file with *sma extension containing S M.A.R.T module with factory defaults. An* Sma file can be obtained by plain renaming of module ID=70h from a drive with required values of respective attributes 5.7.3 Clear S M.A.R.T. parameters Quantum drives have a command for self-initialization of S M.A.R. T. attributes. Using this
Change configuration parameters option serves for control of cache parameters. ECC control and defects relocation in standard mode of operation. Please see details in section 9.3. 5.4.3.2 Software heads deactivation Software heads deactivation means switching heads off by means of editing firmware zone and allows to adjust drive’s firmware for work with a different number of magnetic heads without modification of existing adaptive data for still operational head/surfaces. 5.4.3.3 Zone removal Zone removal means exclusion of zones from logical translation. Please see details in Section 6.7. 5.4.4. Load LDR file to drive RAM Load LDR file to drive RAM command offers to input an LDR file for its subsequent loading to drive. Then the loading procedure follows with a drive restart. The selected file should correspond to the connected drive’s family. 5.4.5. Spindle stop Spindle stop commands to switch the drive to an energy-saving mode when the drive parks its heads and stops the motor (required for hot swap operations). 5.5. Drive ID Drive ID option serves for modification of logical parameters, model name and its serial number. 5.6 Logical scanning Logical scanning is a drive surface test utilizing logical parameters. This command is described in detail in Section 8.2. 5.7. S.M.A.R.T table S.M.A.R.T table represents a set of commands for review and modification of S.M.A.R.T data. 5.7.1 View S.M.A.R.T table View S.M.A.R.T table command outputs a report containing a table of values for S.M.A.R.T attributes. 5.7.2 Load S.M.A.R.T (external module) Load S.M.A.R.T (external module) command will requests a file with * .sma extension containing S.M.A.R.T module with factory defaults. An *. Sma file can be obtained by plain renaming of module ID=70h from a drive with required values of respective attributes. 5.7.3 Clear S.M.A.R.T. parameters Quantum drives have a command for self-initialization of S.M.A.R.T. attributes. Using this
command you can assign best values to all SMArT parameters except for relocated sectors count 5.8 Defects table Defects table is a set of commands for work with defects table 5.8.1. View defects table View defects table command outputs a report containing a table of relocated defects, their total number and zone allocation Please see detailed description of work with defects table in Section 8. 4 5.8.2 Add lba defect Add lba defect command allows to enter logical LBA defects manually 5.8.3 Add phys. Sector Add phys. Sector command allows to enter physical sector defects manually. 5.8.4 Add physical track Add physical track command serves for addition of one of more physical tracks 5.8. 5 Group into tracks Group into tracks-prior to running this procedure you should enter a limit of grouping into tracks, the a search for tracks will be performed in the defects table looking for tracks containing the number of defective sectors equal to- or greater than the specified limit. Discovered tracks are added to defects table as tracks while previously hidden sectors belonging to such tracks are removed form the table 5.8.6 Import of log defects table Import of long defects table accomplishes loading of the defects table saved in PC-30 or PC-DEFECTOSCOPE programs 5.8. Clear defects table Clear defects table command accomplishes clearing of the defects table 5.8.8. Export defects table Export defects table command records defects to a file in a format specific for Quantum drives. The file has a*. adt extension. If this command is selected you' ll be prompted for a file name without extension 5.8.9. Import defects table Import defects table command allows to write to the drive a previously saved (exported) table of defects. Command start will bring up a list of files with*. qdt extension. File selection is formed by pressing [Enter]. Then you'll be prompted to enter destination for the selected defects table 58.10. Work with module 6oh
command you can assign best values to all SMART parameters except for relocated sectors count. 5.8 Defects table Defects table is a set of commands for work with defects table. 5.8.1. View defects table View defects table command outputs a report containing a table of relocated defects, their total number and zone allocation. Please see detailed description of work with defects table in Section 8.4. 5.8.2 Add LBA defect Add LBA defect command allows to enter logical LBA defects manually. 5.8.3 Add phys. Sector Add phys. Sector command allows to enter physical sector defects manually. 5.8.4 Add physical track Add physical track command serves for addition of one of more physical tracks. 5.8.5 Group into tracks Group into tracks-prior to running this procedure you should enter a limit of grouping into tracks, the a search for tracks will be performed in the defects table looking for tracks containing the number of defective sectors equal to – or greater than the specified limit. Discovered tracks are added to defects table as tracks while previously hidden sectors belonging to such tracks are removed form the table. 5.8.6 Import of log. defects table Import of long. defects table accomplishes loading of the defects table saved in PC-3000AT or PC-DEFECTOSCOPE programs. 5.8.7 Clear defects table Clear defects table command accomplishes clearing of the defects table. 5.8.8. Export defects table Export defects table command records defects to a file in a format specific for Quantum drives. The file has a *.qdt extension. If this command is selected you’ll be prompted for a file name without extension. 5.8.9. Import defects table Import defects table command allows to write to the drive a previously saved (exported) table of defects. Command start will bring up a list of files with *.qdt extension. File selection is performed by pressing [Enter]. Then you’ll be prompted to enter destination for the selected defects table. 5.8.10. Work with module 60h
Firmware module ID-60h contains copy of factory defects table that may be handy during restoration of translator module ID=6lh This command forces reading the module and outputs a report on defects contained in it Then you can run "Export defects table" and the utility will ask for a file with* qdt extension. Restoration of ID-6lh using the ID-60h module data module is reviewed in detail in Section 6.5 5.9 Automatic mode Automatic mode allows to create a sequence of tests and launch it. Please see an automatic mode description in the section devoted to Quantum TM.ST, and SE drives 5.10 SELFSCAN SELFSCAN Starts a drive's self-testing program 5.10.1 Status review Status review is a command that outputs a repot on current status of selfSCAn tests In case of successful completion the keyword value is "PASS 5.10.2 Start SelfScan and used at the manufacturing factory. This command changes the keyword to"SELFSCAN" Start SelfScan is a command activating the self-testing program already present in the dr 5.10.3 Load SelfScan Load selfscan command loads an external module of selfscan tests contained in a -sso file. You should select a module corresponding to the family of the connected drive and press [Ente 5.10.4 Stop SelfScan Stop SelfScan command discontinues automatic start of selfSCan tests at drive power-up. This command changes the“ SELFSCAN"” keyword to^“ STOPPED 6. Drive firmware Head and disk assembly(HDA)in Quantum drives bears a painted label consist ing of two lines(Fig 6.1). The first line contains a family code and the second -firmware version number. The same line is present in CP4. For example, CP4 record reads: AlY 1312; the second line of HDA label in that case will be: 1310. Please note that the last symbol in the lower line of HDA label will al ways be 0, regardless of the symbol in the actual firmware version stored in CP4 Unfortunately there is no way to tell the rOM version by PCB itself, but incompatible versions are encountered in AS and D740-X6L families only Fig. 6.1. Location of label indicating the version of firmware recorded in had
Firmware module ID=60h contains copy of factory defects table that may be handy during restoration of translator module ID=61h. This command forces reading the module and outputs a report on defects contained in it. Then you can run “Export defects table” and the utility will ask for a file with *.qdt extension. Restoration of ID=61h using the ID=60h module data module is reviewed in detail in Section 6.5. 5.9 Automatic mode Automatic mode allows to create a sequence of tests and launch it. Please see an automatic mode description in the section devoted to Quantum TM.ST, and SE drives. 5.10 SELFSCAN SELFSCAN starts a drive’s self-testing program. 5.10.1 Status review Status review is a command that outputs a repot on current status of SELFSCAN tests. In case of successful completion the keyword value is “PASS”. 5.10.2 Start SelfScan Start SelfScan is a command activating the self-testing program already present in the drive and used at the manufacturing factory. This command changes the keyword to “SELFSCAN”. 5.10.3 Load SelfScan Load SelfScan command loads an external module of SELFSCAN tests contained in a *-sso file. You should select a module corresponding to the family of the connected drive and press [Ente]. 5.10.4 Stop SelfScan Stop SelfScan command discontinues automatic start of SELFSCAN tests at drive power-up. This command changes the “SELFSCAN” keyword to “STOPPED”. 6. Drive firmware Head and disk assembly (HDA) in Quantum drives bears a painted label consisting of two lines (Fig 6.1).The first line contains a family code and the second-firmware version number. The same line is present in CP4. For example, CP4 record reads: AIY.1312; the second line of HDA label in that case will be: 1310. Please note that the last symbol in the lower line of HDA label will always be 0, regardless of the symbol in the actual firmware version stored in CP4. Unfortunately there is no way to tell the ROM version by PCB itself, but incompatible versions are encountered in AS and D740-X6L families only. Fig. 6.1. Location of label indicating the version of firmware recorded in HAD
1310 6.1. Firmware structure In preparation of this chapter we used materials kindly provide by Vadim Agulov (alien@serv.neta.ru)andLevKoriagin(hdd3k@cef.spbsturu) Quantum drives control firmware consists of two parts. The main initial firmware part is stored in shadow ROM combined with the processor and disk controller in a single chip. Some shipments of drives also are equipped with external ROM with serial additional firmware portion is recorded in the drives firmware zone as a set of modules. Those modules contain besides code some data, for example, defects table, S M.A.R. Ttables, etc CHECK FIRMWARE STRUCTURE"command(para. 5.4.2. 1)in case of its successful completion outputs a report on firmware contents and settings. In the beginning of the report you can see the values of configuration parameters(see section 9.3). Then general information on configuration pages follows with details on several pages. The report completes with the information on modules that constitute a firmware zone. even in functional drives some modules are either read with a checksum error or with reading errors. Please refer to Section 1l of this manual for information on modules that may contain errors irrelevant for drives operation Table 6. 1. 1. Sample module's report ID Cyl Head ec Length Famcod Rev Status OE 0 03 OK Purpose of modules required for operation of Quantum drives belonging to families eviewed beren. ID=0Eh-module with settings for reading firmware zone(firmware zone adaptives) ID=65h-firmware zone defect table ID=06h-loadable overlay ID=05h-module containing data ID=0Oh-module containing data. ID=0lh, lIh, 12h, 13h, 14h, 15h, 16h, 17h-loadable overlays ID-6lh-module containing the translator and implicitly stored defects table ID=66h, 62h-modules pertaining to the defects relocation system
6.1. Firmware structure. “In preparation of this chapter we used materials kindly provide by Vadim Agulov ( alien@serv.neta.ru) and Lev Koriagin (hdd3k@cef.spbstu.ru).” Quantum drives control firmware consists of two parts. The main initial firmware part is stored in shadow ROM combined with the processor and disk controller in a single chip. Some “sample” shipments of drives also are equipped with external ROM with serial access. The second additional firmware portion is recorded in the drive’s firmware zone as a set of modules. Those modules contain besides code some data, for example, defects table, S.M.A.R.T. tables, etc. “CHECK FIRMWARE STRUCTURE” command (para. 5.4.2.1) in case of its successful completion outputs a report on firmware contents and settings. In the beginning of the report you can see the values of configuration parameters (see section 9.3). Then general information on configuration pages follows with details on several pages. The report completes with the information on modules that constitute a firmware zone. Even in functional drives some modules are either read with a checksum error or with reading errors. Please refer to Section 11 of this manual for information on modules that may contain errors irrelevant for drive’s operation. Table 6.1.1. Sample module’s report. # ID Cy1 Head Sec Length Famcod Rev Status 1 0E -3 0 0 1 36 A03 OK Purpose of modules required for operation of Quantum drives belonging to families reviewed berein: ID=0Eh-module with settings for reading firmware zone (firmware zone adaptives). ID=65h-firmware zone defect table. ID=06h-loadable overlay. ID=05h-module containing data. ID=00h-module containing data. ID=01h,11h, 12h, 13h, 14h, 15h, 16h, 17h-loadable overlays. ID=61h-module containing the translator and implicitly stored defects table. ID=66h, 62h-modules pertaining to the defects’ relocation system
ID-08h-module containing all the configuration pages ID=09h-module containing data ID=7xh-modules containing S M.A.R. Tsystem table Modules that are not essential for functioning in user mode ID=60h-module with factory log of relocated defects ID=2hh, 3xh, 4xh-modules of self-testing program (SELFSCAN The following modules are critical for data safety(they cannot be copied from another drive): ID=0Eh, 05h, 08h, 6xh Possible values of Fam Cod(family code)column are shown in the Table 6. 1.2 Table 6.1.2 Famil Family code, hex Family Family code, hex EL Lct20 2B D540X-4k CR D KA CX 31 KX Lcto8 2A LM Lctl Lcts 41 D740X-6L 6.2 Firmware saving Firmware saving commands are"ADD Fw TO DATABASE"(para.5.4.22),"READ CONFIGURATION PAGES"(para.5.4.2.3)and"READ MODULES"(para.5.4.2.5) ADD FW TO DATABASE accomplishes addition of all firmware zone modules and configuration pages to a resource file Resource files for drives, EL, CR and CX are compatible with earlier versions of utilities for those families, but they also contain configuration pages which were not added to the database previously. It is recommended to indicate drive model and firmware version when entering a record name in a database. For example: Ict10 5GB A03.093A” "READ CONFIGURATION PAGES" command allows to read configuration pages (or CP) of a drive. Read CPs are placed into QUxX MOD directory, where xx is the family name. Prior to the operation of CP reading a list of CPs available for reading appears on screen, where you hould select the necessary ones by pressing [Space] or choose the option"SELECT ALL After pressing [Enter the selected pages will be read to the respective subdirectory. If the directory already contains CPs with the same names repeated reading procedure will overwrite them without warning "READ MODULES" command allows to read program modules of a drive. The process of reading and the subdirectory where the modules are written to are the same as with reading of configuration pages. If a module cannot be read the file with its copy will have zero size Since the drive uses a one-time programmable RoM, you need not create a database of programs contained in ROM 63. Firmware transfer The transfer is accomplished by writing previously saved firmware to a drive. The utility allows to transfer firmware using two methods: as a whole and separate modules. Transfer of
ID=08h-module containing all the configuration pages. ID=09h-module containing data. ID=7xh-modules containing S.M.A.R.T system table. Modules that are not essential for functioning in user mode: ID=60h-module with factory log of relocated defects. ID=2hh, 3xh . 4xh-modules of self-testing program (SELFSCAN). The following modules are critical for data safety (they cannot be copied from another drive):ID=0Eh, 05h, 08h, 6xh. Possible values of FamCod (family code) column are shown in the Table 6.1.2. Table 6.1.2 Family Family code, hex Family Family code,hex EL 1F Lct20 39 EX 2B D540X-4k 44 CR 2D KA 2C CX 31 KX 32 Lct08 2A LM 37 Lct10 36 AS 35 Lct15 41 D740X-6L 3B 6.2 Firmware saving Firmware saving commands are “ADD FW TO DATABASE” (para.5.4.22), “READ CONFIGURATION PAGES” (para.5.4.2.3) and “READ MODULES” (para.5.4.2.5). “ADD FW TO DATABASE” accomplishes addition of all firmware zone modules and configuration pages to a resource file. Resource files for drives, EL, CR and CX are compatible with earlier versions of utilities for those families, but they also contain configuration pages which were not added to the database previously. It is recommended to indicate drive model and firmware version when entering a record name in a database. For example:”lct10 5GB A03.093A”. “READ CONFIGURATION PAGES” command allows to read configuration pages (or CP) of a drive. Read CPs are placed into QUxx_MOD directory, where xx is the family name. Prior to the operation of CP reading a list of CPs available for reading appears on screen, where you should select the necessary ones by pressing [Space] or choose the option “SELECT ALL”. After pressing [Enter]the selected pages will be read to the respective subdirectory. If the directory already contains CPs with the same names repeated reading procedure will overwrite them without warning. “READ MODULES” command allows to read program modules of a drive. The process of reading and the subdirectory where the modules are written to are the same as with reading of configuration pages. If a module cannot be read the file with its copy will have zero size. Since the drive uses a one-time programmable ROM, you need not create a database of programs contained in ROM. 6.3. Firmware transfer The transfer is accomplished by writing previously saved firmware to a drive. The utility allows to transfer firmware using two methods: as a whole and separate modules. Transfer of