HP Integrity Superdome SX1000 SmartSetup Scripting Toolkit Deployment Guide: H - Page 64

The Logical Drive ID is not valid., Reason, Error

Get HP Integrity Superdome SX1000 PDF manuals and user guides View all HP Integrity Superdome SX1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 64 highlights

Table 6-8 Error Codes (continued) Code 2849 2825 2826 2827 2828 2829 2830 2831 2832 2833 1053 1052 2834 2835 2836 Error Reason Invalid ClearConfigurationWithDataLoss parameter The specified ClearConfigurationWithDataLoss parameter is not correct. Invalid Array The Array ID is invalid. Array not specified The array command is missing from the script file. Some commands were found that require an array to work on. New Array ID does not match the The Array ID in the script file does not match the Array ID next available 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. New Array ID already exists 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. Cannot create Array 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. Cannot expand Array 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. Cannot change Array Spare 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. Invalid Physical Drive 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. Invalid Spare 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. Cannot remove Physical Drives from existing array 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. Array requires an odd number of This error message can occur if the user is attempting to add drives 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. Invalid Logical Drive The Logical Drive ID is not valid. Logical Drive not specified The Logical Drive command is missing from the script file. Some commands were found that require a Logical Drive to work on. New Logical Drive ID does not The Logical Drive ID in the script file does not match the match the next available Logical Logical Drive ID of the newly created logical drive. For Drive ID 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. 64 Utilities Reference

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
Table 6-8 Error Codes
(continued)
Reason
Error
Code
The specified ClearConfigurationWithDataLoss parameter
is not correct.
Invalid
ClearConfigurationWithDataLoss
parameter
2849
The Array ID is invalid.
Invalid Array
2825
The array command is missing from the script file. Some
commands were found that require an array to work on.
Array not specified
2826
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.
New Array ID does not match the
next available Array ID
2827
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.
New Array ID already exists
2828
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.
Cannot create Array
2829
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.
Cannot expand Array
2830
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.
Cannot change Array Spare
2831
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.
Invalid Physical Drive
2832
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.
Invalid Spare
2833
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.
Cannot remove Physical Drives
from existing array
1053
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.
Array requires an odd number of
drives
1052
The Logical Drive ID is not valid.
Invalid Logical Drive
2834
The Logical Drive command is missing from the script file.
Some commands were found that require a Logical Drive to
work on.
Logical Drive not specified
2835
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.
New Logical Drive ID does not
match the next available Logical
Drive ID
2836
64
Utilities Reference