Blocklevelvolumeclonemgr Error
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
Failed An Error Occurred During The Conversion 'platform-specific Error 2338'
14, 2015 5:32 AM by Pska P2V windows 2003 R2 64 bit error: unable to clone volume 'c:'. failed Error: Unable to clone volume 'D:'. JohnnyLeung Nov 18, 2012 10:32 PM Hello everyoneCan someone help me
Detected A Write Error During The Cloning Of Volume Windows Bitmap Driver Volumeid
with the issue P2V a win2k3 64 bit machine into vmware?I am using esxi 4.1 Update 1 with vmware converter standalone 4.3, it always stopped at Drive D, while unable to clone volume c vmware converter 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 shut down during conversion.many thanks in advance for your help. Thank you.Johnny ConverterDiagnostics20121119131405.zip 504.1 K 28409Views Tags: none vmware converter error 209 type 1 code 13 (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 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 abo
discovers during daily operations - as well as, hopefully, being helpful to others in the community. Wednesday, June 6, 2012 P2V error
Failed: An Error Occurred During The Conversion: 'volumebasedclonetask::stopprevioustrackingbitmaps:
- BlockLevelVolumeCloneMgr and Sysimgbase_DiskLib_Write The other day we had to do a number chkdsk /b of hot P2V's on some Citrix servers running Win2k3. I had succesfully completed a test migration a week before
A File I/o Error Occurred While Accessing
(with VMware Converter Standalone 5 installed locally on the 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 https://communities.vmware.com/thread/426060?tstart=0 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 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 http://www.vi-tips.com/2012/06/p2v-error-blocklevelvolumeclonemgr-and.html 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 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 'servernam
Converter Dyn 1082 Followers Follow VMware 396221 Followers Follow Join the Community! Creating your account only takes a few minutes. Join Now I am in the process of converting 2 physical servers into virtual server using tghe latest vmware converter. When I try to https://community.spiceworks.com/topic/288806-vmware-p2v-conversions-fail 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 error during the cloning of volume \WindowsBitmapDriverVolumeId=[2E-E6-5D-9E-00-00-80-02-00-00-00-00]. Error: 37409 (type: 1, code: 2338)' So I tried a different route, converting it into a workstation virtual machine then converting onto the esxi host machine. Both these machine have two drives. c:\ and d:\. I read that if split up the conversion by drives then that might work. When I try error occurred converting just the C:\ into a vmware workstation virtual machine and then onto the esxi host, no problems. 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 file Can anyone help me out, Its been hassling me for a while now and I forget I have folks out there who know a whole lot more about these things than I do. Appreciative for all an error occurred help, BT Reply Subscribe View Best Answer RELATED TOPICS: Vmware conversions - P2V thick or thin ? 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 have the option of getting the machine offline? If so, what I do is to clone the system using Acronis True Image, then convert that image to a VM using the VMWare Standalone Converter. I've had better success with this method personally rather than cloning a live system. (Plus you get the added benefit of having a clone of the server "just in case.") 1 Tabasco OP me again Jan 8, 2013 at 4:43 UTC Cold cloning like Alaerus said might be another option for you to try 0 Ghost Chili OP _Justin_ Jan 8, 2013 at 5:18 UTC I have seen some strange errors like that when trying to convert a machine that is using dynamic disks. 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 trying to convert a machine that is using dynamic disks. Are the drives basic or dynamic? The disks are dynamic...RAID 5 config. As for the drives that I am not sure of, I would assume dynamic because they are on dynamic disk but not sure. How could I tell? As for your error, we