XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    recovery startup failed

    Scheduled Pinned Locked Moved Xen Orchestra
    13 Posts 5 Posters 1.8k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N Offline
      ninghe
      last edited by

      we used a backup with memory to recovery a vm , then, we clicked "recovery start" button to start the vm, but we got a error: "no bootable device". Does anyone know what's going on?

      C 1 Reply Last reply Reply Quote 0
      • C Offline
        creoleMalady @ninghe
        last edited by

        @ninghe I may be having a similar issue.

        I have both Delta backups and full backups failing to restore properly from an NFS source. I have them throwing into a UEFI rescue mode. I have Debian Buster images doing this and Centos 8 with xo-server 5.81.2 and XCP-NG 8.2.0.

        My original VM's are using Secure Boot with UEFI, I have not yet tested non-Secure Boot or non-UEFI VM's and their backups.

        I do not know what I am missing, nothing about the restore fails, they just will not boot.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          We do not yet support secure boot with UEFI so I wonder how it's possible 🤔 Am I missing something @stormi ?

          1 Reply Last reply Reply Quote 0
          • stormiS Offline
            stormi Vates 🪐 XCP-ng Team
            last edited by

            Unless @creoleMalady installed testing packages, there's no UEFI SecureBoot support yet in XCP-ng 8.2 (though XO offering the option in advanced parameters may suggest otherwise).

            C 1 Reply Last reply Reply Quote 0
            • C Offline
              creoleMalady @stormi
              last edited by creoleMalady

              @stormi

              Well that's news to me.

              I just tested disabling secure boot on a VM and rebooting it. It made no difference, which is what I'd expect if it was unsupported.

              I guess we can rule it out as a factor in why our backups don't work.

              1 Reply Last reply Reply Quote 0
              • N Offline
                ninghe
                last edited by

                Hi guys, we are not using UEFI boot mode, we use "bios boot" mode.

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  @ninghe is it a PV or a HVM guest?

                  1 Reply Last reply Reply Quote 0
                  • C creoleMalady referenced this topic on
                  • R Offline
                    ricky222
                    last edited by

                    I believe I'm having the same problem. A VM failed to reboot and ended up in busy box recovery state. I also tried the recovery start and it failed. First it claimed that the DVD drive was not connected and I needed to start up and shut down the VM. I did so, the DVD drive is connected but with nothing in the drive, I get

                    f94db092-8f6c-42c3-b4f4-1cff36de4a18-image.png

                    With the guest tools DVD in the drive I get:

                    32ba9938-1014-4fa5-a7e5-daa00e3abec5-image.png

                    Am I missing some sort of disk image the rescue mode needs?

                    1 Reply Last reply Reply Quote 0
                    • stormiS Offline
                      stormi Vates 🪐 XCP-ng Team
                      last edited by

                      The guest tools ISO is not a bootable rescue device. Rescuing the VM's system itself is not XCP-ng's area. Just upload a generic rescue ISO image to your ISO SR and boot it.

                      R 1 Reply Last reply Reply Quote 0
                      • stormiS Offline
                        stormi Vates 🪐 XCP-ng Team
                        last edited by

                        This said, it's totally possible that the issue is not within the VM OS itself but rather at storage level. I'd check the storage logs: https://xcp-ng.org/docs/troubleshooting.html#storage-related-eg-coalescing-snapshots

                        R 1 Reply Last reply Reply Quote 0
                        • R Offline
                          ricky222 @stormi
                          last edited by

                          @stormi this is the recovery boot I was speaking about.

                          537fd0e2-952f-4e55-ad27-aebaaac45694-image.png

                          Clicking the recovery start and I get:

                          4ce2cac3-4c58-4729-a390-3bb7494ec42c-image.png

                          Am I misunderstanding something about the functionality provided by the recovery start button?

                          I tried to boot off a rescue image earlier but there was some problem with the DVD virtual device attached to the VM. A couple of reboots later it seems to not be a problem anymore and I was able to successfully boot onto PartitionMagic. Now I can look into the logs in the VM and see if they show any hints as to why it's failing.

                          1 Reply Last reply Reply Quote 0
                          • R Offline
                            ricky222 @stormi
                            last edited by

                            @stormi that's a good thing to look at and I am paying attention to it. Things I've learned since my original post are leading me to suspect a bet update is has caused the VM to crash.

                            1 Reply Last reply Reply Quote 0
                            • olivierlambertO Offline
                              olivierlambert Vates 🪐 Co-Founder CEO
                              last edited by

                              "Recovery" is only an option for PV guest (not HVM), when you want to re-use the initial bootloader. It has nothing to do to recover anything else.

                              You should be in HVM for all your VMs by the way, it's more secure and even faster.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post