OPERATIONAL DEFECT DATABASE
...
...
An issue exists on the MR Gen10 Plus Controllers where I/O performance may drop or fail on the Guest OS of the VM to the NVMe drives installed on the MR controller. This issue may occur in a VMware environment when the following configuration is set: A VM is created with more than 2GB of memory. An MR controller is configured as a PCI Passthrough and is assigned to a VM. NVMe drives are installed on an MR controller. In the Linux VM, the following messages are displayed in the kernel log using the dmesg command. sd ##:#:#:#: Power-on or device reset occurred In the Windows VM, a consecutive Disk Event ID 153 is displayed in the Windows System Log. Select Event Viewer > Windows Logs > System. Disk 153 None The IO operation at logical block address 0x###### for Disk # (PDO name: \Device\########) was retried. In the Linux Guest OS, the kernel message shows I/O errors and power on or a device reset that may occur on the block device in the following example: [ 961.206072] sd 33:2:6:0: Power-on or device reset occurred [ 961.340095] sd 33:2:6:0: [sdc] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x40000/0x0 [ 961.340141] sd 33:2:6:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=4s [ 961.340150] sd 33:2:6:0: [sdc] tag#0 Sense Key : Aborted Command [current] [ 961.340158] sd 33:2:6:0: [sdc] tag#0 Add. Sense: No additional sense information [ 961.340166] sd 33:2:6:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 02 00 00 02 00 00 [ 961.340174] blk_update_request: I/O error, dev sdc, sector 512 [ 961.788541] sd 33:2:6:0: Power-on or device reset occurred [ 962.030277] sd 33:2:6:0: [sdc] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x1000/0x0 [ 962.030397] sd 33:2:6:0: Power-on or device reset occurred [ 963.442472] sd 33:2:6:0: [sdc] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x40000/0x0 [ 963.454232] sd 33:2:6:0: [sdc] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x40000/0x0 [ 963.454359] sd 33:2:6:0: Power-on or device reset occurred [ 963.550834] sd 33:2:6:0: [sdc] tag#0 BRCM Debug mfi stat 0x2d, data len requested/completed 0x40000/0x0 In the Windows Guest OS, the System Event log shows consecutive warnings, "I/O operation was retried" in the following example: Warning 11/3/2022 7:35:59 AM Disk 153 None The IO operation at logical block address 0x5f0b58 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:57 AM Disk 153 None The IO operation at logical block address 0x607638 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:57 AM Disk 153 None The IO operation at logical block address 0x607360 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:57 AM Disk 153 None The IO operation at logical block address 0x607358 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:52 AM Disk 153 None The IO operation at logical block address 0x607358 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:51 AM Disk 153 None The IO operation at logical block address 0x606360 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:51 AM Disk 153 None The IO operation at logical block address 0x606358 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:46 AM Disk 153 None The IO operation at logical block address 0x606358 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:45 AM Disk 153 None The IO operation at logical block address 0x604f80 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:44 AM Disk 153 None The IO operation at logical block address 0x604b60 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:44 AM Disk 153 None The IO operation at logical block address 0x604b58 for Disk 4 (PDO name: \Device\00000041) was retried. Warning 11/3/2022 7:35:43 AM megasas35 44801 None "The description for Event ID 44801 from source megasas35 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
This issue impacts all platforms that support MR Gen10 Plus Controllers. See the HPE MR Gen10 Plus Controller User Guide for the latest update of Gen10 Plus Controllers.
Add the following parameter to the .vmx file of the VM. This will prevent the Guest OS from using the physical memory address that may overlap with the controller BAR setting. pciHole.start = "2048" For details on the VMware PCI Passthrough requirement, refer to the VMware KB: vSphere VMDirectPath I/O and Dynamic DirectPath I/O: Requirements for Platforms and Devices (2142307) . Disclaimer : One or more of the links above will take you outside the HPE website. HPE is not responsible for content outside of its domain. 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 Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches and other support software downloads, refer to the Navigation Tips document. SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips document.
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
