• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5985
  • Last Modified:

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

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
cberrymd
Asked:
cberrymd
  • 2
  • 2
1 Solution
 
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
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
 
cberrymdAuthor Commented:
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
 
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
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
 
cberrymdAuthor Commented:
The boot.ini entry contained the /3GB switch. The P2V was successful after that switch was removed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now