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

[jhaanane]

The convert operation always fails whith this error on a 2003 server std r2:

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

2009-07-08 18:18:42.703 07280 verbose 'TaskSummary' UpdateTask
(converter.task.TaskInfo) {
dynamicType = <unset>,
key = "task-13",
task = 'converter.task.Task:task-13',
name = "Convert",
descriptionId = "Convert.P2V",
userName = "user",
source = "x.x.x.x",
target = "x.x.x.x/servername",
state = "error",
cancelled = false,
cancelable = true,
data = <unset>,
error = (converter.fault.ReconfigurationNoSystemVolumeFault) {
dynamicType = <unset>,
faultCause = (vmodl.MethodFault) null,
description = "InternalError",
msg = "Unable to find the system volume, reconfiguration is not possible.",

I've seen some posts about it and the "boot.ini" file but nothing seems to work.

Anybody can help me?

Thanks

jhaanane

[IamTHEvilONE]

jhaanane,

Welcome to the VMware Community Forums!

It looks like the source system may be either dual boot or contains a software mirror inside of windows. The easiest thing to do might be to break the mirror, remove the software plex from boot.ini, and then reconvert the machine.

If you wish to try and repair the virtual machine that had failed, there is a bit of work to do and you will need something like gparted to fix it in ESX.

1. Set the virtual machine to boot from ISO

- Edit settings

- Set the CD-Rom to the gparted ISO, check connect at power on

- Set the virtual machine to boot into the BIOS

- Options Tab > Boot Options > Force BIOS

- Confirm the settings change

2. Boot from CD-ROM

- boot the virtual machine, it will enter the bios

- change the boot options to have the CD-Rom as first boot option

- Save and exit the BIOS

- gParted will start to boot this time around

- As gParted boots, there will be several options to select

- choose all of the default options by pressing enter

- eventually an desktop screen will come up

3. Set the boot flag on the correct disc

- Click the /dev/sda drop down on the right, and search for the correct size OS drive (drive select.jpg)

- Right click the partition to get the context menu (Context Menu.jpg), choose Manage Flags

- Set the 'boot' flag (boot flags.jpg), and click okay

- double click the Exit button on the top right, and shutdown the virtual machine

4. Check the hard drive order and boot.ini file

- double check the settings of the virtual machine and ensure that the disk that is on SCSI0:0 matches the drive that should be the OS partition

- add this disk to another virtual machine, so you can ensure the boot.ini is correct

- the boot.ini should point to multi(0)rdisk(0)disk(0)partition(1)...

- once this is done, power off the virtual machine and detach (without deleting) the additional hard disk

- finally use the 'Reconfigure Machine' option

Regards,

EvilOne

VMware vExpert 2009

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

[sasar]

Hi,

I just can not make Gpart to boot

I tried versions gparted-live-0.5.0-3 and gparted-live-0.4.8-6, but none of them will boot.

You can see in screenshot error.

[continuum]

you may need to adjust guestOS to boot gparted. Use oldest version you can find.

Better use a BartPE - that also allows registry editing




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[sasar]

What should I use, Linux guest OS?

I tried but same error...

[sasar]

..also I have tried BartPE but I don't know what do you mean by I can use it to edit registry?

I need to change flag as it is mentioned above...

Diskpart can not be started...

[continuum]

don't you have diskmanagement in your BartPE ?

Have a look at MOA then - it comes with diskmanagement and Converter and all the stuff you need for this tasks




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[sasar]

yes I have but it doesn't start

I have downloaded latest version...

[continuum]

? - what does not start ?




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[sasar]

diskmanagement in BartPE...maybe because computer I converted was on RADI5...

I dont have this problems when I convert machines who resides on RAID0 or on only one hd...