Troubleshooting, Known issues, Write cache not flushed on shutdown – HP 10 User Manual
Page 38
Troubleshooting 38
Troubleshooting
This chapter describes common problems and probable causes, known issues, and provides general
troubleshooting advice.
To begin troubleshooting deployment problems, review the list of Known Issues below first to see if
any issues match the environment and symptoms. If none of the known issues apply, see “Common ”
for issue diagnosis. For general troubleshooting advice, see “Basic troubleshooting techniques.”
Known issues
The following is a list of known issues associated with Solaris deployment and ProLiant servers.
Write cache not flushed on shutdown
Solaris does not flush hard drive controller cache to disk on shutdown.
•
OS releases affected—Solaris 10 update 5/10
•
Hardware affected—HP Third Generation Smart Array Controllers with Battery Backed Write
Cache.
•
Description—There is a known issue causing Solaris to not properly flush the disk controller
caches to disk at shutdown. As a result of this issue, the following error message may be
displayed on a ProLiant server running Sun Solaris 10 and configured with a Smart Array
Controller equipped with Battery-Backed Write Cache (BBWC):
POST Error: 1792 - Drive Array Reports Valid Data Found in Array
Accelerator
For more information please refer advisory
•
Workaround—Ensure that the cache is properly flushed prior to shutdown. Do this by executing
the following command before every shutdown:
# swap -d
Optionally, shutdown the system using these commands:
# init 0
# halt
Solaris stops responding on HP ProLiant DL580 G5 server
Solaris may stop responding, or will respond poorly if a PCI-Express Controller is configured in PCI-
Express slots 1, 2, 4, 5, 7, or 8 on a DL580 G5 server.
•
OS releases affected—Solaris 10 8/07, 5/08
•
Hardware affected—HP ProLiant DL580 G5
•
Description—Solaris may stop responding, or will not respond properly during deployment if a
PCI-Express Controller, such as a Smart Array P800 is installed in slots 1, 2, 4, 5, 7, or 8. The
issue occurs because hot swap is enabled but not supported by the DL580 G5 server. For more