Abort checking media failed
|
Abort checking parity failed
|
Abort clone failed
|
Abort creating logical drive failed
|
Abort expanding logical drive failed
|
Abort rebuilding logical drive failed
|
Access device failure
|
Adding disk failed
|
Adding disk only applicable on raid0/raid1/raid3/raid5
|
Another disk or logical drive operation under progress or not applicable operation for current disk or logical drive status
|
Assigned
|
Bad connection to the Primary Agent
|
Bad data returned from controller
|
Bad event data
|
Bad firmware data for download
|
Bad fru id data
|
Bad logical drive channel number
|
Bad logical drive id in library database
|
Bad logical drive index in library database
|
Bad logical host channel number
|
Bad logical volume id in library database
|
Bad logical volume index in library database
|
Bad parameter specified
|
Bad parameters specified
|
Bad physical channel number
|
Bad ses configuration page
|
Bad socket error
|
Bad status returned
|
Battery board does not exist
|
Battery board FRU ID not programmed
|
Battery type too old
|
Can not configure SIDs on single controller environment
|
Check media failed
|
Check parity failed
|
Check parity only applicable on raid1/raid3/raid5
|
Clear events failure
|
Clone failed
|
Clone only applicable on raid0/raid1/raid3/raid5
|
Close file failure
|
Close inband/outband device error
|
Configuration file format error
|
Controller access error
|
Controller busy
|
Controller firmware download ok, but can not engage firmware without redundant controller
|
Controller firmware download ok, but engage firmware failed
|
Controller firmware download ok, but engage operation is not allowed
|
Controller not ready
|
Controller not shutdown yet as expected
|
Create host wwn name failed
|
Data transfer time out
|
ddb information not programmed
|
Delete host wwn name failed
|
Device excluded by redundant path software
|
Device not supported
|
Disk drives do not match saved configuration
|
Drive type unknown
|
Element not found in ses pages
|
Element type not found in ses pages
|
Failed to assign logical drive
|
Failed to bypass a device
|
Failed to bypass sfp
|
Failed to check/set password
|
Failed to convert logical volume
|
Failed to create logical drive
|
Failed to create logical volume
|
Failed to delete logical volume
|
Failed to download nvram data
|
Failed to get battery information
|
Failed to get cache parameters
|
Failed to get caching statistics
|
Failed to get channel data
|
Failed to get channel statistics
|
Failed to get controller configuration page
|
Failed to get controller configuration string page
|
Failed to get controller module version
|
Failed to get controller network interface
|
Failed to get controller redundant mode
|
Failed to get controller statistics
|
Failed to get ctrl param in upload config command
|
Failed to get drive statistics
|
Failed to get fru id in upload config command
|
Failed to get host statistics
|
Failed to get ld and lv info in upload config command
|
Failed to get logical drive partition
|
Failed to get logical drive status
|
Failed to get loop map
|
Failed to get lun map in upload config command
|
Failed to get offset in enclosure page for specified element type
|
Failed to get peripheral configuration
|
Failed to get peripheral device status
|
Failed to get pld register raw data
|
Failed to get pld rev
|
Failed to get redundant controller configuration
|
Failed to get scsi drv info in upload config command
|
Failed to get ses page
|
Failed to get sfp bypass information
|
Failed to get write-policy
|
Failed to issue a lip
|
Failed to map logical volume
|
Failed to map logical volume filter
|
Failed to map partition to host channel
|
Failed to mute controller beep
|
Failed to parse ses configuration page
|
Failed to partition logical drive/volume
|
Failed to partition logical volume
|
Failed to program fru id
|
Failed to read fru id
|
Failed to remove logical drive
|
Failed to remove logical volume
|
Failed to reset sata router via specified ses target
|
Failed to reset timeout
|
Failed to scan fru id
|
Failed to scan safte
|
Failed to scan ses target
|
Failed to send ses page
|
Failed to set battery all information
|
Failed to set battery in service date
|
Failed to set cache parameters
|
Failed to set channel data
|
Failed to set controller network interface
|
Failed to set drive side parameters
|
Failed to set host side parameters
|
Failed to set peripheral configuration
|
Failed to set redundant controller configuration
|
Failed to set sata serial connector
|
Failed to set statistics
|
Failed to set write-policy
|
Failed to set/reset caching statistics
|
Failed to set/reset channel statistics
|
Failed to set/reset controller statistics
|
Failed to set/reset drive statistics
|
Failed to set/reset host statistics
|
Failed to show drive side parameters
|
Failed to show host side parameters
|
Failed to show logical volumes
|
Failed to show mapping on host channel
|
Failed to unbypass a device
|
Failed to unbypass sfp
|
Failed to unmap partition from host channel
|
Failed to upload nvram
|
Filter map exist
|
Firmware download failure
|
Firmware download failure on one or more drives, see status report above for failures
|
Firmware download failure on some targets
|
Firmware download not performed
|
Firmware type and unit type do not match
|
Get events failure
|
Get host wwn name list failed
|
Get network protocol failed
|
Get raid configuration error
|
Get raid configuration from file error
|
Get ses wdt status jbod failed
|
Get slot status failed
|
Getting network parameters failure
|
Host wwn entry existing
|
Host wwn entry not existing
|
Host wwn name too long
|
Illegal operation on mixed type of disk drive or unit
|
Illegal operation while a logical drive exists
|
Illegal request
|
In service date not set in the battery
|
Initializing
|
Invalid command
|
Invalid host wwn
|
Invalid protocol name
|
Invalid request
|
Invalid ses enclosure page length
|
IO chl diagnostic command aborted by user
|
IO chl diagnostic command bad target parameters
|
IO chl diagnostic command busy
|
IO chl diagnostic command completed with errors
|
IO chl diagnostic command completed with no error
|
IO chl diagnostic command failed
|
IO chl diagnostic command in progress
|
IO chl diagnostic command not ready
|
IO chl diagnostic command not running
|
IO chl diagnostic command not valid
|
IO chl diagnostic command out of resource
|
IO chl diagnostic command parameter error
|
IO chl diagnostic command too much ops running
|
Is member of logical volume
|
Library database data not valid
|
Library database update error
|
Local spare can not be assigned to NRAID or RAID0
|
Logical drive rebuild failed
|
Logical drive/volume expand failed
|
Logical drive/volume expand only applicable on raid0/raid1/raid3/raid5
|
Logical error of operation on ses
|
LUN map exist
|
Maximum error status value
|
Mixed drive type for a logical drive operation
|
Mixed drive type in the raid system
|
Network traffic
|
No available disk to create logical drive
|
No controller network interface
|
No disk clone found
|
No firmware data for download
|
No logical drive
|
No logical volume
|
No mux board found
|
No path found to inquiry sr-1216
|
No sr-1216 found
|
No valid data returned
|
No valid safte target found
|
No valid ses target found
|
No valid target found
|
Not a device mapped on primary controller
|
Not a drive channel
|
Not a host channel
|
Not a primary controller
|
Not a qualified channel
|
Not a spare drive
|
Not a supported SAFTE target
|
Not a supported SES target
|
Not a valid target
|
Not an existing channel
|
Not an existing target
|
Not spare drive
|
Not valid as spare drive
|
OK
|
Only offline creating can be aborted
|
Only offline expanding can be aborted
|
Open file failure
|
Open inband/outband device error
|
Operation not valid on this logical drive
|
Operation specified not available on the drive type
|
Out of resource
|
Partition was not specified
|
pc-150 firmware download failure
|
Primary Agent not found
|
RAID1 requires an even number of disks
|
Read configuration data error
|
Rebuild only applicable on raid1/raid3/raid5
|
Rebuilding
|
Restore host wwn name list failed
|
Retrieve
|
Retrieving
|
Retrieving controller name failure
|
Retrieving controller unique id failure
|
Retrieving ddb information failure
|
Retrieving pc-150 information failure
|
Retrieving rs232 configuration failure
|
Retrieving sr-1216 information failure
|
Save raid configuration to file error
|
Scanning fru is done, but at least one fru missing
|
SCSI device model missing
|
SCSI drive already exists
|
SCSI drive not found
|
SES operation on invalid target
|
Set controller current time failure
|
Set logical drive failed
|
Set logical volume failed
|
Set network protocol failed
|
Set ses wdt failed on jbod
|
Set slot operation failed
|
Setting controller name failure
|
Setting controller unique id failure
|
Setting rs232 configuration failure
|
Show shutdown status failed
|
Shutdown controller failed
|
Some frus missing
|
Specified firmware does not support logical drive or logical volume with more than 32 partitions
|
Specified firmware does not support more than 8 logical drives
|
Specified lds must have only a single \n partition (P0), no host LUN mappings, and they must have the same controller \n assignment
|
SR-1216 firmware download failure
|
Start of error values
|
Stripe block size not available
|
Target device not found
|
Target device not ready
|
The capacity of target disk too small
|
The current firmware does not support check parity on raid1
|
The current firmware does not support more than 8 logical drives
|
The current firmware does not support more than 32 partitions in logical drives/volumes
|
The current firmware does not support this operation on raid1
|
This operation is only supported on Fibre Channel primary RAID controller devices
|
Valid host channel, target, and lun were not specified
|
Verify bypass information failed
|
Write parameters error
|
Writing_download_raid_config
|
Wrong unit type specified for sata related operation
|