While installing a fresh copy if ESXi (version 623860) on to UCS blade I get the following error:
Operation failed.
This program has encountered an error:
(Use the arrow keys to scroll)
Error (see log for more info):
vmfstools failed with message: Device path name
"/vmfs/devices/disks/naa.68a980000646e4c4b2f4a6e2d627a385a:8" is not
a valid absolute or realtive path
Failed to resolve device name
/vmfs/devices/disks/naa.68a980000646e4c4b2f4a6e2d627a385a:8
Usage: vmfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/vml... or,
vmfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/naa... or,
vmfstools -C [vmfs3|vmfs5]
/vmfs/devices/disks/mpx.vmhbA:T:L:P
Error: No such file or directory
The preceeding information will assist VMware Support team with your problem. Please record this information before prceeding.
UCS Blade: Cisco UCS B200 M3, Intel Xeon E5-2600 series processor
No faults indicated in UCS Manager
BIOS: B230.2.0.3a.0.060520121139
Boot from LUN
Ran over 72 hours of MemTest86+ v4.0s: 0 faults.
The boot LUN has been recreated twice and I have tried the ESXi build 3 times.
See attached screen shot.
Any suggestions on how to resolve this are welcome.
I have updated this myself.
The igroups, LUNs and vHBA settings are all configured correctly for VMware. We have reconfigured the boot LUN, so that we weren’t getting the issue described in KB 2012053. The blade itself has been replaced and we get a slightly different error message:
Operation failed.
This program has encountered an error:
(Use the arrow keys to scroll)
Error (see log for more info):
vmfstools failed with message: Checking if remote hosts are using
this device as a valid file system. This may take a few seconds ...
Creating vfat file system on
"naa.68a980000646e4c4b2f4a6e2d627a385a:8" with blockSize 10848576 and
Volume label “none”.
Usage: vmfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/vml... or,
vmfstools -C [vmfs3|vmfs5] /vmfs/devices/disks/naa... or,
vmfstools -C [vmfs3|vmfs5]
/vmfs/devices/disks/mpx.vmhbA:T:L:P
Error: Connection timed out.
The preceeding information will assist VMware Support team with your problem. Please record this information before proceeding.
Hi
The original problem was caused by the UCS blade, which is now reporting a fault. Once this was replaced it created the second error message. The second error message just indicated that the infornation on the boot LUN was corrupt, so all that was required was to remove that information by re-running the ESXi installation program.
All's well that ends well.