VM Ware Converter Error: Warning: Unable to update drive letters for the destination volume layout.

I have been able to P2V quite a few machines but for some reason this particular server is not going thru the process.

I was wondering if anyone had encounter this prior and could suggest a solution or work around.

The VM will not start manually. I tried that just to see what would happen.
converter-gui-50.log
armgonAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Manual conversion may be possible using Ultimate P2V
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What is the OS ?

what type of volume types ?

have you changed ANY of the configuration in the P2V process, e.g. just accept the Defaults ?
0
 
armgonAuthor Commented:
What is the OS ?

--Windows 2008 Server - Standard - 64bit

What type of volume types ?
-- The destination: SCSI LSI Logic SAS Disk Controllers with RAID 5 all SSD

Source is NTFS , c: Drive is Qty 2 of 232.83GB  HDD mirror

have you changed ANY of the configuration in the P2V process, e.g. just accept the Defaults ?
--For most machines i have converted in the past I normally keep standard configurations. Put I have some which I have altered the processors, memory, and disk provisioning sizes to smaller disk as well as switching them to Thin Disk. No issues with any of those.

Also, most of the other machines have had multiple HDD, no issues as well.

Any pointers you can give me would be greatly appreciated
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
so with this conversion, did you change any of the configuration ?
0
 
armgonAuthor Commented:
Negative. No Changes.

Even left the Thick Provision Disk.

Is there a tool out there to analyze the crazy error log files produced by the converter utility. Perhaps is something I need to remove from the source, like a corrupted file.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is there a tool out there to analyze the crazy error log files produced by the converter utility. Perhaps is something I need to remove from the source, like a corrupted file.

there are no tools.

I'll have a look at the log..

"Whether you are a VMware vSphere Beginner, Intermediate, Advanced or Expert, Physical to Virtual conversions sometimes are not easy, and many issues can arise, a successful conversion requires 50% technical knowledge, 25% patience and  25% luck to get a successful conversion. Sometimes it is not as simple, as install VMware vCenter Converter Standalone, and click next to obtain a successful conversion."

from my EE Article

HOW TO: FAQ VMware P2V Troubleshooting
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
did you try a Reconfigure Machine task, on the newly converted VM ?

e.g. click Configure Machine ....

and despite the error message you have tried to start the VM that's been created ?
0
 
armgonAuthor Commented:
when starting the VM that is created I get a windows boot error.

Should I try to reconfigure that newly created VM instance?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes,
0
 
armgonAuthor Commented:
No luck.

I remove Symantec Endpoint , just a thought that perhaps there is something within the configuration for Endpoint on this Server that was causing issues.

I restarted the conversion.

I am seeing this error:
FAILED: An error occurred during the conversion: 'converter.fault.FileIOFault' now.

We are not experiencing any kind of other problems with the server when used as a regular Physical Server.

What could be going on here.
0
 
armgonAuthor Commented:
I ran the following command prompt utility:

SFC /scannow

it found corrupted files that could not be be fixed. See attached log. Could this be part of the problem?
CBS.log
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Read fault on OS disk.
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.

All Courses

From novice to tech pro — start learning today.