How to avoid mounting partition at startup in Ubuntu 17.10

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








up vote
0
down vote

favorite












How to avoid mounting partition at startup in Ubuntu 17.10 in dual boot? I have 2 installations on the different device, one not mounts the partitions at startup/login, another mount all partitions found. Is there a configuration to switch on/off globally this behavior?



This is my fstab and blkid:



https://pastebin.ubuntu.com/p/fyCdTqCWdt/







share|improve this question


























    up vote
    0
    down vote

    favorite












    How to avoid mounting partition at startup in Ubuntu 17.10 in dual boot? I have 2 installations on the different device, one not mounts the partitions at startup/login, another mount all partitions found. Is there a configuration to switch on/off globally this behavior?



    This is my fstab and blkid:



    https://pastebin.ubuntu.com/p/fyCdTqCWdt/







    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      How to avoid mounting partition at startup in Ubuntu 17.10 in dual boot? I have 2 installations on the different device, one not mounts the partitions at startup/login, another mount all partitions found. Is there a configuration to switch on/off globally this behavior?



      This is my fstab and blkid:



      https://pastebin.ubuntu.com/p/fyCdTqCWdt/







      share|improve this question














      How to avoid mounting partition at startup in Ubuntu 17.10 in dual boot? I have 2 installations on the different device, one not mounts the partitions at startup/login, another mount all partitions found. Is there a configuration to switch on/off globally this behavior?



      This is my fstab and blkid:



      https://pastebin.ubuntu.com/p/fyCdTqCWdt/









      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 25 at 7:49

























      asked Apr 24 at 18:29









      rkpisanu

      263




      263




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The file /etc/fstab is where all disk mounts occur at boot time.



          Your second computer's /etc/fstab has additional disk mounts that the first computer doesn't perform.



          To change the behaviour of the second computer, edit the /etc/fstab file, like so...



          In terminal...



          sudo cp /etc/fstab /etc/fstab.bck # to make a backup of the file



          sudo pico /etc/fstab # edit the file



          locate individual disk mounts, and place a # comment marker at the beginning of that line.



          Example:



          change:



          UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          to:



          #UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          then:



          control+o # to save the edits



          return # to confirm the filename to save



          control+x # to exit the editor



          reboot



          Update #1:



          After reviewing your blkid and fstab, it looks like you've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.



          Update #2:



          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that. Use tune2fs to change to unique UUID's.






          share|improve this answer






















          • I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
            – rkpisanu
            Apr 25 at 7:50











          • @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
            – heynnema
            Apr 25 at 11:39










          • @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
            – heynnema
            Apr 25 at 11:40










          • It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
            – rkpisanu
            Apr 25 at 17:57










          • You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
            – heynnema
            Apr 25 at 20:45











          Your Answer







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

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

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027895%2fhow-to-avoid-mounting-partition-at-startup-in-ubuntu-17-10%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          The file /etc/fstab is where all disk mounts occur at boot time.



          Your second computer's /etc/fstab has additional disk mounts that the first computer doesn't perform.



          To change the behaviour of the second computer, edit the /etc/fstab file, like so...



          In terminal...



          sudo cp /etc/fstab /etc/fstab.bck # to make a backup of the file



          sudo pico /etc/fstab # edit the file



          locate individual disk mounts, and place a # comment marker at the beginning of that line.



          Example:



          change:



          UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          to:



          #UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          then:



          control+o # to save the edits



          return # to confirm the filename to save



          control+x # to exit the editor



          reboot



          Update #1:



          After reviewing your blkid and fstab, it looks like you've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.



          Update #2:



          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that. Use tune2fs to change to unique UUID's.






          share|improve this answer






















          • I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
            – rkpisanu
            Apr 25 at 7:50











          • @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
            – heynnema
            Apr 25 at 11:39










          • @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
            – heynnema
            Apr 25 at 11:40










          • It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
            – rkpisanu
            Apr 25 at 17:57










          • You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
            – heynnema
            Apr 25 at 20:45















          up vote
          0
          down vote













          The file /etc/fstab is where all disk mounts occur at boot time.



          Your second computer's /etc/fstab has additional disk mounts that the first computer doesn't perform.



          To change the behaviour of the second computer, edit the /etc/fstab file, like so...



          In terminal...



          sudo cp /etc/fstab /etc/fstab.bck # to make a backup of the file



          sudo pico /etc/fstab # edit the file



          locate individual disk mounts, and place a # comment marker at the beginning of that line.



          Example:



          change:



          UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          to:



          #UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          then:



          control+o # to save the edits



          return # to confirm the filename to save



          control+x # to exit the editor



          reboot



          Update #1:



          After reviewing your blkid and fstab, it looks like you've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.



          Update #2:



          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that. Use tune2fs to change to unique UUID's.






          share|improve this answer






















          • I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
            – rkpisanu
            Apr 25 at 7:50











          • @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
            – heynnema
            Apr 25 at 11:39










          • @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
            – heynnema
            Apr 25 at 11:40










          • It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
            – rkpisanu
            Apr 25 at 17:57










          • You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
            – heynnema
            Apr 25 at 20:45













          up vote
          0
          down vote










          up vote
          0
          down vote









          The file /etc/fstab is where all disk mounts occur at boot time.



          Your second computer's /etc/fstab has additional disk mounts that the first computer doesn't perform.



          To change the behaviour of the second computer, edit the /etc/fstab file, like so...



          In terminal...



          sudo cp /etc/fstab /etc/fstab.bck # to make a backup of the file



          sudo pico /etc/fstab # edit the file



          locate individual disk mounts, and place a # comment marker at the beginning of that line.



          Example:



          change:



          UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          to:



          #UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          then:



          control+o # to save the edits



          return # to confirm the filename to save



          control+x # to exit the editor



          reboot



          Update #1:



          After reviewing your blkid and fstab, it looks like you've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.



          Update #2:



          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that. Use tune2fs to change to unique UUID's.






          share|improve this answer














          The file /etc/fstab is where all disk mounts occur at boot time.



          Your second computer's /etc/fstab has additional disk mounts that the first computer doesn't perform.



          To change the behaviour of the second computer, edit the /etc/fstab file, like so...



          In terminal...



          sudo cp /etc/fstab /etc/fstab.bck # to make a backup of the file



          sudo pico /etc/fstab # edit the file



          locate individual disk mounts, and place a # comment marker at the beginning of that line.



          Example:



          change:



          UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          to:



          #UUID=0C0F93CE58153D42 /media/username/Shared_Data ntfs-3g defaults 0 0



          then:



          control+o # to save the edits



          return # to confirm the filename to save



          control+x # to exit the editor



          reboot



          Update #1:



          After reviewing your blkid and fstab, it looks like you've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.



          Update #2:



          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that. Use tune2fs to change to unique UUID's.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 26 at 13:43

























          answered Apr 24 at 23:51









          heynnema

          15.4k21945




          15.4k21945











          • I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
            – rkpisanu
            Apr 25 at 7:50











          • @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
            – heynnema
            Apr 25 at 11:39










          • @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
            – heynnema
            Apr 25 at 11:40










          • It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
            – rkpisanu
            Apr 25 at 17:57










          • You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
            – heynnema
            Apr 25 at 20:45

















          • I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
            – rkpisanu
            Apr 25 at 7:50











          • @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
            – heynnema
            Apr 25 at 11:39










          • @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
            – heynnema
            Apr 25 at 11:40










          • It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
            – rkpisanu
            Apr 25 at 17:57










          • You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
            – heynnema
            Apr 25 at 20:45
















          I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
          – rkpisanu
          Apr 25 at 7:50





          I added my fstab and blkid configuration. The partitions aren't listed in the fstab, very strange.
          – rkpisanu
          Apr 25 at 7:50













          @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
          – heynnema
          Apr 25 at 11:39




          @rkpisanu You've got an Android Development System (?) installed on your SSD that's created a bunch of ext4/ntfs partitions that get mounted. You've also got a second /boot/efi partition at /dev/sda4.
          – heynnema
          Apr 25 at 11:39












          @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
          – heynnema
          Apr 25 at 11:40




          @rkpisanu if my answer(s) were helpful, please remember to vote/accept them. Thanks.
          – heynnema
          Apr 25 at 11:40












          It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
          – rkpisanu
          Apr 25 at 17:57




          It is not an Android Development, it is Alfawise x5 mini pc. I resolve using GNOME Disks and set noauto flag to emmc partitions. But my question remains, because in other devices there isn't automount feature.
          – rkpisanu
          Apr 25 at 17:57












          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
          – heynnema
          Apr 25 at 20:45





          You have 4 partitions with the same UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b". Can't do that.
          – heynnema
          Apr 25 at 20:45


















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027895%2fhow-to-avoid-mounting-partition-at-startup-in-ubuntu-17-10%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491