Failed assigned drives

Failed to upgrade an assigned drive in the storage array.

One reason for the failure might be that the drive does not have the appropriate signature. Make sure that the affected drive is an authorized drive. Contact technical support for more information.

When replacing a drive, make sure that the replacement drive has a capacity equal to or greater than the failed drive you are replacing.

You can replace the failed drive while the storage array is receiving I/O.

Integrated hot spare drives

If the drive is marked as a hot spare and is in use for a volume group, the firmware upgrade process fails.

This error condition must be corrected before you can upgrade the firmware. Launch System Manager and use the Recovery Guru to resolve the problem.

Incomplete volume groups

If any drive that is part of a volume group is bypassed, removed or unresponsive, it is considered an incomplete volume group. An incomplete volume group prevents firmware upgrades.

If one or more volume groups or disk pools are incomplete, you must correct this error condition before you can upgrade the firmware. Launch System Manager and use the Recovery Guru to resolve the problem.

Exclusive operations (other than background media/parity scan) currently running on any volume groups

Cannot upgrade the firmware if any exclusive operations are in progress on a volume.

If one or more exclusive operations are in progress, the operations must complete before the firmware can be upgraded. Use System Manager to monitor the progress of the operations.

Missing volumes

Cannot upgrade the firmware if any volume is missing.

You must correct the missing volume condition before the firmware can be upgraded. Launch System Manager and use the Recovery Guru to resolve the problem.

Either controller in a state other than Optimal

Cannot upgrade the firmware if either controller is in a state other than optimal.

One of the storage array controllers needs attention. This condition must be corrected before the firmware can be upgraded. Launch System Manager and use the Recovery Guru to resolve the problem.

SPM Verify Database Controller check fails

Cannot upgrade the firmware because the storage partitions mappings database is corrupted.

A storage partitions mapping database error occurred on a controller. Contact technical support to resolve this issue.

Configuration Database Validation (If supported by the storage array's controller version)

Cannot upgrade the firmware because the configuration database is corrupted.

A configuration database error occurred on a controller. Contact technical support to resolve this issue.

MEL Related Checks

Cannot upgrade the firmware because the event log contains errors.

Contact technical support to resolve this issue.

More than 10 DDE Informational or Critical MEL events were reported in the last 7 days

Cannot upgrade the firmware because there are more than 10 DDE informational or critical MEL events reported in the last seven days.

Contact technical support to resolve this issue.

More than 2 Page 2C Critical MEL Events were reported in the last 7 days

Cannot upgrade the firmware because there are more than two page 2C critical MEL Events reported in the last seven days.

Contact technical support to resolve this issue.

More than 2 Degraded Drive Channel Critical MEL events were reported in the last 7 days

Cannot upgrade the firmware because there are more than two degraded drive channel critical MEL events reported in the last seven days.

Contact technical support to resolve this issue.

More than 4 critical MEL entries in the last 7 days

Cannot upgrade the firmware because there are more than four critical event log entries reported in the last seven days.

Contact technical support to resolve this issue.

A valid management IP address is required.

A valid controller IP address is required to perform this operation.

Contact technical support to resolve this issue.

The command requires an active management IP address for each controllers to be provided.

A controller IP address for each controller associated with the storage array is required for this operation.

Contact technical support to resolve this issue.

Unhandled download file type returned.

The specified download file is not supported.

Contact technical support to resolve this issue.

An error occurred during the firmware download upload procedure.

The firmware download failed because the controller cannot process the request. Verify the storage array is optimal and retry the operation.

If this error occurs again after verifying the storage array is optimal, contact technical support to resolve this issue.

An error occurred during the firmware activation procedure.

The firmware activation failed because the controller cannot process the request. Verify the storage array is optimal and retry the operation.

If this error occurs again after verifying the storage array is optimal, contact technical support to resolve this issue.

Timeout has reached while waiting for controller {0} to reboot.

The management software is unable to reconnect to controller {0} following a reboot. Validate there is an operational connection path to the storage array and retry the operation if it did not complete successfully.

If this error occurs again after verifying the storage array is optimal, contact technical support to resolve this issue.