Errors when gathering disk information during a physical to virtual conversion

KB Article: 1010341


When gathering disk information during a physical to virtual conversion, you may see the following errors:

  • Fatal error occurred. The most common reason for this is loss of network connection.
  • The wizard will now be closed.
  • Please check your network connection and try again.
  • Exception getting Disks and Volumes
  • sourceStorageInfo is missing


This article provides troubleshooting steps for converting a physical Windows source computer to a virtual machine. It assists you in eliminating common causes for this issue by verifying that networking is still in place between the Converter server and the the Windows source, and that the Windows source is not using any virtual disks.


Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Note: If you perform corrective action in any of the following steps, attempt the conversion again.

  1. Verify that networking is still in place between the Converter server and the source computer. For more information, see Required VMware vCenter Converter ports (1010056).
  2. Confirm that there are no virtual disks appearing as disk devices in the Disk Management utility.
    1. Click Start > Run.
    2. Type diskmgmt.msc and press Enter.
    3. Review the list of drive letters and devices in the bottom window. If there is a drive that is not associated with a physical device then remove it.

      Note:  You must determine what software process has mounted this virtual drive and consult with its product documentation.

Note: If your problem still exists after trying the steps in this article, please:

VMotion error CPUID mismatch on same hardware

We recently acquired a new Dell PowerEdge for our VMware Cluster. Although the hardware was the same, we did get a vmotion error like this one:

vmotion error

After investigating the problem, it looked like the virtual center server added maskid’s on it own to the virtual machines. After deleting this masks vmotion could occur without any problem. You can see themas settings in the following picture:


To remove the mask id, do the following:

  • Shut down the virtual machine
  • Edit the settings of the virtual machine
  • Go to the options tab
  • Click the CPUID Maks setting
  • Click the Advanced Button
  • Press Reset all to default
  • Power on the virtual machine

After doing this, you should have no settings in this advanced page.

This happened on ESX 3.5 u2, an alternative for this solution is to upgrade to ESX 3.5 u4 and use EVC.