Are there any alternatives to VMWare Converter that we can recommend?
Re: Anyone succesfull with 6.0.0
Re: Unable to obtain hardware information for selected machine
Here are the logs from the Remote Machine.
Re: Converter Job failing trying to copy live system.
Made the changes to the converter-worker.xml file (The KB is for 4 and 5, it doesn't say anything about 6.0) , it only seems to partially work. I can't ssh into the helper machine from anywhere (my Mac, the ESXI host), but it did keep the helper machine from getting deleted after the failure.
attaching a screen shot of the console, which explains why I can't ssh into it, and also has a shell script error in the converter code. I've tried to logon on the console, but it won't let me.
Re: Converter Job failing trying to copy live system.
It works the same way in 6.0. If you have restarted the worker service before starting the conversion, the helper console will let you log in. You might need to strike an 'enter' to let it show the prompt. Eventually try another tty (ctrl+alt+space+f2).
Log in using the credentials you supplied for the conversion, don't be mislead by the password message.
Re: Anyone succesfull with 6.0.0
If you lose a little time to read User's Manual you'll not hit many troubles
Re: Unable to obtain hardware information for selected machine
Log in the source physical machine you want to convert, go to " C:\ProgramData\VMware\VMware vCenter Converter Standalone Agent\logs." and get all vmware-converter-agent-*.log files
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
there was no change after booting the esxi .....
thanks for the hints, but the converted machine is a 2008 r2 server and there is no more boot.ini
and the other KB do not work
i think that this is a general problem with esxi ( converter ?) and running windows 2008 servers
i converted the machine again and took only the C: Drive in the hope that there is a problem with multiple drives
but no change .....
thanks
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
Do you change some parameter(s) of conversion? Do you uncheck the reconfiguration of destination machine?
The only one reason to fail start of VM is to have some specific hardware in source machine and its driver are not removed during clone and could not start in virtual environment.
Could you upload log bundle?
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
What you mean with "no harddrive recognized"? It's obvious that all volumes are recognized properly. Also the data is transferred and just final step reconfiguration probably failed.
You can start resque procedure from CD installation of Win2k8 in VM, hope this will fix boot problems.
HTH
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
i got it running.
i tried a new converting process with creating the disk as "Thick provisioned disk [VM-Volumen]"
that helped to to boot the vm.
now i will test to convert the 2008 server with all disks.
thanks for your help
Re: Converted running Windows 2008 r2 Foundation VM won't boot in ESXi 6.0
Ok but this will not change the content of disks Hope you succeed!
However the rescue procedure seems only one useful step if GOS do not start.
VMWARE Converter standalone 03564 error 'ConversionState'
I try to convert a physical machine, after submitting the job, the converter generates the VM and after that an error occurs: [03564 error 'ConverterWizardWindow'] Next/Finish failed: Ein allgemeiner Systemfehler ist aufgetreten: Server closed connection after 0 response bytes read; <io_obj p:0x0368645c, h:704, <pipe '\\.\pipe\vmware-converter-worker-soap'>, <pipe '\\.\pipe\vmware-converter-worker-soap'>>
I didnt find anything about this error., Enviroment: Converter 6, Vcenter 6, ESXi 6, Machine to convert is SVR 2K3
anyone able to help?... thx
Re: Standardised approach renaming NIC assigning IP across w2k3/w2k8/w2k12
Thanks Poceh! - sorry for such a later reply - things been a little busy.
This is still an open question for me, i have a manual workaround (steps in a work instruction) which is ok for now, but prone to human error.
If i ever find anything out, ill post a reply.
Thanks
BlockLevelVolumeCloneMgr::CloneVolume: Error: 37409 (type: 1, code: 2338)'
Hi all,
This ones got me a little stumped, hoping someone has some more experience.
Source windows 2012 64bit (fresh deployment, test server for newbies in team)
Converter version 6
ESX 5.5
I 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 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::DeleteVM
2015-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.228
2015-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.228
2015-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:\Windows\TEMP\vmware-temp\vmware-SYSTEM\agentTask-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:\Windows\TEMP\vmware-temp\vmware-SYSTEM\agentTask-task-1-vzohlwml.zip".
2015-11-08T02:17:26.931-06:00 error vmware-converter-worker[07764] [Originator@6876 sub=Default] Task failed:
The only clue i can give thus far is that i received an ADMIN$ error when connecting initially, resolved by changing "Turn on network discovery" to on.
There are no other errors in the worker log to give any clues, so far i have tried the following
EDIT: Checked the agent log, found the following.
Will review: VMware KB: Troubleshooting issues when vCenter Converter fails during conversion
Will review 2: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2018582
2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpRead: bRead: -1
2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNet_Recv: requested 264, recevied only 0 bytes
2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcGetMessage: recv failed:
2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_IO: failed to receive io reply
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=Default] Sysimgbase_DiskLib_Write failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06348] [Originator@6876 sub=task-1] TargetVolumeWriter::WriteToVolume(): Error (type: 1, code: 2338) writing 655360 bytes to the destination volume at offset 0x0000000037894000
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06348] [Originator@6876 sub=task-1] Converter::BackgroundWriter::WriteToVolume: Write failed with error 37409.
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::QueueItem: CircularBuffer AddItem error, destroy workItem!
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] 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)
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=task-1] BackgroundWriter::ThreadFunc: Broadcasting "ThreadDone" condition.
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=ThreadPool] Thread delisted
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] BlockLevelVolumeCloneMgr::CloneVolume: failed with exception 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)
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] ScopedBackgroundWriter::~ScopedBackgroundWriter: Error in ReleaseBackgroundWriter 37409.
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] [StreamCacheWriter] - TotalZeros : 0, TotalWrites : 1331
-->
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] SingleVolumeCloneTask:DoRun: Volume cloning failed with clone 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)
2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault
2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-3)=-;5;00000010000000000 updates, state: 4, percentage: 3, xfer rate (Bps): 47286047
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CompositeTask canceling #2 subtasks
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] TaskImpl issuing Cancel command
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-3)=-;5;00000010000000000 updates, state: 4, percentage: 3, xfer rate (Bps): 47286047
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] TaskImpl issuing Cancel command
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[09-7B-3F-8E-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-90;7?3>(0000010000000000 updates, state: 0, percentage: 0, xfer rate (Bps): <unknown>
2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_Close: failed to send close message
2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] VolumeBasedCloneTask source computer (unknown name) --> target VM (unknown name) updates, state: 4, percentage: 3, xfer rate (Bps): 47286047
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] VolumeBasedCloneTask failed
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CloneTask updates, state: 4, percentage: 3, xfer rate (Bps): 47286047
2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CloneTask failed
2015-11-08T02:16:48.750-06:00 error vmware-converter-agent[04340] [Originator@6876 sub=Default] Task failed:
Actions
- Rerun job a couple more times - failed
- Convert only C:\ - failed
- Run Check disk /R on C:\ - failed
Points to consider.
- Next step would be to install converter locally but i want to avoid this for now.
- No workarounds to be deployed, i.e. use acronis - must be able to proceed with converter alone
- Normally a checkdisk resolves this issue for me.
Question: What other things can cause the following errorBlockLevelVolumeCloneMgr::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)'
Re: BlockLevelVolumeCloneMgr::CloneVolume: Error: 37409 (type: 1, code: 2338)'
Is this error consistently arrive? Seems like network drop which is interpreted as bad write and conversion terminates.
Please do not post logs - if you want to check them - simply attach them.
Re: RDM disk conversion using vconverter
hi Poceh,
i can see the RDM disk and able to choose to export it as thick when i went through the vconverter wizard.
But when the conversion starts, the task fails at 1 % with File IO error.
Saw this in vmware-converter-worker
Disk number 1 has been skipped because of errors while reading partition table
Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
Re: RDM disk conversion using vconverter
Could you upload log bundle?
Re: VMWARE Converter standalone 03564 error 'ConversionState'
Hello
Please upload the logs files. Since the error probably occurred before creating a job, you may need to find them in "%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\logs".
Regards,
Plamen
Re: vmware converter without infrastructure server?
Guys!
Any update on this? Any possible workaround.
I have same issue I tried converter 6 and 5 as well with client alone and client-server both mode.
But getting same issue.