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.
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:
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
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.
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.
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.
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:
timeout = 30
default = multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS
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?
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.
multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS
that will only work if you include partition 1 in the import
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
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?