• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8681
  • Last Modified:

VMware vCenter Converter Error: unable to clone volume 'C:'

Another error I received while converting a physical machine onto my ESXi server.  

FAILED: An error occurred during the conversion: 'File-level volume clone error failed with source volume id \WindowsBitmapDriverVolumeId=[06-CF-59-CB-00-00-50-06-00-00-00-00] and target volume id 60?,95;,0000056000000000. Error code:

There are three partitions on this server.  SBS 2011 is the OS.  I read where multiple partitions could cause this issues so I selected only C and got this error at 79%.  

Currently I have 3 partitions as follows ::

System Reserved - 100MB NTFS System, Active, Primary Partition
C - 149.15GB NTFS Boot, Page File, Crash Dump, Primary Partition
D - 781.25GB NTFS Primary

The only thing I haven't tried is converting the image locally and migrating it into ESXi.

I attached the log file for the conversion.
  • 3
  • 2
1 Solution
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Try to convert the physical server but only convert one disk at a time...

TripapHoniCAuthor Commented:
Try to convert the physical server but only convert one disk at a time...


Did that, failed.  I didn't select the System Reserved & C: separately from the D: drive.
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

TripapHoniCAuthor Commented:
I found the solution buried in an old article referenced here ::


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.
Thanks for sharing how you fixed your issue..

Good Tip
TripapHoniCAuthor Commented:
Was unable to find answer from community.  Found answer on own accord.  Sharing with community.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now