ESXi Storage Registration Failure for Unmounted Volumes Actively Presented on Storage Array
Article ID: 443358
Updated On:
Products
Issue/Introduction
VMware vSphere ESXi storage subsystems experience repetitive path validation, claiming exceptions, and device registration failures. The vmkernel.log reports cyclical exceptions stating that registration has been aborted due to unsupported attributes, coupled with failed unregistration actions for unit attention parameters.
- Stale path validation loops re-triggering every few minutes during background storage polling cycles.
Manual storage rescans temporarily mitigate the warnings, but the alerts return upon the next discovery phase.
The following error traces are systematically recorded in
vmkernel.log:
2026-06-08T15:08:54.976Z cpu42:2097944)ScsiDevice: 5211: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:08:54.976Z cpu42:2097944)ScsiDevice: 5221: Failed to register for 'TARGET MICRO CODE CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:08:54.976Z cpu42:2097944)ScsiDevice: 5231: Failed to Unregister 'POWER ON RESET' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:08:54.976Z cpu42:2097944)ScsiDevice: 5299: Unregistered device 'naa.ID' [0x4308f85e4940]
2026-06-08T15:13:54.931Z cpu41:2097944)VMWARE SCSI Id: Id for vmhba64:C1:T69:L0
2026-06-08T15:13:54.932Z cpu41:2097944)VMWARE SCSI Id: Id for vmhba64:C0:T69:L0
2026-06-08T15:13:54.933Z cpu41:2097944)ScsiDeviceIO: 9672: QErr is correctly set to 0x0 for device naa.ID.
2026-06-08T15:13:54.933Z cpu41:2097944)ScsiDevice: 2803: Failing registration of device 'naa.ID': Unsupported device attributes isLocal:0, isSSD:1, isNmpOrHppPlugin:1
2026-06-08T15:13:54.933Z cpu41:2097944)ScsiDevice: 5171: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.933Z cpu41:2097944)ScsiDevice: 5181: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5191: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5201: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5211: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5221: Failed to register for 'TARGET MICRO CODE CHANGED' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5231: Failed to Unregister 'POWER ON RESET' unit attention for device:naa.ID. Reason: Not found
2026-06-08T15:13:54.934Z cpu41:2097944)ScsiDevice: 5299: Unregistered device 'naa.ID' [0x4308f89e0280]
Environment
VMware vSphere ESXi 7.0.3
Cause
The target block storage volume was unmounted and logically detached from the vSphere cluster layer, but the physical presentation pathways remain actively mapped within the host access group (initiator group, storage masking view, or fabric zoning) on the storage array side.
As a result, automated background discovery sweeps continually detect the advertised storage endpoints. When the Native Multipathing (NMP) or High Performance Plug-in (HPP) subsystems attempt to register the device, the validation checks fail because the logical volume registry entries have already been torn down.
Resolution
To resolve this issue permanently, the physical presentation layer on the storage area network (SAN) must be fully aligned with the logical state of the ESXi hosts.
1) Contact your storage admin or array vendor and ensure all references of the volume are removed from the ESXi presentation.
2) From the cluster object in vCenter perform a storage rescan to update the LUN information presented from the array
Additional Information
For the correct sequence regarding planned hardware target decommissioning workflows, see Broadcom TechDocs: Detach Storage Devices
Feedback
