Install Grub when ssd is hd1

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0














I have a Dell G3 17 3779 laptop.

It has sata HDD as hd0 and m.2 ssd as hd1. Both in GPT.



I deleted everything in the ssd and installed Windows 10.

I used 4 partitions:



  • Windows recovery environment (499M) | /dev/sdb1

  • EFI System (100M) | /dev/sdb2

  • Microsoft reserved (MSR) (16M) | /dev/sdb3

  • Main Windows NTFS partition (70G) | /dev/sdb4

Also I added for Arch Linux 2 partitions:



  • For / (47.7G) | /dev/sdb5

  • For swap (980.3M) | /dev/sdb6

HDD disk has 2 partitions:



  • Microsoft reserved (MSR) (16M) | /dev/sda1

  • Some NTFS (900G) | /dev/sda2

After Windows I installed arch linux from UEFI following the wiki manual.



GRUB was installed with the usual grub-install without keys



I tried to configure GRUB with manual config:



/boot/grub/grub.cfg



. $prefix/menu.cfg


/boot/grub/menu.cfg



set default=0
set timeout=10
menuentry "ArchLinux"
linux /boot/vmlinuz-linux root=/dev/sdb4 rw
initrd /boot/initramfs-linux.img

menuentry "Windows"
regexp -s root '((.+))' "$cmdpath"
chainloader /EFI/Microsoft/Boot/bootmgfw.efi



After rebooting just started Windows 10 without any boot menus.



I installed os-prober and tried grub-mkconfig and get some warning like:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.

or
WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.



Instead /dev/loop0 was in all partitions.



And still booting only Windows.



May be it because my HDD is first in BIOS unlike SSD (hd0 vs hd1)?



How to fix this problem?



update: this answer https://askubuntu.com/a/816347/879272 allows me to open grub.



But why BIOS started EFI/Microsoft/Boot/bootmgfw.efi ignoring another boot loaders.

Can I disable this behavior?



fdisk



EFI










