Hi team!
Here is a case about analysis and handling of common SDTester error codes.
I hope it can be helpful when you learn about it :)
Symptom
Analysis and handling of common SDTester error codes
Solution
Check the CLI of SDTester when an I/O error occurs. Common error codes: 2, 55, 1167, 1117, and Timeout.
Error codes: 2, 55, 1167
When links are connected or disconnected or an upgrade is being performed, the following error codes occur simultaneously. Meanings of the error codes are as follows:
ERROR_FILE_NOT_FOUND
2 (0x2)
The system cannot find the file specified.
ERROR_DEV_NOT_EXIST
55 (0x37)
The specified network resource or device is no longer available.
ERROR_DEVICE_NOT_CONNECTED
1167 (0x48F)
The device is not connected.
When the error codes are displayed, the disk or the file does not exist. Check whether links are working properly. For instance, check whether paths on controllers are reported properly during an online upgrade, and ensure no redundant path exists before disconnecting links.
Error code 1117:
Meaning
ERROR_IO_DEVICE
1117 (0x45D)
The request could not be performed because of an I/O device error.
Cause: The array returns to UltraPath an error code (IoStatus: STATUS_IO_DEVICE_ERROR.) and SCSI error code is caused by I/O pass-through. Logs similar to the following are printed:
Figure1 Log printing information
After SDTester reports error code 1117, testers can find the xmp_logx.txt log file in the multipathing software installation path (generally C:\Program Files(x86)\Huawei\OceanStor UltraPath\log). Find error code 0x2 0x4 0x0 0x0. Ask colleagues responsible for arrays to locate the root cause for the array.
Error code timeout:
When testers are testing specifications of the multipathing software, they need to switch over I/Os within 30s when links are disconnected. SDTester is set with the 30s timeout error, but an HBA timeout error is not set. When a link is down, the HBA returns I/Os following the default timeout configurations, and the time required for returning I/Os exceeds 30s. SDTester takes the information as an I/O error and information similar to RIO/WIO timeout is printed in SDTester CLI.
To solve this problem, testers can configure the HBA linkdown timeout parameter following chapter 7 Timeout Parameter Settings upon a Link Down Failure in the OceanStor UltraPath for Windows V100R008C50 User Guide 01.
