# 1. OS Level status codes

In this scenario LSA will get the error code and the description from OS (Windows/Linux) and return the same. This scenario applies to all the LOGIN modes. If the Authentication fails, LSA get the specific error code and description from the OS and will return.

| Host / Domain Authentication | LDAP Authentication | SMIS Authentication
Windows | Refer system error codes from https://msdn.microsoft.com | Refer winldap.h from your file system | Refer below table
Linux | Refer below table | Refer ldap.h from your file system | Refer below table

LSA_OS_STATUS_MAIN= 0x10000

Status Code | Description
LSA_OS_STATUS_MAIN + 0x01 | Logon failure: unknown user name or bad password
LSA_OS_STATUS_MAIN + 0x02 | No write permissions for this user

# 2. LSA status codes:

LSA_STATUS_MAIN= 0x11000

Status Code | Description
LSA_STATUS_MAIN + 0x01 | Schema validation error
LSA_STATUS_MAIN + 0x02 | Requested element <element details> not found
LSA_STATUS_MAIN + 0x03 | Requested element <element details> is missing
LSA_STATUS_MAIN + 0x04 | Current state of the target element <element details> does not support the operation <operation name>
LSA_STATUS_MAIN + 0x05 | Operation <operation name> is either not allowed or not supported
LSA_STATUS_MAIN + 0x06 | Operation <operation name> already in progress
LSA_STATUS_MAIN + 0x07 | Element does not contain the expected parameters, so the requested operation cannot be performed
LSA_STATUS_MAIN + 0x08 | Another operation <operation name> is in progress. The system cannot perform the requested operation now
LSA_STATUS_MAIN + 0x09 | Maximum limit is reached, cant perform the requested operation
LSA_STATUS_MAIN + 0x0A | User action may require to complete the performed operation <Actions> Actions: 1. LSA re-login required 2. LSA service restart required 3. Online Controller Reset required 4. System reboot required 5. Power On Reset required
LSA_STATUS_MAIN + 0x0B | 1. ATTENTION: Update failed. Please check support Portal to make sure firmware version is compatible with the controller 2. ATTENTION: Online Firmware update was not possible. System reboot is required for the firmware to take effect 3. ATTENTION: Online Firmware Update failed. Please check support Portal to make sure firmware version is compatible with the controller 4. Please perform Power On Reset before performing any other Operation(s). If ignored, the behavior can be un-predictable and un-defined 5. Please Logout and Re-login to the destination server once reboot is complete 6. Please Logout and Re-login to the destination server once Power on Reset is complete Possible LSA level error, 1. Firmware update failed. You are trying to flash iMR firmware on MR controller 2. Firmware update failed. You are trying to flash MR firmware on iMR controller 3. Firmware update failed. Base Version(s) of the image(s) are not matching 4. Firmware update failed. Selected image file is equal to or exceeds the 16 MB size limit 5. Firmware update failed. Reading flash file failed 6. This file is equal to or exceeds the 16 MB size limit. Please select a firmware image with size less than 16 MB 7. The firmware version and the NVDATA version of the image being flashed is same as the image already existing on the controller 8. The current operation is not allowed because the controller has data in cache for offline or missing virtual disks 9. The firmware version of the image being flashed is older than existing image on the controller
LSA_STATUS_MAIN + 0x0C | Online Controller Reset requested, further request will not be served until the reset is complete
LSA_STATUS_MAIN + 0x0D | Controller is in safe mode, cant serve your request
LSA_STATUS_MAIN + 0x0E | Element Collection call failed. <collection details>. e.g., 1. Some of VDs delete operation failed 2. Some of PDs state change operation failed

# 3. LSA internal status codes:

These status code and description will be logged in syslog.

LSA_INTERNAL_STATUS_MAIN= 0x12000

