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

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 ?

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

so with this conversion, did you change any of the configuration ?

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.

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

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 ?

when starting the VM that is created I get a windows boot error.

Should I try to reconfigure that newly created VM instance?

Yes,

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.

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

Read fault on OS disk.