Local datastore missing after upgrading ESXi host to 8.0 Update 3

Products

• VMware vSphere ESXi

Issue/Introduction

• Datastores residing on local storage are no longer visible or accessible in the vSphere Client or command-line interface (CLI) after an ESXi host upgrade to version 8.0 Update 3.
• A "Rescan" operation fails to locate or mount the local datastore.
• The vmkernel.log file contains errors from the High Performance Plug-in (HPP) regarding unclaiming paths:
  
  /var/run/log/vmkernel.log
  
  YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### HPP: HppUnclaimPath:3696: Unclaiming path mpx.vmhba#:C#:T###:L#
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5339: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#.Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5349: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5359: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5369: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5379: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5389: Failed to register for 'TARGET MICRO CODE CHANGED' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
YYYY-MM-DD:T:HH:MM:SS In(###) vmkernel: cpu12:###### ScsiDevice: 5399: Failed to Unregister 'POWER ON RESET' unit attention for device:mpx.vmhba#:C#:T###:L#. Reason: Not found
  
  

Environment

VMware ESXi 8.0

Cause

The ESXi host fails to maintain communication with the local storage controller due to a driver incompatibility or a firmware level issue introduced during the version transition.

Resolution

To resolve this issue, perform the following steps:

1. Verify the current firmware and driver versions for the local RAID controller. Refer to  Determining Network/Storage firmware and driver version in ESXi for detailed commands.
2. Ensure the specific driver and firmware combination is certified for ESXi 8.0 Update 3  Broadcom Hardware Compatibility List (HCL) .
3. If a newer certified driver is available, download and install the asynchronous driver Refer to Download and install async drivers in VMware ESXi.
4. If the issue persists after verifying HCL compliance and updating drivers, engage the hardware vendor to investigate potential controller firmware defects or hardware failure.