Appendix B: Error Messages and Descriptions

> Appendix B: Error Messages and Descriptions

> Error Handling

> Each message that appears in the event log has an error level that indicates the severity of the event, as shown in the following table.

> Table 16. Error Messages and Descriptions

> Number | Event Text
> 0x00 | Command completed successfully
> 0x01 | Invalid command
> 0x02 | DCMD Opcode is invalid
> 0x03 | Input parameters are invalid
> 0x04 | Invalid sequence number
> 0x05 | Abort is not possible for the requested command
> 0x06 | Application host code not found
> 0x07 | Application already in use - try later
> 0x08 | Application not initialized
> 0x09 | Given array index is invalid
> 0x0a | Unable to add missing drive to array, as row has no empty slots
> 0x0b | Some of the CFG resources conflict with each other or the current configuration
> 0x0c | Invalid device ID/select-timeout
> 0x0d | Drive is too small for requested operation
> 0x0e | Flash memory allocation failed
> 0x0f | Flash download already in progress
> 0x10 | Flash operation failed
> 0x11 | Flash image was bad
> 0x12 | Downloaded Flash image is incomplete
> 0x13 | Flash OPEN was not done
> 0x14 | Flash sequence is not active
> 0x15 | Flush command failed
> 0x16 | Specified application does not have host-resident code
> 0x17 | LD operation not possible - CC is in progress
> 0x18 | LD initialization in progress
> 0x19 | LBA is out of range
> 0x1a | Maximum LDs are already configured
> 0x1b | LD is not OPTIMAL
> 0x1c | LD Rebuild is in progress
> 0x1d | LD is undergoing reconstruction
> 0x1e | LD RAID level is wrong for requested operation
> 0x1f | Too many spares assigned
> 0x20 | Scratch memory not available - try command again later
> 0x21 | Error writing MFC data to SEEPROM
> 0x22 | SuperCap is missing Do not hot plug the SuperCap when power is supplied to the controller or if there is residual charge on the SuperCap, doing so might damage both the SuperCap and the controller board.
> 0x23 | Item not found
> 0x25 | PD CLEAR operation is in progress
> 0x27 | Patrol Read is disabled
> 0x28 | Given row index is invalid
> 0x2d | SCSI command done, but non-GOOD status was received-see mf.hdr.extStatus for SCSI_STATUS
> 0x2e | I/O request for MFI_CMD_OP_PD_SCSI failed
> 0x2f | Matches SCSI RESERVATION_CONFLICT
> 0x30 | One or more of the flush operations failed
> 0x31 | Firmware real-time currently not set
> 0x32 | Command issues while firmware in wrong state (that is, GET RECON when op not active)
> 0x33 | LD is not OFFLINE - I/O not possible
> 0x34 | Peer controller rejected request (possibly due to resource conflict)
> 0x35 | Unable to inform peer of communication changes (retry might be appropriate)
> 0x36 | LD reservation already in progress
> 0x37 | I2C errors were detected
> 0x38 | PCI errors occurred during XOR/DMA operation
> 0x39 | Diagnostics failed - see event log for details
> 0x3a | Unable to process command as boot messages are pending
> 0x3b | Returned if foreign configurations are incomplete
> 0x3d | Returned if a command is tried on unsupported hardware
> 0x3e | CC scheduling is disabled
> 0x3f | PD CopyBack operation is in progress
> 0x40 | Selected more than one PD per array
> 0x41 | Microcode update operation failed
> 0x42 | Unable to process command as drive security feature is not enabled
> 0x43 | Controller already has a lock key
> 0x44 | Lock key cannot be backed-up
> 0x45 | Lock key backup cannot be verified
> 0x46 | Lock key from backup failed verification
> 0x47 | Rekey operation not allowed, unless controller already has a lock key
> 0x48 | Lock key is not valid, cannot authenticate
> 0x49 | Lock key from escrow cannot be used
> 0x4a | Lock key backup (pass-phrase) is required
> 0x4b | Secure LD exist
> 0x4c | LD secure operation is not allowed
> 0x4d | Reprovisioning is not allowed
> 0x4e | Drive security type (FDE or non-FDE) is not appropriate for requested operation
> 0x4f | LD encryption type is not supported
> 0x50 | Cannot mix FDE and non-FDE drives in same array
> 0x51 | Cannot mix secure and unsecured LD in same array
> 0x53 | Physical device errors were detected
> 0x54 | Controller has LD cache pinned
> 0x55 | Requested operation is already in progress
> 0x56 | Another power state set operation is in progress
> 0x57 | Power state of device is not correct
> 0x58 | No PD is available for patrol read
> 0x59 | Controller reset is required
> 0x5a | No EKM boot agent detected
> 0x5c | For consistency SET PiTs, some PiT creations might fail or succeed
> 0xFF | Invalid status - used for polling command completion
> 0x5f | Maximum allowed unconfigured (configurable) PDs exist
> 0x60 | I/O metrics are not being collected
> 0x61 | AEC capture needs to be stopped before proceeding
> 0x62 | Unsupported level of protection information
> 0x63 | PDs in LD have incompatible EEDP types
> 0x64 | Request cannot be completed because protection information is not enabled
> 0x65 | PDs in LD have different block sizes
> 0x66 | LD Cached data is present on a (this) SSCD
> 0x67 | Config sequence number mismatch
> 0x68 | Flash image is not supported
> 0x69 | Controller cannot be online-reset
> 0x6a | Controller booted to safe mode, command is not supported in this mode
> 0x6b | SSC memory is unavailable to complete the operation
> 0x6c | Peer node is incompatible
> 0x6d | Dedicated hot spare assignment is limited to array(s) with same LDs.
> 0x6e | Signed component is not part of the image
> 0x6f | Authentication failure of the signed firmware image
> 0x70 | Flashing was ok but FW restart is not required, ex: No change in FW from current
> 0x71 | FW is in some form of restricted mode, example: passive in A/P HA mode

DB15-000988-08-December 2013
Copyright© 2013 by LSI Corporation. All rights reserved.