3.4.0 Matrix Server Administration Guide

Appendix B: Error and Event Log Messages 228

Fencing operation failed, reboot NN.NN.NN.NN ASAP.

NN.NN.NN.NN stopped matrix communication DATE HH:MM but

cannot be excluded from the matrix because of a networking

or fencing hardware failure or misconfiguration. To protect

filesystem integrity, some or all filesystem operations may

be paused until NN.NN.NN.NN is rebooted or until fencing

operations can be performed.

The server is unresponsive but Matrix Server is unable to exclude it from

the matrix because the fencing device is not responding to the fencing

request. Possibly the Ethernet connection to the FibreChannel switch has

failed. The server should be rebooted as soon as possible.

IllegalDisks: One or more imported disks has more than 31

partitions. Matrix Server only supports 31 partitions per

disk. Some volume operations may fail on partitions higher

than this limit. See the Administrator's Guide for further

information.

As of Matrix Server 3.4, the maximum number of partitions on a disk or

LUN is limited to 31. If you upgraded to Matrix Server 3.4, you may have

imported disks or LUNs with more than 31 partitions, and may have

created dynamic volumes using those higher-numbered partitions. The

higher-numbered partitions will continue to work correctly; however,

you should be aware of the following:

• A new volume cannot include subdevices having partition numbers

above 31. Existing volumes cannot be extended to include the higher-

numbered partitions.

• You will not be able to take a hardware snapshot of partitions with

numbers above 31.

The Alert will remain until the disks containing more than 31 partitions

are deported.

Internal error: unable to initialize security

Internal error: unable to initialize security. Java program

problem. Contact service.