After Debian installation, how to add Grub Entries for new/other bootable disks/installations?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







5















I have two SSDs, one is for my Windows 7, and one is for testing and tweaking it (like installing Linux, or other operating systems...).



I've already installed Windows 7 on the first SSD,
and I tried to install Debian distribution on the second SSD, the installation was successful.



But the problem is that I installed something called boot loader into first SSD (which Windows 7 is installed), so if I run second SSD, nothing happens and if I run the first SSD, automatically Debian boot loader runs, and what thing fundamentally makes me annoying is that there is no option for Windows, just for Debian. (I thought I can use both of the choices if I install the boot loader into any SSD.)



If I open the SSD which Win installed, I can see those files and folders.



[Folder] Boot
[Folder] Documents and Settings
[Folder] Intel
[Folder] Perflogs
[Folder] ProgramData
[Folder] Program files
[Folder] Program files (x86)
[Folder] Recovery
[Folder] $Recycle.Bin
[Folder] System Volume Information
[Folder] Users
[Folder] Windows
[File] bootmgr
[File] BOOTSECT.BAK
[File] hiberfil.sys
[File] pagefile.sys


I think those all folders & files have relationships to Windows OS, but actually I don't know. (I just googled it.)



Can I change the directory of the boot loader or delete it?
What can I do?










share|improve this question































    5















    I have two SSDs, one is for my Windows 7, and one is for testing and tweaking it (like installing Linux, or other operating systems...).



    I've already installed Windows 7 on the first SSD,
    and I tried to install Debian distribution on the second SSD, the installation was successful.



    But the problem is that I installed something called boot loader into first SSD (which Windows 7 is installed), so if I run second SSD, nothing happens and if I run the first SSD, automatically Debian boot loader runs, and what thing fundamentally makes me annoying is that there is no option for Windows, just for Debian. (I thought I can use both of the choices if I install the boot loader into any SSD.)



    If I open the SSD which Win installed, I can see those files and folders.



    [Folder] Boot
    [Folder] Documents and Settings
    [Folder] Intel
    [Folder] Perflogs
    [Folder] ProgramData
    [Folder] Program files
    [Folder] Program files (x86)
    [Folder] Recovery
    [Folder] $Recycle.Bin
    [Folder] System Volume Information
    [Folder] Users
    [Folder] Windows
    [File] bootmgr
    [File] BOOTSECT.BAK
    [File] hiberfil.sys
    [File] pagefile.sys


    I think those all folders & files have relationships to Windows OS, but actually I don't know. (I just googled it.)



    Can I change the directory of the boot loader or delete it?
    What can I do?










    share|improve this question



























      5












      5








      5


      1






      I have two SSDs, one is for my Windows 7, and one is for testing and tweaking it (like installing Linux, or other operating systems...).



      I've already installed Windows 7 on the first SSD,
      and I tried to install Debian distribution on the second SSD, the installation was successful.



      But the problem is that I installed something called boot loader into first SSD (which Windows 7 is installed), so if I run second SSD, nothing happens and if I run the first SSD, automatically Debian boot loader runs, and what thing fundamentally makes me annoying is that there is no option for Windows, just for Debian. (I thought I can use both of the choices if I install the boot loader into any SSD.)



      If I open the SSD which Win installed, I can see those files and folders.



      [Folder] Boot
      [Folder] Documents and Settings
      [Folder] Intel
      [Folder] Perflogs
      [Folder] ProgramData
      [Folder] Program files
      [Folder] Program files (x86)
      [Folder] Recovery
      [Folder] $Recycle.Bin
      [Folder] System Volume Information
      [Folder] Users
      [Folder] Windows
      [File] bootmgr
      [File] BOOTSECT.BAK
      [File] hiberfil.sys
      [File] pagefile.sys


      I think those all folders & files have relationships to Windows OS, but actually I don't know. (I just googled it.)



      Can I change the directory of the boot loader or delete it?
      What can I do?










      share|improve this question
















      I have two SSDs, one is for my Windows 7, and one is for testing and tweaking it (like installing Linux, or other operating systems...).



      I've already installed Windows 7 on the first SSD,
      and I tried to install Debian distribution on the second SSD, the installation was successful.



      But the problem is that I installed something called boot loader into first SSD (which Windows 7 is installed), so if I run second SSD, nothing happens and if I run the first SSD, automatically Debian boot loader runs, and what thing fundamentally makes me annoying is that there is no option for Windows, just for Debian. (I thought I can use both of the choices if I install the boot loader into any SSD.)



      If I open the SSD which Win installed, I can see those files and folders.



      [Folder] Boot
      [Folder] Documents and Settings
      [Folder] Intel
      [Folder] Perflogs
      [Folder] ProgramData
      [Folder] Program files
      [Folder] Program files (x86)
      [Folder] Recovery
      [Folder] $Recycle.Bin
      [Folder] System Volume Information
      [Folder] Users
      [Folder] Windows
      [File] bootmgr
      [File] BOOTSECT.BAK
      [File] hiberfil.sys
      [File] pagefile.sys


      I think those all folders & files have relationships to Windows OS, but actually I don't know. (I just googled it.)



      Can I change the directory of the boot loader or delete it?
      What can I do?







      debian system-installation dual-boot boot-loader






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 28 '16 at 12:00









      Alex Stragies

      3,4001640




      3,4001640










      asked May 28 '16 at 9:50









      Eunsu JangEunsu Jang

      3614




      3614






















          2 Answers
          2






          active

          oldest

          votes


















          10














          It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.



          Boot the computer with all disks containing bootable installations attached and powered.



          you need to open Root Terminal application to open a terminal as root, then enter these commands:



          apt-get update
          apt-get install os-prober


          if os-prober package is already installed, apt will let you know, without doing any changes to the system.



          Then edit /etc/default/grub and make sure you have a line like



          GRUB_DISABLE_OS_PROBER=false


          you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.



          Using Gedit:



          gksu gedit /etc/default/grub


          You need to close gedit to be able to use the terminal again



          Using Nano



          nano /etc/default/grub


          I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.



          Once you're done with editing the file, if necessary, enter this command



          update-grub


          Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.






          share|improve this answer


























          • More complete answer than mine; well done :)

            – Alex Stragies
            May 28 '16 at 10:54











          • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

            – Jenny T-Type
            May 28 '16 at 10:58








          • 1





            Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

            – Alex Stragies
            May 28 '16 at 11:05











          • Solved the problem, thank you so much. :D

            – Eunsu Jang
            May 28 '16 at 11:18













          • @EunsuJang I'm glad it worked well for you.

            – Jenny T-Type
            May 28 '16 at 11:25



















          4














          You could:




          • start the computer with both disks attached,

          • boot into (your currently only choice) Debian

          • run update-grub


          It should detect Windows on the first Disk, and add an entry to the boot-loader choices.



          And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb



          sdb is what I assume to be the device node for the second attached disk, else try sda






          share|improve this answer
























            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%2f286079%2fafter-debian-installation-how-to-add-grub-entries-for-new-other-bootable-disks%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









            10














            It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.



            Boot the computer with all disks containing bootable installations attached and powered.



            you need to open Root Terminal application to open a terminal as root, then enter these commands:



            apt-get update
            apt-get install os-prober


            if os-prober package is already installed, apt will let you know, without doing any changes to the system.



            Then edit /etc/default/grub and make sure you have a line like



            GRUB_DISABLE_OS_PROBER=false


            you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.



            Using Gedit:



            gksu gedit /etc/default/grub


            You need to close gedit to be able to use the terminal again



            Using Nano



            nano /etc/default/grub


            I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.



            Once you're done with editing the file, if necessary, enter this command



            update-grub


            Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.






            share|improve this answer


























            • More complete answer than mine; well done :)

              – Alex Stragies
              May 28 '16 at 10:54











            • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

              – Jenny T-Type
              May 28 '16 at 10:58








            • 1





              Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

              – Alex Stragies
              May 28 '16 at 11:05











            • Solved the problem, thank you so much. :D

              – Eunsu Jang
              May 28 '16 at 11:18













            • @EunsuJang I'm glad it worked well for you.

              – Jenny T-Type
              May 28 '16 at 11:25
















            10














            It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.



            Boot the computer with all disks containing bootable installations attached and powered.



            you need to open Root Terminal application to open a terminal as root, then enter these commands:



            apt-get update
            apt-get install os-prober


            if os-prober package is already installed, apt will let you know, without doing any changes to the system.



            Then edit /etc/default/grub and make sure you have a line like



            GRUB_DISABLE_OS_PROBER=false


            you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.



            Using Gedit:



            gksu gedit /etc/default/grub


            You need to close gedit to be able to use the terminal again



            Using Nano



            nano /etc/default/grub


            I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.



            Once you're done with editing the file, if necessary, enter this command



            update-grub


            Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.






            share|improve this answer


























            • More complete answer than mine; well done :)

              – Alex Stragies
              May 28 '16 at 10:54











            • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

              – Jenny T-Type
              May 28 '16 at 10:58








            • 1





              Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

              – Alex Stragies
              May 28 '16 at 11:05











            • Solved the problem, thank you so much. :D

              – Eunsu Jang
              May 28 '16 at 11:18













            • @EunsuJang I'm glad it worked well for you.

              – Jenny T-Type
              May 28 '16 at 11:25














            10












            10








            10







            It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.



            Boot the computer with all disks containing bootable installations attached and powered.



            you need to open Root Terminal application to open a terminal as root, then enter these commands:



            apt-get update
            apt-get install os-prober


            if os-prober package is already installed, apt will let you know, without doing any changes to the system.



            Then edit /etc/default/grub and make sure you have a line like



            GRUB_DISABLE_OS_PROBER=false


            you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.



            Using Gedit:



            gksu gedit /etc/default/grub


            You need to close gedit to be able to use the terminal again



            Using Nano



            nano /etc/default/grub


            I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.



            Once you're done with editing the file, if necessary, enter this command



            update-grub


            Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.






            share|improve this answer















            It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.



            Boot the computer with all disks containing bootable installations attached and powered.



            you need to open Root Terminal application to open a terminal as root, then enter these commands:



            apt-get update
            apt-get install os-prober


            if os-prober package is already installed, apt will let you know, without doing any changes to the system.



            Then edit /etc/default/grub and make sure you have a line like



            GRUB_DISABLE_OS_PROBER=false


            you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.



            Using Gedit:



            gksu gedit /etc/default/grub


            You need to close gedit to be able to use the terminal again



            Using Nano



            nano /etc/default/grub


            I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.



            Once you're done with editing the file, if necessary, enter this command



            update-grub


            Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 4 hours ago









            Rui F Ribeiro

            41.9k1483142




            41.9k1483142










            answered May 28 '16 at 10:49









            Jenny T-TypeJenny T-Type

            443315




            443315













            • More complete answer than mine; well done :)

              – Alex Stragies
              May 28 '16 at 10:54











            • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

              – Jenny T-Type
              May 28 '16 at 10:58








            • 1





              Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

              – Alex Stragies
              May 28 '16 at 11:05











            • Solved the problem, thank you so much. :D

              – Eunsu Jang
              May 28 '16 at 11:18













            • @EunsuJang I'm glad it worked well for you.

              – Jenny T-Type
              May 28 '16 at 11:25



















            • More complete answer than mine; well done :)

              – Alex Stragies
              May 28 '16 at 10:54











            • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

              – Jenny T-Type
              May 28 '16 at 10:58








            • 1





              Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

              – Alex Stragies
              May 28 '16 at 11:05











            • Solved the problem, thank you so much. :D

              – Eunsu Jang
              May 28 '16 at 11:18













            • @EunsuJang I'm glad it worked well for you.

              – Jenny T-Type
              May 28 '16 at 11:25

















            More complete answer than mine; well done :)

            – Alex Stragies
            May 28 '16 at 10:54





            More complete answer than mine; well done :)

            – Alex Stragies
            May 28 '16 at 10:54













            @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

            – Jenny T-Type
            May 28 '16 at 10:58







            @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol

            – Jenny T-Type
            May 28 '16 at 10:58






            1




            1





            Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

            – Alex Stragies
            May 28 '16 at 11:05





            Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them)

            – Alex Stragies
            May 28 '16 at 11:05













            Solved the problem, thank you so much. :D

            – Eunsu Jang
            May 28 '16 at 11:18







            Solved the problem, thank you so much. :D

            – Eunsu Jang
            May 28 '16 at 11:18















            @EunsuJang I'm glad it worked well for you.

            – Jenny T-Type
            May 28 '16 at 11:25





            @EunsuJang I'm glad it worked well for you.

            – Jenny T-Type
            May 28 '16 at 11:25













            4














            You could:




            • start the computer with both disks attached,

            • boot into (your currently only choice) Debian

            • run update-grub


            It should detect Windows on the first Disk, and add an entry to the boot-loader choices.



            And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb



            sdb is what I assume to be the device node for the second attached disk, else try sda






            share|improve this answer




























              4














              You could:




              • start the computer with both disks attached,

              • boot into (your currently only choice) Debian

              • run update-grub


              It should detect Windows on the first Disk, and add an entry to the boot-loader choices.



              And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb



              sdb is what I assume to be the device node for the second attached disk, else try sda






              share|improve this answer


























                4












                4








                4







                You could:




                • start the computer with both disks attached,

                • boot into (your currently only choice) Debian

                • run update-grub


                It should detect Windows on the first Disk, and add an entry to the boot-loader choices.



                And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb



                sdb is what I assume to be the device node for the second attached disk, else try sda






                share|improve this answer













                You could:




                • start the computer with both disks attached,

                • boot into (your currently only choice) Debian

                • run update-grub


                It should detect Windows on the first Disk, and add an entry to the boot-loader choices.



                And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb



                sdb is what I assume to be the device node for the second attached disk, else try sda







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 28 '16 at 10:49









                Alex StragiesAlex Stragies

                3,4001640




                3,4001640






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f286079%2fafter-debian-installation-how-to-add-grub-entries-for-new-other-bootable-disks%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

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震