Error message: "Some of the disks of the virtual machine "VM_NAME" on host "HOSTNAME" failed to load. The information present for them in the virtual machine configuration may be incomplete" when powering on the VM.

Products

• VMware

Issue/Introduction

Symptom:

• Upon attempting to power on the virtual machine, the user encounters the following warning message.

"Some of the disks of the virtual machine "VM_NAME" on host "HOSTNAME" failed to load. The information present for them in the virtual machine configuration may be incomplete"

• Summary tab of the VM gives you the same prompt "Some of the disks of the virtual machine "VM_NAME" on host "HOSTNAME" failed to load. The information present for them in the virtual machine configuration may be incomplete".



Environment

VMware vSphere ESXi 7.x

Cause

• The issue happens when there is a connectivity problem while accessing the devices associated with the VM since the underlying LUN is directly unmapped from the storage side without following proper process.

In '/var/run/log/vobd.log', we can see below events -

2025-06-02T04:23:38.795Z: [scsiCorrelator] 10822206148769us: [esx.problem.scsi.device.state.permanentloss.noopens] Permanently inaccessible device: naa.xxxxxxxxxxxxxxxxxxxxxxxxxxx has no more opens. It is now safe to unmount datastores (if any): "DS_Name" and delete the device 

In '/var/run/log/vmkernel.log', we can see below events -

2025-04-29T09:00:15.788Z cpu111:2098741)NMP: nmp_ThrottleLogForDevice:3815: last error status from device naa.xxxxxxxxxxxxxxxxxxxxxxxxxxx repeated 222 times
2025-04-29T09:00:15.788Z cpu111:2098741)NMP: nmp_ThrottleLogForDevice:3867: Cmd 0x2a (0x45dad6ce6108, 7021084) to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxx" on path "vmhba4:C0:T10:L7" Failed:
2025-04-29T09:00:15.788Z cpu111:2098741)NMP: nmp_ThrottleLogForDevice:3875: H:0x1 D:0x0 P:0x0 . Act:FAILOVER. cmdId.initiator=0x430eb9c434c0 CmdSN 0x340 sllid: e2000000001e0000



 

Resolution

• The user needs to fix the connectivity issue with the storage devices for seamless communication. After fixing the connectivity issue, the VM can be powered on without any issues. In case the issue is caused due to LUN being unmapped directly from the storage array and formatted then this is a data loss scenario and now the VM needs to be recovered from backup.

Additional Information

Troubleshooting fibre channel storage connectivity