GRUB - Unable to boot correct partition











up vote
0
down vote

favorite












To preface, everything I'm doing here is EFI, I'm not touching MBR or legacy boot at all.



I have a USB drive with multiple partitions.
On the first partition, I have Clonezilla Live.
On the second partition, I have GParted Live
On the third partition, I have the Windows 10 installer.



Depending on which partition I select in the UEFI, I go to the respective loader. Clonezilla and GParted load their respective GRUBs, and Windows loads it's installer.



However, if I select any option on the GParted partition, it loads clonezilla.



I figured this was simply a case of GRUB being configured incorrectly, and assumed it had to do with how root was being set.

By default, the menuentry is this;



menuentry "GParted Live (Default settings)"{
search --set -f /live/vmlinuz
linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
initrd /live/initrd.img
}


My assumption was that the search parameter was finding vmlinuz on the clonezilla partition first, and setting that to root since that's the default of the --set flag.



I tried three different alternatives to correctly set root to the GParted partition;



menuentry "GParted Live (set root)"{
set root=(hd0,gpt2)
linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
initrd /live/initrd.img
}
menuentry "GParted Live (uuid)"{
search --set=root --fs-uuid 12FA-2F46
linux /live/vmlinuz root=UUID=12FA-2F46 boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
initrd /live/initrd.img
}
menuentry "GParted Live (name)"{
search --set=root --label GPARTED
linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
initrd /live/initrd.img
}


All three of these options boot Clonezilla, even though it's clearly pointing to the correct partition with GParted on it.

However, if I delete clonezilla from the first partition, these all boot GParted as they should.



I've got no idea why GRUB is looking at the Clonezilla partition during boot.



My original intention was to have a small EFI partition with a GRUB install, and then have different options for the three installers, as well as an EFI firmware edit and memtest. Essentially turn it into a swiss army knife USB drive. However, I don't really want to spend the time setting that all up if for whatever reason I can only boot Clonezilla and not GParted.



Any ideas?










share|improve this question









