Hi Guys...
Im having this problem also.
It is a new setup of esxi 5.5 with 5 luns / 1 datastore per lun & vice versa.
Using vSphere Client 5.5 and vCenter Standalone COnverter 5.5.2 Build 1890136.
I have 4 vms, one vm per datastore. None of the vms are interdependent nor do they share any files between them.
One datastore is empty, and Ive been trying to move a VM from another datastore to this one, to free up the bigger disk for another new vm.
But it is impossible now for me to either copy the vm through the datastore browser, or to access the vms via vcenter converter standalone, to convert it and move it that way.
For the latter, it tells me it is unable to obtain hardware information. It says this now for all vms in my esxi!
I have tried to create a new admin for the whole esxi but it makes no difference.
When trying to copy and paste, via vsphere client, it attempts the task, then reports errors and halts, the error being unable to access vmdk.
I have the vms split into resource pools, but obviously the admin root user has full access.
I have tried to re-propagate the admin permissions, but no difference after doing this either.
When I try to create a new Administrator User Group, to try to add this / propagate this group to the vm, I receive the following error:
Call "HostLocalAccountManager.CreateGroup" for object "ha-localacctmgr" on ESXi "192.168.2.70" failed
SO then I tried to create a new vm in the empty datastore, and use the old vm disk for it. Once created, I tried to copy and paste the vmdk to the new datastore, with a view to changing the path for the new vm disk.
20% through the 60gb copy, it halts and says: Error caused by file /vmfs/volumes/_____.vmdk.
All vms were powered off prior to this. The vm works fine and has no issues when running from the old datastore. No errors or bugs, no performance issues hinting towards any data corruptions.
When trying to download the vmdk to a local folder, it returns an immediate error "failed" with no further explanation.
If this is an error or corruption solely related to this one vm, why does vcenter converter now no longer read the configurations of any of the other vms?