Hobarmn5
Contributor
Contributor

FAILED: Unable to find the system volume, reconfiguration is not possible.

Jump to solution

While converting a Server 2003 server to an ESX 3.5 server I received this message after 95% Complete. Error Reconfiguration failed. With a status of: FAILED: Unable to find the system volume, reconfiguration is not possible.

I'm using VMware vCenter Converter Standalone 4.0.1

Anyone run into to this problem and find a solution?

Attached is the Log file.

1 Solution

Accepted Solutions
IamTHEvilONE
Immortal
Immortal

You have an unsupported Boot.ini file.

timeout=30

default=signature(e6d6ab31)disk(0)rdisk(0)partition(1)\WINDOWS

signature(e6d6ab31)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect

If the virtual machine still exists, if you can mount the vmdk file to another virtual machine and modify the ARC Path to being something like:

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" /fastdetect

Then use the 'reconfigure machine' option from converter, and it should work.

Otherwise, temporarily modify the source physical version of boot.ini and then convert again.



Regards,

EvilOne

VMware vExpert 2009

5441_5441.jpg

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

View solution in original post

0 Kudos
108 Replies
IamTHEvilONE
Immortal
Immortal

You have an unsupported Boot.ini file.

timeout=30

default=signature(e6d6ab31)disk(0)rdisk(0)partition(1)\WINDOWS

signature(e6d6ab31)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect

If the virtual machine still exists, if you can mount the vmdk file to another virtual machine and modify the ARC Path to being something like:

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" /fastdetect

Then use the 'reconfigure machine' option from converter, and it should work.

Otherwise, temporarily modify the source physical version of boot.ini and then convert again.



Regards,

EvilOne

VMware vExpert 2009

5441_5441.jpg

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

View solution in original post

0 Kudos
Hobarmn5
Contributor
Contributor

Thanks! Worked Like a Charm! Appreciate the Help!

Joshua

0 Kudos
RoadRunnerBris
Contributor
Contributor

Thanks for the info.

Found that my server did not have a boot.ini file, and a few others as well (AUTOEXEC.BAT, MSDOS.SYS, IO.SYS and CONFIG.SYS). Found the files on another server, copied them to the server I wanted to converted, and all worked like a charm.

Thanks for pointing me in the right direction.

Now...I'd like to find the culprit who thought that removing those Hidden System Files would be a good idea.

Smiley Happy

Craig

0 Kudos
Ashmai
Contributor
Contributor

Although this pointed me in the right direction, my situation was slightly different. The error message was caused because of a small 64 meg partition at the start of the system volume (a recovery partition from a manufacture, IBM I believe) that was converting over. When you de-selected this option from converter app telling it not to move over, it prompts you with a nastygram about "IF YOU REMOVED THIS YOUR VM WON'T BOOT"... I ignored that, migrated the rest of the drives, and it all worked fine.

Hope it helps someone.

0 Kudos
SoonerCG30
Contributor
Contributor

IamTHevilOne and RoadRunnerBris, your suggestions helped. Thanks. Smiley Happy

0 Kudos
SR2010
Contributor
Contributor

Found that recovery console loaded on original OS may also cause this error.

Removed "C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons" from boot.ini and reran conversion.

0 Kudos
kcspkd
Contributor
Contributor

hi all,

i am also facing issue.i was converting 2003 server standard to virtual machine. at 95% it stopped.It showed Failed:unable to find system volume,reconfiguration not possible.I have mounted the vmdk to a local machine and checked the boot.ini and found that its OK.These are the entries in it

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" /fastdetect

My purpose is to convert 2003 server physical to VM in VMWARE ESXi 4.1 host server.I am using the free version with license provided by VMware after registering.

The server has two harddisk.First disk 0 is D drive and second disk (ie 1) has C: and E drive.While converting i ommitted e drive,bcuse its consuming huge time.

I have used VCetre Converter standalone and in for destination type chose WMWare workstation or other vmware virtual machine and for vmware product selected vmware server 2.x

I am attaching the logs. I doubting that something has missed out or any mis-configuration i have made.

Please help me to find a solution for this..

0 Kudos
chrisbockhop
Contributor
Contributor

I am having this error as well.

Actions I have already taken:

completely deleting the second partition where I previously had a Win7 image for dualboot

ran Vistabootpro to remove the boot manager so now XP loads freely

edited boot.ini to ensure it is clear

still getting the same 98% failure every time, and when I try to play the vm I have created, it bluescreens every time.

host image is WiIndows XP SP3

creating VM to run on VMWare Player 3

0 Kudos
continuum
Immortal
Immortal

you used converter 3.0.3 I hope ?
in case you use 4.3 did you select buslogic as scsi-controller ?

you can try to simply run "configure machine" option again

>  ran Vistabootpro to remove the boot manager so now XP loads  freely

do you have  ntldr, ntdetect.com and boot.ini in an active partition ?

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
chrisbockhop
Contributor
Contributor

Thanks for the quick look.

you used converter 3.0.3 I hope ?  using 4.3
in case you use 4.3 did you select buslogic as scsi-controller ? ran again with SCSI selected and still failed

you can try to simply run "configure machine" option again

>  ran Vistabootpro to remove the boot manager so now XP loads  freely

do you have  ntldr, ntdetect.com and boot.ini in an active partition ?

boot files are all located in the root (C:) but to be safe I recovered them from the XP CD, rebooted the host, and ran the conversion again with yet another failure.

I've attached my latest log file.

I'm thinking that this image has just been through to much to be clean enough for conversion and I'll have to build it from scratch.

0 Kudos
continuum
Immortal
Immortal

a few failed reconfiguration attempts do not hurt

to clarify - do you speak about a XP or 2003 VM ?
did you ever boot the result ?

maybe it already works ...

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
chrisbockhop
Contributor
Contributor

This is a Windows XP image.  I've attempted to boot each failed image with the same result each time, the image bluescreens on boot (even into safemode/command prompt)

0 Kudos
continuum
Immortal
Immortal

then the controller does not match the registry settings

this can be fixed quite easily - post the vmx-file

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
chrisbockhop
Contributor
Contributor

Here it is!

0 Kudos
continuum
Immortal
Immortal

controller is set to buslogic already = good

if the boot.ini is correct a simple "configure machine" with converter 3.0.3 should fix it

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
chrisbockhop
Contributor
Contributor

Success!

So for the education, why was version 3.03 of the converter able to make this work where the newest version could not?

0 Kudos
continuum
Immortal
Immortal

> why was version 3.03 of the converter able to make this work where the  newest version could not?

Oh - the new Converter could do this too - but it tries to make the process as easy as possible for the enduser and then fails because the enduser is guided to use unwise defaults.

You will get used to it Smiley Wink

I highly recommend 3.0.3 for NT, 2000, XP and 2003 as the chances NOT to misconfigure the task at first attempt is higher then with 4.3

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
continuum
Immortal
Immortal

> why was version 3.03 of the converter able to make this work where the  newest version could not?

both versions CAN do that ...

in 3.0.3 converter does not ask you and configures the job so that it will most probably work
in 4.3 converter asks the user and an unexperienced user will most probably pick the wrong option

you will get used to it

if you are in a hurry and want to avoid failed attempts use 3.0.3 for NT, 2000, 2003 and XP

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
chrisbockhop
Contributor
Contributor

Thank you!

0 Kudos