Removable volume not appearing in file managers

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












0















Neither Nautilus, Caja or Thunar show my removable storage device in the list of devices.



I can mount it manually using udisksctl:



$ udisksctl mount --block-device /dev/sdd1 Mounted /dev/sdd1 at
/run/media/user/RECOVERY.


It shows up in gvfs:



$ gio mount -l
...
"Drive(4): Generic Flash Disk


But gvfs can't mount it:



$ gio mount -d /dev/sdd1 
gio: /dev/sdd1: No volume for device file"


Nothing I've tried seems to work.










share|improve this question


























    0















    Neither Nautilus, Caja or Thunar show my removable storage device in the list of devices.



    I can mount it manually using udisksctl:



    $ udisksctl mount --block-device /dev/sdd1 Mounted /dev/sdd1 at
    /run/media/user/RECOVERY.


    It shows up in gvfs:



    $ gio mount -l
    ...
    "Drive(4): Generic Flash Disk


    But gvfs can't mount it:



    $ gio mount -d /dev/sdd1 
    gio: /dev/sdd1: No volume for device file"


    Nothing I've tried seems to work.










    share|improve this question
























      0












      0








      0








      Neither Nautilus, Caja or Thunar show my removable storage device in the list of devices.



      I can mount it manually using udisksctl:



      $ udisksctl mount --block-device /dev/sdd1 Mounted /dev/sdd1 at
      /run/media/user/RECOVERY.


      It shows up in gvfs:



      $ gio mount -l
      ...
      "Drive(4): Generic Flash Disk


      But gvfs can't mount it:



      $ gio mount -d /dev/sdd1 
      gio: /dev/sdd1: No volume for device file"


      Nothing I've tried seems to work.










      share|improve this question














      Neither Nautilus, Caja or Thunar show my removable storage device in the list of devices.



      I can mount it manually using udisksctl:



      $ udisksctl mount --block-device /dev/sdd1 Mounted /dev/sdd1 at
      /run/media/user/RECOVERY.


      It shows up in gvfs:



      $ gio mount -l
      ...
      "Drive(4): Generic Flash Disk


      But gvfs can't mount it:



      $ gio mount -d /dev/sdd1 
      gio: /dev/sdd1: No volume for device file"


      Nothing I've tried seems to work.







      file-manager udisks gvfs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 16 at 15:33









      Emily L.Emily L.

      1858




      1858




















          1 Answer
          1






          active

          oldest

          votes


















          1














          It turns out that udisks has an attribute for drives that marks them as ignored.



          You can see if this attribute is set with the following:



          $ udevadm info /dev/sdd1 | grep -i ignore
          UDISKS_IGNORE=1


          Udisks sets this attribute on devices based on heuristics and configuration. See man udisks and search for ignore.



          In this case it turns out that partitions named "RECOVERY" among others are set as ignored by the default udev rules. See here.



          So the solution was to rename my linux recovery usb stick to something else than "RECOVERY".






          share|improve this answer























          • Now that was a quick solution.

            – Panki
            Jan 16 at 16:28










          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%2f494856%2fremovable-volume-not-appearing-in-file-managers%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          It turns out that udisks has an attribute for drives that marks them as ignored.



          You can see if this attribute is set with the following:



          $ udevadm info /dev/sdd1 | grep -i ignore
          UDISKS_IGNORE=1


          Udisks sets this attribute on devices based on heuristics and configuration. See man udisks and search for ignore.



          In this case it turns out that partitions named "RECOVERY" among others are set as ignored by the default udev rules. See here.



          So the solution was to rename my linux recovery usb stick to something else than "RECOVERY".






          share|improve this answer























          • Now that was a quick solution.

            – Panki
            Jan 16 at 16:28















          1














          It turns out that udisks has an attribute for drives that marks them as ignored.



          You can see if this attribute is set with the following:



          $ udevadm info /dev/sdd1 | grep -i ignore
          UDISKS_IGNORE=1


          Udisks sets this attribute on devices based on heuristics and configuration. See man udisks and search for ignore.



          In this case it turns out that partitions named "RECOVERY" among others are set as ignored by the default udev rules. See here.



          So the solution was to rename my linux recovery usb stick to something else than "RECOVERY".






          share|improve this answer























          • Now that was a quick solution.

            – Panki
            Jan 16 at 16:28













          1












          1








          1







          It turns out that udisks has an attribute for drives that marks them as ignored.



          You can see if this attribute is set with the following:



          $ udevadm info /dev/sdd1 | grep -i ignore
          UDISKS_IGNORE=1


          Udisks sets this attribute on devices based on heuristics and configuration. See man udisks and search for ignore.



          In this case it turns out that partitions named "RECOVERY" among others are set as ignored by the default udev rules. See here.



          So the solution was to rename my linux recovery usb stick to something else than "RECOVERY".






          share|improve this answer













          It turns out that udisks has an attribute for drives that marks them as ignored.



          You can see if this attribute is set with the following:



          $ udevadm info /dev/sdd1 | grep -i ignore
          UDISKS_IGNORE=1


          Udisks sets this attribute on devices based on heuristics and configuration. See man udisks and search for ignore.



          In this case it turns out that partitions named "RECOVERY" among others are set as ignored by the default udev rules. See here.



          So the solution was to rename my linux recovery usb stick to something else than "RECOVERY".







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 16 at 15:33









          Emily L.Emily L.

          1858




          1858












          • Now that was a quick solution.

            – Panki
            Jan 16 at 16:28

















          • Now that was a quick solution.

            – Panki
            Jan 16 at 16:28
















          Now that was a quick solution.

          – Panki
          Jan 16 at 16:28





          Now that was a quick solution.

          – Panki
          Jan 16 at 16:28

















          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%2f494856%2fremovable-volume-not-appearing-in-file-managers%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

          Peggy Mitchell

          Palaiologos

          The Forum (Inglewood, California)