HP ProLiant ML100 Series User Manual page 65

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 Uti
operating system documentation.
When migrating encrypted data to a new server, b
4.
operating system documentation.
Server response time is slower than usual
Action: Be sure the hard drive is not full, and increa
needed. It is recommended that hard drives should
Memor y p oblems r
General memory problems are occurring
Actio n:
•
Isolate and minimize the memory configuration.
guidelines" on page 44).
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
memory bank must be the same size, type, and speed. To determine if the memory is install
properly, see the server documentation.
Check any server LE
o
If you are unsure which DIMM has fa
o
DIMMs. Then, isolate the failed DIMM by switching each DIMM in a bank with a k
DIMM.
Remove any third-party memory.
o
•
To test the memory, run HP Insight Diagnostics.
Server is out of memory
Action:
Be sure the memory is configured properly. Refer to the application documentation to determine the
1.
me ory configuration requirements. m
Be su re no operating system errors are indicated.
2.
Be sure a memory count error
3.
message displaying memory count during POST.
lity" on page 30). See the TPM replacement recovery procedure in the
se the amount of free space on the hard drive, if
have a minimum of 15 percent free space.
Ds that correspond to memory slots.
iled, test each bank of DIMMs by removing all other
("Memory count error
e sure to follow the recovery procedures in the
Use care when handling DIMMs
exists" on page 66) did not occur. Refer to the
("DIMM handling
a
ed
nown working
Troubleshooting 65