I have a small ESXI installation with only a few VMs. These are mostly OracleLinux 6 x64 systems.
I have built a new ESXI on better hardware, and am beginning to migrate some machines to the new system. This has gone pretty well, but for some VMs, I get the error: "Unable to obtain hardware information for the selected machine."
Looking into the logs, it appears that, although I have chosen (for example) hcm92-pristine as the VM to copy, the converter complains that it cannot lock a disk from a completely different (hcm92ssd) VM. Both of these VMs are valid, and both can be running at the same time. I do not see anything in the .VMX of either one that is out of place; nothing "points to" another system's objects. In fact, the examples (hcm92-pristine and hcm92ssd) are on different filesystems, with hcm92-pristine being on /vmfs/volumes/RaidDS and hcm92ssd being on /vmfs/volumes/datastore1.
This is VMware vCenter Converter Standalone client Version 5.5.3 build-2183569.
When I exported logs, I received the error: "The diagnostic package cannot be retrieved from the VMware vCenter Converter standalone server. Error: Could not generate VMware vCenter Converter Standalone Server diagnostic file. But then a file is generated. I have attached that file. I've also attached vmware-converter-server-20.log.gz file from C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs. This shows the result of being unable to lock hcm92ssd although I chose the hcm92-pristine VM. (I don't see evidence of what I chose, however.)