4535 612 10261 HD11 Service Manual Page 173
CSIP Level 1 Troubleshooting: All Troubleshooting Starts Here
• Check if the symptom and probable cause may already be listed (Tab le 9 -2 ) for quick refer-
ence and resolution.
Investigating and Testing
If you haven’t discovered the cause of the problem yet, more in-depth analysis is necessary:
• Take a moment to review the data you’ve collected about the problem so far. Hopefully, you
have been able to categorize the symptom as a hardware, software, operator-induced, or
environmental failure.
- Hardware failure: Cause usually determined through use of troubleshooting tools. A fix is
typically realized by replacing suspect/candidate hardware until the problem is resolved.
NOTE Consider the value against the difficulties of swapping (suspect) hardware components
with good ones. Do not cause additional problems or confuse your search. Never swap
parts if a known good item might be damaged.
- Software failure or corruption: Even if a fix is realized by reloading software, the cause of
the failure or corruption needs to be investigated: Is there a system architecture failure, is
the user doing anything to cause the problem?
- Operator-induced: Is the user expecting more than the system is designed to deliver,
exceeding the capability of the system, or mis-operating it (over-filling the hard disk drive,
pulling the plug, or other)? A solution can be more user training or a work-around. Inves-
tigate to see if an option ought to be enabled or if there is an enhancement scheduled in
a future release that might solve the problem.
- Environmental: Are there any electrical power, EMI/RFI, or network connectivity difficul-
ties external to the system affecting its performance?
• Verify more easily checked factors first, such as system setup/configuration.
To Next Page
Loading...
