How to stop update-grub from scanning all drives?












15














Every time update-grub is run all hard drives are scanned. Each drives that is in standby state will spin up to go idle. This is a waste of energy. We use update-grub version 1.98:



# update-grub -v
grub-mkconfig (GRUB) 1.98+20100804-14+squeeze1


Regression




  1. There is a GRUB_DISABLE_OS_PROBER=true option in the /etc/default/grub file. But that seems to only work from version 2 and up. At least it doesn't stop scanning all drives in our version 1.98.


  2. There is a /etc/grub.d/20_linux_xen script that might be run as a part of update-grub. After removing execute rights for all users with chmod a-x /etc/grub.d/20_linux_xen all drives do still spin up.



How to stop update-grub from scanning each and every hard drive?










share|improve this question
























  • It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
    – jordanm
    Nov 17 '12 at 23:04










  • One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
    – Pro Backup
    Nov 17 '12 at 23:17










  • How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
    – psusi
    Nov 18 '12 at 3:00










  • I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
    – tkbx
    Dec 29 '12 at 21:01
















15














Every time update-grub is run all hard drives are scanned. Each drives that is in standby state will spin up to go idle. This is a waste of energy. We use update-grub version 1.98:



# update-grub -v
grub-mkconfig (GRUB) 1.98+20100804-14+squeeze1


Regression




  1. There is a GRUB_DISABLE_OS_PROBER=true option in the /etc/default/grub file. But that seems to only work from version 2 and up. At least it doesn't stop scanning all drives in our version 1.98.


  2. There is a /etc/grub.d/20_linux_xen script that might be run as a part of update-grub. After removing execute rights for all users with chmod a-x /etc/grub.d/20_linux_xen all drives do still spin up.



How to stop update-grub from scanning each and every hard drive?










share|improve this question
























  • It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
    – jordanm
    Nov 17 '12 at 23:04










  • One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
    – Pro Backup
    Nov 17 '12 at 23:17










  • How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
    – psusi
    Nov 18 '12 at 3:00










  • I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
    – tkbx
    Dec 29 '12 at 21:01














15












15








15


6





Every time update-grub is run all hard drives are scanned. Each drives that is in standby state will spin up to go idle. This is a waste of energy. We use update-grub version 1.98:



# update-grub -v
grub-mkconfig (GRUB) 1.98+20100804-14+squeeze1


Regression




  1. There is a GRUB_DISABLE_OS_PROBER=true option in the /etc/default/grub file. But that seems to only work from version 2 and up. At least it doesn't stop scanning all drives in our version 1.98.


  2. There is a /etc/grub.d/20_linux_xen script that might be run as a part of update-grub. After removing execute rights for all users with chmod a-x /etc/grub.d/20_linux_xen all drives do still spin up.



How to stop update-grub from scanning each and every hard drive?










share|improve this question















Every time update-grub is run all hard drives are scanned. Each drives that is in standby state will spin up to go idle. This is a waste of energy. We use update-grub version 1.98:



# update-grub -v
grub-mkconfig (GRUB) 1.98+20100804-14+squeeze1


Regression




  1. There is a GRUB_DISABLE_OS_PROBER=true option in the /etc/default/grub file. But that seems to only work from version 2 and up. At least it doesn't stop scanning all drives in our version 1.98.


  2. There is a /etc/grub.d/20_linux_xen script that might be run as a part of update-grub. After removing execute rights for all users with chmod a-x /etc/grub.d/20_linux_xen all drives do still spin up.



How to stop update-grub from scanning each and every hard drive?







debian grub






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '12 at 21:40

























asked Nov 17 '12 at 21:30









Pro Backup

1,96062957




1,96062957












  • It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
    – jordanm
    Nov 17 '12 at 23:04










  • One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
    – Pro Backup
    Nov 17 '12 at 23:17










  • How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
    – psusi
    Nov 18 '12 at 3:00










  • I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
    – tkbx
    Dec 29 '12 at 21:01


















  • It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
    – jordanm
    Nov 17 '12 at 23:04










  • One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
    – Pro Backup
    Nov 17 '12 at 23:17










  • How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
    – psusi
    Nov 18 '12 at 3:00










  • I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
    – tkbx
    Dec 29 '12 at 21:01
















It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
– jordanm
Nov 17 '12 at 23:04




