5 Replies Latest reply on Sep 19, 2017 1:21 PM by ateja90

    Conversion fails at 98% and VM fails to start

    ateja90 Lurker

      Hi,

       

      I'm having an issue converting a Windows 7 machine to a virtual machine running on VMWare ESXi 6.0. I'm using vCenter Converter 6.1.1.

       

      The conversion stops at 98% with an "Internal error." I can see the VM has been created on the ESXi server, but when attempting to start the VM, it goes into a boot loop failing at the "Starting Windows" logo, so I'm thinking it has something to do the configuration after the conversion. This is what I see in the vmware-converter-server log around the time of the failure:

       

      2017-08-23T13:04:55.318-05:00 info vmware-converter-server[04188] [Originator@6876 sub=Default] Started task "task-4" for job="job-4", item ="3" -- void __thiscall Converter::Server::Job::JobProcessorImpl::StartProcessingJobs(void) ("d:/build/ob/bora-3533064/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:384")

      2017-08-23T13:04:55.370-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [task,338] [task-4] -- BEGIN -- Convert

      2017-08-23T13:04:55.387-05:00 info vmware-converter-server[03984] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded

      2017-08-23T13:04:55.391-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [taskSpec,618] [task-4] [TaskMap] task-4:task-7

      2017-08-23T13:24:50.751-05:00 error vmware-converter-server[03848] [Originator@6876 sub=Ufa.HTTPService] Failed to read request; stream: <io_obj p:0x040e75c4, h:-1, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, error: class Vmacore::TimeoutException(Operation timed out)

      2017-08-23T13:24:55.751-05:00 error vmware-converter-server[04000] [Originator@6876 sub=Ufa.HTTPService] Failed to read request; stream: <io_obj p:0x03f67894, h:-1, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, error: class Vmacore::TimeoutException(Operation timed out)

      2017-08-23T14:46:34.235-05:00 error vmware-converter-server[01944] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError

      2017-08-23T14:46:34.284-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [task,379] [task-4] -- ERROR -- Convert: vmodl.fault.SystemError

      --> (vmodl.fault.SystemError) {

      -->    faultCause = (vmodl.MethodFault) null,

      -->    reason = "InternalError",

      -->    msg = ""

      --> }

      2017-08-23T14:46:34.284-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [diagnosticManager,260] Retrieved taskInfo for "converter.task.Task:task-4" mapping it to "converter.task.Task:task-4".

      2017-08-23T14:46:34.284-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [diagnosticManager,300] The task with id = "task-4" was found to be a "recent" task.

      2017-08-23T14:46:34.284-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [diagnosticManager,314] No existing log bundle found for task with id = "task-4". The task is still "recent" so a log bundle will now be generated for it.

      2017-08-23T14:46:34.295-05:00 info vmware-converter-server[01944] [Originator@6876 sub=Default] [diagnosticManager,1092] Retrieving task related diagnostics for server task with id = "task-4".

      2017-08-23T14:46:34.431-05:00 info vmware-converter-server[04184] [Originator@6876 sub=Default] Run 0 of job "job-4" finished with an error. -- struct Converter::Server::Job::JobExecutor::SchedulerUpdateSpec __thiscall Converter::Server::Conversion::ConversionJobExecutorImpl::UpdateJob(class Converter::Server::Job::InternalJob &,bool,const class Converter::Server::Scheduler::SchedulerItemStatistics &,const class Converter::Task::TaskInfo &) ("d:/build/ob/bora-3533064/bora/sysimage/lib/converter/server/conversion/conversionJobExecutorImpl.cpp:405")

      2017-08-23T14:46:34.523-05:00 info vmware-converter-server[04184] [Originator@6876 sub=Default] Suspended 1 scheduler items for job (job-4) -- void __thiscall Converter::Server::Job::JobProcessorImpl::SuspendJobAux(const class Converter::Server::Job::InternalJob &,class Converter::VdbConnection &) ("d:/build/ob/bora-3533064/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:829")

       

      I've attached that log as well as the ConverterDiag log. I'm thinking the "faultCause = (vmodl.MethodFault) null, reason - "Internal error" " is somehow related the "Failed to read request" and "Vmacore::TimeoutException" error message, but I'm not 100% sure. I've been trying to research this issue, but cannot find anything in Google to resolve this issue.

       

      I have tried using SCSI LSI Logic as well as SATA (which is what is in the machine) to no avail.

       

      Any help would be GREATLY appreciated! Thank you very much!

        • 1. Re: Conversion fails at 98% and VM fails to start
          msripada Expert
          vExpert

          from the logs uploaded,

           

           

          -->

          2017-08-23T13:04:53.021-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading partition table

          2017-08-23T13:04:53.021-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

          2017-08-23T13:04:53.022-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176

          2017-08-23T13:04:53.704-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] Partition:Invalid sector magic number.

          2017-08-23T13:04:53.705-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] Partition:Invalid sector magic number.

          2017-08-23T13:04:53.705-05:00 info vmware-converter-worker[01204] [Originator@6876 sub=Default] Reusing existing VIM connection to 10.30.1.12

          2017-08-23T13:04:53.709-05:00 warning vmware-converter-worker[01204] [Originator@6876 sub=Default] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>

          2017-08-23T13:04:53.709-05:00 info vmware-converter-worker[01204] [Originator@6876 sub=Default] [LogMessagesForQA] System volume is not detected.

          2017-08-23T13:04:53.709-05:00 info vmware-converter-worker[01204] [Originator@6876 sub=Default] [BaseComputerImpl::Open] Config file: [ds1] VM name-p00/VM name-p00.vmx (modified VM name)

           

          similar issue is discussed on the community earlier and looks to be a dns issue...hope this helps

           

          Converter 5.1 - error 2338

           

          Thanks,

          MS

          • 2. Re: Conversion fails at 98% and VM fails to start
            ateja90 Lurker

            Thank you for your response msripada.

             

            I'm not sure if it is a DNS issue because the VM gets created in the destination machine. I will give this a shot and provide an update though.

             

            Thanks!

            Abhishek

            • 3. Re: Conversion fails at 98% and VM fails to start
              continuum Guru
              Community WarriorsvExpertUser Moderators

              The VM is already bootable so this is definetely no DNS-problem.
              Run Converter "confgure machine" again.
              If that does not help - boot into recovery mode , load the system hive and set the boot parameter of LSI-SAS service to 0 manually.

              • 4. Re: Conversion fails at 98% and VM fails to start
                ateja90 Lurker

                To follow up on this, here was my final solution:

                - Install Disk2VHD on the physical box

                - Copy the .vhdx to my system

                - Use Starwind V2V converter to convert the .vhdx to a .vmdk

                - Create a new VM with the .vmdk file

                 

                All of the software I used was free and the process itself was painless! I wasn't able to find the ultimate reason for the failure.

                • 5. Re: Conversion fails at 98% and VM fails to start
                  ateja90 Lurker

                  Hi Continuum,

                   

                  I did try these out before I eventually performed the workaround I posted.

                   

                  Thank you for your input!