Home > Vmware Converter > Failed An Error Occurred During The Conversion 'platform-specific Error 2338'

Failed An Error Occurred During The Conversion 'platform-specific Error 2338'

Contents

I found this KB article that says it is a "known issue" and that you should convert the disks individually. The KB simply states that VMware is aware of this issue... How could I tell? Is C:\ it's own disk or are C:\ and D:\ 2 partitions on the same physical disk/array?2. weblink

An important point to mention in this process is that when transferring the second VM only containing the D drive, the transfer will fail with an error around 98% stating something How could I tell? There's no middleground, as it seems. Join Now I am in the process of converting 2 physical servers into virtual server using tghe latest vmware converter.

Failed An Error Occurred During The Conversion 'platform-specific Error 2338'

This time the conversion completed, but the final sync failed. Restore will create the VM (all the settings, like RAM, can be tuned) and also will take care of OS settings and drivers. Login.

  • By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.
  • Are you resizing the disks during conversion?--> I did not resize it, just selected thin provisioning4.
  • We're running vSphere Enterprise 5.1.
  • I noticed that you said you tried converting the disks individually to VMware Workstation - but have you tried them individually to the ESXi host (skipping the Workstation)?
  • http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2018582&sliceId=1&docTypeID=DT_KB_1_1&dialogID=325909453&stateId=0%200%20325915661

    I also found this blog post that mentions that changing the network speed fixed it: http://geekcubo.com/2011/11/vmware-converter-failed-clone-volume-c

    I would also run a chkdsk on the source machine. So I ran

By cold clone I mean using the cold clone iso that can be found among the vCenter installation files (not for vSphere 5, only v4 and earlier) to boot the server Join our community for more solutions or to ask questions. Suggested Solutions Title # Comments Views Activity Hyper-V VM migration fails 14 43 29d Getting Citrix (Xen-App 5.0) session to recognize a bar-code scanner 2 19 23d Fault Tolerance - VMware Error: Unable To Clone Volume 'c:'. I noticed that you said you tried converting the disks individually to VMware Workstation - but have you tried them individually to the ESXi host (skipping the Workstation)?

Go to Solution 7 Comments LVL 42 Overall: Level 42 VMware 30 Virtualization 16 Message Active 1 day ago Expert Comment by:paulsolov2013-05-06 What type of OS? Unable To Clone Volume C Vmware Converter Given the server was a production SQL server with over 700 GB of data, the conversion and cut-over had to be scheduled over the weekend. Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. check over here Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'.

Be aware that the newly attached disk will deafult to drive letter D. Vmware Converter Error 209 Type 1 Code 13 Looking a bit more at the logs, I found the following entries which pointed towards a network error: [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR [NFC ERROR] NfcFssrvr_IO: failed to send io D:\ is not a Windows dynamic disk, right?3. in my scenario, my network is 1GBps, but I have the physical machine that is being cloned on a 100MBps switch - so the ESXi server AND the machine running the

Unable To Clone Volume C Vmware Converter

The C: drive would clone, but the remaining three drives would fail with this, or a similar, message "BlockLevelVolumeCloneMgr: Detected a write error during the cloning of volume …. internet This means that if it had another drive letter before, you'll have to change it manually. Failed An Error Occurred During The Conversion 'platform-specific Error 2338' Required fields are marked *Comment Name * Email * Website Recent Posts "You must specify the PrimaryOnly parameter" error when you try to move a primary mailbox to Exchange Online in Detected A Write Error During The Cloning Of Volume Windows Bitmap Driver Volumeid When both P2V's are done the second one is removed from inventory.

SysCast podcast In the SysCast podcast I talk about Linux & open source projects, interview sysadmins or developers and discuss web-related technologies. http://discusswire.com/vmware-converter/vmware-converter-a-general-system-error-occurred-unknown-internal-error.html Be aware that the newly attached disk will deafult to drive letter D. Comments Hamid Monday, October 3, 2011 at 17:21 I am getting a similar error message attempting to convert a Linux machine to VM I am using "Vmware vCenter Converter Standalone Ver Tim Doty I know this is a couple years old but want to say thanks. Failed An Error Occurred During The Conversion Converter Fault Fileiofault

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2018582&sliceId=1&docTypeID=DT_KB_1_1&dialogID=325909453&stateId=0%200%20325915661

I also found this blog post that mentions that changing the network speed fixed it: http://geekcubo.com/2011/11/vmware-converter-failed-clone-volume-c

I would also run a chkdsk on the source machine. 0 By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. That geekcubo link didnt take me any where. http://discusswire.com/vmware-converter/vmware-converter-file-i-o-error-occurred-while-accessing.html YEP IT WORKED!! 😀 Joe This worked for me too… Thanks.

Does anybody have a cure? Failed: An Error Occurred During The Conversion: 'volumebasedclonetask::stopprevioustrackingbitmaps: Previously, Jakob was employed for 7,5 years in NNIT (Danish IT service provider owned by Novo Nordisk) working mainly with VMware virtual infrastructure and design. When I try to convert the physical machine straight to the esxi 5 host, I get an error that states: FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write

Dst error: Network error -- Failed to send header message", msg = "", } The chkdsk fixed the disk problems but it always shows errors when converts the VM.

POCEH Nov 19, 2012 1:23 AM (in response to JohnnyLeung) There is network error when second disk cone is started:[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcNetTcpRead: bRead: -1[2012-11-19 13:08:59.703 Both these machine have two drives. But when I try the d:\ drive or converting both drives in a single task, it failes with this error: FAILED: A general system error occurred: SQL_CANTOPEN: unable to open database Vmware Converter 6 Help Desk » Inventory » Monitor » Community » skip to main | skip to sidebar Virtual Infrastructure Tips - VMware A blog about VMware virtual infrastructure with howto's, tips, and

Please type your message and try again. 1 2 Previous Next 25 Replies Latest reply: Jun 14, 2015 5:32 AM by Pska P2V windows 2003 R2 64 bit failed Error: Unable http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2020517 This reduced the conversion time from 20 hours to 5.5 hours Stop the SQL service before starting the conversion. VMware Free edition & P2V conversions p2v vmware deployment build, I appreciate your insight   15 Replies Chipotle OP Alaerus Jan 8, 2013 at 4:37 UTC Do you this content Solved Vmware 5.1 P2 V error FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId Posted on 2013-05-06 VMware Virtualization 1 Verified