Service manual

Chapter 5 Troubleshooting
63
16. Check that all SCSI devices LVD (low votage differential) SCSI and that no SE (single-ended)
SCSI devices have been added to the bus.
Hot-swap drives shipped by HP are set for LVD operation. Drives set for SE operation may
used, but they will slow down the transfer rate considerably. Please refer to the user
documentation for the device to determine which device you are using.
CAUTION Don't use high voltage differential SCSI devices, they can destroy circuitry on LVD
and SE devices.
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.
The SCSI subsystem stops working
If the SCSI subsystem should stop working, do the following:
1. Review the Troubleshooting Checklist before you continue.
2. Run the DiagTools either from the HP NetServer Navigator CD-ROM or from the boot disk that
comes with the server. 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. Check if there is a resource conflict between any new board added and existing boards. 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 drivers? Refer to the software documentation for more
information.
5. Check the SCSI cables for problems that may have been caused by recent computer
maintenance, hardware upgrades, or physical damage.
6. 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.
7. Check the ROM BIOS version associated with the SCSI controller to make sure it is the most
recently issued version.
PCI Board Problems
Use this topic to help solve any PCI board problems.
System does not recognize the PCI board.
• Verify you have the most up-to-date driver for the NOS in use. Check the part number and
revision level of the board and check with its manufacturer for the latest driver for your NOS.
• Verify the PCI board is properly seated in its socket.
• If you have two PCI boards of the same type, try putting them on different buses.