Message | Comment or explanation (if not |
|
|
Invalid read cache/write cache | The specified cache ratio is not supported by either the controller or |
ratio | the current controller configuration. |
|
|
Invalid rebuild priority | |
|
|
Invalid Sectors | The specified Max Boot setting is invalid or is not supported with the |
| current configuration. |
|
|
Invalid Size | The specified size is invalid or is not possible with the current |
| configuration. |
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. |
|
|
Invalid SSP adapter ID | |
|
|
Invalid SSP state | |
|
|
Invalid stripe size | The specified stripe size is either invalid, not supported with the |
| current RAID level, or not supported with the current configuration. |
|
|
Invalid SurfaceScanDelay | |
|
|
License key is not a controller | The entered license key is for a feature that the controller does not |
feature license key | support. |
Logical drive not specified | Some commands require a logical drive, but no logical drive is |
| specified in the script file. |
|
|
More than one (text) command | The specified command should be used only once per section. |
cannot exist in the same section |
|
|
|
New array ID already exists | This error occurs in Configure mode when the array ID in the script |
| file already exists in the configuration. You can only use Configure |
| mode to create new arrays. |
|
|
New array ID does not match the | The array ID that you specified in the script file does not match the |
next available array ID | ID of the newly created array. For example, the script generates this |
| error if you have only an array A and the script file specifies |
| creation of array C (missing array B). |
|
|
New logical drive ID already | This error occurs in Configure mode when the logical drive ID in the |
exists | script file already exists in the configuration. You can only use |
| Configure mode to create new logical drives. |
|
|
New logical drive ID does not | The logical drive ID that you specified in the script file does not |
match the next available logical | match the ID of the newly created logical drive. For example, the |
drive ID | script generates this error if you have only logical drive 1 and the |
| script file specifies creation of logical drive 3 (missing logical drive |
| 2). This error can occur when using an input file with logical drive |
| numbers that are not sequential. In this case, change the logical |
| drive numbers so that they are sequential in the input file. |
No controllers detected | This error applies to input mode only. If no controllers are detected |
| in capture mode, the capture file is empty. |
|
|
Slot information is not available | You cannot run Input mode on internal controllers that do not have |
| slot information online. For Microsoft® Windows®, this means that |
| you must load the System Management Driver. |
Too many coinciding expansion, | ACU does not support multiple simultaneous expansions, migrations, |
migration, or extension operations | or extensions without saving the configuration between operations. |
| Limit the number of such configuration changes in this script. |
|
|
(text) is not an HBA command | A command found in the HBA section is not a valid command for |
| this section. |
Scripting in ACU 42
