Miscellaneous return codes
This section describes miscellaneous return codes, include the following:
For cmos-related return codes, see Table 1.
For edgeserver-related return codes, see Table 2.
For FFDC-related return codes, see Table 3.
For FFDC-related return codes, see Table 4.
For raid-related return codes, see Table 5.
For servicelog-related return codes, see Table 6.
For smartdata-related return codes, see Table 7.
For usblan-related return codes, see Table 8.
For vm-related return codes, see Table 9.
Return codes | Description |
---|---|
122 | Current command is only supported by OOB mode, so the --bmc parameter is required. |
123 | UEFI PAP (UefiAdminPassword) is invalied. |
124 | The Chassis requires to be powered off to perform this request. |
125 | Current user does not have sufficient privilege to execute the command. |
Return codes | Description |
---|---|
80 | Failed to reset device internal counter. |
81 | Failed to update public key in ThinkShield portal. |
82 | Failed to activate target server machine over XCC. |
83 | Failed to unlock target server. |
84 | Failed to enable portal activation. |
85 | Failed to reboot BMC. |
86 | Failed to disable chassis intrusion detection in target server. |
87 | Failed to disable motion detection in target server. |
88 | Failed to disable security pack in target server. |
89 | Failed to enable chassis intrusion detection in target server. |
90 | Failed to configure motion detection in target server. |
91 | Failed to enable security pack in target server. |
92 | Failed to lock down target server. |
93 | Failed to unlock target server. |
94 | BMC internal error. |
95 | Unable to collect required information from BMC. |
111 | Failed to claim target server in ThinkShield Key Vault Portal. Manufacturing data is missing in the required fields. |
112 | Failed to connect to ThinkShield Key Vault Portal. No response from server. |
113 | Failed to reset counter in ThinkShield Key Vault Portal. |
114 | Failed to update status of target server to active in ThinkShield Key Vault Portal. |
115 | Failed to get challenge response text in ThinkShield Key Vault Portal. |
116 | Failed to activate target server in ThinkShield Key Vault Portal. |
117 | Failed to unclaim machine in ThinkShield portal. |
118 | Failed to claim target server in ThinkShield Key Vault Portal. Invalid machine type. |
119 | Failed to claim target server in ThinkShield Key Vault Portal. Manufactured data not found. |
120 | Failed to claim target server in ThinkShield Key Vault Portal. Invalid activation code. |
121 | Failed to claim target server in ThinkShield Key Vault Portal. User is not allowed to make this request. |
122 | Failed to post data to the ThinkShield portal. |
123 | Unable to collect required information from BMC. |
124 | Unable to be authenticated with ThinkShield Key Vault Portal. Check whether Lenovo ID, password, and organization name for authentication are correct. |
125 | Unable to be authenticated with ThinkShield Key Vault Portal. Organization does not exit. |
Return codes | Description |
---|---|
114 | AMD FFDC can only be downloaded remotely not inside a server's host OS. |
115 | Download AMD FFDC failed. |
117 | Download AMD FFDC error: SFTPor TFTP upload not supported. |
118 | FFDC log has been downloaded to local, but failed to upload to SFTP server. |
119 | Failed to get FFDC log. |
120 | FFDC log has been uploaded to the specified FTP/TFTP server, but failed to download FFDC log from FTP/TFTP server. |
121 | Download SMM FFDC error: TFTP server does not found. |
122 | Download SMM FFDC error: tar FFDC files failed |
123 | Download SMM FFDC error: query failed |
124 | Download SMM FFDC error: start dump failed. |
125 | Download SMM FFDC error: setup environment failed. |
Return codes | Description |
---|---|
124 | There are no logs. |
125 | Failed to get logs. |
Return codes | Description |
---|---|
104 | OneCLI can only enable Volume Encryption, but cannot perform other operations. |
105 | There are no controllers with the Firmware Device Orderfunction. |
106 | Function is not supported on the target device. |
107 | Incorrect use of the --dg option. |
108 | There are no disks to run the makejbod command. |
109 | There are no disks to run the makegood command. |
112 | There are no containers. |
113 | Current system does not support Intel RSTe software raid. |
114 | Disk state error. |
115 | There are no disks of the target device. |
116 | RAID configuration does not support this command on M.2 SSD. |
117 | The operation fails on all targets. |
118 | There are no controllers. |
119 | The operation fails on some targets. |
120 | There are no volumes. |
121 | Failed to operate RAID configuration. |
122 | RAID configuration INI file error. |
123 | There is no raid configuration policy to save. |
124 | The target device does not exist. |
125 | Make sure the RAID configuration command run on the ThinkSystem with the lastest XCC firmware version. |
Return codes | Description |
---|---|
123 | Service Data Log is not supported on current system. |
124 | Failed to get Service Data Log. |
125 | Service Data Log has been uploaded to the specified FTP/TFTP server but failed to be downloaded. |
Return codes | Description |
---|---|
121 | Failed to connect BMC REST API. |
122 | Failed to get system status. |
123 | Failed to get SMART data result. |
124 | Failed to boot to BIOS setup. |
125 | Unable to get SMART data. Confirm the BMC firmware supported. |
Return codes | Description |
---|---|
116 | Failed to configure the LAN-over-USB device with non-administrator user. |
117 | BMC LAN-over-USB device driver is not detected. |
118 | Failed to change BMC LAN-over-USB device status. |
119 | BMC LAN-over-USB node number is out of range. |
120 | No BMC LAN-over-USB device is detected. |
121 | BMC LAN-over-USB device conflicts. |
122 | BMC LAN-over-USB device is disabled. |
123 | BMC LAN-over-USB device is enabled. |
124 | IP network segments of LAN-over-USB host side and BMC side conflict. |
125 | Invalid IP address. |
Return codes | Description |
---|---|
122 | Remote Physical Presence is disabled on the target system. |
123 | Failed to get status of Remote Physical Presence. |
124 | Failed to de-assert Remote Physical Presence. |
125 | Failed to assert Remote Physical Presence. |
Give documentation feedback