Fan Problems; Hard Drive Problems - HP ML150 - ProLiant - G6 User Manual

Fan problems

General fan problems are occurring
Action:
Be sure the fans are properly seated and working.
1.
Follow the procedures and warnings in the server documentation for removing the access panels
a.
and accessing and replacing fans.
Unseat, and then reseat, each fan according to the proper procedures.
b.
Replace the access panels, and then attempt to restart the server.
c.
Be sure the fan configuration meets the functional requirements of the server. Refer to the server
2.
documentation.
Be sure no ventilation problems exist. If you have been operating the server for an extended period
3.
of time with the access panel removed, airflow may have been impeded, causing thermal damage
to components. Refer to the server documentation for further requirements.
Be sure no POST error messages are displayed while booting the server that indicate temperature
4.
violation or fan failure information. Refer to the server documentation for the temperature
requirements for the server.
Replace any required non-functioning fans and restart the server. Refer to the server documentation
5.
for specifications on fan requirements.
Be sure all fan slots have fans or blanks installed. Refer to the server documentation for requirements.
6.
Verify the fan airflow path is not blocked by cables or other material.
7.

Hard drive problems

System completes POST but hard drive fails
Action:
Be sure no loose connections (on page 52) exist.
1.
Be sure no device conflict exists.
2.
Be sure the hard drive is properly cabled and terminated if necessary.
3.
Be sure the hard drive data cable is working by replacing it with a known functional cable.
4.
Run Insight Diagnostics
5.
indicated.
No hard drives are recognized
Action:
Be sure no power problems (on page 65) exist.
1.
Check for loose connections (on page 52).
2.
Be sure that the controller supports the hard drives being installed.
3.
Be sure the controller has the most recent firmware.
4.
("HP Insight Diagnostics" on page 42) and replace failed components as
Troubleshooting 71