ESXi: FC switch storage paths are not detected after host reboot, resulting in fewer paths

Products

• VMware vSphere ESXi

Issue/Introduction

On an ESXi host, after a reboot, storage paths through an FC switch may not be detected as expected.
For example, in a configuration where four paths should be present, only two paths may be visible, or a specific FC switch port may appear not to be link-up.

The following messages may be recorded in vobd.log.

When the issue occurs:

 [vob.scsi.scsipath.pathstate.deadver2] scsiPath vmhba#:C#:T#:L# changed state from on (device ID: naa.#####)

When the path recovers:

 [vob.scsi.scsipath.pathstate.on] scsiPath vmhba#:C#:T#:L# changed state from dead

Also, the vob.scsi.scsipath.pathstate.on event may not be logged during host startup.

Environment

VMware vSphere ESXi 8.0

Cause

If the device is not detected during ESXi host startup, the corresponding device paths are not created.
ESXi does not preserve the number of paths that existed prior to the reboot. This behavior is expected.

Resolution

To recover the paths without rebooting the host, perform a manual storage rescan.

vSphere Client steps

1. Select the target ESXi host.
2. Click the Configure tab.
3. Go to Storage > Storage Adapters.
4. Click Rescan Storage.
5. Select both options and run the rescan:
   • Scan for new storage devices
   • Scan for new VMFS volumes
     
     
   

Note: If you want to rescan a specific adapter only, select the adapter and click Rescan Adapter.

Additional Information

For details about storage rescans, refer to Performing a rescan of the storage on an ESXi host.