It's just a shell script... Modify it? It should only run after kernel updates, which doesn't occur very often.
– jordanm
Nov 17 '12 at 23:04












One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
– Pro Backup
Nov 17 '12 at 23:17




One of the script lines executes /usr/sbin/grub-probe --target=device /. That command also causes all drives to spin up. The /usr/sbin/grub-probe is not a shell script.
– Pro Backup
Nov 17 '12 at 23:17












How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
– psusi
Nov 18 '12 at 3:00




How often are you running update-grub? This should only happen when you install a new kernel, so who cares?
– psusi
Nov 18 '12 at 3:00












I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
– tkbx
Dec 29 '12 at 21:01




I know, that entire picojoule it uses is such a waste - if you ran update-grub 24/7 for a month on 1000 computers with 3 HDDs each, it might add a cent or two to your electric bill.
– tkbx
Dec 29 '12 at 21:01










5 Answers
5






active

oldest

votes


















12














In file /etc/grub.d/30_os-prober the line



OSPROBED="`os-prober | tr ' ' '^' | paste -s -d ' '`"


makes all drives spin (standby -> idle). Os-prober is a utility to find Linux installations at drives other then your boot drive. It is the os-prober that needs to be disabled.




  1. One way is to remove the package: apt-get --purge remove os-prober.

  2. Another way is to remove executable rights for os-prober. First find the location of os-prober using $ which os-prober. Output might look like: /usr/bin/os-prober. The remove the executable rights for all users for that file: # chmod a-x /usr/bin/os-prober

  3. Another way is to remove executable rights for 30_os-prober. Find the location of 30_os-prober using $ locate /30_os-prober. Output might look like: /etc/grub.d/30_os-prober. The remove the executable rights for all users for that file: # chmod a-x /etc/grub.d/30_os-prober

  4. Yet another way is to skip the execution of /etc/grub.d/30_os-prober. For example by making the GRUB_DISABLE_OS_PROBER=true option work in our grub version 1.98. This can be done by inserting in file /etc/grub.d/30_os-prober the code below the line set -e:


...



if [ "x${GRUB_DISABLE_OS_PROBER}" = "xtrue" ]; then
exit 0
fi





