forumyaren.com

Home > Vmware Converter > Vmware Converter Write Error 2338

Vmware Converter Write Error 2338

Contents

continuum Nov 20, 2012 7:37 PM (in response to JohnnyLeung) > robocopy is not possible, since both physical and virtual cannot online at the sametime.To robocopy into a vmdk you can Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? 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 JohnnyLeung Nov 18, 2012 10:32 PM Hello everyoneCan someone help me with the issue P2V a win2k3 64 bit machine into vmware?I am using esxi 4.1 Update 1 with vmware converter weblink

create a Windows-share using the whole new vmd4. 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 Feel free to join the discussion by leaving comments, and stay updated by subscribing to the RSS feed. © 2016 Explored Spaces Send to Email Address Your Name Your Email Address Always failed while still on 1%. try here

Vmware Converter Detected A Write Error During The Cloning Of Volume

Thank you! Are the drives basic or dynamic? when i was using converter version 4.3, drive C can be finish in 2 hrs, but while using 5.0.1, it cannot finish after 10hrs.Do you have any other idea to solve You won't be able to fit the full 400GB C:\ and 1.7TB D:\ on the same VMFS as ESXi <5.0 only supports LUNs of up to 2TB.You can also try using

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. It failed at 51%. The good news is that there is a workaround: The trick is to only transfer one drive at a time. Vmware Converter Error Code 1450 Join Now For immediate help use Live now!

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. I am in Failed An Error Occurred During The Conversion 'platform-specific Error 2338' An alternative workaround that will most likely work as well is to do a cold clone. Error: 37409 (type: 1, code: 2338)2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: https://communities.vmware.com/thread/426060?tstart=0 You won't be able to fit the full 400GB C:\ and 1.7TB D:\ on the same VMFS as ESXi <5.0 only supports LUNs of up to 2TB.--> it has enough space

Are the drives basic or dynamic? 1 Jalapeno OP bmeiont Jan 8, 2013 at 5:29 UTC   _Justin_ wrote: I have seen some strange errors like that when Vmware Converter A General System Error Occurred Unknown Internal Error Suggested Solutions Title # Comments Views Activity Configuring Network Adapters on Vmware. 5 60 31d Error while connecting to VMware device 4 42 21d connect 10G with 1G 16 46 21d thanks! ][Q][ Rajeev Welcome! 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

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

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://www.vi-tips.com/2012/06/p2v-error-blocklevelvolumeclonemgr-and.html Provide feedback Please rate the information on this page to help us improve our content. Vmware Converter Detected A Write Error During The Cloning Of Volume 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)? Unable To Clone Volume C Vmware Converter Better fit would probably be Acronis Backup & Recovery.

Join our community for more solutions or to ask questions. have a peek at these guys This is ok - as long as the drive has been succesfully cloned, this is what matters (see below). Simply install Windows Agent on your source machines, ESXi Agent to your VMware, Backup the source and then Restore it to new VM on ESX. As for your error, were you ever able to rectify them? Detected A Write Error During The Cloning Of Volume Windows Bitmap Driver Volumeid

We tried running checkdisk which showed no errors and we defragmented all drives. What VMFS block size do you have on your destination datastore on the ESX(i) side? Error: 37409 (type: 1, code:2338)' This refers to a problem with source disks. http://forumyaren.com/vmware-converter/vmware-standalone-converter-error-2338.php No I have not, Im not sure that the error was concerning block SIZE necessarily.    Will speak more to changing the block size of the new disk?

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 A General System Error Occurred Unexpected Element Tag Storage Software VMware Virtualization Storage How to move your VMs from a dead ESXi host Article by: Luciano When we have a dead host and we lose all connections to the I ended up converting with the C: drive only and then doing a robocopy to a "new" D: drive that I presented to the VM.  1 Jalapeno OP

Do PM me if you need more details or guidance. 0 Pimiento OP kevincao Sep 23, 2014 at 11:40 UTC 1st Post this maybe kind of a late

I had same problem and changed from Auto to 100/Full and My image is up to 10% now. Wednesday, June 6, 2012 P2V error - BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write The other day we had to do a number of hot P2V's on some Citrix servers running Win2k3. Paper:PrintEmailMoreLinkedInGooglePinterestTwitterFacebookLike this:Like Loading... Error: Unable To Clone Volume 'c:'. JohnnyLeung Nov 20, 2012 5:38 PM (in response to continuum) robocopy is not possible, since both physical and virtual cannot online at the sametime.I justed disabled the SSL and trying to

POCEH Nov 19, 2012 1:59 AM (in response to JohnnyLeung) The Converter 5.0.x allows to deselect system/bootable disk C:So you need one conversion for disk D: (don't warry fail at reconfig 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 Join & Ask a Question Need Help in Real-Time? this content The disks are dynamic...RAID 5 config.

Conversion finally worked. Error: Failed to connect to server 192.168.80.3:902 2015-06-06T00:56:14.019+02:00 info vmware-converter-worker[02740] [[email protected] sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338) 2015-06-06T00:56:14.019+02:00 info vmware-converter-worker[02740] [[email protected] sub=Default] Error 2338 opening disk vpxa-nfcssl://[VSA-LUN01] LR-3CX/[email protected]:902!52 Same error occurred. VCP3, VCP4, VCP5, VTSP, VSP, ITIL Foundation 2+3, PRINCE2 Foundation, MCP.

Finally booted system into Recovery Console and recreated it there with bootcfg /rebuild. What VMFS block size do you have on your destination datastore on the ESX(i) side? This means that if the source has a C and a D drive you'll be P2V'ing this machine twice creating to seperate VMs - one only containing the C drive including can you ping and traceroute to vcenter server ?

Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. Error: 37409 (type: 1, code: 2338) This log entry is found by right clicking the job in Converter and choosing 'export logs'. Also - what percentage is the conversion at when it fails? JohnnyLeung Nov 21, 2012 5:37 PM (in response to POCEH) it does not work with convert D drive seperately, C dirve can complete while D drive was failedsee attached logerror message:

Go to Solution 5 Comments LVL 117 Overall: Level 117 VMware 109 Virtualization 69 Message Active today Expert Comment by:Andrew Hancock (VMware vExpert / EE MVE)2015-06-06 What is the error Tried to recover this with Windows on-board utilities, but no success. 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. 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

Share This Page Legend Correct Answers - 10 points Home VMware P2V conversions fail by bmeiont on Jan 8, 2013 at 4:27 UTC | Virtualization 0Spice Down Next: Bad performance on Copyright © 2015 - Made with Love in New Delhi , India TecheZone Privacy Policy Agile World Virtual Hints Enterprise Data About the Authors Mindmap for Performance Testing Specifications for Enterprise As it turns out, this is not network related at all, it is a known error in the Converter Standalone (both v4 and v5) software.