New contributor




Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
























    up vote
    0
    down vote

    favorite












    To preface, everything I'm doing here is EFI, I'm not touching MBR or legacy boot at all.



    I have a USB drive with multiple partitions.
    On the first partition, I have Clonezilla Live.
    On the second partition, I have GParted Live
    On the third partition, I have the Windows 10 installer.



    Depending on which partition I select in the UEFI, I go to the respective loader. Clonezilla and GParted load their respective GRUBs, and Windows loads it's installer.



    However, if I select any option on the GParted partition, it loads clonezilla.



    I figured this was simply a case of GRUB being configured incorrectly, and assumed it had to do with how root was being set.

    By default, the menuentry is this;



    menuentry "GParted Live (Default settings)"{
    search --set -f /live/vmlinuz
    linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
    initrd /live/initrd.img
    }


    My assumption was that the search parameter was finding vmlinuz on the clonezilla partition first, and setting that to root since that's the default of the --set flag.



    I tried three different alternatives to correctly set root to the GParted partition;



    menuentry "GParted Live (set root)"{
    set root=(hd0,gpt2)
    linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
    initrd /live/initrd.img
    }
    menuentry "GParted Live (uuid)"{
    search --set=root --fs-uuid 12FA-2F46
    linux /live/vmlinuz root=UUID=12FA-2F46 boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
    initrd /live/initrd.img
    }
    menuentry "GParted Live (name)"{
    search --set=root --label GPARTED
    linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
    initrd /live/initrd.img
    }


    All three of these options boot Clonezilla, even though it's clearly pointing to the correct partition with GParted on it.

    However, if I delete clonezilla from the first partition, these all boot GParted as they should.



    I've got no idea why GRUB is looking at the Clonezilla partition during boot.



    My original intention was to have a small EFI partition with a GRUB install, and then have different options for the three installers, as well as an EFI firmware edit and memtest. Essentially turn it into a swiss army knife USB drive. However, I don't really want to spend the time setting that all up if for whatever reason I can only boot Clonezilla and not GParted.



    Any ideas?










    share|improve this question









    New contributor




    Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      To preface, everything I'm doing here is EFI, I'm not touching MBR or legacy boot at all.



      I have a USB drive with multiple partitions.
      On the first partition, I have Clonezilla Live.
      On the second partition, I have GParted Live
      On the third partition, I have the Windows 10 installer.



      Depending on which partition I select in the UEFI, I go to the respective loader. Clonezilla and GParted load their respective GRUBs, and Windows loads it's installer.



      However, if I select any option on the GParted partition, it loads clonezilla.



      I figured this was simply a case of GRUB being configured incorrectly, and assumed it had to do with how root was being set.

      By default, the menuentry is this;



      menuentry "GParted Live (Default settings)"{
      search --set -f /live/vmlinuz
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }


      My assumption was that the search parameter was finding vmlinuz on the clonezilla partition first, and setting that to root since that's the default of the --set flag.



      I tried three different alternatives to correctly set root to the GParted partition;



      menuentry "GParted Live (set root)"{
      set root=(hd0,gpt2)
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }
      menuentry "GParted Live (uuid)"{
      search --set=root --fs-uuid 12FA-2F46
      linux /live/vmlinuz root=UUID=12FA-2F46 boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }
      menuentry "GParted Live (name)"{
      search --set=root --label GPARTED
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }


      All three of these options boot Clonezilla, even though it's clearly pointing to the correct partition with GParted on it.

      However, if I delete clonezilla from the first partition, these all boot GParted as they should.



      I've got no idea why GRUB is looking at the Clonezilla partition during boot.



      My original intention was to have a small EFI partition with a GRUB install, and then have different options for the three installers, as well as an EFI firmware edit and memtest. Essentially turn it into a swiss army knife USB drive. However, I don't really want to spend the time setting that all up if for whatever reason I can only boot Clonezilla and not GParted.



      Any ideas?










      share|improve this question









      New contributor




      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      To preface, everything I'm doing here is EFI, I'm not touching MBR or legacy boot at all.



      I have a USB drive with multiple partitions.
      On the first partition, I have Clonezilla Live.
      On the second partition, I have GParted Live
      On the third partition, I have the Windows 10 installer.



      Depending on which partition I select in the UEFI, I go to the respective loader. Clonezilla and GParted load their respective GRUBs, and Windows loads it's installer.



      However, if I select any option on the GParted partition, it loads clonezilla.



      I figured this was simply a case of GRUB being configured incorrectly, and assumed it had to do with how root was being set.

      By default, the menuentry is this;



      menuentry "GParted Live (Default settings)"{
      search --set -f /live/vmlinuz
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }


      My assumption was that the search parameter was finding vmlinuz on the clonezilla partition first, and setting that to root since that's the default of the --set flag.



      I tried three different alternatives to correctly set root to the GParted partition;



      menuentry "GParted Live (set root)"{
      set root=(hd0,gpt2)
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }
      menuentry "GParted Live (uuid)"{
      search --set=root --fs-uuid 12FA-2F46
      linux /live/vmlinuz root=UUID=12FA-2F46 boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }
      menuentry "GParted Live (name)"{
      search --set=root --label GPARTED
      linux /live/vmlinuz boot=live union=overlay username=user config components quiet noswap ip= net.ifnames=0 nosplash
      initrd /live/initrd.img
      }


      All three of these options boot Clonezilla, even though it's clearly pointing to the correct partition with GParted on it.

      However, if I delete clonezilla from the first partition, these all boot GParted as they should.



      I've got no idea why GRUB is looking at the Clonezilla partition during boot.



      My original intention was to have a small EFI partition with a GRUB install, and then have different options for the three installers, as well as an EFI firmware edit and memtest. Essentially turn it into a swiss army knife USB drive. However, I don't really want to spend the time setting that all up if for whatever reason I can only boot Clonezilla and not GParted.



      Any ideas?







      grub2






      share|improve this question









      New contributor




      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited Nov 23 at 11:07









      Rui F Ribeiro

      38.3k1475127




      38.3k1475127






      New contributor




      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked Nov 23 at 6:21









      Jademalo

      1




      1




      New contributor




      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Jademalo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Jademalo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483601%2fgrub-unable-to-boot-correct-partition%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Jademalo is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Jademalo is a new contributor. Be nice, and check out our Code of Conduct.













          Jademalo is a new contributor. Be nice, and check out our Code of Conduct.












          Jademalo is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483601%2fgrub-unable-to-boot-correct-partition%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Morgemoulin

          Scott Moir

          Souastre