HP StorageWorks Scalable File Share System Installation and Upgrade Guide Version 2.2

Error messages from the configure array command J–7
J.6 Error messages from the configure array command
J.6.1 Invalid LUN size
The largest LUN size possible is 2TB. If an error message similar to the following is displayed when you
enter the configure array array_number command, it indicates that the LUN size specified in the
command is too large:
09:28:26 south1 -- Error encountered configuring array 2
09:28:26 south1 -- Invalid LUN size (2327055MB). Max size is 2097151MB
To correct the problem, enter the configure array array_number command again, specifying LUNs
of 2TB or less.
J.6.2 Array is not connected to the same controller and port
The configure array command may fail and show output similar to the following:
sfs> configure array 5
Command id 360
16:19:31 south3 -- <Unallocated>
16:19:38 south3 -- <Allocated>
16:19:38 south3 -- Initialize MSA20 CLI
16:20:36 south3 -- <Error> Command Failed on: south3
16:20:36 south3 -- Checking CCISS Host Bus Adaptors
16:20:36 south3 -- Configuring array 5
16:20:36 south3 -- Checking array 5 is valid
16:20:36 south3 -- Error encountered configuring array 5
16:20:36 south3 -- Failed configure: Array 5 is not connected to the same
16:20:36 south3 -- controller and port on south3 and south4
16:20:36 south3 -- Array 5 is not configured. Check cables, correct the problem
16:20:36 south3 -- and try the configure arra
This indicates that the cables used to connect the servers in the server pair to the SFS20 array are not
connected to the correct port on the servers. See Section 1.4.2 of this guide for information on cabling
requirements for servers connected to SFS20 arrays.
When you have connected the cables to the correct port on the servers, reboot both of the servers, then
enter the configure array array_number command again.
J.6.3 Preferred server for the SFS20 array is down
If the preferred server for the SFS20 is down, the configure array command fails and shows output
similar to the following:
sfs> configure array 5
Command id 20
16:29:09 south5 -- <Unallocated>
16:29:24 south5 -- <Error> Failed to signal daemon south5
Command has finished:
south5 -- <Error> Failed to signal daemon south5
*** Server States ***
To work around this problem, change the preferred server for the array using the set array command,
as shown in the following example. The new preferred server must be the peer server of the server that is
down (that is, it must be connected to the array):
sfs> set array 5 preferred_server=south6
When you have changed the preferred server for the array, enter the configure array command again.