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.

108 Replies
dthompson024
Contributor
Contributor

Just had the same issue occur.  I'm trying to convert a Windows 7 virtual machine and there is no boot.ini on the system so I cannot get that to work.

Any help would be appreciated.  I have attached my vmx file.

0 Kudos
continuum
Immortal
Immortal

Did you use version 5.0.1 ?

did you configure the job using the defaults ?

Then you should know that the defaults must have been set by a guy with a mean streak.
Setting IDE when p2ving a Windows 7 never works - you should use LSI-SAS.

If you search this forum a bit you should find several posts where I walk someone through the procedure to fix this issue.

In short : rewrite the vmx so that the vmdk is added as a LSI-SAS drive.
Then do the patching part I described here:
http://sanbarrow.com/p2v2008r2.html

dont worry if it mentions 2008 R2 - the procedure works for both the same way

Patching - easy variant


This procedure is used when otherwise the VM would boot into a bluescreen              type 7B.
This assumes that VMware is the target and you configure the VM with              VirtualHardware type 7.
It only applies if the virtual disk is configured like this
scsi0.virtualDev = "lsisas1068"
scsi0:0.fileName = "imported.vmdk"

On the target platform boot the newly created VM into the Windows              7 Recovery CD.
After boot is finished click on the CMD-button and run regedit.
Select HKLM and then Menu > File > Load Hive.
Browse to the Windows-directory on the virtualdisk > system32\config              and select the file SYSTEM.
When asked for a name enter p2v.
Then find the key

HKLM\p2v\ControlSet001\services\LSI_SAS

and set the start type to REG_DWORD 0
Then select HKLM\p2v and click Menu > File > Unload Hive.
You can close regedit now and restart.
On next boot you can start into the 2008 R2 system. It should find              drivers and probably needs a reboot when done.

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

Thanks for the help.  All is well now thanks to your help.

0 Kudos
cidfits
Contributor
Contributor

i dont understand any of these suggestions. i have no clue where to start. all i know is that i am getting the unable to find system volume error.

any help appreciated.

0 Kudos
HashimSharif
Contributor
Contributor

Please also help me resolve my problem. I'm using VMware Vcenter converter 5.0.1 to convert my windows 7 PC to a VM workstation version 8 .

It alwasy fails after 98% or 99 % of the process.

Please find attached my the log export.

0 Kudos
POCEH
VMware Employee
VMware Employee

Too many 'Error 5' during reconfig, are you administrator of the local machine? If your UAC is enabled try to start Converter.exe "As administrator".

HTH

0 Kudos
dasabaja
Contributor
Contributor

How can this be performed on Win 7? There is no boot.ini as such. I've attached the "fail-converted" vmdk to another virtual machine and it appeared as another drive. How can I edit it's boot.ini? Any tampering with boot.ini directs me to the boot.ini of the virutual machine the "fail-converted" disk is attached to.

0 Kudos
Br1x1
Contributor
Contributor

Hello everyone!
Using the vCenter converter standalone client version 5.0.1 I'm trying to convert a windows 2003 server but I always get the following error:
FAILED: Unable to find the system volume, reconfiguration is not possible.

The system is installed on a hard drive with two partitions: C and D.
The operating system is installed on the disk D.
The boot.ini file is located on drive C and the content is as follows:
[boot loader]
timeout = 30
default = multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS
[operating systems]
multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS = "Windows Server 2003, Standard" / noexecute = optout / fastdetect.

Attached vmx file.
I can not understand where is the problem can someone help me please?
thanks

0 Kudos
dthompson024
Contributor
Contributor

Hello,

I am out of the office in meetings until Friday but will be checking messages regularly. If the matter is urgent please call my cell phone at +1 (440) 666-7210, otherwise I will return your message as soon as possible.

Thanks,

Dean

0 Kudos
continuum
Immortal
Immortal

multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS

that will only work if you include partition 1 in the import

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

First of all thanks for the immediate response!


I have a question what do you mean by:
That will only work if you include partition 1 in the import

If it means also convert the C partition I can confirm that I did.
Imported both partitions C and D as you can see in the image

Import.png

0 Kudos
Br1x1
Contributor
Contributor

Tx for the quick answer!

I'll make some tests in theese days.

Isn't urgent I hope to do the conversion at the end of this week.

0 Kudos
continuum
Immortal
Immortal

did you try to boot the VM ?

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

Yes I did, VM starts with windows 2003  logo but after 3-4 secs it crash with BOD then restart.

I'll try to make a shot of screen to understand what's happens

0 Kudos
continuum
Immortal
Immortal

post a screenshot of diskmanagement please

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

Excuse me, I don't understood what kind of diskmanagement you refer

Did you mean that I have to connect the Virtual disk on another VM and I open system management and disk management?

DiskManagement2.png

0 Kudos
Br1x1
Contributor
Contributor

Or you mean the diskmanagement on the original machine?

DiskManagement.png

0 Kudos
POCEH
VMware Employee
VMware Employee

The problem here could be dynamic boot volume. Try with reconfigure task only.

0 Kudos
Br1x1
Contributor
Contributor

Tx for the hint, I've already done it without success.

0 Kudos
POCEH
VMware Employee
VMware Employee

Hmm, one crazy idea: try to convert VM to other VM this could solve problem with dynamic boot partition because it is not dynamic in VM ... HTH

0 Kudos