Status Code | Description
LSA_INTERNAL_STATUS_MAIN + 0x01 | Operation failed because of a resource reservation error
LSA_INTERNAL_STATUS_MAIN + 0x02 | Refresh operation not performed because of event notification error
LSA_INTERNAL_STATUS_MAIN + 0x03 | Resource not yet initialized
LSA_INTERNAL_STATUS_MAIN + 0x04 | Scheduled Job is in progress
LSA_INTERNAL_STATUS_MAIN + 0x05 | Invalid job ID or Job not present
LSA_INTERNAL_STATUS_MAIN + 0x06 | Error. Maximum number array is already configured
LSA_INTERNAL_STATUS_MAIN + 0x07 | Invalid Activation Key. Key length should be equal to 40
LSA_INTERNAL_STATUS_MAIN + 0x08 | This installation package could not be supported. Please contact the application vendor( Support team) to verify that this is a valid software for the controller Firmware
LSA_INTERNAL_STATUS_MAIN + 0x09 | File Size Exceeds supported size of 16 MB
LSA_INTERNAL_STATUS_MAIN + 0x0a | Maximum volume already configured
LSA_INTERNAL_STATUS_MAIN + 0x0b | Error fetching Spare PD information

# 4. Lower layer status codes:

Firmware:

Status Code | Description
0x01 | The requested command is not supported at this time.
0x02 | The requested command is invalid.
0x03 | The requested command has invalid arguments.
0x04 | Please check the configuration and retry the operation.
0x05 | The requested operation cannot be terminated.
0x06 | The pre boot application is not found.
0x07 | The pre boot application is already in use. Please try loading it later.
0x08 | The pre boot application is not initialized. Please try again later.
0x09 | Specified array index is not valid. Please provide valid array index and try again.
0x0a | Unable to add a physical disk to the disk group, as a physical disk exists in the specified position in the disk group.
0x0b | The requested command cannot be completed, as specified resources are already in use.
0x0c | The requested command cannot be completed, as the specified device does not exist.
0x0d | The specified physical disk doesn't have enough capacity to complete the requested command.
0x0e | There is not enough flash memory to complete the requested command.
0x0f | Flash is in use. Please retry the command later.
0x10 | The operation failed due to a flash error.
0x11 | The requested command cannot be completed as the image is corrupted.
0x12 | The image received by controller is incomplete.
0x13 | Failed to flash firmware image because flash command sequence is incorrect or previous firmware flash operation was terminated.
0x14 | The flash operation is not currently in progress.
0x15 | The controller cache memory could not be flushed.
0x16 | Pre boot application is not found.
0x17 | The requested virtual disk operation cannot be performed because consistency check is in progress.
0x18 | The requested virtual disk operation cannot be performed because initialization is in progress.
0x19 | The specified block is beyond the capacity of the virtual disk.
0x1a | Requested command cannot be completed as maximum supported virtual disks are already configured.
0x1b | The requested command cannot be completed as the virtual disk is not in an optimal state.
0x1c | The requested virtual disk operation cannot be performed because rebuild is in progress.
0x1d | The requested virtual disk operation cannot be performed because reconstruction is in progress.
0x1e | The specified operation is not possible for the current RAID level.
0x1f | The controller cannot support any additional hot spares.
0x20 | Memory is unavailable to complete the requested command. Please try again later.
0x21 | Manufacturing data could not be written due to a hardware error.
0x22 | The required hardware component is not present.
0x23 | The requested command cannot be completed as the specified object does not exist.
0x24 | The device is not part of an enclosure.
0x25 | The current operation cannot be performed because the physical disk clear is in progress.
0x26 | The specified physical disk does not have the appropriate attributes to complete the requested command.
0x27 | The Patrol Read operation cannot be performed, because it is disabled.
0x28 | Command cannot be completed as the specified position in the disk group in not valid.
0x2d | The requested operation could not be completed as device is busy or unexpected error occurred." ;
0x2e | The requested I/O operation failed.
0x2f | The resource is already in use.
0x30 | The controller shut down command is not successful.
0x31 | The controller real time is not set.
0x32 | The specified device is in a state that doesn't support the requested command.
0x33 | The requested command cannot be completed as the virtual disk is offline.
0x34 | Peer controller rejected request (possibly due to resource conflict)
0x35 | Unable to inform peer of communication changes (retry may be appropriate)
0x36 | LD reservation already in progress
0x37 | The requested operation cannot be completed due to a hardware error (I2C).
0x38 | The requested operation cannot be completed due to a hardware error (PCI).
0x39 | The diagnostic test failed. Please check the event log for more details.
0x3a | The requested operation is not possible because controller firmware is in boot message pending state.
0x3b | Foreign drives cannot be imported, as they do not form a complete configuration.
0x3c | Malformed SGL - counts don't match hdr length (only returned if debug code enabled)
0x3d | The requested command is not supported by the hardware.
0x3e | Consistency check is disabled.
0x3f | The requested operation cannot be initiated for the virtual disk as a copyback operation is in progress.
0x40 | Selected more than one PD per array
0x41 | Microcode update operation failed.
0x42 | The requested operation cannot be completed because the physical disk security feature is not enabled.
0x43 | The requested command cannot be completed as the controller already has a passphrase.
0x44 | The passphrase back up is not supported.
0x45 | Verification of the passphrase back up is not supported.
0x46 | The specified passphrase is not valid.
0x47 | The requested re-key operation cannot be initiated as the device must be first secured.
0x48 | Passphrase is not valid, authentication failed.
0x49 | The backup passphrase from escrow cannot be used.
0x4a | The passphrase must be backed-up, before the requested operation can be completed.
0x4b | The current operation cannot be completed because a secure virtual disk is present.
0x4c | The requested operation cannot be completed as the secure virtual disk is not permitted.
0x4d | Cryptographic erase is not allowed on this physical disk.
0x4e | The physical disks security properties are not valid for the requested operation.
0x4f | The virtual disk security type is not supported.
0x50 | The requested command cannot be completed, as it will result in a mix of FDE and non-FDE physical disk in a disk group, where such a mix is not allowed.
0x51 | Cannot mix secure and non secured virtual disk in the same disk group.
0x52 | The passphrase is not allowed.
0x53 | Physical device errors were detected
0x54 | The current operation is not allowed because the controller has data in cache for offline or missing virtual disks.
0x55 | The requested power state update operation is in progress." ;
0x56 | The requested operation cannot be performed because another power state update operation is in progress." ;
0x57 | The requested command cannot be completed because the physical disks are not in the expected power state.
0x58 | There are no physical disk(s) available to execute a patrol read operation.
0x59 | To complete the requested operation, please reboot the system.
0x5a | No EKM boot agent detected
0x5b | No space on the snapshot repositiry VD
0x5c | For consistency SET PiTs, some PiT creations may fail and some succeed
0x5d | Secondary iButton cannot be used and is incompatible with controller
0x5e | PFK doesn't match or cannot be applied to the controller
0x5f | The drive cannot be converted from JBOD to unconfigured good because, Maximum allowed drive conversion has been reached.
0x60 | IO metrics are not being collected.
0x61 | AEC capture need to be stopped before proceeding.
0x62 | Unsupported level of protection information
0x63 | PDs in LD have incompatible EEDP types
0x64 | 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 is booted to safe mode. Command is not supported in this mode
0x6b | SSC memory is unvailable to complete the operation
0x6c | Peer node is incompatible
0x6d | A Dedicated Hot Spare can only be assigned to drive groups that possess a common VD.
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, as no change in FW.
0x71 | FW is running in restricted mode
0x72 | Exceed number of entries
0x73 | Subsequent flush can't start because previous flush is active
0x74 | Status ok and reboot is required to take effect
0x75 | Operation can't perform due to background operation in progress
0x76 | Operation is not possible
0x77 | FW update is in progress on the peer node
0x78 | Hidden policy not set for all virtual disks in Drive Group containing this LD
0x79 | Indicates that there are one or more secure system drives in the system
0x7a | Selected virtual disk is a boot device
0x7b | Maximum transportable disk group count reached
0x7c | DHSP is associated with more than one disk group
0x7d | Operation not possible as the disk group or virtual drive is in transport ready state
0x7e | IO request encountered a SCSI DATA UNDERRUN
0x7f | FW Flash not allowed in the current mode
0x80 | Operation not possible as the device is in transport ready state
0x81 | Operation not possible as the disk group or virtual drive is in transport ready state
0x82 | Operation not possible as the disk group or virtual drive is not in transport ready state
0x83 | Operation not possible since the PD in removal ready state
0x84 | Status ok but host reboot is required for changes to take effect
0x85 | Microcode update is pending on the device
0x86 | Microcode update is in progress on the device
0x87 | Mismatch between the drive type and the erase option
0x88 | Operation not allowed, Auto Configurations exists.
0x89 | Operation not allowed, Secure devices exists
0x8a | Operation not possible because host FRU data is invalid
0x8b | Operation not possible because controller FRU data is invalid
0x8c | Requested image not found
0x8d | Error reported with NVCache
0x8e | Requested LD size is less than minimum virtual disk size
0x8f | Requested drive count is invalid for this raid level
0x90 | OEM specific backplane authentication failure
0x91 | OEM specific backplane not found
0x92 | Flashing image is not possible because downloaded and running firmware on the controller are same
0x93 | Unmap is not supported atleast on one device
0x94 | Device doesn't support the sanitize type thats specified
0x95 | There is no valid snap dump available
0x96 | Snapdump feature is not enabled
0x97 | Virtual disk/device does not support the requested policy
0x98 | Requested operation cannot be performed because of existing configuration
0x99 | Status ok but shutdown is required for the changes to take effect
0x9a | Drive cannot participate in RAID Configuration
0x9b | Secure boot needs another key slot and the efuse is full
0x9c | Clear snapdump is required before proceeding
0x9d | Cannot mix unmap and non-unmap physical drives in same array
0xFF | Invalid error status.

