I am getting the above error when try to convert (import) a physical Windows 2003 server into ESX3.
I've been through these forums, but there seems to be little advice other than it doesn't work with software RAID, which I'm not running, or complex boot.ini which I also don't have.
The following all fail with the exact same message:
Running converter remotely from the VIC host.
Running converter locally
Booting from the Converter boot CD
It fails when I click next after chosing the remote or local machine to import.
The hard drives are SCSI Raid1 hardware mirrors on an LSI SAS 3000 Series, partitioned into 2 partitions within Windows.
The relevant log files are below
boot.ini
redirect=UseBiosSettings
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect /redirect
c:\windows\temp\Vmware-converter.log
5 2007-11-28 18:37:03.684 'App' 1476 verbose attachedComputerWin32,464 Found volume with name "
?\Volume{1ca0bfe1-126d-11db-a6ce-806e6f6e6963}\"
5 2007-11-28 18:37:03.684 'App' 1476 verbose attachedComputerWin32,464 Found volume with name "
?\Volume{1ca0bfe3-126d-11db-a6ce-806e6f6e6963}\"
5 2007-11-28 18:37:03.684 'App' 1476 verbose attachedComputerWin32,464 Found volume with name "
?\Volume{3a8b24c5-1315-11db-a3e1-806e6f6e6963}\"
5 2007-11-28 18:37:03.684 'App' 1476 verbose attachedComputerWin32,464 Found volume with name "
?\Volume{3a8b24c7-1315-11db-a3e1-806e6f6e6963}\"
5 2007-11-28 18:37:03.684 'App' 1476 verbose attachedComputerWin32,464 Found volume with name "
?\Volume{866a1fea-1bcf-11db-878f-00144f29d07b}\"
5 2007-11-28 18:37:03.699 'App' 1476 warning attachedComputerWin32,579 GetVolumesForComputer Windisk_GetVolumeDiskExtents failed with error 1
5 2007-11-28 18:37:03.730 'App' 1476 warning attachedComputerWin32,579 GetVolumesForComputer Windisk_GetVolumeDiskExtents failed with error 50
5 2007-11-28 18:37:03.824 'App' 1476 warning attachedComputerWin32,579 GetVolumesForComputer Windisk_GetVolumeDiskExtents failed with error 50
?? 2007-11-28 18:37:04.246 'App' 3176 info stub,42 error Windisk_GetVolumePartitionInfoFailed to get
.\Volume{866a1fea-1bcf-11db-878f-00144f29d07b} Volume's partition info: The request is not supported (50)
5 2007-11-28 18:37:04.246 'App' 1476 info attachedComputerWin32,162 GetVolumeInfo Cannot get
?\Volume{866a1fea-1bcf-11db-878f-00144f29d07b}\ volume's legacy partition info. The partition number is 35164769
5 2007-11-28 18:37:04.465 'App' 1476 verbose disposable,122 object explicitly disposed: computer= 5 2007-11-28 18:37:04.465 'App' 1476 verbose diskSet,119 Cleaning up computer's child objects 5 2007-11-28 18:37:04.465 'App' 1476 verbose diskSet,135 Unregistring volume id=attVol={computer=,1}
5 2007-11-28 18:37:04.465 'App' 1476 verbose diskSet,135 Unregistring volume id=attVol={computer={8d56326b536472341b75b4f61b479869dbeb1967},2}
5 2007-11-28 18:37:04.465 'App' 1476 verbose diskSet,145 Unregistring disk id=disk=
5 2007-11-28 18:37:04.465 'App' 3412 error client,164 Rethrowing MethodFault sysimage.fault.PlatformError:
5 2007-11-28 18:37:04.465 'App' 6120 error importSource,357 Unable to read OS info from system disk: sysimage.fault.PlatformError
5 2007-11-28 18:37:04.465 'App' 6120 error imageProcessingTaskImpl,552 VmiQuerySourceInfoTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.UnableToDetermineGuestOs 5 2007-11-28 18:37:04.465 'App' 6120 verbose imageProcessingTaskImpl,154 VmiQuerySourceInfoTask::task: SetState to error
5 2007-11-28 18:37:04.512 'App' 6120 verbose disposable,122 object explicitly disposed: VmiQuerySourceInfoTask::task 5 2007-11-28 18:37:04.512 'App' 6120 verbose imageProcessingTaskImpl,123 VmiQuerySourceInfoTask::task being destroyed
2007-11-28 18:38:41.086 'App' 3412 verbose CloseSession called for session id=7B528158-A86E-44F0-9310-25D0FDBF078E
2007-11-28 18:38:41.086 'VmdbAdapter' 3412 verbose Removed vmdb connection /db/connection/#5/
C:\Documents and Settings\Administrator\Local Settings\Temp\2\vmware-temp
2007-11-28 18:40:42.458 'App' 4416 verbose imageProcessingTaskWrapper,109 Successfully connected to VmiQuerySourceInfoTask::task 2007-11-28 18:40:42.473 'App' 4416 verbose imageProcessingTaskWrapper,817 Start managed object method for task VmiQuerySourceInfoTask::task
2007-11-28 18:40:42.473 'App' 4416 verbose imageProcessingTaskWrapper,437 Waiting for updates from VmiQuerySourceInfoTask::task 2007-11-28 18:40:42.473 'App' 4416 verbose imageProcessingTaskWrapper,668 (Re)Start waiting for property updates from VmiQuerySourceInfoTask::task
2007-11-28 18:40:42.473 'App' 4440 verbose imageProcessingTaskWrapper,749 Got an update from VmiQuerySourceInfoTask::task 2007-11-28 18:40:42.489 'App' 4416 verbose imageProcessingTaskWrapper,437 Waiting for updates from VmiQuerySourceInfoTask::task
2007-11-28 18:40:42.489 'App' 4416 verbose imageProcessingTaskWrapper,668 (Re)Start waiting for property updates from VmiQuerySourceInfoTask::task 2007-11-28 18:40:43.271 'App' 4440 verbose imageProcessingTaskWrapper,886 Remote task VmiQuerySourceInfoTask::task completed
2007-11-28 18:40:43.271 'App' 2704 verbose imageProcessingTaskWrapper,749 Got an update from VmiQuerySourceInfoTask::task 2007-11-28 18:40:43.286 'App' 4416 verbose imageProcessingTaskWrapper,515 Cleaning up remote task VmiQuerySourceInfoTask::task
2007-11-28 18:40:43.302 'App' 4416 verbose imageProcessingTaskWrapper,1201 Disposing task wrapper for task VmiQuerySourceInfoTask::task
2007-11-28 18:40:43.333 'P2V' 4416 error task,295 Task failed: P2VError UNABLE_TO_DETERMINE_GUEST_OS()
2007-11-28 18:40:43.333 'P2V' 4416 verbose task,339 Transition from InProgress to Failure requested
2007-11-28 18:40:43.333 'P2V' 4416 verbose task,388 Transition succeeded
Does anyone have any ideas as to what is causing this, it's very frustrating!
This turned out to be a problem with Suns Virtual floppy drivers that the slimline sun servers use for remote floppy and CD.
After speaking to VMWare technical support, they removed the floppy from the "add/remove hardware" within windows and it seems to have fixed the problem.
[edit, orignally put "Sun technical support" above by mistake, meant VMWare]
This is a known issue for IBM blades as they use a central media center. http://kb.vmware.com/kb/1000508
Thanks for updating the post.