Processor Problems - HP Netserver LP2000r Service Manual

Chapter 5
Use only the HP Netserver SCSI cables for the SCSI hot swap subsystem.
16. Verify all SCSI devices on the bus are appropriate for that bus (only single-ended SCSI devices
on the single-ended bus; only differential SCSI devices on the differential bus).
17. Disconnect all SCSI devices except the SCSI adapter and the drive at SCSI address 0, and try
again. If this fails, try substituting a known good SCSI adapter and disk drive.
18. Use the Setup Utility to check for resource conflicts, especially if new boards or accessories
have been added.
Symptom:
•
The SCSI subsystem stops working
If the SCSI subsystem should stop working, do the following:
1. Review the Troubleshooting Checklist and Mass Storage Guidelines before you continue.
2. Run DiagTools. Verify that the SCSI ID and other switch settings are correct and get specific
information or verification that the problem is the SCSI bus.
3. If an accessory board was added recently, check if there is a resource conflict between the new
board and an existing accessory board. Also, if you have changed the options on an existing
board, there may be a resource conflict.
a. Remove the new board and restart the computer. If this corrects the problem, the board is
either defective or it is trying to use a system resource used by the SCSI subsystem.
b. Check if the board is using memory, I/O addresses, or interrupt lines that are also used by
the SCSI subsystem.
4. Check to see if there have been recent changes to any software. For example, has anyone
moved, removed, or changed the configuration files or drivers? Refer to the software
documentation for more information.
5. If you suspect hardware failure and there are no system error messages, check each
component associated with the failure. Equipment failure is probably the most unlikely reason
for a SCSI subsystem failure.

Processor Problems

If a problem exists with the Netserver processor;
1. Remove and reseat the processor module(s).
2. Replace each of these components, one-at-a-time, with a known-good component, and retest
the Netserver:
• Processor
• Terminator (if so equipped)
• Heatsink
CAUTION
3. Check the event log for indication of processor overheating.
4. If the fault persists, replace the system board.
64
Do not push on the processor components; push only on the edge. Pushing on the
device may damage it.
Troubleshooting