HP Integrity rx1600 Deployment Manual page 64

Smartsetup scripting toolkit deployment guide: hp integrity servers with linux
Hide thumbs Also See for Integrity rx1600:
Table of Contents

Advertisement

Table 6-8 Error Codes (continued)
Code
Error
2849
Invalid
ClearConfigurationWithDataLoss
parameter
2825
Invalid Array
2826
Array not specified
2827
New Array ID does not match the
next available Array ID
2828
New Array ID already exists
2829
Cannot create Array
2830
Cannot expand Array
2831
Cannot change Array Spare
2832
Invalid Physical Drive
2833
Invalid Spare
1053
Cannot remove Physical Drives
from existing array
1052
Array requires an odd number of
drives
2834
Invalid Logical Drive
2835
Logical Drive not specified
2836
New Logical Drive ID does not
match the next available Logical
Drive ID
64
Utilities Reference
Reason
The specified ClearConfigurationWithDataLoss parameter
is not correct.
The Array ID is invalid.
The array command is missing from the script file. Some
commands were found that require an array to work on.
The Array ID in the script file does not match the Array ID
of the newly created array. For example, if you have Array
A already and the script file tries to create Array C (without
Array B), the script generates this error.
When running in Configure mode, this error happens when
the Array ID in the script file already exists in the
configuration. Configure mode can only create new arrays.
The controller does not allow a new array to be created. This
could be because there are no unassigned physical drives on
the controller, or the maximum number of arrays or logical
drives has already been reached.
The array could not be expanded. This could be because the
controller does not support expansion, or the current
configuration does not allow expansion to occur on the array.
The spare state of the array could not be changed. This can
happen when you are trying to add a spare or drop a spare.
The current configuration does not allow a spare state change
for the array.
The physical drive listed for the array is not a valid physical
drive, or it is a physical drive that is not capable of being
placed in the array.
The spare drive listed for the array is not a valid spare drive,
or it is a drive that is not capable of being placed on the array
as a spare.
One or more drives are not listed in an existing array. This
is illegal because removing physical drives from a configured
array causes data loss.
This error message can occur if the user is attempting to add
an odd number of drives to an existing array that has RAID
1 logical drives. If the controller has RAID 1 logical drives
and supports RAID 1 -> RAID 5/RAID ADG migration, this
error does not occur. However, if the controller does not
support migration, this error occurs.
The Logical Drive ID is not valid.
The Logical Drive command is missing from the script file.
Some commands were found that require a Logical Drive to
work on.
The Logical Drive ID in the script file does not match the
Logical Drive ID of the newly created logical drive. For
example, if you already have Logical Drive 1 and the script
file attempts to create Logical Drive 3 (without Logical Drive
2), the script generates this error. This error can occur when
using an input file with logical drive numbers that are not
sequential. In this case, the logical drive numbers need to be
changed so that they are sequential in the input file.

Advertisement

Table of Contents
loading

Table of Contents