Error Unable To Clone Disk Vmware Converter
Contents |
to clone disk *.vmdk when converting a VM with Paravirtual disk with VMwareConverter March 16, 2011 boerlowie Leave a comment Go to comments Last week i was trying to migrate/convert (V2V) a VM with Paravirtual SCSI Controllers. As vmware converter disk based cloning you all know, Hard disks attached to Paravirtual SCSI Controllers is ‘the way to unable to clone volume c vmware converter go’ in vSphere: - Lower CPU utilization - Better performance - Virtualization aware - … However, when you try to convert vmware converter manual a VM with Paravirtual SCSI Controller, VMware Converter 4.3 throws you a nice error and the task fails with Status: FAILED: An error occurred during the conversion: When you look at the Log Highlights window, you vmware converter unable to contact the specified host get a little bit more information:
Looking even deeper in the logfile, a message is logged that an Unknown controller is detected. So VMware Converter 4.3 doesn’t know the Paravirtual Controller! The solution is quite simple for this problem: - Change all Paravirtual controllers to LSI Logic (VM MUST be powered off) - Do NOT poweron the VM from now on - Perform the Convert, make sure VM is not poweredVmware Converter Unable To Contact The Specified Host The Host Might Not Be Available
on automatically after convert - Change SCSI controller back to Paravirtual - Power on VM To change a SCSI controller, open Edit Settings… from the VM and select the SCSI Controller. Click the Change Type… button and modify the SCSI Controller Type. Done! VMware confirmed this as a known bug in Converter 4.3. It will be solved in version 5.0 Share this:EmailLike this:Like Loading... Related Categories: VMware, vSphere Comments (1) Trackbacks (1) Leave a comment Trackback guymontag October 20, 2011 at 19:20 Reply Thanks, that solved my import machine issue March 1, 2012 at 11:46 Vmware Converter | TagHall Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Find VMs with Mismatched OS usingPowerCLI Enable RSS (Receive Side Scaling) on Windows 2008 (R2) VirtualMachines RSS feed Google Youdao Xian Guo Zhua Xia My Yahoo! newsgator Bloglines iNezha Recent Posts How to Shrink a Thin VMDK on ESXi5.0vSphere
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware Converter Standalone > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 8 Replies Latest reply: Oct 8, 2014 6:59 AM by Fred Weston Error: https://communities.vmware.com/thread/491523?start=0&tstart=0 Unable to clone volume C: Fred Weston Oct 2, 2014 2:26 PM I'm using converter standalone v5.5 build 1362012 and am trying to copy a VM that is presently in Amazon Web Services to my local vSphere environment. I've done it successfully before with this exact same VM as a test, but now I'm actually trying to move the VM and encountering this problem.The vmware converter error message is FAILED: An error occurred during the conversion: converter.fault.FileIOFaultAt first I was trying to use converter to directly copy the VM from AWS to vSphere. When that failed twice, I tried using converter to convert the VM to a Workstation VM, which I could later import into vCenter and that failed as well.The VM in question is Win2008R2. It has three disks, unable to clone each with one basic volume that takes up the entire disk: C: 30 GBD: 20 GBE: 40 GBI am not trying to resize volumes as part of the conversion. There is plenty of free space on the volume I am writing the VM files to (that folder is on a shared volume on the host running converter).I've tried running chkdsk on the VM being converted and it did not report any errors. I also tried defragmenting the volumes but it made no difference.Here is the log bundle from converter:https://lpga.box.com/s/1e62weqjzq6lkv87eis9Any suggestions on how I can fix this problem? 947Views Tags: none (add) converterContent tagged with converter This content has been marked as final. Show 8 replies 1. Re: Error: Unable to clone volume C: POCEH Oct 3, 2014 12:48 AM (in response to Fred Weston) Your error is:2014-10-02T14:05:54.323-04:00 [01912 error 'task-3'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Error (type: 2, code: 2) reading 655360 bytes starting at 0x000000023f83a000 from the source volume C:2014-10-02T14:05:54.323-04:00 [01912 error 'task-3'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Unrecoverable error (type: 2, code: 2) reading 655360 bytes starting from 0x000000023f83a000 from the source volume C:so you need to do 'chkdsk c: /B' in order to fix errors