...
Document Version Release Date Details 7 11/21/2019 Removed a note in the Description section. 6 02/11/2019 Updated the Resolution section with new patches. 5 01/17/2019 Revised the last two paragraphs in the Description section. 4 01/04/2019 Revised the Description and Resolution sections. 3 08/24/2018 Revised the Resolution section. 2 07/17/2018 Added a note to the Description section and added products to the affected products list. 1 06/26/2018 Original Document Release. An issue has been identified for all HPE 3PAR StoreServ arrays with the following SDD model numbers installed: AREX0400S5xnNTRI AREA7680S5xnNTRI AREX1920S5xnFTRI AREA7680S5xnFTRI AREA0400S5xnNTRI AREX0920S5xnNTRI AREA3840S5xnFTRI AREX0480S5xnNTRI AREX3840S5xnNTRI AREA15T4S5xnFTRI AREA0920S5xnNTRI AREA0480S5xnNTRI AREA3840S5xnNTRI AREX1920S5xnNTRI AREX0920S5xnFTRI AREA0920S5xnFTRI AREX3840S5xnFTRI AREA1920S5xnNTRI AREA1920S5xnFTRI AREA15T4S5xnNTRI These drive models may perform a self-initiated internal reset during normal operations or SDD firmware updates, which may result in host committed writes not being committed to the drive. In rare occurrences, this internal reset may lead to data inconsistency due to the writes not being committed to the drive. If this internal reset occurs, the HPE 3PAR OS will record an event in the evtlog for a Sense Code: 0x06 and anASC/ASCQ of 0x29/0x04 . Through ongoing internal quality testing, HPE has discovered a new corner case trigger to encounter this situation that is not addressed with the currently released patches. This corner case has been diagnosed and addressed with HPE 3PAR OS 3.2.2 MU6-P138, 3.3.1 MU1 P47, and 3.3.1 MU2 P48 patches released to change the action that the HPE 3PAR OS takes when the drive performs an internal drive reset. As these new patches will obsolete the prior patches, they are required to be installed to replace the previously released patches. When the new patches are installed, the previous patches will be removed thru obsolescence. The drive performing the internal reset will still be removed immediately by the HPE 3PAR OS, allowing the normal raid set reconstruction to take place from the remaining drives.
All HPE 3PAR StoreServ arrays with the identified model numbers of SSDs installed are affected by this issue.
This issue is addressed with new patches 3.3.1 MU3+P53, 3.3.1 MU2+P48, 3.3.1 MU1 P47, 3.2.2 MU4 P133, and 3.2.2 MU6+P138. These new patches must be installed on systems with the previously released patches already installed. For arrays running HPE 3PAR OS 3.2.2 MU6 with or without P119, patch P138 must be installed. For arrays running HPE 3PAR OS 3.3.1 MU2 with or without P30, patch P48 must be installed. For arrays running HPE 3PAR OS 3.3.1 MU3 patch P53 must be installed. For arrays running HPE 3PAR OS 3.3.1 MU1 with or without P31, patch P47 must be installed, or upgrade to HPE 3PAR OS 3.3.1 MU2 + P48. For arrays not on 3.2.2 MU6 or 3.3.1 MU2, you must upgrade to 3.2.2 MU6 or 3.3.1 MU2, and install patch P138 or patch P48 respectively. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form.