SSA Scripting 92
The specified rebuild priority is not supported.
The specified expand priority is not supported. This
error also occurs if the controller does not allow
expansion, and therefore does not support expand
priority.
The Array command is missing from the script file.
Some commands were found that require an Array
to be specified.
New Array ID does not match the next
available Array ID
The array ID in the script file does not match the
array ID of the next available array. For example, if
the configuration has an Array A and the input file
specifies Array C (without Array B), then the script
generates this error.
New Array ID already exists
The array ID specified in the script file (in Configure
mode) already exists in the configuration. Configure
mode can only create new arrays.
The controller will not allow a new array to be
created, either because the controller has no
unassigned physical drives attached or because the
maximum number of arrays or logical drives has
been reached already.
The Array could not be expanded, either because the
controller does not support expansion, or the current
configuration does not allow expansion to occur on
the array.
Cannot change Array Spare
The spare state of the array could not be changed.
This error can occur when you attempt to add or
drop a spare and the current configuration does not
allow a spare state change for the array.
Invalid physical drive. Possible reasons for
this include: a typing error, the drive already
exists in an array, the drive type does not
match, or it is a failed drive.
A specified physical drive is not a valid physical
drive, or it cannot be placed in the array.
A specified spare is not a valid spare drive, or it
cannot be placed in the array as a spare.
The logical drive ID is not valid.
New Logical Drive ID does not match the
next available logical drive ID.
If you are attempting to replicate a
configuration that has non-consecutive
logical drive numbers, then you must
change the script file so that the logical
drive numbers are consecutive.
The script file specifies a logical drive ID that is not
the first unused ID in the sequence. For example,
this message appears if the controller has only
Logical Drive 1 and the script file specifies creation
of Logical Drive 3 (omitting Logical Drive 2). A
common cause of this error is that the input file
specifies nonsequential logical drive numbers. In
this case, change the logical drive numbers in the
input file so that they are sequential.
New Logical Drive ID already exists
This error occurs in Configure mode when the logical
drive ID specified in the script file already exists in
the configuration. In Configure mode, you can create
new logical drives only.
Cannot create Logical Drive
The array has no free space, or the maximum
number of logical drives has been reached already.
Cannot migrate Logical Drive RAID
The controller does not support RAID migration, or
migration is not possible with the current controller
configuration.
Cannot extend Logical Drive
The controller does not support extension, or the
current controller configuration cannot be extended.
For example, extension is not possible if the array
To Next Page
Loading...
Need help?
General