Error Type: DF
Error Description: Drive-resident diagnostics detected bad RAM external to the master processor.
Fault Isolation/Correction:
1. ECM
87 Master Processor ROM Checksum failure Error Type: DF
Error Description: Drive-resident diagnostics detected bad ROM internal to the master processor.
Fault !solAtio-n/Correetion:
1. ECM
88 Master Processor EEPROM Write Violation Error
Error Type: DE
. Error Description: EEPROM was addressed and written to while in read-only mode.
Fault Isolation/Correction:
1. ECM
89 Seek Speed Out of Range
Error Type: DE
Error Description: While monitoring the speed of the actuator, the servo processor determined that seek velocity is beyond prescribed speed.
DIGITAL INTERNAL USE ONLY
5-88 Troubleshooting and Error Codes
Fault IsolatioDlCorrection:
1. ECM
2. Power supply 3. HDA
8A Servo Processor Inside of Destination Track During Settle State Error Type: DE
Error Description: Servo processor has determined that the positioner has placed heads inside of the destination track during settle state.
Fault IsolatioDlCorreetion:
1. ECM
88 Gray Code Error After Settling WIth Fine Track Error Type: DE
Error Description: Head settling on a track normally occurs following a SEEK command.
A gray code comparison is made to ensure the heads have settled on the requested track.
In this case, the servo was settling within 114 track of the desired track and fine track had been asserted when suddenly the servo gray coded information indicated that movement of
>1 cylinder has taken place away from the desired target cylinder. Such an occurrence may be related to a significant amount of vibration in the vertical axis of the drive, or electrical transients from the positioner control voltage and holding current circuitry.
Fault IsolatioDlCorreetion:
1. ECM 2. HDA
8e Uncallbrated and PLO Error Error Type: DE
Error Description: A PLO elTOr occurred and the head offsets were uncalibrated.
Fault IsolatioDlCorreetion:
1. ECM 2. PCM 3. HDA
8D Polarity Error on Velocity Command During a Multi-Track Seek Error Type: DE
Error Description: The polarity indication bit in a velocity command profile was clear (zero) during a multi-track seek. This bit should have been set. (This is one of the setup functions the servo processor checks before it executes the digital servo seek profiles.)
Fault lsolatioDlCorrection:
1. ECM
DIGITAL INTERNAL USE ONLY
SE Master Processor ROMlEEPROM Consistency Code Mismatch
Error Type: DF
Troub!eshooting and Error Codes 5-89
Error Description: Master processor microcode is incompatible with EEPROM microcode.
Fault Isolation/Correction:
1. Reload microcode 2. ECM
SF EEPROM Checksum Failure
Error Type: DF
Error Description: Drive-resident diagnostics detected bad EEPROM external to the master processor. The calculated checksum did noi maicb the stored checksum.
FaultIsolation/Co~tion:
1. ECM
90 Unable to Force Index Error
Error Type: DF
Error Description: Drive-resident diagnostics were unable to force and/or detect an index error.
Fauit IsoiationiCorrection:
1. ECM
91 No InterRipt Detected During RIW Force Fault
Error Type: DF
Error Description: No interrupt to the master processor was detected by the drive during the read/write force fault diagnostic.
Fault Isolation/Correction:
1. ECM
92 Inner Guardband WIthout a Servo Fault Set Error Type: DF
Error Description: The actuator was positioned in the inner guard band area and the inner guardband flag was set; however, a servo fault condition was not detected.
Fault Isolation/Correction:
1. ECM
93 Inner GuardbandlServo Fault: No Interrupt Detected
Error Type: DF
Error Description: The actuator was positioned at a cylinder in the inner guardband area, the inner guardband flag was set, and a servo fault error was detected, but the master processor was not interrupted.
Fault Isolation/Correction:
1. ECM
DIGITAL INTERNAL USE ONLY
5-90 Troubleshooting and Error Codes
94 SOl Loopback Test Failure on Both Ports Error Type: DF
Error Description: Drive-resident diagnostics detected an SDI gate array or TSID gate array failure involving both SDI ports A and B logic. If the drive internal test 09 fails, the failure could be in the hardware external to the SDIfl'SID gate aITay as well. Dming internal T09, the testing expects SDI loopback connectors to be attached to the ECM or at the cab bulkhead.
Fault Isolation/Correction:
If test number 08 fails:
1. ECM
If test number 09 fails:
1. Loopback connectors are not installed 2. Defective SDI cable
3. Defective bulkhead connector 4. ECM
5. SDI connectors JI0l or JI02 95 SOl Test Failure: Port A
Error Type: DF
Error Description: A drive-resident diagnostic detected a failure with the SDI gate array or the TSID gate array involving SDI Port A. If the drive internal test 09 fails for this error code, the failure could be in the SDI Port A hardware external to the SDursID gate array as well.
During internal TOO, the testing expects SDI loopback connectors to be attached to the ECM or at the cabinet SDI bulkhead.
Fault IsolatioDlCorrection:
If test number 08 fails:
1. ECM
If test number 09 fails:
1. Port A loopback connectors are not installed 2. Defective SDI cable (Port A)
3. Defective bulkhead connector (Port A) . 4. ECM
5. SDI connector JI02 (Port A) 96 SOl Failure: Port B
Error Type: DF
Error Description: A drive-resident diagnostic detected a failure with the SDI gate array or the TSID gate array involving SDI Port B. If the drive internal test 09 fails for this error code, the failure could be in the SDI Port B hardware external to the SDIIl'SID gate array as well.
During internal T09, the testing expects SDI loopback connectors to be attached to the ECM or at the cabinet SDI bulkhead.
DIGITAL INTERNAL USE ONLY
Fault Isolation/Correction:
if test number 08 fails:
1. ECM
If test number 09 fails:
1. Port B loopback connectors are not installed 2. Defective SDI cable (Port B)
3. Defective bulkhead connector (Port B) 4. ECM
5. SDI connector J101 (Port B) 98 Can't Execute Diagnostic/Jumper
Error Type: DF
Troubleshooting and Error Codes 5-91
Error Description: A diagnostic test could not be run because a hardware jumper was not installed. If this error is seen in the field, do not attempt to alter jumpers.
Fault Isolation/Correction:
1. Operator (do not attempt to alter jumpers)
9A Positioner Corrected Event During Data Transfer
This is typically an event unless analyzed by VAXsimPLUS to be worthy of correction.
Reference expanded di~on
or
9A, 9B, and 9C events under error code 9C.Error Type: DE
Error Description: Heads were not fine positioned or locked on track (relative to the embedded servo information) at the time a read or write operation was ready to start. The drive took necessary procedures to re-establish on-track condition. The drive command was received but READ GATE or WRITE GATE had not yet been asserted.
Fault Isolation/Correction:
1. IillA (if only one head) 2. ECM (if 10
or
13 heads)98 Write and Positioner Corrected Event
This is typically an event unless analyzed by VAXsimPLUS to be worthy of correction.
Reference expanded discussion
or
9A, 9B, and 9C events under error code 9C.Error'Type: DE
Error Description: The master processor determined that the selected read/write head moved off track when WRITE GATE was asserted. The condition was corrected. (The readlwrite heads must be within 57.1 microinches from track centerline.)
Fault Isolation/Correction:
1. HDA (if only one head) 2. ECM (if 10 of 13 heads)
DIGITAL INTERNAL USE ONLY
5-92 Troubleshooting and Error Codes
9C Read Gate and Positioner Corrected Event Error Type: DE
Error Description: The master processor determined that the selected read/write head moved off track when READ GATE was asserted. The condition was corrected. (The read/write heads must be within 57.1 microinches from track centerline.)
TROUBLESHOOTING 9A, 9B, AND 9C:
This is typically an event unless analyzed by VAXsimPLUS to be worthy of correction.
For HSCIKDM controllers, event rates of <5 per day may be considered normal for disks that operate with fairly high I/O rates (continually or in significant bursts) provided that the following pattern is noted:
• Ninety percent of occurrences are with the top five heads (heads 0 through 4).
• One of the top five heads will have few if any errors.
• No one head in the top five has 90 percent of the errors. (This might point to a track/surface problem.)
If the event pattern matches this, and the event rate exceeds these guidelines, then HDA replacement may be necessary.
If the event pattern does not match this, then further analysis is required.
For KDAlKDB/UDA controllers, event rates should not exceed 16 per day on heavily used disks (110 rates of 30 per second).
If these events occur over 10 of the 13 heads, then the occurrence may be related to a general servclread path problem. This is possibly an electro~cs problem that may not involve the HDA.
If these errorS occur primarily on one head, there is strong head/surface correlation and possible HDA replacement is warranted.
The above number of events to be expected was determined by analysis and experience with the RA90 HDA 70-22951~1. With the introduction of the RA92 (HDA 70-27492-(1), the number of 9A, 9B, and 9C events has decreased significantly. The phase-in of the RA92 HDA hardware mechanics (resulting in an RA9O-compatible HDA 70-27268-01) into RA90 production has substantially reduced the occurrence of these events because of the new design.
Fault Isolation/Correction:
1. HDA (if only one head) 2. ECM (if 10 of 13 heads) 9D Error Log Header Corrupted
Error Type: DF
Error Description: A location in EEPROM containing drive-resident error log identifier information, device type, or descriptor size is invalid.
Fault Isolation/Correction:
1. Attempt to load new microcode 2. ECM
DIGITAL INTERNAL USE ONLY
9E Drive FauHed, Test Cannot Run
Error Type: DF
Troubleshooting and Error Codes 5-93
Error Description: Drive-resident diagnostics cannot run while the drive is faulted.
Fault IsolatioDlCorreetion:
1. Check fault condition 2. ECM
9F Error Log Check Point Code
Error Type: Informational Only.
Error Description: If drive-resident diagnostic T50 has been used to place a checkpoint between errors in the drive internal error iog, a 9F entry will be seen in ihe drive iniernai error log. This makes drive troubleshooting easier by placing a null field between errors in the drive internal error log to partition repair activity.
Fault IsolatioDlCorreetion:
1. None (read Error Description above)
AO Unable to Clear SDI Array Safety St..atus Register
Error Type: DF
Error Description: Drive-resident diagnostics attempted to clear the SDI gate array safety status registers but were unsuccessful.
Fault IsolatioDlCorrection:
1. To isolate the stuck bit, check the preceding error in the drive internal error log storage silo.
Base corrective action on the preceding error.
2. ECM
A 1 Unable to Force Encoder Error
Error Type: DF
Error Description: Drive-resident diagnostics were unable to force a read/write encoder/decoder (RWENDEC) error.
Fault IsolatioDlCorrection:
1. ECM
A2 Unable to Force Multiple Head Select While Reading
Error Type: DF
Error Description: Drive-resident diagnostics were unable to force read gate and multi-chips error.
Fault IsolatioDlCorreetion:
1. PCM 2. ECM 3. HDA
DIGITAL INTERNAL USE ONLY
5-94 Troubleshooting and Error Codes
A3 Unable to Force Write Gate and Write U . . . t.
Error Type: DF
Error Description: A drive-resident diagnostic was unable to force write gate and write unsafe error conditions.
Fault Isolation/Correction:
1. ECM 2. PCM
A4 Unable to Force Write Current and No Write Gate
Error Type: DF
Error Description: Drive-resident diagnostics were unable to force write current and no write gate error conditions and detect such a condition.
FaultlsolationlCorrection:
1. ECM 2. PCM
AS Unable to Force Write Gate and No Write Current Error Type: DF
Error Description: Drive-resident diagnostics were unable to force write gate and no write current error conditions.
Fault IsolatioDlCorrection:
1. ECM 2. PCM
A6 Unable to Force Read Gate and Off Track Error Error Type: DF
Error Description: Drive-resident diagnostics were unable to force read gate and off track error conditions.
Fault IsolationlCorrection:
1. ECM
A7 Unable to Force Write Gate and Off Track Error Error Type: DF
Error Description: Drive-resident diagnostics were unable to force write gate and off track error conditions.
Fault IsolationlCorrection:
1. PJW cable to PCM 2. ECM
DIGITAL INTERNAL USE ONLY
AS Unable to Force Read and Write Fault While Writing
Error Type: DF
Troubleshooting and Error Codes 5-95
Error Description: Drive-resident diagnostics were unable to force a readlwrite-while-faulted
en ui' condition.
Fawt~mtio~Co~on:
1. ECM
A9 Servo FaultIForce Fault Test
Error Type: DF
Error Description: A servo check occurred while the diagnostic firmware was attempting to execute the force fault subtest.
Fawthomtio~Co~tion:
1. ECM 2. HDA
AS Forced Read and Write Fauil While Reading
Error Type: DF
Error Description: Drive-resident diagnostics were unable to force a readlwrite-while-faulted error condition.
Fault ~mtio~Correction:
1. ECM
AD UART Overrun or Framing Error
Error Type: DE
Error Description: The master processor internal UART detected an overrun condition or a framing error condition on data received from the OCP.
Fault Isolation/Correction:
1. OCP