EasyManua.ls Logo

HP Guardian Errors - Page 84

HP Guardian Errors
283 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Recovery Take appropriate action to recover the disk process and then retry the request.
5017 (%11631) Unable to read one of the SMF catalog
tables. (device type: 3.36, 25.0, or 52.0)
Cause A process other than the NonStop Storage Management Foundation (SMF) subsystem
attempted to directly access an SMF catalog file and a file-system error occurred.
Effect The requested operation is not performed.
Recovery Refer to the event log for detailed information and take appropriate action.
5018 (%11632) An error occurred during message processing.
(device type: 3.36, 25.0, or 52.0)
Cause A file-system request (create, purge, or alter) was made against a NonStop Storage
Management Foundation (SMF) object, and the reply from the disk process contained an error.
This often indicates a HP internal error.
Effect The requested operation is not performed.
Recovery Refer to the event log for additional information and take action as appropriate. Retry
the request. If the problem persists, contact your service provider.
5028 (%11644) Unable to read a received message.
(device type: 3.36, 25.0, or 52.0)
Cause A NonStop Storage Management Foundation (SMF) process received an invalid message
from any process.
Effect The message is ignored and the requested operation is not performed.
Recovery Refer to the event log for additional information and take action as appropriate. Retry
the request. If the problem persists, contact your service provider.
5034 (%11652) Unable to start the thread manager.
(device type: 3.36, 25.0, or 52.0)
Cause A request was made to a NonStop Storage Management Foundation (SMF) disk process
or pool process, which was unable to start the thread manager while processing the request. This
error is typically caused by a shortage of some resource, usually memory.
Effect The requested operation is not performed.
Recovery Refer to the event log for additional information and take action as appropriate. The
recovery might be to wait and retry the request when the system is less busy. If the problem persists
or if it occurs frequently, contact your service provider.
5035 (%11653) Unable to start a thread.
(device type: 3.36, 25.0, or 52.0)
Cause A request was made to a NonStop Storage Management Foundation (SMF) disk process
or pool process, which was unable to start a thread while processing the request. This error is
typically caused by a shortage of some resource, usually memory.
Effect The requested operation is not performed.
84 File-System Errors

Table of Contents

Related product manuals