Unable to update drive letters for the destination volume layout

[Boanna09]

Hello Community!

I try to convert a local System to a virtual one using  VMware vCenter Converter Standalone.

Should be an easy job. But I fail.

I get:

Warning: Unable to update drive letters for the destination volume layout.

Error: An error occurred during reconfiguration.

And then FAILED: A general system error occurred:
Platform-specific error 2.

I already studied the log files – but no success.

Can somebody help me to fix this problem? 

Thanks

Erhard

The logs are attached for your analysis

[POCEH]

These logs are not useful because they are for GUI. Please attach worker's log found in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs

[jagdish_rana]

Hi There,

Did you unistall the unwanted driver from converted Vm and installed the VMtools?

Please keep posted the status.

Thanks

[Boanna09]

Hi Poceh!

Hopefully I uploaded now more useful logs.

Best regards

Erhard

[POCEH]

I see two important errors:

1016 which means "An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry." and

1450 which means "Insufficient system resources exist to complete the requested service."

Your option is to try to 'Reconfig' only your target VM and try to boot it.

Otherwise you need to check your source system for disk errors, for example with 'chkdsk /B'.

HTH

[Boanna09]

Hi PECEH!

Well, I have performed chckdsk and will try again

Can you please provide me some more details:

• which of the logs exactly contain these errors
• how can I 'Reconfig' only the target VM'

I'm not experienced with VW stuff.

Thanks

Erhard

[vijayrana968]

On Source server open registry > go to HKLM>System>MountedDevices. Export 'MountedDevices' and restore it on destination VM then reboot once.

[POCEH]

This is *not* recommended! The VM could not boot if you restore the MountedDevices!

[POCEH]

Instead of choose 'Convert machine', choose the 'Configure machine' and point your newly created VM.

HTH

[IBM_India]

you can follow belew steps

To resolve this issue:

1. Import the virtual machine to vCenter Server.
2. Boot the virtual machine from the correct Microsoft Windows installation media (Correct architecture and version of the operating system).
3. Select the appropriate keyboard layout and language options and click Next.
4. Click Repair your computer.
5. Select the operating system to be repaired and click Next.
6. Click Start > Run, type cmd and click OK.
7. Type bcdedit and press Enter.
8. Under the Windows Boot Manager title with the identifier set to {bootmgr}, you may see that the device is set to boot. Similarly, under the Windows Boot Loader with the identifier set to {default}, you may see that the device and osdevice are set to boot. These items should be set properly for your environment. Usually these appear as partition=C:. In some cases the {default} identifier may have them set to partition=D:.
   
   Run these commands to correct the configuration:
   
   Note: bcdedit is located in this path: c:\windows\system32.
   
   bcdedit /set {bootmgr} device partition=C:
   
   bcdedit /set {default} device partition=C:
   
   bcdedit /set {default} osdevice partition=C:
9. Type exit at the command prompt and select Shutdown.
10. Try to reconfigure using VMware Converter. The reconfigure should now complete successfully. If it fails again, repeat Steps 1 to 7 and then run these commands to set the default device to partition=D::
    
    bcdedit /set {bootmgr} device partition=C:
    
    bcdedit /set {default} device partition=D:
    
    bcdedit /set {default} osdevice partition=D:
    Note: The 😧 partition is used as an example. You can use any available drive letter.

Note: If, after running the preceding bcdedit commands, the virtual machine boots and then fails with a blue screen, perform these steps to resolve the issue:

1. Boot the virtual machine from the Windows 2008 ISO.
2. Load the Recovery Console.
3. Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
4. Click HKEY_LOCAL_MACHINE (HKLM) and then click Menu > File > Load Hive.
5. Browse to C:\Windows\system32\config and select the file SYSTEM.
6. When prompted for a name enter p2v.
7. Locate the key HKLM\p2v\ControlSet001\services\LSI_SAS.
8. Set the value of the start type to REG_DWORD 0.
9. Select HKLM\p2v and click Menu > File > Unload Hive.
10. Close Registry Editor and restart the virtual machine.

For more information, see Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after using VMware....

Note: If your problem persists even after trying the steps in this article, file a support request with VMware Support and note this Knowledge Base article ID (1037507) in the problem description. For more information, see How to Submit a Support Request.

[Boanna09]

Hi all!

Thanks for all your hints.

I tried a lot. But no success till now.

Always the same ugly error messages.

Starting machine. Always Crashes bluescreen evwn in save mode etc etc. Really frustrating.

The bluescreen disappears rather quickly. I can’t catch it

After some days off I will try again or give anopther platform a chance to vitualize my machine.

Best regards

Erhard