VMware Cloud Community
Hobarmn5
Contributor
Contributor
Jump to solution

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

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
POCEH
VMware Employee
VMware Employee
Jump to solution

Please post log bundle with failed conversion.

Reply
0 Kudos
santadpor
Contributor
Contributor
Jump to solution

Thank you Continuum. In my case, the 3.0.3 converter resolves the reconfiguration error of my Windows 2000 Server conversion. It has nothing to do with the boot.ini that most people encounters. Thanks a lot.

Reply
0 Kudos
vsaltech
Contributor
Contributor
Jump to solution

I have this exact problem.  I have a windows 2003 server that I saved by puting on a compaq desktop with out doing anything about the recovery partition (E:) .

Which tool did you use to do these steps?

continuum wrote:

short summary of what I did:
copy ntldr, boot.ini, ntdetect.com from the boot partition to the large one
edit boot.ini
delete the 15 Gb partition at the start of the disk
convert the extended partition into a primary one
resize the large partition so that it fills the empty space at the beginning
rebuild mbr
set symmpy driver to start 0

run "configure machine" from Converter again

TIA

Reply
0 Kudos
vsaltech
Contributor
Contributor
Jump to solution

"set symmpy driver to start 0"

Can you give a little more detail of what this is and what tool to use for this?

Thanks,

Vince

Reply
0 Kudos
OseeLogic
Contributor
Contributor
Jump to solution

I tried several things without success .

Finally, even though the configuration failed, I opened the VM and changed the settings for it to use the Windows 8 install CD to boot from .

From there I tried the auto repair, but it did not work .

So, I opened command prompt and did the usual

bootrect /nt60 c: /force

bootsec /fixboot

bootsec /fixmbr

bootsec /rebouldbcd

After that finished, the VM booted normally .

35
Reply
0 Kudos
sda88
Contributor
Contributor
Jump to solution

hi, i know the post is from many years back. but currently am trying to convert windows 2000 server using vcentre standalone converter and getting the same error.. " unable to find the system volume, reconfiguration is not possible" could anyone please help with this, as i am new to p2v conversions..

thank you

Reply
0 Kudos
patanassov
VMware Employee
VMware Employee
Jump to solution

Hello,

Run a check disk, it seems there are bad sectors

[#38] [task-6] [2017-03-22 13:06:37.685 03748 warning 'App'] [blockLevelVolumeCloningTaskImpl,508] Detected bad sector on the source, error=38, offset=0x00000004dbccd000

[#38] [task-6] [2017-03-22 13:06:37.685 03748 warning 'App'] [blockLevelVolumeCloningTaskImpl,508] Detected bad sector on the source, error=38, offset=0x00000004dbccd200

Reply
0 Kudos
sda88
Contributor
Contributor
Jump to solution

thanks. I will do the chkdsk  and will let you know about the result.

Reply
0 Kudos
sda88
Contributor
Contributor
Jump to solution

Hi,

I did the chkdsk and ran the conversion again, it failed again at 97%. error.PNG