share|improve this question




























    0














    I have a Dell G3 17 3779 laptop.

    It has sata HDD as hd0 and m.2 ssd as hd1. Both in GPT.



    I deleted everything in the ssd and installed Windows 10.

    I used 4 partitions:



    • Windows recovery environment (499M) | /dev/sdb1

    • EFI System (100M) | /dev/sdb2

    • Microsoft reserved (MSR) (16M) | /dev/sdb3

    • Main Windows NTFS partition (70G) | /dev/sdb4

    Also I added for Arch Linux 2 partitions:



    • For / (47.7G) | /dev/sdb5

    • For swap (980.3M) | /dev/sdb6

    HDD disk has 2 partitions:



    • Microsoft reserved (MSR) (16M) | /dev/sda1

    • Some NTFS (900G) | /dev/sda2

    After Windows I installed arch linux from UEFI following the wiki manual.



    GRUB was installed with the usual grub-install without keys



    I tried to configure GRUB with manual config:



    /boot/grub/grub.cfg



    . $prefix/menu.cfg


    /boot/grub/menu.cfg



    set default=0
    set timeout=10
    menuentry "ArchLinux"
    linux /boot/vmlinuz-linux root=/dev/sdb4 rw
    initrd /boot/initramfs-linux.img

    menuentry "Windows"
    regexp -s root '((.+))' "$cmdpath"
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi



    After rebooting just started Windows 10 without any boot menus.



    I installed os-prober and tried grub-mkconfig and get some warning like:
    WARNING: Failed to connect to lvmetad. Falling back to device scanning.

    or
    WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.



    Instead /dev/loop0 was in all partitions.



    And still booting only Windows.



    May be it because my HDD is first in BIOS unlike SSD (hd0 vs hd1)?



    How to fix this problem?



    update: this answer https://askubuntu.com/a/816347/879272 allows me to open grub.



    But why BIOS started EFI/Microsoft/Boot/bootmgfw.efi ignoring another boot loaders.

    Can I disable this behavior?



    fdisk



    EFI










    share|improve this question


























      0












      0








      0







      I have a Dell G3 17 3779 laptop.

      It has sata HDD as hd0 and m.2 ssd as hd1. Both in GPT.



      I deleted everything in the ssd and installed Windows 10.

      I used 4 partitions:



      • Windows recovery environment (499M) | /dev/sdb1

      • EFI System (100M) | /dev/sdb2

      • Microsoft reserved (MSR) (16M) | /dev/sdb3

      • Main Windows NTFS partition (70G) | /dev/sdb4

      Also I added for Arch Linux 2 partitions:



      • For / (47.7G) | /dev/sdb5

      • For swap (980.3M) | /dev/sdb6

      HDD disk has 2 partitions:



      • Microsoft reserved (MSR) (16M) | /dev/sda1

      • Some NTFS (900G) | /dev/sda2

      After Windows I installed arch linux from UEFI following the wiki manual.



      GRUB was installed with the usual grub-install without keys



      I tried to configure GRUB with manual config:



      /boot/grub/grub.cfg



      . $prefix/menu.cfg


      /boot/grub/menu.cfg



      set default=0
      set timeout=10
      menuentry "ArchLinux"
      linux /boot/vmlinuz-linux root=/dev/sdb4 rw
      initrd /boot/initramfs-linux.img

      menuentry "Windows"
      regexp -s root '((.+))' "$cmdpath"
      chainloader /EFI/Microsoft/Boot/bootmgfw.efi



      After rebooting just started Windows 10 without any boot menus.



      I installed os-prober and tried grub-mkconfig and get some warning like:
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.

      or
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.



      Instead /dev/loop0 was in all partitions.



      And still booting only Windows.



      May be it because my HDD is first in BIOS unlike SSD (hd0 vs hd1)?



      How to fix this problem?



      update: this answer https://askubuntu.com/a/816347/879272 allows me to open grub.



      But why BIOS started EFI/Microsoft/Boot/bootmgfw.efi ignoring another boot loaders.

      Can I disable this behavior?



      fdisk



      EFI










      share|improve this question















      I have a Dell G3 17 3779 laptop.

      It has sata HDD as hd0 and m.2 ssd as hd1. Both in GPT.



      I deleted everything in the ssd and installed Windows 10.

      I used 4 partitions:



      • Windows recovery environment (499M) | /dev/sdb1

      • EFI System (100M) | /dev/sdb2

      • Microsoft reserved (MSR) (16M) | /dev/sdb3

      • Main Windows NTFS partition (70G) | /dev/sdb4

      Also I added for Arch Linux 2 partitions:



      • For / (47.7G) | /dev/sdb5

      • For swap (980.3M) | /dev/sdb6

      HDD disk has 2 partitions:



      • Microsoft reserved (MSR) (16M) | /dev/sda1

      • Some NTFS (900G) | /dev/sda2

      After Windows I installed arch linux from UEFI following the wiki manual.



      GRUB was installed with the usual grub-install without keys



      I tried to configure GRUB with manual config:



      /boot/grub/grub.cfg



      . $prefix/menu.cfg


      /boot/grub/menu.cfg



      set default=0
      set timeout=10
      menuentry "ArchLinux"
      linux /boot/vmlinuz-linux root=/dev/sdb4 rw
      initrd /boot/initramfs-linux.img

      menuentry "Windows"
      regexp -s root '((.+))' "$cmdpath"
      chainloader /EFI/Microsoft/Boot/bootmgfw.efi



      After rebooting just started Windows 10 without any boot menus.



      I installed os-prober and tried grub-mkconfig and get some warning like:
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.

      or
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.



      Instead /dev/loop0 was in all partitions.



      And still booting only Windows.



      May be it because my HDD is first in BIOS unlike SSD (hd0 vs hd1)?



      How to fix this problem?



      update: this answer https://askubuntu.com/a/816347/879272 allows me to open grub.



      But why BIOS started EFI/Microsoft/Boot/bootmgfw.efi ignoring another boot loaders.

      Can I disable this behavior?



      fdisk



      EFI







      grub2 dual-boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 25 '18 at 23:43









      Rui F Ribeiro

      39.2k1479130




      39.2k1479130










      asked Dec 23 '18 at 12:00









      MrModest

      1012




      1012




















          3 Answers
          3






          active

          oldest

          votes


















          1














          Several weeks ago I had the same problem on my laptop. It ignored my GRUB2 and start Windows directly. Here is how I solved this problem:



          1. Rename the directory /boot/efi/EFI/Microsoft to Microsoft0

          2. Change the path in chainloader /EFI/Microsoft/Boot/bootmgfw.efi accordingly, to /EFI/Microsoft0/Boot/bootmgfw.efi

          It seems that the BIOS in my laptop will always put Microsoft boot loader at the top of the list, no matter how you configure it. So, renaming the Microsoft directory in the EFI partition can fool the BIOS and it won't boot into Windows automatically.






          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.

















          • Seems like this: askubuntu.com/a/816347/879272 :)
            – MrModest
            19 hours ago


















          0














          I think the BIOS is still telling the G3 to boot Windows.



          The Dell BIOS has a good file browser to select the bootloader. Enter the BIOS setup (maybe F2 or F8) as soon as you see the Dell logo screen and before Windows starts. Next use the file browser to locate the bootloader grubx64.efi you want to boot and select. Then review the boot order and save the new settings to reboot to Grub.






          share|improve this answer






















          • F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
            – MrModest
            Dec 25 '18 at 20:25











          • Anyway, will try something again in weekend
            – MrModest
            Dec 25 '18 at 20:26










          • Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
            – MrModest
            Dec 30 '18 at 14:23










          • Bios boot config: imgur.com/a/CVSabQ4
            – MrModest
            Dec 30 '18 at 15:41










          • Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
            – beginner6789
            Dec 30 '18 at 16:13


















          0














          Maybe there is something wrong with the grubx64.efi bootloader. Here is an amazing utility that can boot anything anywhere without a bootloader:



          SuperGrub2






          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%2f490588%2finstall-grub-when-ssd-is-hd1%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Several weeks ago I had the same problem on my laptop. It ignored my GRUB2 and start Windows directly. Here is how I solved this problem:



            1. Rename the directory /boot/efi/EFI/Microsoft to Microsoft0

            2. Change the path in chainloader /EFI/Microsoft/Boot/bootmgfw.efi accordingly, to /EFI/Microsoft0/Boot/bootmgfw.efi

            It seems that the BIOS in my laptop will always put Microsoft boot loader at the top of the list, no matter how you configure it. So, renaming the Microsoft directory in the EFI partition can fool the BIOS and it won't boot into Windows automatically.






            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.

















            • Seems like this: askubuntu.com/a/816347/879272 :)
              – MrModest
              19 hours ago















            1














            Several weeks ago I had the same problem on my laptop. It ignored my GRUB2 and start Windows directly. Here is how I solved this problem:



            1. Rename the directory /boot/efi/EFI/Microsoft to Microsoft0

            2. Change the path in chainloader /EFI/Microsoft/Boot/bootmgfw.efi accordingly, to /EFI/Microsoft0/Boot/bootmgfw.efi

            It seems that the BIOS in my laptop will always put Microsoft boot loader at the top of the list, no matter how you configure it. So, renaming the Microsoft directory in the EFI partition can fool the BIOS and it won't boot into Windows automatically.






            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.

















            • Seems like this: askubuntu.com/a/816347/879272 :)
              – MrModest
              19 hours ago













            1












            1








            1






            Several weeks ago I had the same problem on my laptop. It ignored my GRUB2 and start Windows directly. Here is how I solved this problem:



            1. Rename the directory /boot/efi/EFI/Microsoft to Microsoft0

            2. Change the path in chainloader /EFI/Microsoft/Boot/bootmgfw.efi accordingly, to /EFI/Microsoft0/Boot/bootmgfw.efi

            It seems that the BIOS in my laptop will always put Microsoft boot loader at the top of the list, no matter how you configure it. So, renaming the Microsoft directory in the EFI partition can fool the BIOS and it won't boot into Windows automatically.






            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.









            Several weeks ago I had the same problem on my laptop. It ignored my GRUB2 and start Windows directly. Here is how I solved this problem:



            1. Rename the directory /boot/efi/EFI/Microsoft to Microsoft0

            2. Change the path in chainloader /EFI/Microsoft/Boot/bootmgfw.efi accordingly, to /EFI/Microsoft0/Boot/bootmgfw.efi

            It seems that the BIOS in my laptop will always put Microsoft boot loader at the top of the list, no matter how you configure it. So, renaming the Microsoft directory in the EFI partition can fool the BIOS and it won't boot into Windows automatically.







            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 22 hours ago









            liuqx

            211




            211




            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.











            • Seems like this: askubuntu.com/a/816347/879272 :)
              – MrModest
              19 hours ago
















            • Seems like this: askubuntu.com/a/816347/879272 :)
              – MrModest
              19 hours ago















            Seems like this: askubuntu.com/a/816347/879272 :)
            – MrModest
            19 hours ago




            Seems like this: askubuntu.com/a/816347/879272 :)
            – MrModest
            19 hours ago













            0














            I think the BIOS is still telling the G3 to boot Windows.



            The Dell BIOS has a good file browser to select the bootloader. Enter the BIOS setup (maybe F2 or F8) as soon as you see the Dell logo screen and before Windows starts. Next use the file browser to locate the bootloader grubx64.efi you want to boot and select. Then review the boot order and save the new settings to reboot to Grub.






            share|improve this answer






















            • F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
              – MrModest
              Dec 25 '18 at 20:25











            • Anyway, will try something again in weekend
              – MrModest
              Dec 25 '18 at 20:26










            • Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
              – MrModest
              Dec 30 '18 at 14:23










            • Bios boot config: imgur.com/a/CVSabQ4
              – MrModest
              Dec 30 '18 at 15:41










            • Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
              – beginner6789
              Dec 30 '18 at 16:13















            0














            I think the BIOS is still telling the G3 to boot Windows.



            The Dell BIOS has a good file browser to select the bootloader. Enter the BIOS setup (maybe F2 or F8) as soon as you see the Dell logo screen and before Windows starts. Next use the file browser to locate the bootloader grubx64.efi you want to boot and select. Then review the boot order and save the new settings to reboot to Grub.






            share|improve this answer






















            • F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
              – MrModest
              Dec 25 '18 at 20:25











            • Anyway, will try something again in weekend
              – MrModest
              Dec 25 '18 at 20:26










            • Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
              – MrModest
              Dec 30 '18 at 14:23










            • Bios boot config: imgur.com/a/CVSabQ4
              – MrModest
              Dec 30 '18 at 15:41










            • Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
              – beginner6789
              Dec 30 '18 at 16:13













            0












            0








            0






            I think the BIOS is still telling the G3 to boot Windows.



            The Dell BIOS has a good file browser to select the bootloader. Enter the BIOS setup (maybe F2 or F8) as soon as you see the Dell logo screen and before Windows starts. Next use the file browser to locate the bootloader grubx64.efi you want to boot and select. Then review the boot order and save the new settings to reboot to Grub.






            share|improve this answer














            I think the BIOS is still telling the G3 to boot Windows.



            The Dell BIOS has a good file browser to select the bootloader. Enter the BIOS setup (maybe F2 or F8) as soon as you see the Dell logo screen and before Windows starts. Next use the file browser to locate the bootloader grubx64.efi you want to boot and select. Then review the boot order and save the new settings to reboot to Grub.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 25 '18 at 23:44









            Rui F Ribeiro

            39.2k1479130




            39.2k1479130










            answered Dec 25 '18 at 11:56









            beginner6789

            914




            914











            • F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
              – MrModest
              Dec 25 '18 at 20:25











            • Anyway, will try something again in weekend
              – MrModest
              Dec 25 '18 at 20:26










            • Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
              – MrModest
              Dec 30 '18 at 14:23










            • Bios boot config: imgur.com/a/CVSabQ4
              – MrModest
              Dec 30 '18 at 15:41










            • Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
              – beginner6789
              Dec 30 '18 at 16:13
















            • F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
              – MrModest
              Dec 25 '18 at 20:25











            • Anyway, will try something again in weekend
              – MrModest
              Dec 25 '18 at 20:26










            • Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
              – MrModest
              Dec 30 '18 at 14:23










            • Bios boot config: imgur.com/a/CVSabQ4
              – MrModest
              Dec 30 '18 at 15:41










            • Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
              – beginner6789
              Dec 30 '18 at 16:13















            F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
            – MrModest
            Dec 25 '18 at 20:25





            F12, then choose Setup Bios. I saw boot menu and grubx64.efi was before than Windows Boot Manager in Boot Order
            – MrModest
            Dec 25 '18 at 20:25













            Anyway, will try something again in weekend
            – MrModest
            Dec 25 '18 at 20:26




            Anyway, will try something again in weekend
            – MrModest
            Dec 25 '18 at 20:26












            Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
            – MrModest
            Dec 30 '18 at 14:23




            Now I tried again install arch and grub. After rebooting started Windows. When I open boot menu (F12) and choose arch started Support Assistent memory test
            – MrModest
            Dec 30 '18 at 14:23












            Bios boot config: imgur.com/a/CVSabQ4
            – MrModest
            Dec 30 '18 at 15:41




            Bios boot config: imgur.com/a/CVSabQ4
            – MrModest
            Dec 30 '18 at 15:41












            Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
            – beginner6789
            Dec 30 '18 at 16:13




            Could you try to go into the BIOS and turn off the HDD in the SATA section leaving just the SSD to boot? If you can boot to Arch then maybe try to install another kernel and see if the pacman makes a good grubx64.efi automatically? You are very close now.
            – beginner6789
            Dec 30 '18 at 16:13











            0














            Maybe there is something wrong with the grubx64.efi bootloader. Here is an amazing utility that can boot anything anywhere without a bootloader:



            SuperGrub2






            share|improve this answer

























              0














              Maybe there is something wrong with the grubx64.efi bootloader. Here is an amazing utility that can boot anything anywhere without a bootloader:



              SuperGrub2






              share|improve this answer























                0












                0








                0






                Maybe there is something wrong with the grubx64.efi bootloader. Here is an amazing utility that can boot anything anywhere without a bootloader:



                SuperGrub2






                share|improve this answer












                Maybe there is something wrong with the grubx64.efi bootloader. Here is an amazing utility that can boot anything anywhere without a bootloader:



                SuperGrub2







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 26 '18 at 0:36









                beginner6789

                914




                914



























                    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%2f490588%2finstall-grub-when-ssd-is-hd1%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

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay