I can't make a GRUB config












0














A few weeks ago, I accidentally updated my kernel, and out of nowhere I got these strange pixelated lines all over my screen. So, I decided to try and use the linux-lts kernel. But, when I tried to chroot into my root directory run
grub-mkconfig /dev/sda
I got
/usr/bin/grub-probe: error: cannot find a device for / (is /dev mounted?)
I am running 32 bit Void.










share|improve this question


















  • 1




    Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
    – JigglyNaga
    Dec 22 '18 at 13:38






  • 1




    Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
    – Dani_l
    Dec 23 '18 at 21:08
















0














A few weeks ago, I accidentally updated my kernel, and out of nowhere I got these strange pixelated lines all over my screen. So, I decided to try and use the linux-lts kernel. But, when I tried to chroot into my root directory run
grub-mkconfig /dev/sda
I got
/usr/bin/grub-probe: error: cannot find a device for / (is /dev mounted?)
I am running 32 bit Void.










share|improve this question


















  • 1




    Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
    – JigglyNaga
    Dec 22 '18 at 13:38






  • 1




    Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
    – Dani_l
    Dec 23 '18 at 21:08














0












0








0







A few weeks ago, I accidentally updated my kernel, and out of nowhere I got these strange pixelated lines all over my screen. So, I decided to try and use the linux-lts kernel. But, when I tried to chroot into my root directory run
grub-mkconfig /dev/sda
I got
/usr/bin/grub-probe: error: cannot find a device for / (is /dev mounted?)
I am running 32 bit Void.










share|improve this question













A few weeks ago, I accidentally updated my kernel, and out of nowhere I got these strange pixelated lines all over my screen. So, I decided to try and use the linux-lts kernel. But, when I tried to chroot into my root directory run
grub-mkconfig /dev/sda
I got
/usr/bin/grub-probe: error: cannot find a device for / (is /dev mounted?)
I am running 32 bit Void.







grub2 void-linux grub2-mkconfig lts






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 21 '18 at 23:17









Gosh Darn

1




1








  • 1




    Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
    – JigglyNaga
    Dec 22 '18 at 13:38






  • 1




    Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
    – Dani_l
    Dec 23 '18 at 21:08














  • 1




    Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
    – JigglyNaga
    Dec 22 '18 at 13:38






  • 1




    Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
    – Dani_l
    Dec 23 '18 at 21:08








1




1




Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
– JigglyNaga
Dec 22 '18 at 13:38




Why are you using chroot? Are you trying to do this from a recovery disk/live CD, or the system itself?
– JigglyNaga
Dec 22 '18 at 13:38




1




1




Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
– Dani_l
Dec 23 '18 at 21:08




Generally speaking, before chrooting into a dir, mount bind /dev and /sys and mount -t proc the /proc. See the archlinux wiki wiki.archlinux.org/index.php/chroot
– Dani_l
Dec 23 '18 at 21:08










2 Answers
2






active

oldest

votes


















0














The Supergrub utility can boot an installation without a lot of trouble. Then you can fix your bootloader from inside the running distribution.
Supergrub



There is also the excellent SysrescueCD with more features except with more of a learning curve.
SysrescueCD






share|improve this answer





























    0














    Before you chroot into your root partition ("chroot /mnt/sysimage/" for example), you need to mount some system directories first.

    mount --bind /proc /mnt/sysimage/proc
    mount --bind /dev /mnt/sysimage/dev
    mount --bind /sys /mnt/sysimage/sys
    mount --bind /run /mnt/sysimage/run



    Then chroot /mnt/sysimage, regenerate grub.cfg and initramfs.






    share|improve this answer








    New contributor




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


















      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',
      autoActivateHeartbeat: false,
      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
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490418%2fi-cant-make-a-grub-config%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      The Supergrub utility can boot an installation without a lot of trouble. Then you can fix your bootloader from inside the running distribution.
      Supergrub



      There is also the excellent SysrescueCD with more features except with more of a learning curve.
      SysrescueCD






      share|improve this answer


























        0














        The Supergrub utility can boot an installation without a lot of trouble. Then you can fix your bootloader from inside the running distribution.
        Supergrub



        There is also the excellent SysrescueCD with more features except with more of a learning curve.
        SysrescueCD






        share|improve this answer
























          0












          0








          0






          The Supergrub utility can boot an installation without a lot of trouble. Then you can fix your bootloader from inside the running distribution.
          Supergrub



          There is also the excellent SysrescueCD with more features except with more of a learning curve.
          SysrescueCD






          share|improve this answer












          The Supergrub utility can boot an installation without a lot of trouble. Then you can fix your bootloader from inside the running distribution.
          Supergrub



          There is also the excellent SysrescueCD with more features except with more of a learning curve.
          SysrescueCD







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 25 '18 at 3:04









          beginner6789

          913




          913

























              0














              Before you chroot into your root partition ("chroot /mnt/sysimage/" for example), you need to mount some system directories first.

              mount --bind /proc /mnt/sysimage/proc
              mount --bind /dev /mnt/sysimage/dev
              mount --bind /sys /mnt/sysimage/sys
              mount --bind /run /mnt/sysimage/run



              Then chroot /mnt/sysimage, regenerate grub.cfg and initramfs.






              share|improve this answer








              New contributor




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























                0














                Before you chroot into your root partition ("chroot /mnt/sysimage/" for example), you need to mount some system directories first.

                mount --bind /proc /mnt/sysimage/proc
                mount --bind /dev /mnt/sysimage/dev
                mount --bind /sys /mnt/sysimage/sys
                mount --bind /run /mnt/sysimage/run



                Then chroot /mnt/sysimage, regenerate grub.cfg and initramfs.






                share|improve this answer








                New contributor




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





















                  0












                  0








                  0






                  Before you chroot into your root partition ("chroot /mnt/sysimage/" for example), you need to mount some system directories first.

                  mount --bind /proc /mnt/sysimage/proc
                  mount --bind /dev /mnt/sysimage/dev
                  mount --bind /sys /mnt/sysimage/sys
                  mount --bind /run /mnt/sysimage/run



                  Then chroot /mnt/sysimage, regenerate grub.cfg and initramfs.






                  share|improve this answer








                  New contributor




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









                  Before you chroot into your root partition ("chroot /mnt/sysimage/" for example), you need to mount some system directories first.

                  mount --bind /proc /mnt/sysimage/proc
                  mount --bind /dev /mnt/sysimage/dev
                  mount --bind /sys /mnt/sysimage/sys
                  mount --bind /run /mnt/sysimage/run



                  Then chroot /mnt/sysimage, regenerate grub.cfg and initramfs.







                  share|improve this answer








                  New contributor




                  liuqx 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 answer



                  share|improve this answer






                  New contributor




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









                  answered 43 mins ago









                  liuqx

                  1




                  1




                  New contributor




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





                  New contributor





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






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






























                      draft saved

                      draft discarded




















































                      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%2f490418%2fi-cant-make-a-grub-config%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