ESXi host hangs at boot with vmw_vaaip_netapp loaded successfully and system-storage activation.

Products

• VMware vSphere ESXi

Issue/Introduction

• The Esxi host is stuck at the boot screen:

       

• The "SCSI Reservation Conflicts" messages observed in the DCUI logs:

LVM: 16209: Failed to open device naa.#################################### :1 : Timeout
WARNING: ScsiCore: 2139: Invalid sense buffer: error=0x0, valid=0x0
NMP : nmp_ResetDeviceLogThrottling:3845: Error status H:0x0 D:0x18 P:0x0 Sense Data: 0x0 0x0 0x0 from dev "naa .####################################
WARNING: ScsiCore: 2139: Invalid sense buffer: error=0x0, valid=0x0
NMP : nmp_ResetDeviceLogThrottling:3845: Error status H:0x0 D:0x18 P:0x0 Sense Data: 0x0 0x0 0x0 from dev "naa .####################################
ScsiDevice I0: 4686: Cmd(0x45d9db30fe40) Oxfe, CmdSN 0x4 from wor ld 2097891 to dey "naa.####################################
LVM: 7076: Forcing APD unregistrat ion of deyID 696e58bb-33d5c0f8-e4ff-6e8dfc8000e6 in state 1.
LVM: 16209: Failed to open device naa.#################################### :1 : Timeout
WARNING: ScsiCore: 2139: Invalid sense buffer: error=0x0, valid=0x0
NMP: nmp_ResetDeviceLogThrottling:3845: Error status H:0x0 D:0x18 P:0x0 Sense Data: 0x0 0x0 0x0 from dev "naa.####################################
WARNING: ScsiCore: 2139: Invalid sense buffer: error=0x0, valid=0x0
NMP: nmp_ResetDeviceLogThrottling:3845: Error status H:0x0 D:0x18 P:0x0 Sense Data: 0x0 0x0 0x0 from dev "naa .####################################  

Device Status

[0x18]

RESERVATION CONFLICT

This status is returned when a LUN is in a Reserved status and commands from initiators that did not place that SCSI reservation attempt to issue commands to it.

Environment

VMware vSphere ESXi  8.0U3

Cause

SCSI reservation conflicts occur when one host in a cluster has placed a SCSI reservation on a LUN and has not released it. This can happen due to:

• A SAN switch reboot during a reservation operation
• Path failures during storage operations
• Networking issues interrupting storage communications Hardware failures
• Duplicate HBA World Wide Names (WWNs) are assigned to multiple ESXi hosts. This leads to the same HBA WWN being incorrectly associated with various hosts within the backend storage's zoning configuration.

Resolution

Contact the Storage Array vendor to clear the SCSI Reservation Conflict from the Storage Array end.