VMware Cloud Community
pinco_pallo
Contributor
Contributor
Jump to solution

ERROR: at 98% conversion failed || Unable to find the system volume, reconfiguration is not possible.

Hi all,

I'm currently using Vmware vCenter Conversion v. 5.0.1 and I tried to convert a local machine running Windows 7 64bit SP1 Ent two a three times , but I've always got the message reported in the title.

My local machine has two physical HDDs:

1) Boot HDD (system reserved part + boot part)

2) Data HDD where Users dir is (one part)

as I'm quite a noob in Vmware I ask for an help. I really don't know how to troubleshoot this error. :smileyconfused:

Thanks in advance! Smiley Happy

Reply
0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

Ok - boot the VM into recovery mode or use a Win7 Recovery or LiveCD.
After start is finished start regedit - select HKLM and then click "load hive"
Select the file C:\windows\system32\config\SYSTEM and give it a name - "p2v" for example.
Then find HKLM\p2v\ControlSet001\services\LSI_SAS and set the value for Start to 0.
Then unload the hive again and reboot


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

Reply
0 Kudos
14 Replies
continuum
Immortal
Immortal
Jump to solution

Converter 5 is designed to fail when used by unexperienced users.

Very likely the VM arrived completely and it would probably even boot into a bluescreen which is a good sign.

You probably did not change the controller and accepted the default choice - which usually fails.

Post the vmx-file - this can be fixed in most cases


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

pinco_pallo
Contributor
Contributor
Jump to solution

thanks for your contribute continuum! Smiley Happy

here you can find my vmx file.

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

... as expected ...
Converter misconfigured the job - your VM uses an IDE-disk and Converter can not patch VMs with IDE-disks.

Either rerun the job and select LSI-SAS controller yourself - or just fix the VM you already have.

I explained this lots of times already - so here just the summary:

Redefine the vmdk in the vmx as LSI-SAS disk - boot into recovery mode and enable lsi-sas driver in registry.

See my notes 

http://sanbarrow.com/p2v2008r2.html - patching easy variant


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

thanks... I'll give a try to a fresh new conversion. Smiley Happy

By the way I get a warning on the number of virtual cores:

Capture.JPG

what am I supposed to choose here for not having problems afterwards? I use an Intel i7-27600k.

thanks again for the support! Smiley Happy

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

start with one or two vCPUs - can be adjusted later


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

I remade the conversion but got still the same error! :smileyconfused:

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Ok - boot the VM into recovery mode or use a Win7 Recovery or LiveCD.
After start is finished start regedit - select HKLM and then click "load hive"
Select the file C:\windows\system32\config\SYSTEM and give it a name - "p2v" for example.
Then find HKLM\p2v\ControlSet001\services\LSI_SAS and set the value for Start to 0.
Then unload the hive again and reboot


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

ok, I booted in recovery mode with the CD ... and when the automatic recovery finished I did as you told me but the start value is already =0 in LSI-SAS, as you can see from the attached picture:

Capture.JPG

but when I rebooted I got again the blue screen of death and then, after a sec, the menu proposed me to launch startup repair again! Smiley Sad

now what? any other hint? ... :smileyconfused:

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

which system file did you load ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

not sure exactly about what you mean... both the file system (guest and host) are NTFS ....

if you need any log file, please feel free to ask ...

Capture.JPG

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

I've just added the log file if it can be of any help ...

thanks in advance! Smiley Happy

have a nice weekend!

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

if you boot witha LiveCD or into recovery mode there are two SYSTEM hives: one of the Livesystem in X:\ and the one you need to edit in C:, 😧 or E:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

ahhhh!! Now i got it! Let me try again and then I'll post the results! Thanks!

Reply
0 Kudos
pinco_pallo
Contributor
Contributor
Jump to solution

Thank you!

Everything is working properly now! :smileycool: even if it's really slow compared to the phisical machine.

Thanks again! Smiley Happy

Reply
0 Kudos