5. Now go back to vCenter and browse the datastore hosting the VM. Both ‘mydisk.vmdk’ and ‘mydisk1.vmdk’ should be present.

(Optional: Download the original disk (if practical) to preserve in case of further issue.)

6. Remove mydisk.vmdk from the VM folder.

7. Rename ‘mydisk1.vmdk’ to ‘mydisk.vmdk’.

8. Power-on the VM and check for further errors in vCenter.

Jeremy loves all things technology! Has been in IT for years, loves Macs (but doesn't preach to others about their virtues), loves virtualization (and does shout about it's virtues), and sometimes skis, bikes and directs amateur plays!

Comments

Hi Mirc,
You can use VMware Converter – if you have it available. Personally, if the VM is already in residence on the LUN then I find that using vmkfstools and the command line is usually much quicker from an administrative perspective when restoring a service.
Cheers.
Jeremy.

Perfect. Saved me from several botched P2V conversions on an SBS 2011 server. I was using VMware vCenter Converter and it was still not recognizing the drive structure. I resorted to converting one drive at a time and that didn’t work either. Your method worked first time. Thanks for this.

The simple way to fix this issue to perform svmotion to some other datastore, if you see the disk which is giving error will be a sparse disk, once you convert it to thick or thin, it will boot properly.