Summary

This Knowledgebase article provides information about an error occuring when converting a physical server to a virtual machine using VMware vCenter Converter.   

More Information

Symptom

• 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 fails
• Converting the C: drive completes successfully, but converting the D: drive fails
• P2V 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: send failed: NFC_NETWORK_ERROR

[05628 warning 'Default'] [,0] [NFC ERROR] NfcFssrvr_IO: failed to send io message

[05628 info 'Default'] [,0] Sysimgbase_DiskLib_Read failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)

[02720 info 'Default'] [,0] Vmount library: Error 2338 while while reading from device

[05340 error 'task-2'] SingleVolumeCloneTask:DoRun: Volume cloning failed with clone error File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId=[CA-8C-48-E9-00-00-10-00-00-00-00-00] and target volume id :,<(849.0000010000000000. Error code: 31

[05340 error 'task-2'] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault

[05340 info 'task-2'] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[CA-8C-48-E9-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-:,<(849.0000010000000000 updates, state: 4, percentage: 0, xfer rate (Bps): <unknown>

[05340 warning 'Default'] [,0] SSL: Unknown SSL Error

[05340 warning 'Default'] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1

[05340 warning 'Default'] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR

[05340 warning 'Default'] [,0] [NFC ERROR] NfcFssrvr_Close: failed to send close message

[05340 warning 'Default'] [,0] SSL: Unknown SSL Error

[05340 warning 'Default'] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1

[05340 warning 'Default'] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR

[05340 info 'task-2'] VolumeBasedCloneTask source computer (unknown name) --> target VM (unknown name) updates, state: 4, percentage: 92, xfer rate (Bps): 12707246

[05340 info 'task-2'] VolumeBasedCloneTask failed

[05340 info 'task-2'] CloneTask updates, state: 4, percentage: 92, xfer rate (Bps): 12707246

[05340 info 'task-2'] CloneTask failed

or:

[03984 warning 'Default'] [,0] * The host certificate chain is incomplee.

[03984 warning 'Default'] [,0] * unable to get local issuer certificate

[03984 info 'Default'] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)

• This issue occurs even if Converter is installed locally on the source machine
• This issue occurs irrespective of whether:
  • The physical machine is converted to the same datastores or different datastores 
  • The drives have been resized or not during the conversion 

Cause

This issue occurs when Converter attempts to access a disk with an expired ticket.

During the reconfiguration task, Converter opens disks on the target machine. When opening the target disks, Converter requests an NFC ticket for each disk on the target machine. NFC ticket is valid only for 60 seconds. During this process, Converter opens one disk at a time. If a disk operation time exceeds 60 seconds, there is a possibility that Converter attempts to access a disk with an expired ticket in which the conversion fails.  

Resolution

This is a known issue affecting VMware vCenter Converter 4.x and VMware vCenter Converter Standalone 4.x/5.x.

To work around this issue, use Converter to convert the physical drives separately, one at a time.

For example

1. Convert the physical C: drive.
2. Convert the physical D: drive.
3. Attach the converted D: drive to the virtual machine which contains the C: drive.
4. Power on the virtual machine.

Applies To

Neverfail IT Continuity Engine v7[.n] and v8.0

Neverfail Continuity Engine v8.1

Related Information

None

KBID-2889