Error 37409 Vmware Converter
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 Next 25 Replies Latest reply: Jun 14, 2015 5:32 AM by Pska P2V unable to clone volume c vmware converter windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. JohnnyLeung Nov failed an error occurred during the conversion 'platform-specific error 2338' 18, 2012 10:32 PM Hello everyoneCan someone help me with the issue P2V a win2k3 64 bit machine into vmware?I detected a write error during the cloning of volume windows bitmap driver volumeid am using esxi 4.1 Update 1 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 error: unable to clone volume 'c:'. 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 shut down during conversion.many thanks in advance for your help. Thank you.Johnny ConverterDiagnostics20121119131405.zip 504.1 K 28437Views 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
Vmware Converter Error 209 Type 1 Code 13
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 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 Converter 5 as it supports ESX(i) 4.x destinations too.Check out this article referencing the above error too:http://www.vi-tips.com/2012/06/p2v-error-blocklevelvolumeclonemgr-and.html Like Show 0 Likes (0) Actions 2. Re: P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'. 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 09
discovers during daily operations - as well as, hopefully, being helpful to
Failed: An Error Occurred During The Conversion: 'volumebasedclonetask::stopprevioustrackingbitmaps:
others in the community. Wednesday, June 6, 2012 P2V error - vmware converter 6 BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write The other day we had to do a number of hot P2V's on vmware standalone converter some Citrix servers running Win2k3. I had succesfully completed a test migration a week before (with VMware Converter Standalone 5 installed locally on the source) on one https://communities.vmware.com/thread/426060?tstart=0 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 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 http://www.vi-tips.com/2012/06/p2v-error-blocklevelvolumeclonemgr-and.html 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 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 be
• November 8, 2015 Vote Up 0 Vote http://www.techezone.com/question/blocklevelvolumeclonemgrclonevolume-error-37409-type-1-code-2338/ Down Open Public VmwareQuestions Guest asked November 8, 2015 Hi all,This ones got me a little stumped, hoping someone has some more experience.Source windows 2012 64bit (fresh deployment, test server for vmware converter newbies in team)Converter version 6ESX 5.5I start conversion and fails at 3%~ with error.BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code:2338)'In worker unable to clone logs all i can see is after the Worker InitialSyncFullCloneTask updates, state: 4, percentage: 3, xfer rate (Bps): 47285248 rows is as follows, no other errors - it just ends....2015-11-08T02:16:48.945-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] TargetVmManagerImpl::DeleteVM2015-11-08T02:16:48.945-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] Reusing existing VIM connection to 10.27.132.2282015-11-08T02:16:48.976-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] Destroying vim.VirtualMachine:83 on 10.27.132.2282015-11-08T02:16:49.241-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Generating Agent Task bundle for task with id="task-1".2015-11-08T02:17:26.916-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Retrieving agent task log bundle to "C:WindowsTEMPvmware-tempvmware-SYSTEMagentTask-task-1-vzohlwml.zip".2015-11-08T02:17:26.931-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Bundle successfully retrieved to "C:WindowsTEMPvmware-tempvmware-SYSTEMagentTask-task-1-vzohlwml.zip".2015-11-08T02:17:26.931-06:00 error vmware-converter-worker[077