1 2 Previous Next 20 Replies Latest reply on Dec 13, 2018 4:02 AM by coco666 Go to original post
      • 15. Re: FAILED: Unable to obtain the lock on virtual disks
        goldeneye*007 Enthusiast

        I believe the issue to be in this instance, the motherboard chipset is nVidia nForce.

        The converter software is not able to retrieve complete disk information which may be

        a Windows issue. nForce is not a supported Windows 10 chipset, but a machine so

        upgraded will continue to function using the previously installed chipset drivers.

        I have seen other disk related issues surrounding nForce machines updated to Windows 10.

         

        This is what I am seeing in the log.

         

        2018-02-14T16:15:59.265-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Parsing \\Vm1\u\demo1\demo1.vmx
        2018-02-14T16:15:59.281-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [BaseDiskSetComputer::OpenDiskSet] Will use open retries count 3
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading partition table
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] [PopulateCapabilities] Volume-based cloning was disabled due to: <no volumes are recognized>
        2018-02-14T16:15:59.314-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [LogMessagesForQA] System volume is not detected.
        2018-02-14T16:15:59.314-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] [BaseComputerImpl::Open] Config file: \\Vm1\u\demo1\demo1.vmx
        2018-02-14T16:15:59.314-05:00 warning vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition:Invalid sector magic number.
        2018-02-14T16:15:59.316-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ---------------------------
        2018-02-14T16:15:59.316-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ....Creating MBR Partition Table ....
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ..... Partition Entry: 0 .....
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] .....Current Partition Offset 0: .....
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Boot Indicator: 0X80
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Partition Type Id 0X7
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Head 32
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Sector 33
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Starting Cylinder 0
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Head 45
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Sector 63
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Ending Cylinder 1023
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Relative Sectors 2048
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] ...Total Sectors 124119040
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] --------------------------
        2018-02-14T16:15:59.317-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition 0: offset: 0
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk signature found 489802585, disk size in sectors 124125184, sector size 512
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Partition found type HPFS/NTFS(7) name:HPFS/NTFS start:2048 size:124119040 attribs:0x0 active primary 
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Disk with signature 489802585, recognized partitions 1
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] TargetVmManagerImpl::PartitionTargetDisks: Target Disk Id: disk-5
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] TargetVmManagerImpl::PartitionTargetDisks: Source volume Id: \WindowsBitmapDriverVolumeId=[59-CB-31-1D-00-00-10-00-00-00-00-00] Target Volume Id: 95;,13=10000010000000000
        2018-02-14T16:15:59.320-05:00 info vmware-converter-worker[07292] [Originator@6876 sub=ThreadPool] Thread enlisted
        2018-02-14T16:15:59.322-05:00 info vmware-converter-worker[03864] [Originator@6876 sub=Default] Scheduled timer canceled, StopKeepAlive succeeds
        2018-02-14T16:15:59.391-05:00 info vmware-converter-worker[03856] [Originator@6876 sub=Default] Stopped impersonating in session 52b8335a-5624-fccb-77e6-f9ab9d4dfed8
        2018-02-14T16:15:59.391-05:00 info vmware-converter-worker[03856] [Originator@6876 sub=Default] Session is closing, releasing cached session objects

        • 16. Re: FAILED: Unable to obtain the lock on virtual disks
          50chickens Lurker

          this maybe a solution for some people. i installed the converter on a physical server. when writing the image out to a local disk it all worked ok, but when i specified the target as a unc path (eg \\server\share) i got the 'unable to obtain lock on virtual disk' error. eventually i found the solution as changing the vmware converter server and worker services to run under a domain account that had permissions to the unc share and path (eg, permissions on the share, and permissions on the filesystem on that share) rather than localsystem. once i did that the export worked fine.

           

          the odd part is if you run the converter on a third party (eg your workstation) and then try and convert a remote machine, it asks you for credentials that have access to the remote share. this does not work (in my case). i think it's because the kerberos delegation is not enabled on the AD object for the target computer account so the account you specified cannot be impersonated.

          • 17. Re: FAILED: Unable to obtain the lock on virtual disks
            heapik Lurker

            Hi,

            I have the same issue, trying to convert phy machine to remote location which is smb share ... I have mounted the share as VM_Conv_SA user... but its still failing with error Unable to obtain the lock on virtual drive. I do not use AD. Is this normal? why you are not providing what users are required to that .. this is pretty solid stupidity of VMware to provide a software for a conversion which is partially black box or doesn't work.

            • 18. Re: FAILED: Unable to obtain the lock on virtual disks
              VASILIS1977 Lurker

              I had the same problem..i chose from the options in vcenter the virtual hdd as pre-alocated and now the conversion has started. My problem solved but error again at 98%

               

              https://prnt.sc/ixi4jb

              • 19. Re: FAILED: Unable to obtain the lock on virtual disks
                fgerber Lurker

                I set the permission on the destination-share to everyone-full access and then it worked.

                • 20. Re: FAILED: Unable to obtain the lock on virtual disks
                  coco666 Lurker

                  Run VMware Vcenter Converter like Administrator. Run -> as-> Administrator.

                  1 2 Previous Next