Troubleshooting
Problem
Symptom
Since the array is no longer accessible, the controller firmware may not recover the cache for all LUNs under this array. This behavior may lead to data not being written.
This issue is present at interposer levels earlier than 2264 on the following hard drives:
| ST9300605SS | 300 GB/10K/Base PI |
| ST9600204SS | 600 GB/10K/Base PI |
| ST9600205SS | 600 GB/10K/Base PI |
| ST9900805SS | 900 GB/10K/Base PI |
| ST33000650SS | 3TB/7200/Base non-PI |
| ST9600104SS | 600 GB/10K/SED PI |
| ST9600105SS | 600 GB/10K/SED PI |
| SG9XCA2E200GEIBM | (200G/SSD/4Gbps FC-3Gbps SAS) |
| SG9XCA2E400GEIBM | (400G/SSD/4Gbps FC-3Gbps SAS) |
Affected configurations
The system may be any of the following IBM servers:
- IBM System Storage DS3950 Express, type 1814, any model
- IBM System Storage DS5020 Disk Controller (1814-20A), any model
- IBM System Storage DS5100 Storage Controller, type 1818, any model
- IBM System Storage DS5300 Storage Controller, type 1818, any model
The system is configured with one or more of the following IBM Options:
- EXP395 Express Expansion Unit (1814-92H), any model
- IBM System Storage EXP5000 Storage Expansion Unit, type 1818, any model
- IBM System Storage EXP520 Storage Expansion Unit (1814-52A), any model
This tip is not software specific.
Solution
The fix for this problem is in the versions 2264 and later of the interposer firmware. This firmware can be found in the versions 1.78 and later of the ESM/HDD firmware package. Customers should upgrade to 1.78 or later of the ESM/HDD firmware package as soon as possible.
The file is available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and operating system on IBM Support's Fix Central web page, at the following URL:
Workaround
If you believe that you have encountered this issue, please call IBM Support for assistance with the recovery actions.
Additional information
In order to encounter this issue, the following conditions must be met:
- Drive interposer firmware must be earlier than 2264
- I/O must be in process
- The controller reboots with data in cache
- Drive reports incorrect inquiry data causing the controller to mark drive as uncertified and take the array offline
When the above all happen, the data in cache is not recovered for the LUNs in the offline array.
If any of the above conditions are not met, then this issue will not occur.
Was this topic helpful?
Document Information
Modified date:
28 November 2019
UID
ssg1S1004763