Memory problems, Y p oblems – HP ProLiant Series ML100 User Manual
Page 65
Data is inaccessible
Action:
1.
Be sure the files are not corrupt. Run the repair utility for the operating system.
lity
" on page
). See the TPM replacement recovery procedure in the
e sure to follow the recovery procedures in the
se the amount of free space on the hard drive, if
have a minimum of 15 percent free space.
Memor
r
Actio
Use care when handling DIMMs ("
DIMM handling
Be sure the memory meets the server requirements and is installed as required by the server.
a
ed
Ds that correspond to memory slots.
iled, test each bank of DIMMs by removing all other
nown working
out of memory
Be sure the memory is configured properly. Refer to the application documentation to determine the
m
2.
Be su
Be sure a memory count error ("
Memory count error exists
" on page
) did not occur. Refer to the
2.
Be sure no viruses exist on the server. Run a current version of a virus scan utility.
3.
When a TPM is installed and is being used with BitLocker™, be sure the TPM is enabled in RBSU
("
ROM-Based Setup Uti
operating system documentation.
4.
When migrating encrypted data to a new server, b
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
y p oblems
General memory problems are occurring
n:
•
Isolate and minimize the memory configuration.
guidelines
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.
o
Check any server LE
o
If you are unsure which DIMM has fa
DIMMs. Then, isolate the failed DIMM by switching each DIMM in a bank with a k
DIMM.
o
Remove any third-party memory.
•
To test the memory, run HP Insight Diagnostics.
Server is
Action:
1.
me ory configuration requirements.
re no operating system errors are indicated.
3.
message displaying memory count during POST.
Troubleshooting 65