Error 37409 Vmware
Contents |
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. 1 2 Previous
Vmware Converter Error 37409 Type 1 Code 2338
Next 25 Replies Latest reply: Jun 14, 2015 5:32 AM unable to clone volume c vmware converter by Pska P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. JohnnyLeung
Detected A Write Error During The Cloning Of Volume Windows Bitmap Driver Volumeid
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 failed an error occurred during the conversion 'platform-specific error 2338' with vmware converter standalone 4.3, it always stopped at Drive D, while no problem on Drive C:I tried chkdsk on drive D, but seems doesnot help.more information on the system: OS: windows 2003 R2 64 bit HDD : C: 400GB, D: 1.7TBdatabase: MS SQL 2005 installed by SAPone concern is the system cannot be error: unable to clone volume 'c:'. shut down during conversion.many thanks in advance for your help. Thank you.Johnny ConverterDiagnostics20121119131405.zip 504.1 K 28433Views Tags: none (add) This content has been marked as final. Show 25 replies 1. Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. MKguy Nov 19, 2012 1:16 AM (in response to JohnnyLeung) "BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[59-4E-26-28-00-7E-00-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)",1. Is C:\ it's own disk or are C:\ and D:\ 2 partitions on the same physical disk/array?2. D:\ is not a Windows dynamic disk, right?3. Are you resizing the disks during conversion?4. What VMFS block size do you have on your destination datastore on the ESX(i) side? With 1.7TB the D:\ drive virtual Disk needs a 8MB VMFS blocksize that supports a maximum filesize of 2TB-512Byte.5. Do you have enough free space on that destination datastore (after C:\ finishes)? You won't be able to fit the full
discovers during daily operations - as well as, hopefully, being helpful to others in the community. Wednesday, June 6, 2012 P2V error - BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write The other
Failed An Error Occurred During The Conversion Cannot Format Volume
day we had to do a number of hot P2V's on some Citrix servers vmware converter error 209 type 1 code 13 running Win2k3. I had succesfully completed a test migration a week before (with VMware Converter Standalone 5 installed locally on the
Vmware Converter 6
source) on one of the same servers but when we re-initiated the P2V in the planned maintenance window, both servers failed at 90-something percent with an error stating the following: SingleVolumeCloneTask:DoRun: Volume cloning failed with https://communities.vmware.com/thread/426060?tstart=0 clone error BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[08-03-AE-BE-00-40-00-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338) This log entry is found by right clicking the job in Converter and choosing 'export logs'. Locate the file calledvmware-converter-worker-X.log (where X is an incremental integer). The above error message seems to indicate that there is a problem on the source disk. We tried running checkdisk which showed no errors and http://www.vi-tips.com/2012/06/p2v-error-blocklevelvolumeclonemgr-and.html we defragmented all drives. Same error occurred. 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 message Sysimgbase_DiskLib_Write failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338) By searching a bit on the above entries, I was pointed towards a relevant KB article from VMware. 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. The KB simply states that VMware is aware of this issue... I've done a ton of P2V's but this error I've never seen before... The good news is that there is a workaround: The trick is to only transfer one drive at a time. 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 the system partition and another VM (which I just called 'servername_Ddrive') containing only the D drive. When both P2V's are done the second one is removed from inventory. For the first VM, go to Edit Settings and attach the disk from the second VM, 'servername_Ddr
you'll eventually be forced to dig through their log files (vmware-converter-server.log) to track down errors that occur during conversion. Most of the time, the error you see either tells you the solution straight away, or causes you so much pain you just https://ma.ttias.be/vmware-converter-vmodl-methodfault-clonevolume-error/ stop trying. There's no middleground, as it seems. Black or white. Here's one such http://ipswitchft.force.com/kb/articles/FAQ/Attempting-to-Convert-a-Physical-Server-to-a-Virtual-Server-Fails-With-the-Following-Error-BlockLevelVolumeCloneMgr-and-Sysimgbase-DiskLib-Write error, and a fix for it. [task-1] -- ERROR -- Convert: converter.fault.CloneFault (converter.fault.CloneFault) { dynamicType =
Attempting to Convert a Physical Server to a Virtual Server Fails With the Following Error: BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_WritePrintable View «Go Back Information Article Environment Metadata Information Summary Attempting to Convert a Physical Server to a Virtual Server Fails With the Following Error: BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write Article Type FAQ Last Published Date 12/2/2015 6:04 PM Last Modified Date 12/2/2015 6:04 PM Article Article Number 000003098 Title Attempting to Convert a Physical Server to a Virtual Server Fails With the Following Error: BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write Description This Knowledgebase article provides information about an error occuring when converting a physical server to a virtual machine using VMware vCenter Converter. Solution Attempting to convert a physical server with multiple drives to a virtual server using vCenter Converter fails and displays an error message similar to the following: SingleVolumeCloneTask:DoRun: Volume cloning failed with clone error BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[08-03-AE-BE-00-40-00-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338) or: Converting a Windows physical machine with multiple drives (such as C: and D:) using Standalone Converter failsConverting the C: drive completes successfully, but converting the D: drive failsP2V conversion fails at approximately 90% while converting the D: drive and you see the error:"FAILED: A general system error occurred: Unknown exception" In the vmware-converter-worker.log file, you see entries similar to: [05628 warning 'Default'] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1 [05628 warning 'Default'] [,0] [NFC ERROR] NfcSendMessage: