HP ProLiant MicroServer User Manual page 59

No hard drives are recognized
Action:
Be sure no power problems (on page 52) exist.
1.
Check for loose connections (on page 41).
2.
Be sure that the controller supports the hard drives being installed.
3.
Be sure the controller has the most recent firmware.
4.
If the controller supports license keys and the configuration is dual domain, be sure the license key is
5.
installed.
Hard drive is not recognized by the server
Action:
Check the LEDs on the hard drive to be sure they indicate normal function. Refer to the server
1.
documentation or the HP website (http://www.hp.com) for information on hard drive LEDs.
Be sure no loose connections (on page 41) exist.
2.
Remove the hard drive and be sure the configuration jumpers are set properly.
3.
If using an array controller, be sure the hard drive is configured in an array. Run the array configuration
4.
utility.
Be sure the drive is properly configured. Refer to the drive documentation to determine the proper
5.
configuration.
If it is a non-hot-plug drive, be sure a conflict does not exist with another hard drive. Check for SCSI ID
6.
conflicts.
Be sure the correct drive controller drivers are installed.
7.
A new hard drive is not recognized
Action:
Be sure the drive is supported. To determine drive support, see the server documentation or the HP
1.
website (http://www.hp.com/go/bizsupport).
Be sure the drive bay is not defective by installing the hard drive in another bay.
2.
Run ProLiant MicroServer Insight Diagnostics (on page 32). Then, replace failed components as
3.
indicated.
When the drive is a replacement drive on an array controller, be sure that the drive is the same type and
4.
of the same or larger capacity than the original drive.
Data is inaccessible
Action:
Be sure the files are not corrupt. Run the repair utility for the operating system.
1.
Be sure no viruses exist on the server. Run a current version of a virus scan utility.
2.
When a TPM is installed and is being used with BitLocker™, be sure the TPM is enabled in RBSU
3.
("ROM-Based Setup
operating system documentation.
When migrating encrypted data to a new server, be sure to follow the recovery procedures in the
4.
operating system documentation.
Utility" on page 31). See the TPM replacement recovery procedure in the
Troubleshooting 59