share|improve this answer





























    5














    For those wondering if it's really worth the effort, yes it is. Perhaps not for energy saving but today I encountered a problem with update-grub as it wanted to probe for both /dev/sda (my harddisk) and /dev/sdc (a USB-stick). Without the latter inserted into my laptop, update-grub would hang, even though there is actually no OS on my USB-stick installed nor did I ever boot from this stick. As the USB-stick recently broke, I needed a way for update-grub to continue (alive) without it. Fortuately, GRUB_DISABLE_OS_PROBER=true just did the trick. :)






    share|improve this answer

















    • 1




      I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
      – noamik
      Jul 10 '17 at 15:48



















    3














    (Is this really worth the time and effort to fix?)



    As you mentioned, the probing is probably happening when grub-mkconfig calls grub-probe. You could modify grub-mkconfig by simply hardcoding the result of the grub-probe calls. It is used to fill GRUB_DEVICE, GRUB_DEVICE_UUID, GRUB_DEVICE_BOOT, GRUB_DEVICE_BOOT_UUID, and GRUB_FS.






    share|improve this answer





























      0














      See my solution here to selectively disable which partitions are checked by os-prober with a small patch.



      The configuration of GRUB_OS_PROBER_SKIP_LIST="UUID@device_path" in /etc/default/grub:




      • reduces the numbers of devices in ${OSPROBED} used by /etc/grub.d/30_os-prober


      • which stops the check with ${grub_probe} --target=fs_uuid --device







      share|improve this answer





























        0














        I know this is an old post, but I found another way to accomplish this that doesn't involve making changes to the scripts. in /etc/grub.d/ I renamed the file 30_os-prober to .30_os-prober (start with a period) and it is skipped during the update even though it shows in the same place in ls if you use -a.






        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%2f56004%2fhow-to-stop-update-grub-from-scanning-all-drives%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          12














          In file /etc/grub.d/30_os-prober the line



          OSPROBED="`os-prober | tr ' ' '^' | paste -s -d ' '`"


          makes all drives spin (standby -> idle). Os-prober is a utility to find Linux installations at drives other then your boot drive. It is the os-prober that needs to be disabled.




          1. One way is to remove the package: apt-get --purge remove os-prober.

          2. Another way is to remove executable rights for os-prober. First find the location of os-prober using $ which os-prober. Output might look like: /usr/bin/os-prober. The remove the executable rights for all users for that file: # chmod a-x /usr/bin/os-prober

          3. Another way is to remove executable rights for 30_os-prober. Find the location of 30_os-prober using $ locate /30_os-prober. Output might look like: /etc/grub.d/30_os-prober. The remove the executable rights for all users for that file: # chmod a-x /etc/grub.d/30_os-prober

          4. Yet another way is to skip the execution of /etc/grub.d/30_os-prober. For example by making the GRUB_DISABLE_OS_PROBER=true option work in our grub version 1.98. This can be done by inserting in file /etc/grub.d/30_os-prober the code below the line set -e:


          ...



          if [ "x${GRUB_DISABLE_OS_PROBER}" = "xtrue" ]; then
          exit 0
          fi





          share|improve this answer


























            12














            In file /etc/grub.d/30_os-prober the line



            OSPROBED="`os-prober | tr ' ' '^' | paste -s -d ' '`"


            makes all drives spin (standby -> idle). Os-prober is a utility to find Linux installations at drives other then your boot drive. It is the os-prober that needs to be disabled.




            1. One way is to remove the package: apt-get --purge remove os-prober.

            2. Another way is to remove executable rights for os-prober. First find the location of os-prober using $ which os-prober. Output might look like: /usr/bin/os-prober. The remove the executable rights for all users for that file: # chmod a-x /usr/bin/os-prober

            3. Another way is to remove executable rights for 30_os-prober. Find the location of 30_os-prober using $ locate /30_os-prober. Output might look like: /etc/grub.d/30_os-prober. The remove the executable rights for all users for that file: # chmod a-x /etc/grub.d/30_os-prober

            4. Yet another way is to skip the execution of /etc/grub.d/30_os-prober. For example by making the GRUB_DISABLE_OS_PROBER=true option work in our grub version 1.98. This can be done by inserting in file /etc/grub.d/30_os-prober the code below the line set -e:


            ...



            if [ "x${GRUB_DISABLE_OS_PROBER}" = "xtrue" ]; then
            exit 0
            fi





            share|improve this answer
























              12












              12








              12






              In file /etc/grub.d/30_os-prober the line



              OSPROBED="`os-prober | tr ' ' '^' | paste -s -d ' '`"


              makes all drives spin (standby -> idle). Os-prober is a utility to find Linux installations at drives other then your boot drive. It is the os-prober that needs to be disabled.




              1. One way is to remove the package: apt-get --purge remove os-prober.

              2. Another way is to remove executable rights for os-prober. First find the location of os-prober using $ which os-prober. Output might look like: /usr/bin/os-prober. The remove the executable rights for all users for that file: # chmod a-x /usr/bin/os-prober

              3. Another way is to remove executable rights for 30_os-prober. Find the location of 30_os-prober using $ locate /30_os-prober. Output might look like: /etc/grub.d/30_os-prober. The remove the executable rights for all users for that file: # chmod a-x /etc/grub.d/30_os-prober

              4. Yet another way is to skip the execution of /etc/grub.d/30_os-prober. For example by making the GRUB_DISABLE_OS_PROBER=true option work in our grub version 1.98. This can be done by inserting in file /etc/grub.d/30_os-prober the code below the line set -e:


              ...



              if [ "x${GRUB_DISABLE_OS_PROBER}" = "xtrue" ]; then
              exit 0
              fi





              share|improve this answer












              In file /etc/grub.d/30_os-prober the line



              OSPROBED="`os-prober | tr ' ' '^' | paste -s -d ' '`"


              makes all drives spin (standby -> idle). Os-prober is a utility to find Linux installations at drives other then your boot drive. It is the os-prober that needs to be disabled.




              1. One way is to remove the package: apt-get --purge remove os-prober.

              2. Another way is to remove executable rights for os-prober. First find the location of os-prober using $ which os-prober. Output might look like: /usr/bin/os-prober. The remove the executable rights for all users for that file: # chmod a-x /usr/bin/os-prober

              3. Another way is to remove executable rights for 30_os-prober. Find the location of 30_os-prober using $ locate /30_os-prober. Output might look like: /etc/grub.d/30_os-prober. The remove the executable rights for all users for that file: # chmod a-x /etc/grub.d/30_os-prober

              4. Yet another way is to skip the execution of /etc/grub.d/30_os-prober. For example by making the GRUB_DISABLE_OS_PROBER=true option work in our grub version 1.98. This can be done by inserting in file /etc/grub.d/30_os-prober the code below the line set -e:


              ...



              if [ "x${GRUB_DISABLE_OS_PROBER}" = "xtrue" ]; then
              exit 0
              fi






              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Dec 29 '12 at 17:34









              Pro Backup

              1,96062957




              1,96062957

























                  5














                  For those wondering if it's really worth the effort, yes it is. Perhaps not for energy saving but today I encountered a problem with update-grub as it wanted to probe for both /dev/sda (my harddisk) and /dev/sdc (a USB-stick). Without the latter inserted into my laptop, update-grub would hang, even though there is actually no OS on my USB-stick installed nor did I ever boot from this stick. As the USB-stick recently broke, I needed a way for update-grub to continue (alive) without it. Fortuately, GRUB_DISABLE_OS_PROBER=true just did the trick. :)






                  share|improve this answer

















                  • 1




                    I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                    – noamik
                    Jul 10 '17 at 15:48
















                  5














                  For those wondering if it's really worth the effort, yes it is. Perhaps not for energy saving but today I encountered a problem with update-grub as it wanted to probe for both /dev/sda (my harddisk) and /dev/sdc (a USB-stick). Without the latter inserted into my laptop, update-grub would hang, even though there is actually no OS on my USB-stick installed nor did I ever boot from this stick. As the USB-stick recently broke, I needed a way for update-grub to continue (alive) without it. Fortuately, GRUB_DISABLE_OS_PROBER=true just did the trick. :)






                  share|improve this answer

















                  • 1




                    I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                    – noamik
                    Jul 10 '17 at 15:48














                  5












                  5








                  5






                  For those wondering if it's really worth the effort, yes it is. Perhaps not for energy saving but today I encountered a problem with update-grub as it wanted to probe for both /dev/sda (my harddisk) and /dev/sdc (a USB-stick). Without the latter inserted into my laptop, update-grub would hang, even though there is actually no OS on my USB-stick installed nor did I ever boot from this stick. As the USB-stick recently broke, I needed a way for update-grub to continue (alive) without it. Fortuately, GRUB_DISABLE_OS_PROBER=true just did the trick. :)






                  share|improve this answer












                  For those wondering if it's really worth the effort, yes it is. Perhaps not for energy saving but today I encountered a problem with update-grub as it wanted to probe for both /dev/sda (my harddisk) and /dev/sdc (a USB-stick). Without the latter inserted into my laptop, update-grub would hang, even though there is actually no OS on my USB-stick installed nor did I ever boot from this stick. As the USB-stick recently broke, I needed a way for update-grub to continue (alive) without it. Fortuately, GRUB_DISABLE_OS_PROBER=true just did the trick. :)







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 25 '14 at 9:19









                  PPP

                  5111




                  5111








                  • 1




                    I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                    – noamik
                    Jul 10 '17 at 15:48














                  • 1




                    I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                    – noamik
                    Jul 10 '17 at 15:48








                  1




                  1




                  I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                  – noamik
                  Jul 10 '17 at 15:48




                  I had the inverse problem: update-grub failing if an USB stick was present. The USB stick was a bit unusual, since it has Easy2Boot installed. But since this was on a kiosk with the update-grub command being issued from a script placed on that very USB stick, this solution was very welcome.
                  – noamik
                  Jul 10 '17 at 15:48











                  3














                  (Is this really worth the time and effort to fix?)



                  As you mentioned, the probing is probably happening when grub-mkconfig calls grub-probe. You could modify grub-mkconfig by simply hardcoding the result of the grub-probe calls. It is used to fill GRUB_DEVICE, GRUB_DEVICE_UUID, GRUB_DEVICE_BOOT, GRUB_DEVICE_BOOT_UUID, and GRUB_FS.






                  share|improve this answer


























                    3














                    (Is this really worth the time and effort to fix?)



                    As you mentioned, the probing is probably happening when grub-mkconfig calls grub-probe. You could modify grub-mkconfig by simply hardcoding the result of the grub-probe calls. It is used to fill GRUB_DEVICE, GRUB_DEVICE_UUID, GRUB_DEVICE_BOOT, GRUB_DEVICE_BOOT_UUID, and GRUB_FS.






                    share|improve this answer
























                      3












                      3








                      3






                      (Is this really worth the time and effort to fix?)



                      As you mentioned, the probing is probably happening when grub-mkconfig calls grub-probe. You could modify grub-mkconfig by simply hardcoding the result of the grub-probe calls. It is used to fill GRUB_DEVICE, GRUB_DEVICE_UUID, GRUB_DEVICE_BOOT, GRUB_DEVICE_BOOT_UUID, and GRUB_FS.






                      share|improve this answer












                      (Is this really worth the time and effort to fix?)



                      As you mentioned, the probing is probably happening when grub-mkconfig calls grub-probe. You could modify grub-mkconfig by simply hardcoding the result of the grub-probe calls. It is used to fill GRUB_DEVICE, GRUB_DEVICE_UUID, GRUB_DEVICE_BOOT, GRUB_DEVICE_BOOT_UUID, and GRUB_FS.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 18 '12 at 0:26









                      Jim Paris

                      11.3k42330




                      11.3k42330























                          0














                          See my solution here to selectively disable which partitions are checked by os-prober with a small patch.



                          The configuration of GRUB_OS_PROBER_SKIP_LIST="UUID@device_path" in /etc/default/grub:




                          • reduces the numbers of devices in ${OSPROBED} used by /etc/grub.d/30_os-prober


                          • which stops the check with ${grub_probe} --target=fs_uuid --device







                          share|improve this answer


























                            0














                            See my solution here to selectively disable which partitions are checked by os-prober with a small patch.



                            The configuration of GRUB_OS_PROBER_SKIP_LIST="UUID@device_path" in /etc/default/grub:




                            • reduces the numbers of devices in ${OSPROBED} used by /etc/grub.d/30_os-prober


                            • which stops the check with ${grub_probe} --target=fs_uuid --device







                            share|improve this answer
























                              0












                              0








                              0






                              See my solution here to selectively disable which partitions are checked by os-prober with a small patch.



                              The configuration of GRUB_OS_PROBER_SKIP_LIST="UUID@device_path" in /etc/default/grub:




                              • reduces the numbers of devices in ${OSPROBED} used by /etc/grub.d/30_os-prober


                              • which stops the check with ${grub_probe} --target=fs_uuid --device







                              share|improve this answer












                              See my solution here to selectively disable which partitions are checked by os-prober with a small patch.



                              The configuration of GRUB_OS_PROBER_SKIP_LIST="UUID@device_path" in /etc/default/grub:




                              • reduces the numbers of devices in ${OSPROBED} used by /etc/grub.d/30_os-prober


                              • which stops the check with ${grub_probe} --target=fs_uuid --device








                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Oct 15 at 20:32









                              Stuart Cardall

                              791510




                              791510























                                  0














                                  I know this is an old post, but I found another way to accomplish this that doesn't involve making changes to the scripts. in /etc/grub.d/ I renamed the file 30_os-prober to .30_os-prober (start with a period) and it is skipped during the update even though it shows in the same place in ls if you use -a.






                                  share|improve this answer




























                                    0














                                    I know this is an old post, but I found another way to accomplish this that doesn't involve making changes to the scripts. in /etc/grub.d/ I renamed the file 30_os-prober to .30_os-prober (start with a period) and it is skipped during the update even though it shows in the same place in ls if you use -a.






                                    share|improve this answer


























                                      0












                                      0








                                      0






                                      I know this is an old post, but I found another way to accomplish this that doesn't involve making changes to the scripts. in /etc/grub.d/ I renamed the file 30_os-prober to .30_os-prober (start with a period) and it is skipped during the update even though it shows in the same place in ls if you use -a.






                                      share|improve this answer














                                      I know this is an old post, but I found another way to accomplish this that doesn't involve making changes to the scripts. in /etc/grub.d/ I renamed the file 30_os-prober to .30_os-prober (start with a period) and it is skipped during the update even though it shows in the same place in ls if you use -a.







                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Dec 10 at 22:13









                                      Pro Backup

                                      1,96062957




                                      1,96062957










                                      answered Dec 8 at 21:30









                                      James

                                      1




                                      1






























                                          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%2f56004%2fhow-to-stop-update-grub-from-scanning-all-drives%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