3.5.1 Matrix Server Administration Guide

Appendix B: Error and Log File Messages 338

Singleton matrix unable to take control of SAN. Possibly

this server has not been added to the matrix or has been

deleted from the matrix, or possibly a network failure has

partitioned this server from the rest of the matrix. As a

result, some or all filesystem operations may be paused

throughout the matrix. In addition, filesystem mounts and

unmounts and disk imports and deports cannot be performed.

Check the matrix configuration and add the server if it is not currently a

member. Also check the network connections and configuration for the

server to ensure that it can communicate with the rest of the matrix.

This monitor does not appear to be living on any particular

server. This is a UI bug.

If you receive this message, report it to PolyServe Technical Support at

your earliest opportunity.

Unable to access device information

The mprepair and sandiskinfo utilities issue this error when they cannot

report any disks. Following are some possible causes for the error:

• The node is fenced.

• The matrix is configured for fabric fencing but the FC switches to

which the storage is connected have not been configured properly for

Matrix Server.

• There is a hardware problem with the storage and/or components in

the path to the storage. (In this case, the operating system will not be

able to see and/or access the disks either).

Unknown user - NO_SUCH_USER

Unknown user - SYSTEM_ERROR

Unknown user - SYSTEM_ERROR: Unable to open pmxs_passwd file.

The Management Console experienced an error while trying to

authenticate itself to ClusterPulse. The pmxs_passwd file should be

regenerated with the mxpass command.