Hi, I'm on my 7th attempt at converting my second windows 2000 Advanced Server with latest converter 3.0.1 and consistently getting the error (see full log attached):
Image processing task has failed with MethodFault::Exception: sysimage.fault.OsVersionNotFound
I tried some of the usual tricks (the ones that worked on the 16th attempt for my first W2K server) including just convert C: and slightly reduce destination size to force a filewise clone (failed 97%)
In each case I end up with a VM on my ESX 3.0.2 server, but it Bluescreens on boot with "unable to find boot device"
thanks for any info/tips,
Fletcher
Try this:
1) mount the vmdk file for the vm that is blue screening to another virtual machine in ESX as a secondary drive
2) check the boot.ini on the virtual machine that is blue screening
3) make sure that it is pointing to partition (1), if it needs to be changed, then change it and save it
4) umount the vmdk file from the virtual machine
5) In VMware Converter, run configure virtual machine on the virtual machine that was blue screening
6) Once the reconfiguration finished, turn on the virtual machine
Does it still blue screen?
If so then you will have to do a windows install/repair.
Ok, how do I accomplish step #1 (mount the vmdk file for the vm that is blue screening to another virtual machine in ESX as a secondary drive)?
thanks
Ok, I mounted the drive via the VI Client (Right click another windows VM -> Edit Settings, Add..., Hard Disk, Next, Browse to problem (97%) image, open, rescan HW in Windows VM, explorer picks up C,D as E,F in VM)
I opened E:\boot.ini - it listed
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect
the original physical machine's boot.ini listed partition 2:
timeout=3
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect
I tried updating the boot.ini on the 97% VM to be like the original VM, and following your next step to reconfigure with converter - but it errors out "unable to determine guest OS"
ideas?
thanks
The EISA partition may be causing these issues - I am explicitly deselecting it on this next converter attempt.
You did the right thing by adding the vmdk file as a secondary drive. You do not need to mount it any other way in your case.
You will need to deselect the EISA partition during the conversion and make sure your boot.ini is pointing to partition (1).
Please let me know how this turns out for you.
I deselected the EISA partition, but same error
What I don't understand are these log messages - the first part seems to recognize the OS, then it looks again and fails - why is it doing that?
Associating disposable session object id=localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\boot.ini} with session id=037C9255-02AD-4FD1-BB73-DCBC483CF03B
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect
object explicitly disposed: localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\boot.ini}
SwagNTInfoFromString has Microsoft Windows 2000 Advanced Server
Returning OS as display Microsoft Windows 2000 Advanced Server
Found a candidate system volume at idx=0
OS resides on partition 1 , disk path ostinato093007/ostinato093007.vmdk
Registering disposable session object id=localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\boot.ini}
Associating disposable session object id=localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\boot.ini} with session id=037C9255-02AD-4FD1-BB73-DCBC483CF03B
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect
object explicitly disposed: localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\boot.ini}
Registering disposable session object id=fileRegistry={virtVol={computer={a0f2cb82af8c1f1b23306aa9575ef7cbcb0e2d6c},0}},WINNT\system32\config\SYSTEM
Associating disposable session object id=fileRegistry={virtVol={computer={a0f2cb82af8c1f1b23306aa9575ef7cbcb0e2d6c},0}},WINNT\system32\config\SYSTEM with session id=037C9255-02AD-4FD1-BB73-DCBC483CF03B
object explicitly disposed: fileRegistry={virtVol={computer={a0f2cb82af8c1f1b23306aa9575ef7cbcb0e2d6c},0}},WINNT\system32\config\SYSTEM
Getting extended OS info by parsing boot.ini and/or analyzing the registry failed
Registering disposable session object id=localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\msdos.sys}
Associating disposable session object id=localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\msdos.sys} with session id=037C9255-02AD-4FD1-BB73-DCBC483CF03B
object explicitly disposed: localFile={
.\vstor2-p2v30-80000000007E0000000000002C000000\msdos.sys}
msdos.sys is non-existent or inaccessible
FAILED parsing NTFS or Win9x_DOS partition
Unable to read OS info from system disk: sysimage.fault.OsVersionNotFound
object explicitly disposed: computer= Cleaning up computer's child objects Unregistring volume id=virtVol={computer=,0}
Unregistring volume id=virtVol={computer={a0f2cb82af8c1f1b23306aa9575ef7cbcb0e2d6c},1}
VmiQuerySourceInfoTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.UnableToDetermineGuestOs VmiQuerySourceInfoTask::task: SetState to error
Have you checked the boot.ini now that you did not select the EISA partition?
Make sure it is set to partition (1).
Once it has been set to partition (1), then run "Configure Machine" from Converter. Now boot up the machine and see if it boots up or not.
If it does not boot up then please attach (not post) the error message (blue screen) and the log files from Converter (File -> Export Logs).
Yes, the boot.ini references partition 1 correctly
When I attempt to open the VM with connverter to "configure" I get a similar error while "retrieving OS information":
"Unable to determine guest OS" (but you'll note in the logs it previously determines the OS correctly to be Windows 2000 Server)
Attached the exported logs as requested
Many thanks for any info - I have had a SR open in this since last week - this forum has been much more responsive so far
thanks
Fletch.
If you don't mind me asking, what is the support request number?
I can look into this for you.
I'm happy to report vmware support came through within 5 mins of my previous post I received a call a we were debugging via webex.
within 3 hours I had a new working VM.
We did these things:
1) applied the pending windows 2000 patches and rebooted the host to be converted
2) installed converter 3.0.1 on a helper VM (previously I was running the converter on the host being converted and it only has 384Mb Ram)
3) ran the convert from the helper VM
although the convert ended with a failure at 97%, the resulting VM booted without issue
Further analysis of the logs should determine exactly why these steps resulted in a functional VM, where the previous attempts did not
thanks