IBM 6580 User Manual

SECTION 16. GUIDELINES FOR
ERROR
LOG INTERPRETATION
1. Diskette Error Log
• Write Fault Error
A write fault causes that
drive to be made unavail-
able to the user.
The number of write faults
will never be more than
one, because no operations
are permitted on the drive
after a write fault
occurs.
A write fault may be
caused by either a bad
file card, a bad diskette
adapter card, or cables.
• No Data Error
A no data error indicates
that a sector to be read
could not be located.
The probable cause of a no
data error is a bad
diskette.
• Seek Error
•
A seek error is caused by
a failure to track step to
the correct track.
Most seek errors will be
corrected by an automatic
retry. Frequent seek
errors indicate a problem
in the head track step
area.
Data Field Error *
Data field errors indicate
an error in reading cus-
tomer data. Many will be
corrected by an automatic
retry.
•
Data field errors may
indicate a bad diskette, a
file card problem, a
diskette adapter card
problem, or a head align-
ment problem.
Data Error *
Data errors indicate an
error in reading sector
identification data or
customer data. Many will
be corrected by an auto-
matic retry.
If the number of data
errors is much larger that
the number of data field
errors, this may indicate
poor diskette initializa-
tion or poor head
alignment.
* If read operations equal seek
operations, then all data errors
and data field errors were cor-
rected by automatic retrys without
informing the operator.
2. Keyboard Error Log
• Queue Overruns
•
Queue overruns are possi-
ble during normal opera-
tion.
A large number of queue
overruns indicates a key-
board electronics failure.
Queue overruns may appear
to the operator as missing
key strokes.
Code MAP Errors
Code MAP errors may be
caused by bad keyboard
electronics or electrical
noise picked up by the
keyboard cable.
Chapter 10. Intermittent Problem Diagnostic Approach 10-23

IBM 6580 Specifications

General

Brand	IBM
Model	6580
Category	Desktop
Language	English