Library:

SL_ERR_MAIN= 0x8000

SL_ERR_IR_MAIN= 0x8100

SL_ERR_IR_MEGARAID_MAIN= 0x8200

SL_ERR_MAIN_MCTP= 0x7000

Status Code | Description
SL_ERR_MAIN + 0x09 | Command to driver timed out
SL_ERR_MAIN + 0x17 | Command failed by O/S
SL_ERR_MAIN + 0x1C | The LD to OS drive mapping is not complete
SL_ERR_MAIN + 0x23 | Failed to get partition. Partition may not exist
SL_ERR_IR_MAIN + 0x01 | Incorrect Span Depth, should always be 1
SL_ERR_IR_MAIN + 0x02 | Command to MPT failed
SL_ERR_IR_MAIN + 0x05 | Resync operation in progress
SL_ERR_IR_MAIN + 0x08 | PD is not part of a volume
SL_ERR_IR_MAIN + 0x09 | The firmware flash image checksum is invalid
SL_ERR_IR_MAIN + 0x0A | The firmware flash image product Id is invalid
SL_ERR_IR_MAIN + 0x0B | The firmware flash image attached NVDATA version is older than the NVDATA version of the image already existing on the controller
SL_ERR_IR_MAIN + 0x0C | The BIOS flash image signature is invalid
SL_ERR_IR_MAIN + 0x0D | The BIOS flash image checksum is invalid
SL_ERR_IR_MAIN + 0x0E | The BIOS flash image is invalid. Possible reasons may be due to invalid PCI Device Id, PCI type or PCIR offset
SL_ERR_IR_MAIN + 0x10 | Flash memory size is not matching
SL_ERR_IR_MAIN + 0x11 | Invalid configuration page was requested and request failed by StorelibIR
SL_ERR_IR_MAIN + 0x12 | Device is within an enclosure but enclosure management type is unknown, hence can not send request to enclosure
SL_ERR_IR_MAIN + 0x13 | The firmware version of the image being flashed is older than existing image on the controller
SL_ERR_IR_MAIN + 0x14 | The firmware version and the NVDATA version of the image being flashed is same as the image already existing on the controller
SL_ERR_IR_MAIN + 0x15 | Device specified cannot be formatted
SL_ERR_IR_MAIN + 0x28 | Requested Flash image type is not present in flash
SL_ERR_IR_MAIN + 0x49 | Firmware flashing is unsupported
SL_ERR_IR_MAIN + 0x57 | Controller reset failed
SL_ERR_IR_MAIN + 0x60 | Please perform Power On Reset before performing any other Operation(s). If ignored, the behavior can be un-predictable and un-defined
SL_ERR_IR_MEGARAID_MAIN + 0x0c | Device not found
SL_ERR_IR_MEGARAID_MAIN + 0x32 | Device is in wrong state
SL_ERR_MAIN_MCTP+0x81 | Unexpected failure
SL_ERR_MAIN_MCTP+0x1FF | MCTP failure