Memory Problems - HP ProLiant ML110 - G2 Server User Manual

Run HP Insight Diagnostics (on page 48). Then, replace failed components as indicated.
3.
When the drive is a replacement drive on an array controller, be sure that the drive is the same type
4.
and 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.
See the TPM replacement recovery procedure in the operating system documentation.
When migrating encrypted data to a new server, be sure to follow the recovery procedures in the
4.
operating system documentation.
Server response time is slower than usual
Action: Be sure the hard drive is not full, and increase the amount of free space on the hard drive, if
needed. It is recommended that hard drives should have a minimum of 15 percent free space.

Memory problems

General memory problems are occurring
Action:
•
Isolate and minimize the memory configuration. Use care when handling DIMMs
guidelines" on page 59).
Be sure the memory meets the server requirements and is installed as required by the server.
o
Some servers may require that memory banks be populated fully or that all memory within a
memory bank must be the same size, type, and speed. To determine if the memory is installed
properly, see the server documentation.
Check any server LEDs that correspond to memory slots.
o
If you are unsure which DIMM has failed, test each bank of DIMMs by removing all other
o
DIMMs. Then, isolate the failed DIMM by switching each DIMM in a bank with a known working
DIMM.
Remove any third-party memory.
o
•
To test the memory, run HP Insight Diagnostics (on page 48).
Server is out of memory
Action:
Be sure the memory is configured properly. Refer to the application documentation to determine the
1.
memory configuration requirements.
Be sure no operating system errors are indicated.
2.
Be sure a memory count error
3.
message displaying memory count during POST.
("Memory count error exists" on page 82) did not occur. Refer to the
("DIMM handling
Troubleshooting 81