How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.

I was recently tasked with migrating a Hyper-V machine to our VMware environment. However, each time VMware Converter was ran, the task would fail at 97% with an error “FAILED: Unable to find the system volume, reconfiguration is not possible.“.

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

Looking further into the virtual machine there were a number of concerns I had on the VM. One such issue which I believe might be causing the above error, is that the system volume drive was on drive 0 while the “C:” drive was on drive 1. Whereas these are typically on the same drive in most Windows installs.

Below are the steps I took to fix this VM and made the migration from Hyper-V to VMware a success.

Rebuild boot record to resolve, FAILED: Unable to find the system volume, reconfiguration is not possible.

  1. Attach the server .ISO to the newly migrated virtual machine in VMware and boot from that image. You may need to change the boot order, in order for the VM to boot from the ISO.
  2. Now click on Next at the language, time, keyboard prompt.
    select language, time, keyboard
  3. Then, click Repair your computer in the lower left corner.
    select repair computer
  4. Next, select Troubleshoot.
    choose an option troubleshoot
  5. Now click on Command Prompt under Advanced options.
    advanced options command prompt
  6. In the command prompt, type in the following commands:
    Bootrec /fixmbr
    Bootrec /fixboot
    Bootrec /scanos
    Bootrec /rebuildbcd

    restore commands

  7. Finally, type EXIT in the command prompt and restart the virtual machine.

After the virtual machine rebooted, Windows Server loaded without issue and I was able to complete the migration by re-IPing the VM and updating DNS records.

Similar Posts

  • How to manually delete NetApp SnapMirror snapshots

    The other day, one of our volumes in the lab environment filled up. This volume has a couple large VM’s on it, coupled with a couple different Veeam backup jobs running using the native Veeam backup methods as well as using NetApp snap mirror to snapshot the volume and then using Veeam to ship it out to Azure.

    At any rate the volume filled up to the point where vCenter wasn’t allowing me to migrate VM’s off the datastore. I really didn’t want to expand the volume just so I could move VM’s off of it.

    Instead, I decided to delete some of the older proof of concept snapshots from SnapMirror. Below are the quick and easy steps to clear up some un-used snapshots and free up some space on the datastore.

    Read More “How to manually delete NetApp SnapMirror snapshots”

  • How to update VMware ESXi 6.7 to 6.7 Update 1

    To go along with the newly released VMware vCenter 6.7 Update 1 release, comes VMware ESXi 6.7 Update 1 as well.

    As you might expect with an Update 1 release there are a number of patches, fixes and new additions with ESXi 6.7 U1. If you haven’t already seen, check out the release notes here.

    Below are two ways to easily upgrade your ESXi 6.0-6.7 hosts to ESXi 6.7 U1 using the command line or by using VMware Update Manager.
    Read More “How to update VMware ESXi 6.7 to 6.7 Update 1”

  • Easy ESXi 5.5 upgrade via command line

    ESXi 5.5 was just released general availability (GA) on Sunday (9/22) and I’m itching to upgrade the home lab to run the latest version with all it’s goodies. I wanted to try upgrading my hosts without having to go through the same process that I followed setting up ESXi on the NUC in the first place, injecting custom NIC drivers, etc.

    Enter the command line…

    1. Move all VM’s from the host and then put the host into Maintenance Mode.
    2. Go to the Configuration tab > Security Profile and Enable SSH under Services.
      ssh enabled
    3. Under Firewall, enable httpClient (outbound http).
      httpClient enable
    4. Open PuTTY (or other SSH client) and SSH into your host.
    5. Read More “Easy ESXi 5.5 upgrade via command line”

  • VMware Recertification Policy

    VMware certified

    Starting today, March 10 2014, new VCP certifications must be re-certified within two years of it’s earned date. Anyone who currently has their VCP certification prior to March 10 2013 has until March 10, 2015 to re-certify.

    The new policy gives you three options to re-certify:

    1. Take the current exam for your existing VCP certification solution track. For example, if you are a VCP3, you could take the current VCP5-Data Center Virtualization (VCP5-DCV) exam.
    2. Earn a new VCP certification in a different solution track. For example, if you are a VCP-Cloud, you could recertify by earning VCP5-Desktop (VCP5-DT) certification.
    3. Advance to the next level by earning a VMware Certified Advanced Professional (VCAP) certification. For example, if you are a VCP5-DCV you could earn VCAP5-DCA certification.

    I can understand why they are doing this but I don’t agree with the changes. As per the announcement if you let your certification expire, “Your certification will be revoked,and you will no longer be entitled to use the certification logo or represent yourself as VMware certified“. Really? You mean everything that was done prior and after taking the exam means nothing?

    Read More “VMware Recertification Policy”

  • ESXi 5.5 free edition removes 32GB memory limit

    There have been a ton of exciting announcements coming out of VMword 2013, one of which is vSphere 5.5 and all of it’s improvements and additions. Along that note, VMware has changed ESXi 5.5 free version to remove the physical RAM limit which was limited to only 32GB in version 5.1.

    The new virtual hardware, version 10, we can now grow our home labs into more powerful VM’s as most all configuration maximums have been doubled:

    Read More “ESXi 5.5 free edition removes 32GB memory limit”

  • VMware Site Recovery Manager 8.2 – No more Windows

    VMware has just announced the release of Site Recovery Manager 8.2. There are a number of new items in SRM 8.2, such as enhancements to the HTML5 user interface, support for vSphere 6.7 Update 2, but most notably is Site Recovery Manager 8.2 virtual appliance!

    No more Microsoft Windows license needed! The SRM 8.2 virtual appliance runs on the Photon OS distro, which is similar to what the vCenter virtual appliance has been running on for years now.

    Read More “VMware Site Recovery Manager 8.2 – No more Windows”

Leave a Reply

Your email address will not be published. Required fields are marked *

3 Comments

  1. Do you mean to run this on the existing source VM, not on the failed target VM? I’m not 100% clear on what you mean when you say “Attach the server .ISO to the newly migrated virtual machine in VMware and boot from that image.” How do you perform this if the conversion failed and the destination VM cannot boot?

    1. Mike,

      You are doing exactly as I’ve pointed out “Attach the server .ISO to the newly migrated virtual machine in VMware and boot from that image” this is because the transfer is done using VMware Converter however the boot loader on the transferred machine is busted. Thus the need to mount the ISO on said VM and repair it.

      Hope this helps!

      -Michael

  2. I’m running into this for the first time. I have a set of two test and two production physical HP servers to convert. The two test HP servers converted normally. However, the two production servers are having this Failure. No amount of Option changes in the conversion wizard have resolved it. I’ll be trying again today and trying the options that Mike listed here and report back.

    Thank you for the article!

    -Chad