VM Import: “Unsupported and/or invalid disk type 7” errors….

Full error message from vCenter:

Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first?Unable to create virtual SCSI device for scsi0:0,  Module DevicePowerOn power on failed.”

Came across another issue with importing and moving a VM into vSphere. The VM was created in Workstation 8 and was to be imported into vSphere to be used as a development VM.

Uploading the VM to the LUN worked fine, as did importing it to the vCenter Inventory. However, powering-on the VM resulted in the SCSI error type 7 message in vCenter.


This can happen when importing a VM into vSphere, either from a backup or from another vSphere version. The solution is to re-import the source disk producing the error as ‘zeroedthick’ format.


1. Ensure you have SSH access to your ESXi server hosting your VM. (Host > Configuration > Software > Security Profile > Services > Properties > SSH = Running).

2. Use Putty to SSH to your ESXi host. Authenticate as the root user.

3. Move to the VM folder:


….where <datastore> is your LUN or NFS share and <vm-folder> is your VM container folder.

4. Use vmkfstools to convert the disk to zeroedthick:

vmkfstools -i mydisk.vmdk -d zeroedthick mydisk1.vmdk

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!


  1. jeremyjbowman says

    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.

  2. MarioTunes says

    Hello, What is the correct settings for P2V (to USB), to avoid this error ?
    Thank you

  3. guest says

    I had to use:

    vmkfstools -i mydisk.vmdk mydisk1.vmdk -d zeroedthick

    instead since vmkfstools -i mydisk.vmdk -d zeroedthick mydisk1.vmdk was giving me an error

  4. jeevadotnet says

    Thanks for this 🙂 worked like a charm
    Server 2003 SP2 to Virtual (vCenter 5.1)

  5. JPB says

    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.

  6. says

    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.

  7. says

    Thank you very much! I had to convert a Cloudera VM for a course before I start, and I am a completely noob with my dl360g7 😛
    In my case, it created a -flat.vmdk file too.


Leave a Reply

Your email address will not be published. Required fields are marked *