P2V windows 2003 R2 64 bit failed Error: Unable to clone volume 'D:'.

[JohnnyLeung]

Hello everyone

Can 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 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, 😧 1.7TB

database: MS SQL 2005 installed by SAP

one concern is the system cannot be shut down during conversion.

many thanks in advance for your help. Thank you.

Johnny

[gparker]

Hi all,

I've just experienced a similar issue, i.e., "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)".

I'm running Converter Standalone v5.1.0 Build 1087880 and when I attempted to P2V a Windows 2003 server with a C: and 😧 drive, the C: drive completed successfully and then it failed as it started the 😧 drive. The speed of the P2V was *EXTREMELY SLOW*, I'm talking 566KB/s!!! After reading through all these posts, I disabled the SSL encryption and that fixed my problem. The physical server I'm converting is a very old Proliant model and I'm thinking that its CPU just couldn't handle the load from the encryption.

Thanks,

George.

[Shelds11]

If disabling SSL doesn't work, try adding a host entry for your destination esx host on your source machine.

Even if you have a correct DNS entry for the machine, create the host entry. This worked for me.

If you look in vmware-converter-worker log file and you see the following error:

GetManagedDiskName: Get disklib file name as vpxa-nfc://[SAN-Name] vmname/vmname.vmdk@ESXHostName.yourdomain.local:

the above fix should help you!

[awmcuq]

"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)".

Not sure if it helps with P2V (my guess it would). I encountered a similar error, differs only type & code numbers, using PC Migration Agent.

Using two slightly different revisions of Migration Agent (both are version 5.1.0), the newer revision did work while the older one didn't (i.e. gave the above error). What VMWare did on the newer revision is to warn user upfront that UAC (on Windows) is turned on and this should be off for the migration (or clone) to be successful.

So if your P2V software doesn't warn you on this, you can manually turn of UAC yourself (for instance on Win 7 you could do as per: Turn User Account Control on or off - Microsoft Windows Help, or Go Regedit -> HLM\Software\Microsoft\Windows\CurrentVersion\Policies\System and set the DWORD 'EnableLUA' to '0')

[brunoscota]

I passed through this today.

I can resolve this making a File-level copy of 😧 drive.

What I discovered after the P2V migration is that in the eventviwer of my physical machine i found this error:

"

Event Type:	Error
Event Source:	VolSnap
Event Category:	None
Event ID:	25
Date:		4/25/2014
Time:		12:42:24 AM
User:		N/A
Computer:	Machine Name

Description:

The shadow copies of volume 😧 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 00 00 00 00 02 00 58 00   ......X.

0008: 00 00 00 00 19 00 06 c0   .......À

0010: 03 00 00 00 00 00 00 00   ........

0018: 01 00 00 00 00 00 00 00   ........

0020: 00 00 00 00 00 00 00 00   ........"

"

So, i saw in my 😧 drive that i had only 4Gb free.

Well, now i will check if i have space available on the drive before to try migrate.

I hope it can helps!

Bye!

[ultraCAO]

This maybe kind of a late reply, but I have found that if you have MSSQL server service running it will give this same error. so before converting, stop any MSSQL services.

[Pska]

REG ADD HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v DisableTaskOffload /t REG_DWORD /d 1

Facing same issue, turn out it was a network problem

Hope it helps anyone, necrothread tho:smileylaugh: