Solved

How do I resolve "Unable to update drive letters for the destination volume layout."?

Posted on 2010-09-20
4
5,319 Views
1 Endorsement
Last Modified: 2012-05-10
When using VMWare's vCenter Converter 4.3.0 build 292238 trying to P2V a Windows 2003 SBS server the task fails at 98% with the errors:
Error: An error occurred during reconfiguration.
and
Warning: Unable to update drive letters for the destination volume layout.

The correct Windows Server 2003 SP2 sysprep files are installed to the proper location.
The created Virtual Machine BSOD and reboots. I have attempted using all of the availabile option for a disk controller.
1
Comment
Question by:cberrymd
  • 2
  • 2
4 Comments
 
LVL 22

Expert Comment

by:Luciano Patrão
Comment Utility
Hi

Check this

"Virtual machines created from OVF sources with SCSI LSI Logic disk controller might not start up after conversion to an ESX destination
OVF sources with LSI Logic disk controllers might fail to boot when imported to an ESX destination. This is because Converter Standalone might change the controller type to Bus Logic instead of preserving the source controller type.
Workaround: Using VI client, edit the settings of the imported virtual machine to change the controller type from Bus Logic back to LSI Logic. This will enable the virtual machine to boot."

"Converter places the system boot disk as the first disk on the target virtual machine.
Converter always places the system boot disk as the first disk on the destination virtual machine. The first disk means either the first IDE disk, if the target supports IDE, or the first SCSI disk if the target does not support IDE or if the user explicitly selects a SCSI disk controller for the target machine."

Always check pre and post P2V issues.

Jail
0
 

Author Comment

by:cberrymd
Comment Utility
BestWay:
The converter hadn't changed the disk controller. I attempted to change it to each of the available options but all resulted in the STOP error 7b.
0
 
LVL 22

Expert Comment

by:Luciano Patrão
Comment Utility
Hi

OK have you tried a cold migration? Or is it possible do this on this server? If yes, tried because can fix many of the issues in the P2V

Check this article that i have writed

http://www.experts-exchange.com/Software/VMWare/A_3639-VMware-vConverter-P2V-for-Windows-Servers.html

Jail
0
 

Accepted Solution

by:
cberrymd earned 0 total points
Comment Utility
The boot.ini entry contained the /3GB switch. The P2V was successful after that switch was removed.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now