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, D: 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

[MKguy]

"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

[JohnnyLeung]

1. Is C:\ it's own disk or are C:\ and D:\ 2 partitions on the same physical disk/array?

-->they are on same physical disk/array

2. D:\ is not a Windows dynamic disk, right?

--> it is MBR disk only

3. Are you resizing the disks during conversion?

--> I did not resize it, just selected thin provisioning

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.

-->yes, it is 8MBS VMFS block size

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.

--> it has enough space

[Rosen Tomov]

There is network error when second disk cone is started:

[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcNetTcpRead: bRead: -1
[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcFssrvrRecv: failed with code = 8
[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcFssrvr_DDBSet: failed to receive reply, error = 8
[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcFssrvrSend: failed
[2012-11-19 13:08:59.703 09456 warning 'App'] [,0] [NFC ERROR] NfcFssrvr_IO: failed to send io message
[2012-11-19 13:08:59.703 09456 error 'task-1'] TargetVolumeWriter::WriteToVolume(): Error (type: 1, code: 2338) writing 303104 bytes to the destination volume at offset 0x0000000000000000

You can try to convert disks separately i.e. in 2 different conversions.

[JohnnyLeung]

re POCEH

how can i solve this problem, i can select only c: single drive, but cannot select only d:

Johnny

[Rosen Tomov]

The Converter 5.0.x allows to deselect system/bootable disk C:

So you need one conversion for disk D: (don't warry fail at reconfig task) and one conversion for disk C:, then simply add disk D: to VM with disk C: (don't forget to move VMDK file within 'real' machine folder, then delete the first 'fake' VM).

HTH

[JohnnyLeung]

I tried the converter 5.0.1, but it doesnot help, it was super slow and not likely can be finish. when i was using converter version 4.3, drive C can be finish in 2 hrs, but while using 5.0.1, it cannot finish after 10hrs.

Do you have any other idea to solve this?

[MKguy]

Converter 5.x uses SSL encryption to secure the traffic from source to destination which can result in slow conversions.

Set the Config/nfc/useSsl option to false in converter-worker.xml, then restart the VMware vCenter Converter Standalone Worker service and try converting again.

See:

http://communities.vmware.com/message/1854580

[Rosen Tomov]

You can resolve speed issue with Converter 5 disabling SSL connection.

In the same section in converter-worker.xml you can try to increase Nfc timeouts, especially fssrvr ones (but this is wild guest, I can't offer any concrete value).

HTH

[continuum]

cant you use robocopy for drive D: ?

[JohnnyLeung]

robocopy is not possible, since both physical and virtual cannot online at the sametime.

I justed disabled the SSL and trying to p2v again 2 dirves separately. clone 2 drives together also failed.

[continuum]

> robocopy is not possible, since both physical and virtual cannot online at the sametime.

To robocopy into a vmdk you can just use any other VM you already have - no need to have source and target up at the same time

[JohnnyLeung]

can you provide detail steps? thanks a lot.

[continuum]

assume
host 1 = your p2v source - has two drives C:\ and D:\
VM 1 = the result of your Converter import with only drive C:\ - VM lives in dir1 on the datastore
VM 2 = thats an already existing VM of the same guestOS type - it already has one vmdk used as C:\ - VM lives in dir2 on the datastore

--------------------------------------------------------------------------------------

1. add new vmdk to VM1 - this will be the future D:\ - do not start VM1
2. assign the new blank vmdk to VM2 , start the VM2 and partition and format the new vmdk as needed
3. create a Windows-share using the whole new vmd

4. go to host1 and connect to the Windows-share of VM2 - assign driveletter E:
5. run robocopy d: e: /MIR

that maybe even faster than the Converter  - and is very reliable - as it can be restarted after network dropouts

[JohnnyLeung]

i will find another VM with same OS and try use robocopy method.

but what will be the steps after robocopy? how to add it back to the VM1?

[JohnnyLeung]

it does not work with convert D drive seperately, C dirve can complete while D drive was failed

see attached log

error message: FAILED: An error occurred during the conversion:
'converter.fault.FileIOFault'

[Rosen Tomov]

The error is:

2012-11-21T22:03:01.911+08:00 [07844 error 'task-5'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Unrecoverable error (type: 2, code: 2) reading 655360 bytes starting from 0x000001ae20a92000 from the source volume D:
You need to run chkdsk with  /R (Locates bad sectors) option on your D: disk.

[JohnnyLeung]

i did chkdsk on drice D before, not likely can help, any other suggestion? thanks.

[continuum]

Did you run chkdsk d: /f /x /r ?

If you used other parameters or none at all - that was useless.

[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:

[brunoscota]

I passed through this today.

I can resolve this making a File-level copy of D: 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 D: 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 D: 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!

[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 D: drive, the C: drive completed successfully and then it failed as it started the D: 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 then 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.

[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 D: drive, the C: drive completed successfully and then it failed as it started the D: 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/[e-mail]:

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')

[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.