This topic contains 2 replies, has 2 voices, and was last updated by  Ryosuek S February 8, 2018.

VmwareVMs migrated to Azure does not boot

  •  

    Hello I created centos minimal 7.1 on ESXi6.0 and doing failover test to Azure, but centos does not boot in the recovery site. I got a screenshot of azure boot diagnostics. CentOS outputted an error message about boot. Could you guide me to know that I need to enable to be able to boot the machines of the recovery site?

    The error messages are as follows.
    (Case of Centos install with lvm)
    ————————————-
    [ OK ] Started Show Plymouth Boot Screen.
    [ OK ] Reached target Paths.
    [ OK ] Reached target Basic System.
    dracut-initqueue[502]: Warning: Could not boot.
    dracut-initqueue[502]: Warning: /dev/centos/root does not exist.
    dracut-initqueue[502]: Warning: /dev/centos/swap does not exist.
    dracut-initqueue[502]: Warning: /dev/mapper/centos-root does not exist.
    Starting Dracut Emergency Shell…
    Warning: /dev/centos/root does not exist
    Warning: /dev/centos/swap does not exist
    Warning: /dev/mapper/centos-root does not exist

    Generating “/run/initramfs/rdsosreport.txt”

    Entering emergency mode. Exit the shell to continue.
    Type “journalctl” to view system logs.
    You might want to save “/run/initramfs/rdsosreport.txt” to a USB stick or /boot
    after mounting them and attach it to a bug report.
    ————————————-

    (Case of Centos install with Standard partision)
    ————————————-
    [ OK ] Started Show Plymouth Boot Screen.
    [ OK ] Reached target Paths.
    [ OK ] Reached target Basic System.
    dracut-initqueue[462]: Warning: Could not boot.
    dracut-initqueue[462]: Warning: /dev/disk/by-uuid/6c972c0e-85ce-4f69-80aa-23f6b52b41e5 does not exist
    Starting Dracut Emergency Shell…
    Warning: /dev/disk/by-uuid/6c972c0e-85ce-4f69-80aa-23f6b52b41e5 does not exist

    Generating “/run/initramfs/rdsosreport.txt”

    Entering emergency mode. Exit the shell to continue.
    Type “journalctl” to view system logs.
    You might want to save “/run/initramfs/rdsosreport.txt” to a USB stick or /boot/ after mounting them and attach it to a bug report.
    ————————————-

    Hi Ryosuek,

    There are a number of administration and best practice guides located in the technical documentation folder of myZerto.

    In a preliminary check through, I found this:  http://s3.amazonaws.com/zertodownload_docs/Latest/Zerto%20Virtual%20Manager%20Azure%20Administration%20Guide.pdf

    It does state that if a different static IP address is configured for certain types of VMs, the VM may not boot in Azure.

    I’m not entirely sure if this is the root cause of your problem, but check out the guide(s) and let me know.  You can always open a support ticket through the Zerto Virtual Manager if you cannot solve the issue on your own.

    I hope this helps!

    Hi.Ryan

     

    Thank you for your reply.

    I used zerto version 5.5 but I checked the zerto version 6  153th page of the administration guide and executed the following procedure. CentOS 7 was started!

    Also, static IP setting was done normally.

     

    ===

    1.Add the following to /etc/dracut.conf.

    add_drivers+=”hv_vmbus hv_netvsc hv_storvsc”

    2.Execute the following command.

    #dracut –force -v

    ===

     

    Thank you.

You must be logged in to create new topics. Click here to login