Trailing-Edge
-
PDP-10 Archives
-
BB-M856A-BB
-
dskmsg.spe
There are no other files named dskmsg.spe in the archive.
Disk Subsystem Report Formats
-----------------------------
@@SUB_TOTALS_MSG1
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* Disk Subsystem Error Summary *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Disk Subsystem Error Entries Summarized by Error Type.
Entries Error Type
------- ----------
@@
@@SUB_TOT1
%%%%%% Drive Unsafe Errors
@@
@@SUB_TOT2
%%%%%% Servo System Errors
@@
@@SUB_TOT3
%%%%%% Header Compare Errors
@@
@@SUB_TOT4
%%%%%% Operation Incomplete Errors
@@
@@SUB_TOT5
%%%%%% Massbus (control bus) Parity Errors
@@
@@SUB_TOT6
%%%%%% Massbus (data bus) Parity Errors
@@
@@SUB_TOT7
%%%%%% Read Data Errors (DCK + HCRC + FER)
@@
@@SUB_TOT8
%%%%%% Channel Errors
@@
@@SUB_TOT9
%%%%%% Unanalyzed Disk Entries
@@
@@SUB_TOT10
%%%%%% Drive Index Timing Errors
@@
@@SUB_TOTALS_MSG2
Read Data Errors further summarized by Drive and Media ID.
Drive Media Error Totals
----- ----- ------------
@@
@@SUB_TOTALS_MSG3
%%%%%% %%%%%% %%%%%%%%
@@
@@SUB_TOTALS_MSG4
%%%%%% %%%%%%%%
@@
@@HIST1
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* Disk Subsystem Histogram *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NOTE
Each asterisk (*) represents two errors. If there
are more than 100 errors during a single period,
then only the first 50 asterisks will be printed.
Time Total
Period Errors Histogram
------ ------ ---------
@@
@@HISTOGRAM
%%%%% - %%%%% ! %%%% ##
@@
@@HIST2
! ---1---1---1---1---1---1---1---1---1---1---1---1--
8 16 24 32 40 48 56 64 72 80 88 96
Number of Errors
@@
@@LINE_FEED
@@
@@NEW_PAGE
@@
@@SUMMARY_HEADER
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* This report summarizes all Read Data Errors by Drive and Media ID *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Note
Errors with an unknown Media I.D. (unk) were
not analyzed by the Media Bad Spot theories.
DRIVE MEDIA CYL TRK SECT HARD SOFT RETRIES LBN
----- ----- --- --- ---- ---- ---- ------- ---
@@
@@SUMMARY_MSG1
%%%%%% %%%%%% %%%% %%% %%%% %%%%% %%%%% %%%%%%% %%%%%%%%%%%%%%
@@
@@SUMMARY_MSG2
%%%%%% %%%% %%% %%%% %%%%% %%%%% %%%%%%% %%%%%%%%%%%%%%
@@
@@SUMMARY_MSG3
%%%% %%% %%%% %%%%% %%%%% %%%%%%% %%%%%%%%%%%%%%
@@
@@RETRY_TOTALS_MSG1
## Total Retries (Hard and Soft)
@@
@@TIME_STAMP_MSG1
Time: ## TO ## Span: ##
@@
@@TIME_STAMP_MSG2
Time of Error: ##
@@
@@UNSAFE_THEORY1
If a drive reports either an AC Low or DC Low error condition, then
there is a good chance that the fault lies in the drive and that it
has something to do with either the power distribution system or the
power supply
@@
@@1.1.1
AC Low/DC Low Error - Drive Power Supply Theory ... [1.1.1]
##(##/SN: ##) reports:
%%%% AC-Low errors.
%%%% DC-Low errors.
@@
@@A1_UNSAFE_THEORY
If an RP04 drive detects an AC unsafe condition, the cause is usually
associated with a power brownout or a power failure. It indicates
the AC voltage of the drive power transformer secondary is low.
@@
@@A1.1.1
AC Usafe Error - RP04 AC Power Theory ... [1.1.1A]
##(##/SN: ##) reports:
## AC Unsafe errors.
@@
@@B1_UNSAFE_THEORY
If an RP04 drive detects a 30 Volts Unsafe condition, it points to a bad
DC power supply in the Vendor Logic portion of the drive.
@@
@@B1.1.1
30 Volts Unsafe Error - RP04 DC Power Theory ... [1.1.1B]
##(##/SN: ##) reports:
## 30 Volts Unsafe errors.
@@
@@C1_UNSAFE_THEORY
If an RP06 drive detects a DC Voltage Unsafe condition, it points to a
bad DC power supply in the Vendor Logic portion of the equipment.
@@
@@C1.1.1
DC Unsafe Error - RP06 DC Power Theory ... [1.1.1C]
##(##/SN: ##) reports:
## DC Voltage Unsafe errors
@@
@@UNSAFE_THEORY2
If a drive reports either a No Head Select or a Multi Head Select
error condition, then there is a good chance that the fault lies in
the drive and that it has something to do with the head select logic.
@@
@@1.1.2
Head Select Error - R/W Head Select Logic Theory ... [1.1.2]
##(##/SN: ##) reports:
%%%% NHS errors.
%%%% MHS errors.
@@
@@UNSAFE_THEORY3
If a drive reports a Transitions Unsafe or a Transition Detector
Failure, then chances are the fault lies in the drive and has to
do with the write clock timing logic.
@@
@@1.1.3
R/W Transition Error - Clock Timing Logic Theory ... [1.1.3]
##(##/SN: ##) reports:
%%%% TDF errors.
%%%% TUF errors.
@@
@@UNSAFE_THEORY4
If a drive reports either a Current Sink Failure, a Current Switch
Unsafe, a Write Select Unsafe, or a Write Current Unsafe error
condition, then there is a good chance that the fault lies in the
drive and that it has to do with either the write control logic or
the write current generators.
@@
@@1.1.4
R/W Control Error - R/W Current Control Logic Theory ... [1.1.4]
##(##/SN: ##) reports:
%%%% CSF errors.
%%%% CSU errors.
%%%% WSU errors.
%%%% WCU errors.
@@
@@A4_UNSAFE_THEORY
If a drive detects a Write Ready Unsafe condition, it could point to a
bad servo amplifier, a bad cylinder detector and/or bad write counter
circuits in the SS board of the DCL, or bad write control logic in the
Vendor Logic portion of the drive.
@@
@@A1.1.4
WRU Error - Head to Cylinder Position Theory ... [1.1.4A]
##(##/SN: ##) reports:
## Write Ready Unsafe errors.
@@
@@1PLO_UNSAFE_THEORY
If a drive detects PLO unsafe error(s), and they are detected on
different media or different cylinders on the same media, it points
to problems on the servo head head read path and could be either a
bad servo head or bad servo track.
@@
@@1.1.5
PLO Error - R/W Phase Locked Oscillator Drive Theory ... [1.1.5]
##(##/SN: ##) reports:
## PLO errors on different media or different cylinders of
the same media.
@@
@@2PLO_UNSAFE_THEORY
If a drive reports PLO unsafe errors and they occur on the same media
and on the same cylinder of that media, it is most likely a bad media.
@@
@@A1.1.5
PLO Error - R/W Phase Locked Oscillator Media Theory ... [1.1.5A]
##(##/SN: ##) reports
## PLO errors occurring on the same media with all errors on the same
cylinder.
Media ID: ##
Cylinder: ##
@@
@@UNSAFE_THEORY6
If an RP06 drive detects a Write and Offset error, it could point to
a bad DCL register board, or bad drive command logic in the Vendor Logic
portion of the drive.
@@
@@1.1.6
Write and Offset Error - RP06 Write and Offset Theory ... [1.1.6]
##(##/SN: ##) reports:
## Write and Offset errors.
@@
@@UNSAFE_THEORY7
If an RP04 drive reports a Velocity Unsafe condition, it points to a
bad servo mechanism. It warrants immediate Field Service attention.
@@
@@1.1.7
Velocity Unsafe Error - Head Load Speed Theory ... [1.1.7]
##(##/SN: ##) reports:
## Velocity Unsafe errors
Take drive offline and call Field Service.
@@
@@UNSAFE_THEORY8
If an RP04 drive detects a Pack Speed Unsafe condition, it points to a
variety of causes: loss of phase to the primary power, a bad drive
motor, a broken drive belt, or a bad servo mechanism. Field Service
should be notified immediately.
@@
@@1.1.8
PSU Error - RP04 Pack Speed Theory ... [1.1.8]
##(##/SN: ##) reports:
## Pack Speed Unsafe errors
Take drive offline and call Field Service.
@@
@@UNSAFE_THEORY9
If a drive detects a Drive Timing Error, it indicates a hardware
failure in the drive timing logic.
@@
@@1.1.9
Drive Timing Error - Drive Timing Logic Theory ... [1.1.9]
##(##/SN: ##) reports:
## Drive Timing Errors.
@@
@@SERVO_THEORY1
If a drive reports either a Seek Incomplete or an Off Cylinder error
condition, then chances are the fault is in the drive and has to do
with either the servo mechinism or the servo control logic.
@@
@@1.2.1
Servo Error - Servo System Theory ... [1.2.1]
##(##/SN: ##) reports:
%%%% SKI errors.
%%%% OCYL errors.
@@
@@MEDIA_OPI_THEORY1
If a disk subsystem reports Operation Incomplete errors, and if the
errors involve two or more drives, and if they are associated with
the same medium, cylinder, track and sector, then there is a good
chance that the medium is causing the errors.
@@
@@1.3.1
OPI Error - Media Theory ... [1.3.1]
Media ID: ## - Cyl: ##, Trk: ##, Sect: ## was identified with
## Hard and ## Soft OPI errors on
## and other drives.
@@
@@UNIT_OPI_THEORY1
If a drive reports multiple Operation Incomplete errors, and if those
errors are not associated with a particular medium, then chances are
the fault lies in the drive and has something to do with the timing
logic that controls Search and Header Read operations.
@@
@@1.3.2
OPI Error - Drive Timing Logic Theory ... [1.3.2]
##(##/SN: ##) reports:
## Hard and ## Soft OPI errors.
@@
@@RAE_THEORY1
If a disk subsystem reports Massbus (control bus) parity errors or
bus timeout errors and if the errors involve two or more drives,
then chances are the fault lies in the controller or the Massbus.
If, however, the errors are local to a single drive, then chances
are the fault is in the drive and has something to with the Massbus
interface logic.
@@
@@1.4.1
RH CPE Error - Massbus (control bus) RH Theory ... [1.4.1]
RH No: ## reports:
%%%% Massbus (control bus) Parity Errors.
%%%% different drives were involved.
@@
@@1.4.2
RH CPE Error - Massbus (control bus) Drive Theory ... [1.4.2]
##(##/SN: ##) was identified with
%%%% (controller detected) Massbus (control bus) Parity Errors
or Bus Timeout errors.
@@
@@RDPAR_THEORY1
If a disk subsystem reports Massbus (data bus) parity errors during
data reads, and if the errors involve multiple drives, then chances
are the fault lies in the controller. If, however, the errors involve
a single drive then, chances are the fault lies in the drive and has
something to do with the Massbus interface logic.
@@
@@WRPAR_THEORY1
If a system reports Massbus (data bus) parity errors during data writes,
and if those errors involve multiple controllers, then chances are the
fault has to do with the memory controller or the channel. If, however,
the errors involve a single controller and multiple drives, then chances
are the fault lies in the controller or the Massbus. Finally, if the
errors involve a single drive, then the fault is probably in the drive
and has something to do with the Massbus interface logic.
@@
@@1.5.1
RH DPE Error - Data Read/Massbus (data bus) RH Theory ... [1.5.1]
RH No: ## reports: (during Data Read operations)
%%%% Massbus (data bus) Parity Errors.
%%%% different drives were involved.
@@
@@1.5.2
RH DPE Error - Data Read/Massbus (data bus) Drive Theory [1.5.2]
##(##/SN: ##) was identified with
%%%% (RH detected - Data Read) Massbus (data bus) Parity Errors.
@@
@@1.5.3
RH DPE Error - Data Write/Massbus (data bus) MBox (UBA) Theory [1.5.3]
%%%% different RH controllers report: (during Data Write operations)
%%%% Massbus (data bus) Parity Errors.
@@
@@1.5.4
RH DPE Error - Data Write/Massbus (data bus) RH Theory ... [1.5.4]
RH No: ## reports: (during Data Write operations)
%%%% (RH detected) Massbus (data bus) Parity Errors.
@@
@@1.5.5
RH DPE Error - Data Write/Massbus (data bus) RH Theory ... [1.5.5]
RH No: ## reports: (during Data Write operations)
%%%% (drive detected) Massbus (data bus) Parity Errors.
%%%% different drives were involved.
@@
@@1.5.6
RH DPE Error - Data Write/Massbus (data bus) Lone Drive Theory [1.5.6]
##(##/SN: ##) reports: (during Data Write operations)
%%%% (drive detected) Massbus (data bus) Parity Errors.
@@
@@BAD_SPOT_THEORY1
The following reports are based on the assumption that a radial bad
spot (3 or more adjacent cylinders, same track and sector) may be
causing Read Data errors.
@@
@@BAD_SPOT_THEORY2
The following reports are based on the assumption that a
circumferential bad spot (same track and cylinder, 2 or
more adjacent sectors) may be causing Read Data errors
@@
@@1.6.1
Read Data Error - Single Drive Radial Bad Spot Theory ... [1.6.1]
Media ID: ## may have a radial bad spot at:
Track Sector Cylinder Hard Soft
%%%% %%%% %%%% to %%%% %%%% %%%%
##(##) was the only drive to detect these errors.
@@
@@1.6.2
Read Data Error - Multi Drive Radial Bad Spot Theory ... [1.6.2]
Media ID: ## may have a radial bad spot at:
Track Sector Cylinder Hard Soft
%%%% %%%% %%%% to %%%% %%%% %%%%
##(##) and other drives detected these errors.
@@BAD_SPOT_THEORY3
If a drive detects multiple read data errors, and if those involve the
same medium and the same cylinder, surface, and sector address, then
there is a good chance that the errors were caused by a bad spot on
the medium. The chances of this are greater if the errors are seen
on multiple drives.
@@1.6.3
Read Data Error - Multi Drive Single Bad Spot Theory ... [1.6.3]
Media ID: ## may have a single bad spot at LBN ##
Track Cylinder Sector Hard Soft
%%%% %%%% %%%% %%%% %%%%
##(##) and other drives detected these errors.
@@1.6.4
Read Data Error - Single Drive Single Bad Spot Theory ... [1.6.4]
Media ID: ## may have a single bad spot at LBN ##
Track Cylinder Sector Hard Soft
%%%% %%%% %%%% %%%% %%%%
##(##) was the only drive to detect these errors.
@@
@@1.6.5
Read Data Error - Multi Drive Circumferential Bad Spot Theory [1.6.5]
Media ID: ## may have a circumferential bad spot at LBN ##
Track Cylinder Sector Hard Soft
%%%% %%%% %%%% to %%%% %%%% %%%%
##(##) and other drives detected these errors.
@@
@@1.6.6
Read Data Error - Single Drive Circumferential Bad Spot Theory [1.6.6]
Media ID: ## may have a circumferential bad spot at LBN ##
Track Cylinder Sector Hard Soft
%%%% %%%% %%%% to %%%% %%%% %%%%
##(##) was the only drive to detect these errors.
@@
@@RW_HEAD_THEORY1
If a drive reports multiple read data errors, and if all the errors
involve the same head, then chances are the head is at fault. If,
however, offset was used to recover from one or more of the errors,
then it may be that the head is slightly out of alignment.
@@
@@1.6.7
Read Data Error - Single R/W Head Theory ... [1.6.7]
##(##/SN: ##) reports:
head ## is common to all
## Hard and ## Soft Read Data errors.
@@
@@1.6.8
Read Data Error - Single Head Alignment Theory ... [1.6.8]
## (##/SN: ##) reports:
head ## used offset (at least once) to recover from
## Hard and ## Soft Read Data errors.
@@
@@RW_HEAD_THEORY2
If a drive reports multiple read data errors, and if the errors are not
local to a single head or one of the head matrix modules, then chances
are the fault lies in the common read circuitry.
@@
@@1.6.9
Read Data Error - Common Read Logic Theory ... [1.6.9]
##(##/SN: ##) reports random Read Data errors on:
Head No. Hard Errors Soft Errors Total Retries
%%%% %%%%%%%% %%%%%%%% %%%%%%%%
@@
@@MULTI_HD_MSG1
%%%% %%%%%%%% %%%%%%%% %%%%%%%%
@@
@@RW_HEAD_THEORY3
If a drive reports multiple read data errors, and if all the errors
involve either odd or even heads, then chances are the respective
head matrix module has something to do with the errors.
@@
@@1.6.10
Read Data Error - Odd Head Matrix Module Theory ... [1.6.10]
##(##/SN: ##) reports read errors on odd heads only.
Head No. Hard Errors Soft Errors Total Retries
%%%% %%%%%%%% %%%%%%%% %%%%%%%%
@@
@@1.6.11
Read Data Error - Even Head Matrix Module Theory ... [1.6.11]
##(##/SN: ##) reports read errors on even heads only.
Head No. Hard Errors Soft Errors Total Retries
%%%% %%%%%%%% %%%%%%%% %%%%%%%%
@@
@@RW_HEAD_THEORY4
If a drive reports multiple read data errors involving two or more
heads, and if offset was used in the recovery process, then there
is a possibility that those heads are slightly out of alignment.
@@
@@1.6.12
Read Data Error - Multiple Head Alignment Theory ... [1.6.12]
##(##/SN: ##) reports offset was used (at least once)
to recover from errors associated with the following heads:
Head No. Hard Errors Soft Errors Total Retries
%%%% %%%%%%%% %%%%%%%% %%%%%%%%
@@
@@CHANNEL_ERROR_THEORY1
If two or more disk subsystems report channel errors during data read
operations, and if there are no error bits set in the drive error
register (DRER1), then chances are the fault lies in the MBox (UBA),
the channel, or the Channel Bus. If, however, the errors are local to
one subsystem, then chances are the fault lies in the controller or the
Channel Bus interface logic.
@@
@@CHANNEL_ERROR_THEORY2
If two or more disk subsystems report channel errors during data write
operations, and if there are no error bits set in the drive error
register (DRER1), then chances are the fault lies in the MBox (UBA),
the channel, or the Channel Bus. If, however, the errors are local to
one subsystem, then chances are the fault lies in the controller or the
Channel Bus interface.
@@
@@CHANNEL_ERROR_THEORY3
If disk subsystem(s) report channel errors and the Overrun Bit is the
only other error bit set in the CONI register, with no error bits
set in the drive error register (DRER1), it could be the hardware
configuration or a heavy system load.
@@
@@1.7.1
Channel Error - Read Operation/RH Controller Theory ... [1.7.1]
RH No: ## reports: (during Data Read operations)
%%%% (Hard) and ## (Soft) channel errors.
%%%% total retries.
@@
@@1.7.2
Channel Error - Read Operation/MBox (UBA) Channel Theory ... [1.7.2]
%%%% different channels report: (during Data Read operations)
%%%% (Hard) and ## (Soft) channel errors.
%%%% total retries.
@@
@@1.7.3
Channel Error - Write Operation/RH Controller Theory ... [1.7.3]
RH No: ## reports: (during Data Write operations)
%%%% (Hard and ## (Soft) channel errors.
%%%% total retries.
@@
@@1.7.4
Channel Error - Write Operation/MBox (UBA) Channel Theory ... [1.7.4]
%%%% different channels report: (during Data Write operations)
%%%% (Hard) and ## (Soft) channel errors.
%%%% total retries.
@@
@@1.7.5
Channel Error - Overrun Only Theory ... [1.7.5]
%%%% channel errors occurred with only the overrun bit set
%%%% hard and ## soft errors.
%%%% total retries.
@@
@@IXE_ERROR_THEORY1
If a drive reports IXE (Index Errors) then chances are that the
fault lies in the drive and is local to the Index Pulse timing
and control logic.
@@
@@1.9.1
IXE Error - Index Pulse Timing Logic Theory ... [1.9.1]
##(##/SN: ##) reports:
## Index errors.
Media Cylinder Track Sector Errors Retries
%%%%%% %%%% %%% %%% %%%%%% %%%%%%%
@@
@@IXE_DUMP
%%%%%% %%%% %%% %%% %%%%%% %%%%%%%
@@
@@HEADER_COMPARE_THEORY1
If a drive reports Header Compare Errors, and if the drive does not
report a Header CRC errors at the same time, then chances are the
fault lies in the drive and to do with the head select circuitry or
the header compare logic.
@@
@@1.8.1
HCE Error - Head Select/Header Compare Theory ... [1.8.1]
##(##/SN: ##) reports:
## Header Compare Errors without Header CRC errors.
Media Cylinder Track Sector Errors Retries
%%%%%% %%%% %%% %%% %%%%%% %%%%%%%
@@
@@HEADER_COMPARE_THEORY2
If a drive detects Header Compare Errors without HCRC errors and
there are several errors on the same track, but scattered over several
cylinders, it could be a bad head or bad media. Check for Read Data
Errors for further media analysis.
@@
@@1.8.2
HCE Error - Head or Media Theory ... [1.8.2]
##(##/SN: ##) reports:
## Header Compare Errors without Header CRC errors.
Media Cylinder Track Sector Errors Retries
%%%%%% %%%% %%% %%% %%%%%% %%%%%%%
@@
@@HCE_DUMP
%%%%%% %%%% %%% %%% %%%%%% %%%%%%%
@@
@@NO_DISK_CONCLUSIONS_REACHED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* NOTE *
* Due to insufficent data in the system event file, Analyze *
* was unable to produce any disk subsystem failure reports. *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
@@
@@UNUSED_ENTRIES_MSG1
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* The entries in the following packet do not fit any of the existing *
* disk theories. The packet, therefore, should be evaluated manually. *
* *
* If, after evaluating the packet you are able to formulate a theory *
* we, the Spear team, would like to hear about it. Also, reguardless *
* of whether or not you are able to come up with a theory, we would *
* appreciate it if you would send a Full translation of the packet to: *
* *
* Digital Equipment Corporation *
* The SPEAR Team MR1-1 / S35 *
* 200 Forest Street *
* Marlboro, Mass. 01752 *
* Thank You *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
@@
@@UNUSED_ENTRIES_MSG2
Unused Entries - Manual Analysis Required
Disk analysis was unable to process
## entries.
@@
@@
**************** END OF DISK ENTRIES ***********************
******************** END OF DSKMSG.TXT **************************
@@