Previous Topic

Next Topic

ACU scripting error messages

Error code

Error message

Comment or clarification

1

General error.

The ACU process cannot be initiated. You might see this error message if you are not authenticated to use ACU or if ACU is already running.

268

Error saving controller.

ACU cannot save one or more controller configurations.

278-282

Controller is locked by another machine or user.

โ€”

290

Error communicating with controller.

โ€”

516

Internal error.

An error occurred during the configuration process, but ACU cannot identify the error because there is an internal ACU error.

1052

Array requires an odd number of drives.

This error message occurs if you attempt to add an odd number of drives to an array that has RAID 1 logical drives, and the controller does not support RAID-level migration.

1053

Cannot remove physical drives from existing array.

This error message occurs if a script that is running in Reconfigure action mode lists fewer physical drives than already exist in the array. ACU interprets this script as a request to remove physical drives from an existing array, but satisfying this request causes data loss, so ACU prevents the script from running.

1065-1066

Too many coinciding expansion, migration, or extension operations.

ACU does not support multiple simultaneous expansions, migrations, or extensions without saving the configuration between operations. Limit the number of such configuration changes in the script.

1091

Controller does not support SSP.

โ€”

1093

Controller requires physical drives to set license keys.

โ€”

1102

Slot information is not available.

You cannot run a script in Input mode on internal controllers that do not have slot information online. Systems running Microsoftยฎ Windowsยฎ must have the System Management Driver loaded.

1110

Controller does not support license keys.

โ€”

1111

Invalid license key.

โ€”

1112

Controller has maximum number of license keys.

โ€”

1114

Controller requires non-failed physical drives to set license keys.

โ€”

2564

Controller is locked by another machine or user.

โ€”

2818

Invalid Method.

The scripted Method value is not valid.

2819

Invalid Controller.

The scripted controller does not match any existing controllers.

2820

Could not detect controller <text>.

โ€”

2821

No controllers detected.

This error applies to Input mode only. If no controllers are detected in Capture mode, the capture file is empty.

2822

Invalid read cache/write cache ratio.

The specified cache ratio is not supported by either the controller or the current controller configuration.

2823

Invalid rebuild priority.

โ€”

2824

Invalid expand priority.

This error message appears if the expand priority value specified in the script is not supported. This message also appears if expansion is not possible because the Expand Priority feature is then not supported. (Expansion might be temporarily unavailable on a controller that normally supports expansion if, for example, the cache battery has low charge, another expansion or migration is already in progress, or the array has the maximum supported number of physical drives.)

2825

Invalid array.

The array ID is invalid.

2826

Array not specified.

The script file has commands that require an array, but no array is specified.

2827

New array ID does not match the next available array ID.

The scripted array ID is not the next ID in sequence, based on the IDs of the existing arrays. For example, only array A exists and the script file specifies creation of array C (omitting array B).

2828

New array ID already exists.

This error occurs in Configure mode when the array ID specified in the script file already exists in the configuration. In Configure mode, you can create only new arrays.

2829

Cannot create array.

The controller has no unassigned physical drives, or it already has the maximum number of arrays or logical drives.

2830

Cannot expand array.

The controller does not support expansion, or the current controller configuration is not expandable.

2831

Cannot change array spare.

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.

2832

Invalid physical drive.

A specified physical drive is not a valid physical drive, or it cannot be placed in the array.

2833

Invalid spare.

A specified spare is not a valid spare drive, or it cannot be placed in the array as a spare.

2834

Invalid logical drive.

โ€”

2835

Logical drive not specified.

The script file has commands that require a logical drive, but no logical drive is specified.

2836

New logical drive ID does not match the next available logical drive ID.

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.

2837

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 only new logical drives.

2838

Cannot create logical drive.

The array has no free space, or the maximum number of logical drives has already been reached.

2839

Cannot migrate logical drive RAID.

The controller does not support RAID migration, or migration is not possible with the current controller configuration.

2840

Cannot migrate logical drive stripe size.

The controller does not support stripe size migration, or migration is not possible with the current controller configuration.

2841

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 has no free space.

2842

Invalid RAID.

The specified RAID level is invalid or is not possible with the current configuration.

2843

Invalid size.

The specified size is invalid or is not possible with the current configuration.

2844

Invalid stripe size.

The specified stripe size is invalid, or not supported by the current RAID level, or not possible with the current configuration.

2845

Invalid sectors.

The specified MaxBoot setting is invalid or is not possible with the current configuration.

2846

Cannot change logical drive sectors.

You cannot change the MaxBoot setting on a configured logical drive because doing so causes data loss.

2847

Invalid array accelerator setting.

The specified array accelerator setting is invalid or is not supported by the current configuration.

2848

Cannot change logical drive array accelerator setting.

You cannot change the array accelerator setting for the current controller configuration.

2849

Invalid ClearConfigurationWithDataLoss parameter.

โ€”

2850

Controller does not support RAID Array ID.

โ€”

2851

Invalid RAID Array ID.

The scripted RAID Array ID is invalid. Use characters from the set aโ€“z, Aโ€“Z, 0โ€“9, !, @, #, *, (, ), ,, -, _, +, :, ., /, and [space]. The ID cannot end with a space character or exceed the maximum number of characters allowed by the controller.

2852

Invalid SSP state.

โ€”

2853

Cannot change SSP settings.

โ€”

2854

Invalid SSP adapter ID.

โ€”

2855

Controller does not support logical drive SSP states. Use the SSPState controller command to set the controller SSP state.

โ€”

2856

Controller does not support controller SSP state. Use the LogicalDriveSSPState logical drive command to set SSP states for each logical drive.

โ€”

2857

Invalid surface scan delay.

โ€”

2861

Controller does not support redundancy settings.

The controller is not redundant or does not support redundancy settings.

2864

Invalid preferred path mode.

The specified value for the preferred path mode is not valid, or the controller is not available.

2865

Invalid preferred path.

The specified preferred path is not a valid chassis slot for an available active controller, or the controller is not available.

2866

Failure opening capture file <text>.

โ€”

2867

Failure opening input file <text>.

โ€”

2868

Failure opening error file <text>.

โ€”

2869

<text> command expected.

The <text> command is missing or in the wrong place in the script file.

2870

<text> is not a supported command.

โ€”

2871

<text> is not a Controller command.

The <text> command does not belong in the Controller section of the script file.

2872

<text> is not an Array command.

The <text> command does not belong in the Array section of the script file.

2873

<text> is not a Logical Drive command.

The <text> command does not belong in the Logical Drive section of the script file.

2874

<text> is not an HBA command.

The <text> command does not belong in the HBA section of the script file.

2875

More than one <text> command cannot exist in the same section.

โ€”

2876

Invalid physical drive count.

The script specifies more drives than are available of the specified drive type.

2877

No spares available.

No drives were found that could be used as spares for the specified array.

2878

Spare request for RAID 0 is invalid.

RAID 0 does not support spares.

2879

Reset and reconfigure combined error.

A controller reset with data loss was specified while in Reconfigure mode.

2880

Invalid drive type specified.

โ€”

2882

Invalid value for MNPDelay. Valid range is 0 (disabled) to 60 minutes.

โ€”

2883

Invalid controller configuration value. Expecting Yes or No.

โ€”

2884

Invalid value for QueueDepth. Valid range is from 2 to 32, or Auto.

โ€”