HP Scripting Toolkit 9.10 for Linux User Guide
Table Of Contents
- HP Scripting Toolkit for Linux User Guide
- Contents
- 1 Introduction
- 2 Deployment using the Scripting Toolkit
- 3 Booting and OS installation
- 4 Scripting Toolkit utilities
- Native package formats
- Syntax conventions
- Utility online help
- Using Scripting Toolkit utilities
- Using REBOOT
- Using SETBOOTORDER
- Using STATEMGR
- Using RBSURESET
- Using BOOTEXTRACT
- Using HPDISCOVERY
- Using IFHW
- Using HWQUERY
- Using CONREP
- CONREP command-line syntax
- CONREP command line arguments
- CONREP return codes
- CONREP screen output
- CONREP -s (Store to Data file) Example usage for HP ProLiant servers not using the Oxx ROM family
- CONREP –l (Load from Data File) Example Usage for HP ProLiant servers not using the Oxx ROM family
- CONREP Data File Sample Contents for HP ProLiant servers not using the Oxx ROM family
- CONREP command file contents for HP ProLiant servers not using the Oxx ROM family
- Using HPRCU
- Using HPACUSCRIPTING
- Using HPLPCFG
- Using LO100CFG
- Using HPQLAREP
- Using HPONCFG
- 5 Troubleshooting
- 6 Support and other resources
- 7 Documentation feedback
- Acronyms and abbreviations
- Index

Comment or clarificationError messageError code
This error message appears if you try to change the number
of spares in an array when the configuration does not support
the addition or subtraction of spares.
Cannot change array spare.2831
A specified physical drive is not a valid physical drive, or it
cannot be placed in the array.
Invalid physical drive.2832
A specified spare is not a valid spare drive, or it cannot be
placed in the array as a spare.
Invalid spare.2833
—Invalid logical drive.2834
The script file has commands that require a logical drive, but
no logical drive is specified.
Logical drive not specified.2835
The script file specifies a logical drive ID that is not the first
unused ID in the sequence. For example, this message
New logical drive ID does not match the
next available logical drive ID.
2836
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 non-sequential logical drive numbers. In this case,
change the logical drive numbers in the input file so that they
are sequential.
This error occurs in Configure mode when the logical drive
ID specified in the script file already exists in the
New logical drive ID already exists.2837
configuration. In Configure mode, you can create only new
logical drives.
The array has no free space, or the maximum number of
logical drives has already been reached.
Cannot create logical drive.2838
The controller does not support RAID migration, or migration
is not possible with the current controller configuration.
Cannot migrate logical drive RAID.2839
The controller does not support stripe size migration, or
migration is not possible with the current controller
configuration.
Cannot migrate logical drive stripe size.2840
The controller does not support extension, or the current
controller configuration cannot be extended. For example,
extension is not possible if the array has no free space.
Cannot extend logical drive.2841
The specified RAID level is invalid or is not possible with the
current configuration.
Invalid RAID.2842
The specified size is invalid or is not possible with the current
configuration.
Invalid size.2843
The specified stripe size is invalid, or not supported by the
current RAID level, or not possible with the current
configuration.
Invalid stripe size.2844
The specified MaxBoot setting is invalid or is not possible
with the current configuration.
Invalid sectors.2845
You cannot change the MaxBoot setting on a configured
logical drive because doing so causes data loss.
Cannot change logical drive sectors.2846
The specified array accelerator setting is invalid or is not
supported by the current configuration.
Invalid array accelerator setting.2847
You cannot change the array accelerator setting for the
current controller configuration.
Cannot change logical drive array
accelerator setting.
2848
—Invalid ClearConfigurationWithDataLoss
parameter.
2849
—Controller does not support RAID Array ID.2850
Using HPACUSCRIPTING 49










