Hello
Worker logs look strange. They both stop abruptly after
2013-09-06T20:46:31.559-04:00 [04168 info 'Default'] [PopulateVolumeProperties] volume \\?\Volume{96d0b74a-f562-11e2-810a-005056c00008}\ corresponds to \Device\TrueCryptVolumeP device name.
2013-09-06T20:46:31.562-04:00 [04168 info 'Default'] [GetDriveLetterOrMountPoint] Mount point for volume \\?\Volume{96d0b74a-f562-11e2-810a-005056c00008}\ is P:
This looks like a service crash. Can you check if that's the case? (e.g. in the event viewer). If so, I'd suggest you set the logging level to verbose (see VMware KB: Increasing the logging levels to verbose for vCenter Converter application components ) and attach the new log again for further investigation.
The P: volume seems encrypted ("corresponds to \Device\TrueCryptVolumeP device name"). Perhaps there is something specific in it that has cause the service to crash?
You may alternatively try to bring that volume's disk offline (if possible) and attempt conversion again. But even if that workaround succeeds, I would still ask for the verbose log in order to investigate the crash.
Regards,
Plamen