Error 37409". What VMFS block size do you have on your destination datastore on the ESX(i) side? These are the keys I exported: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\symmpi HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\ pci#ven_1000&dev_0030 The machine you export this from needs to be xp/2003 and use the "LSI Logic Parallel" adapter. Copy the file symmpi.sys over to "%windir%\system32\drivers" 6. http://prcflow.com/vmware-converter/vmware-converter-failed-at-98-unable-to-find-the-system-volume.html
Both these machine have two drives. Error: 37409 (type: 1, code: 2338)2015-11-08T02:16:48.250-06:00 error vmware-converter-agent [[email protected] sub=task-1] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-3)=-;5;00000010000000000 updates, I used Hirens 15.1 2. This went smoothly except for a volume resize, but I'll post about that later. https://communities.vmware.com/thread/426060?tstart=0
An alternative workaround that will most likely work as well is to do a cold clone. Error: 37409 (type: 1, code: 2338)' Any suggestions would be appreciated? 0 Question by:bergquistcompany Facebook Twitter LinkedIn Google LVL 42 Active today Best Solution bypaulsolov If you can login than you Have you checked the physical disk for errors?
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 D:\ is not a Windows dynamic disk, right?--> it is MBR disk only3. After that, you can boot the VM now containing both drives. Failed An Error Occurred During The Conversion Converter Fault Fileiofault Repaired failures on source disks with chkdsk.
Error: 37409 (type: 1, code: 2338)2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=task-1] BackgroundWriter::~BackgroundWriter: Detected A Write Error During The Cloning Of Volume Windows Bitmap Driver Volumeid ReplyDeleteAdd commentLoad more... You can tell by going into Windows Disk Management: 0 Ghost Chili OP _Justin_ Jan 8, 2013 at 5:34 UTC And I never could figure it out. https://community.spiceworks.com/topic/288806-vmware-p2v-conversions-fail Join Now I am in the process of converting 2 physical servers into virtual server using tghe latest vmware converter.
Join & Ask a Question Need Help in Real-Time? Vmware Converter 6 Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. You can tell by going into Windows Disk Management: Yeah they're basic. 0 Ghost Chili OP Best Answer _Justin_ Jan 8, 2013 at 6:47 UTC What version of continuum Nov 21, 2012 1:50 AM (in response to JohnnyLeung) assumehost 1 = your p2v source - has two drives C:\ and D:\VM 1 = the result of your Converter import
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 http://www.techezone.com/question/blocklevelvolumeclonemgrclonevolume-error-37409-type-1-code-2338/ That geekcubo link didnt take me any where. Unable To Clone Volume C Vmware Converter 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 Failed An Error Occurred During The Conversion 'platform-specific Error 2338' It looked like it worked great and during the time it took for me to login to vsphere and boot up the vm I almost convinced myself to get giddy with
Post Tagged with Conversion, P2V, VMware ← Previous Post Next Post → Click on a tab to select how you'd like to leave your comment FacebookGoogleLoginLogin Leave a Reply Cancel reply http://prcflow.com/vmware-converter/failed-unable-to-find-the-system-volume-reconfiguration-is-not-possible.html continuum Nov 20, 2012 11:47 AM (in response to JohnnyLeung) cant you use robocopy for drive D: ? I had succesfully completed a test migration a week before (with VMware Converter Standalone 5 installed locally on the source) on one of the same servers but when we re-initiated the asked by a_unique_name, 2 hours ago Recent Posts Characters and Tokens Structure Of C Program C environment Why C is so much popular ? Vmware Converter Error 209 Type 1 Code 13
Be aware that the newly attached disk will deafult to drive letter D. Acronis True Image Error: 37409 (type: 1, code: 2338)2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=task-1] BackgroundWriter::ThreadFunc: Broadcasting "ThreadDone" condition.2015-11-08T02:16:48.250-06:00 info vmware-converter-agent [[email protected] sub=ThreadPool] Thread delisted2015-11-08T02:16:48.250-06:00 error vmware-converter-agent [[email protected] sub=task-1] BlockLevelVolumeCloneMgr::CloneVolume: failed with exception BlockLevelVolumeCloneMgr::CloneVolume: Detected a Get 1:1 Help Now Advertise Here Enjoyed your answer?
POCEH Nov 20, 2012 11:53 AM (in response to MKguy) You can resolve speed issue with Converter 5 disabling SSL connection.In the same section in converter-worker.xml you can try to increase 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 Source VM is Windows 2003 32 bit. You can not post a blank message.
I've done a ton of P2V's but this error I've never seen before... Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? 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%20325915661I 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 Check This Out This time the conversion completed, but the final sync failed.