Hardware Problems
HP Servers Troubleshooting Guide
2-11
HP CONFIDENTIAL
Writer: Ted Weiman File Name: c-ch2 Hardware Problems.doc
Codename: Generic TSG Part Number: 161759-007 Last Saved On: 11/19/02 9:31 AM
New Hardware
To troubleshoot problems that occur after you add hardware to the server:
IMPORTANT:
Always obtain a printed copy of Inspect data before and after adding,
removing, or repositioning any board or options. Refer to “Inspect Utility” in Chapter 4.
1.
If the system completes POST, run the Inspect Utility, which shows changes
made to the server. Use the resulting changes to troubleshoot possible causes of
the problem. Refer to “Inspect Utility” in Chapter 4 for more information.
2.
Check for memory, I/O, and interrupt conflicts.
3.
Check all cables for loose connections. Be sure that all cables are connected to
the correct locations and are the correct lengths. Refer to your server-specific
user documentation and “Loose Connections” in this chapter.
4.
Be sure that all software updates, such as device drivers, ROMPaq
utilities,
patches, SmartStart releases, and other SoftPaq
utilities, are installed and current.
For example, if you are using a Smart Array controller, you need the latest Smart
Array Controller device driver.
5.
Run the server setup utility after boards or other options are installed or replaced
to be sure that all system components recognize the changes. If you do not run
the utility, you may receive a POST error message indicating a configuration
error. After you check the settings in the server setup utility, save and exit the
utility, and then restart the server.
6.
Be sure that all switch settings are set as indicated by the server setup utility. For
additional information about required switch settings, refer to your server-
specific user documentation.
7.
Be sure that the hard drive signal cables are lined up properly with the connector
pins on the controller and the hard drives. Be sure that there are no bent
connectors.
8.
Be sure that all boards are properly installed in the unit.
9.
Run Diagnostics to see if it will recognize and test the device. Refer to
“Diagnostics” in Chapter 4 for more information.