Troubleshooting 58
2.
Check for and disconnect any non-bootable USB devices.
Diskette drive cannot write to a diskette
Action
:
1.
If the diskette is not formatted, format the diskette.
2.
Be sure the diskette is not write protected. If it is, use another diskette or remove the write protection.
3.
Be sure you are attempting to write to the proper drive by checking the drive letter in the path statement.
4.
Be sure enough space is available on the diskette.
Fan problems
General fan problems are occurring
Action
:
1.
Be sure the fans are properly seated and working.
a.
Follow the procedures and warnings in the server documentation for removing the access panels
and accessing and replacing fans.
b.
Unseat, and then reseat, each fan according to the proper procedures.
c.
Replace the access panels, and then attempt to restart the server.
2.
Be sure the fan configuration meets the functional requirements of the server. Refer to the server
documentation.
3.
Be sure no ventilation problems exist. If you have been operating the server for an extended period 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.
4.
Be sure no POST error messages are displayed while booting the server that indicate temperature
violation or fan failure information. Refer to the server documentation for the temperature requirements
for the server.
5.
Replace any required non-functioning fans and restart the server. Refer to the server documentation for
specifications on fan requirements.
6.
Be sure all fan slots have fans or blanks installed. Refer to the server documentation for requirements.
7.
Verify the fan airflow path is not blocked by cables or other material.
Hard drive problems
System completes POST but hard drive fails
Action
:
1.
Be sure no loose connections (on page
41
) exist.
2.
Be sure no device conflict exists.
3.
Be sure the hard drive is properly cabled and terminated if necessary.
4.
Be sure the hard drive data cable is working by replacing it with a known functional cable.
5.
Run ProLiant MicroServer Insight Diagnostics (on page
32
) and replace failed components as indicated.
Summary of Contents for ProLiant MicroServer
Page 86: ...Support and other resources 86 ...