Google Colab-ValueError: Mountpoint must be in a directory that exists












2















I want to mount google drive on google Colab and I am using this command to mount the drive



from google.colab import drive
drive.mount('/content/drive/')


but I am getting this error



ValueError                               Traceback (most recent call last)
<ipython-input-45-9667a744255b> in <module>()
1 from google.colab import drive
----> 2 drive.mount('content/drive/')

/usr/local/lib/python3.6/dist-packages/google/colab/drive.py in
mount(mountpoint, force_remount)
99 raise ValueError('Mountpoint must either be a directory or not exist')
100 if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
--> 101 raise ValueError('Mountpoint must be in a directory that exists')
102 except:
103 d.terminate(force=True)

ValueError: Mountpoint must be in a directory that exists










share|improve this question

























  • drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

    – u2gilles
    Jan 19 at 3:19


















2















I want to mount google drive on google Colab and I am using this command to mount the drive



from google.colab import drive
drive.mount('/content/drive/')


but I am getting this error



ValueError                               Traceback (most recent call last)
<ipython-input-45-9667a744255b> in <module>()
1 from google.colab import drive
----> 2 drive.mount('content/drive/')

/usr/local/lib/python3.6/dist-packages/google/colab/drive.py in
mount(mountpoint, force_remount)
99 raise ValueError('Mountpoint must either be a directory or not exist')
100 if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
--> 101 raise ValueError('Mountpoint must be in a directory that exists')
102 except:
103 d.terminate(force=True)

ValueError: Mountpoint must be in a directory that exists










share|improve this question

























  • drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

    – u2gilles
    Jan 19 at 3:19
















2












2








2


2






I want to mount google drive on google Colab and I am using this command to mount the drive



from google.colab import drive
drive.mount('/content/drive/')


but I am getting this error



ValueError                               Traceback (most recent call last)
<ipython-input-45-9667a744255b> in <module>()
1 from google.colab import drive
----> 2 drive.mount('content/drive/')

/usr/local/lib/python3.6/dist-packages/google/colab/drive.py in
mount(mountpoint, force_remount)
99 raise ValueError('Mountpoint must either be a directory or not exist')
100 if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
--> 101 raise ValueError('Mountpoint must be in a directory that exists')
102 except:
103 d.terminate(force=True)

ValueError: Mountpoint must be in a directory that exists










share|improve this question
















I want to mount google drive on google Colab and I am using this command to mount the drive



from google.colab import drive
drive.mount('/content/drive/')


but I am getting this error



ValueError                               Traceback (most recent call last)
<ipython-input-45-9667a744255b> in <module>()
1 from google.colab import drive
----> 2 drive.mount('content/drive/')

/usr/local/lib/python3.6/dist-packages/google/colab/drive.py in
mount(mountpoint, force_remount)
99 raise ValueError('Mountpoint must either be a directory or not exist')
100 if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
--> 101 raise ValueError('Mountpoint must be in a directory that exists')
102 except:
103 d.terminate(force=True)

ValueError: Mountpoint must be in a directory that exists







python google-colaboratory valueerror






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 21 at 10:02







clarky

















asked Jan 17 at 7:23









clarkyclarky

61111




61111













  • drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

    – u2gilles
    Jan 19 at 3:19





















  • drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

    – u2gilles
    Jan 19 at 3:19



















drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

– u2gilles
Jan 19 at 3:19







drive.mount('/content/drive') does not work anymore for me too since yesterday (January 19). Did Google Colab change something? I have not changed anything on my side and this command has been working for months.

– u2gilles
Jan 19 at 3:19














7 Answers
7






active

oldest

votes


















1














@clarky: the error you got was correct tried to tell you that your usage of drive.mount() is incorrect: the mountpoint argument to drive.mount() must be an empty directory that exists, or the name of a non-existent file/directory in a directory that does exist so that the mountpoint can be created as part of the mount operation. Your usage of a relative path in drive.mount('content/drive/') (i.e. content/drive/) implies that the mount should happen at '/content/content/drive' because the interpreter's default path is /content; note the doubled content path component there, and likely you don't already have a directory named /content/content inside of which a mountpoint named drive could be created. The fix to your notebook code is to instead use drive.mount('/content/drive') - note the leading / making the mountpount path absolute instead of relative.






share|improve this answer































    3














    I ran into this error this morning as well. I'm not sure what this commit what meant to fix but it certainly caused the error. A workaround is to copy the code for drive.py into colab, comment out lines 100 and 101 like this:



    # drive.py

    ...

    try:
    if _os.path.islink(mountpoint):
    raise ValueError('Mountpoint must not be a symlink')
    if _os.path.isdir(mountpoint) and _os.listdir(mountpoint):
    raise ValueError('Mountpoint must not already contain files')
    if not _os.path.isdir(mountpoint) and _os.path.exists(mountpoint):
    raise ValueError('Mountpoint must either be a directory or not exist')
    # if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
    # raise ValueError('Mountpoint must be in a directory that exists')
    except:
    d.terminate(force=True)
    raise

    ...


    then replace



    from google.colab import drive
    drive.mount('content/drive/')


    with



    mount('/content/drive/')


    using the mount function you copied from drive.py



    Hopefully the issue gets fixed quickly enough so we can do away with this workaround.






    share|improve this answer
























    • I tried using your approach. But the authentication takes forever. Its not working.

      – clarky
      Jan 17 at 13:33











    • What part of the authentication took forever?

      – Jimi
      Jan 17 at 13:45











    • @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

      – Ami F
      Jan 17 at 18:08











    • @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

      – Ami F
      Jan 17 at 18:09











    • @AmiF Nope. I had ‘/content/drive’ when it failed for me

      – Jimi
      Jan 17 at 20:54





















    1














    I received the error as well change to drive.mount('/content/drive')






    share|improve this answer































      1














      just remove the '/' following the drive and it works perfectly..



      That is from drive.mount('/content/drive/') to drive.mount('/content/drive')






      share|improve this answer
























      • can you please explain your answer so OP can understand what is error in his code. thanks

        – Shanteshwar Inde
        Jan 20 at 7:00



















      0














      Run command to unmount drive first.



      !fusermount -u drive


      Then try run again,



      from google.colab import drive
      drive.mount('/content/drive')





      share|improve this answer
























      • FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

        – Ami F
        Jan 17 at 18:10



















      0














      If mounting does not work even if absolute path /content/drive was used, then verify that appropriate directories exist,



      !mdkir -p /content/drive






      share|improve this answer































        0














        Replace drive.mount('/content/drive/') by drive.mount('/content/drive')






        share|improve this answer























          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f54230871%2fgoogle-colab-valueerror-mountpoint-must-be-in-a-directory-that-exists%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          7 Answers
          7






          active

          oldest

          votes








          7 Answers
          7






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          @clarky: the error you got was correct tried to tell you that your usage of drive.mount() is incorrect: the mountpoint argument to drive.mount() must be an empty directory that exists, or the name of a non-existent file/directory in a directory that does exist so that the mountpoint can be created as part of the mount operation. Your usage of a relative path in drive.mount('content/drive/') (i.e. content/drive/) implies that the mount should happen at '/content/content/drive' because the interpreter's default path is /content; note the doubled content path component there, and likely you don't already have a directory named /content/content inside of which a mountpoint named drive could be created. The fix to your notebook code is to instead use drive.mount('/content/drive') - note the leading / making the mountpount path absolute instead of relative.






          share|improve this answer




























            1














            @clarky: the error you got was correct tried to tell you that your usage of drive.mount() is incorrect: the mountpoint argument to drive.mount() must be an empty directory that exists, or the name of a non-existent file/directory in a directory that does exist so that the mountpoint can be created as part of the mount operation. Your usage of a relative path in drive.mount('content/drive/') (i.e. content/drive/) implies that the mount should happen at '/content/content/drive' because the interpreter's default path is /content; note the doubled content path component there, and likely you don't already have a directory named /content/content inside of which a mountpoint named drive could be created. The fix to your notebook code is to instead use drive.mount('/content/drive') - note the leading / making the mountpount path absolute instead of relative.






            share|improve this answer


























              1












              1








              1







              @clarky: the error you got was correct tried to tell you that your usage of drive.mount() is incorrect: the mountpoint argument to drive.mount() must be an empty directory that exists, or the name of a non-existent file/directory in a directory that does exist so that the mountpoint can be created as part of the mount operation. Your usage of a relative path in drive.mount('content/drive/') (i.e. content/drive/) implies that the mount should happen at '/content/content/drive' because the interpreter's default path is /content; note the doubled content path component there, and likely you don't already have a directory named /content/content inside of which a mountpoint named drive could be created. The fix to your notebook code is to instead use drive.mount('/content/drive') - note the leading / making the mountpount path absolute instead of relative.






              share|improve this answer













              @clarky: the error you got was correct tried to tell you that your usage of drive.mount() is incorrect: the mountpoint argument to drive.mount() must be an empty directory that exists, or the name of a non-existent file/directory in a directory that does exist so that the mountpoint can be created as part of the mount operation. Your usage of a relative path in drive.mount('content/drive/') (i.e. content/drive/) implies that the mount should happen at '/content/content/drive' because the interpreter's default path is /content; note the doubled content path component there, and likely you don't already have a directory named /content/content inside of which a mountpoint named drive could be created. The fix to your notebook code is to instead use drive.mount('/content/drive') - note the leading / making the mountpount path absolute instead of relative.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 17 at 18:08









              Ami FAmi F

              74328




              74328

























                  3














                  I ran into this error this morning as well. I'm not sure what this commit what meant to fix but it certainly caused the error. A workaround is to copy the code for drive.py into colab, comment out lines 100 and 101 like this:



                  # drive.py

                  ...

                  try:
                  if _os.path.islink(mountpoint):
                  raise ValueError('Mountpoint must not be a symlink')
                  if _os.path.isdir(mountpoint) and _os.listdir(mountpoint):
                  raise ValueError('Mountpoint must not already contain files')
                  if not _os.path.isdir(mountpoint) and _os.path.exists(mountpoint):
                  raise ValueError('Mountpoint must either be a directory or not exist')
                  # if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
                  # raise ValueError('Mountpoint must be in a directory that exists')
                  except:
                  d.terminate(force=True)
                  raise

                  ...


                  then replace



                  from google.colab import drive
                  drive.mount('content/drive/')


                  with



                  mount('/content/drive/')


                  using the mount function you copied from drive.py



                  Hopefully the issue gets fixed quickly enough so we can do away with this workaround.






                  share|improve this answer
























                  • I tried using your approach. But the authentication takes forever. Its not working.

                    – clarky
                    Jan 17 at 13:33











                  • What part of the authentication took forever?

                    – Jimi
                    Jan 17 at 13:45











                  • @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                    – Ami F
                    Jan 17 at 18:08











                  • @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                    – Ami F
                    Jan 17 at 18:09











                  • @AmiF Nope. I had ‘/content/drive’ when it failed for me

                    – Jimi
                    Jan 17 at 20:54


















                  3














                  I ran into this error this morning as well. I'm not sure what this commit what meant to fix but it certainly caused the error. A workaround is to copy the code for drive.py into colab, comment out lines 100 and 101 like this:



                  # drive.py

                  ...

                  try:
                  if _os.path.islink(mountpoint):
                  raise ValueError('Mountpoint must not be a symlink')
                  if _os.path.isdir(mountpoint) and _os.listdir(mountpoint):
                  raise ValueError('Mountpoint must not already contain files')
                  if not _os.path.isdir(mountpoint) and _os.path.exists(mountpoint):
                  raise ValueError('Mountpoint must either be a directory or not exist')
                  # if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
                  # raise ValueError('Mountpoint must be in a directory that exists')
                  except:
                  d.terminate(force=True)
                  raise

                  ...


                  then replace



                  from google.colab import drive
                  drive.mount('content/drive/')


                  with



                  mount('/content/drive/')


                  using the mount function you copied from drive.py



                  Hopefully the issue gets fixed quickly enough so we can do away with this workaround.






                  share|improve this answer
























                  • I tried using your approach. But the authentication takes forever. Its not working.

                    – clarky
                    Jan 17 at 13:33











                  • What part of the authentication took forever?

                    – Jimi
                    Jan 17 at 13:45











                  • @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                    – Ami F
                    Jan 17 at 18:08











                  • @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                    – Ami F
                    Jan 17 at 18:09











                  • @AmiF Nope. I had ‘/content/drive’ when it failed for me

                    – Jimi
                    Jan 17 at 20:54
















                  3












                  3








                  3







                  I ran into this error this morning as well. I'm not sure what this commit what meant to fix but it certainly caused the error. A workaround is to copy the code for drive.py into colab, comment out lines 100 and 101 like this:



                  # drive.py

                  ...

                  try:
                  if _os.path.islink(mountpoint):
                  raise ValueError('Mountpoint must not be a symlink')
                  if _os.path.isdir(mountpoint) and _os.listdir(mountpoint):
                  raise ValueError('Mountpoint must not already contain files')
                  if not _os.path.isdir(mountpoint) and _os.path.exists(mountpoint):
                  raise ValueError('Mountpoint must either be a directory or not exist')
                  # if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
                  # raise ValueError('Mountpoint must be in a directory that exists')
                  except:
                  d.terminate(force=True)
                  raise

                  ...


                  then replace



                  from google.colab import drive
                  drive.mount('content/drive/')


                  with



                  mount('/content/drive/')


                  using the mount function you copied from drive.py



                  Hopefully the issue gets fixed quickly enough so we can do away with this workaround.






                  share|improve this answer













                  I ran into this error this morning as well. I'm not sure what this commit what meant to fix but it certainly caused the error. A workaround is to copy the code for drive.py into colab, comment out lines 100 and 101 like this:



                  # drive.py

                  ...

                  try:
                  if _os.path.islink(mountpoint):
                  raise ValueError('Mountpoint must not be a symlink')
                  if _os.path.isdir(mountpoint) and _os.listdir(mountpoint):
                  raise ValueError('Mountpoint must not already contain files')
                  if not _os.path.isdir(mountpoint) and _os.path.exists(mountpoint):
                  raise ValueError('Mountpoint must either be a directory or not exist')
                  # if '/' in mountpoint and not _os.path.exists(_os.path.dirname(mountpoint)):
                  # raise ValueError('Mountpoint must be in a directory that exists')
                  except:
                  d.terminate(force=True)
                  raise

                  ...


                  then replace



                  from google.colab import drive
                  drive.mount('content/drive/')


                  with



                  mount('/content/drive/')


                  using the mount function you copied from drive.py



                  Hopefully the issue gets fixed quickly enough so we can do away with this workaround.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 17 at 9:28









                  JimiJimi

                  484418




                  484418













                  • I tried using your approach. But the authentication takes forever. Its not working.

                    – clarky
                    Jan 17 at 13:33











                  • What part of the authentication took forever?

                    – Jimi
                    Jan 17 at 13:45











                  • @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                    – Ami F
                    Jan 17 at 18:08











                  • @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                    – Ami F
                    Jan 17 at 18:09











                  • @AmiF Nope. I had ‘/content/drive’ when it failed for me

                    – Jimi
                    Jan 17 at 20:54





















                  • I tried using your approach. But the authentication takes forever. Its not working.

                    – clarky
                    Jan 17 at 13:33











                  • What part of the authentication took forever?

                    – Jimi
                    Jan 17 at 13:45











                  • @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                    – Ami F
                    Jan 17 at 18:08











                  • @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                    – Ami F
                    Jan 17 at 18:09











                  • @AmiF Nope. I had ‘/content/drive’ when it failed for me

                    – Jimi
                    Jan 17 at 20:54



















                  I tried using your approach. But the authentication takes forever. Its not working.

                  – clarky
                  Jan 17 at 13:33





                  I tried using your approach. But the authentication takes forever. Its not working.

                  – clarky
                  Jan 17 at 13:33













                  What part of the authentication took forever?

                  – Jimi
                  Jan 17 at 13:45





                  What part of the authentication took forever?

                  – Jimi
                  Jan 17 at 13:45













                  @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                  – Ami F
                  Jan 17 at 18:08





                  @Jimi: Your suggestion works because of the replacement of the relative path with an absolute one; the commenting-out is irrelevant.

                  – Ami F
                  Jan 17 at 18:08













                  @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                  – Ami F
                  Jan 17 at 18:09





                  @clarky: if you are seeing timeout errors during authentication please chime in on github.com/googlecolab/colabtools/issues/382

                  – Ami F
                  Jan 17 at 18:09













                  @AmiF Nope. I had ‘/content/drive’ when it failed for me

                  – Jimi
                  Jan 17 at 20:54







                  @AmiF Nope. I had ‘/content/drive’ when it failed for me

                  – Jimi
                  Jan 17 at 20:54













                  1














                  I received the error as well change to drive.mount('/content/drive')






                  share|improve this answer




























                    1














                    I received the error as well change to drive.mount('/content/drive')






                    share|improve this answer


























                      1












                      1








                      1







                      I received the error as well change to drive.mount('/content/drive')






                      share|improve this answer













                      I received the error as well change to drive.mount('/content/drive')







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jan 17 at 19:26









                      PinkertonPinkerton

                      111




                      111























                          1














                          just remove the '/' following the drive and it works perfectly..



                          That is from drive.mount('/content/drive/') to drive.mount('/content/drive')






                          share|improve this answer
























                          • can you please explain your answer so OP can understand what is error in his code. thanks

                            – Shanteshwar Inde
                            Jan 20 at 7:00
















                          1














                          just remove the '/' following the drive and it works perfectly..



                          That is from drive.mount('/content/drive/') to drive.mount('/content/drive')






                          share|improve this answer
























                          • can you please explain your answer so OP can understand what is error in his code. thanks

                            – Shanteshwar Inde
                            Jan 20 at 7:00














                          1












                          1








                          1







                          just remove the '/' following the drive and it works perfectly..



                          That is from drive.mount('/content/drive/') to drive.mount('/content/drive')






                          share|improve this answer













                          just remove the '/' following the drive and it works perfectly..



                          That is from drive.mount('/content/drive/') to drive.mount('/content/drive')







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 20 at 6:52









                          Prashanth SateeshPrashanth Sateesh

                          111




                          111













                          • can you please explain your answer so OP can understand what is error in his code. thanks

                            – Shanteshwar Inde
                            Jan 20 at 7:00



















                          • can you please explain your answer so OP can understand what is error in his code. thanks

                            – Shanteshwar Inde
                            Jan 20 at 7:00

















                          can you please explain your answer so OP can understand what is error in his code. thanks

                          – Shanteshwar Inde
                          Jan 20 at 7:00





                          can you please explain your answer so OP can understand what is error in his code. thanks

                          – Shanteshwar Inde
                          Jan 20 at 7:00











                          0














                          Run command to unmount drive first.



                          !fusermount -u drive


                          Then try run again,



                          from google.colab import drive
                          drive.mount('/content/drive')





                          share|improve this answer
























                          • FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                            – Ami F
                            Jan 17 at 18:10
















                          0














                          Run command to unmount drive first.



                          !fusermount -u drive


                          Then try run again,



                          from google.colab import drive
                          drive.mount('/content/drive')





                          share|improve this answer
























                          • FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                            – Ami F
                            Jan 17 at 18:10














                          0












                          0








                          0







                          Run command to unmount drive first.



                          !fusermount -u drive


                          Then try run again,



                          from google.colab import drive
                          drive.mount('/content/drive')





                          share|improve this answer













                          Run command to unmount drive first.



                          !fusermount -u drive


                          Then try run again,



                          from google.colab import drive
                          drive.mount('/content/drive')






                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 17 at 16:06









                          Pradeep SakhareliaPradeep Sakharelia

                          1




                          1













                          • FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                            – Ami F
                            Jan 17 at 18:10



















                          • FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                            – Ami F
                            Jan 17 at 18:10

















                          FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                          – Ami F
                          Jan 17 at 18:10





                          FYI instead of hard-coding fusermount you should probably use the force_remount=True param to drive.mount()

                          – Ami F
                          Jan 17 at 18:10











                          0














                          If mounting does not work even if absolute path /content/drive was used, then verify that appropriate directories exist,



                          !mdkir -p /content/drive






                          share|improve this answer




























                            0














                            If mounting does not work even if absolute path /content/drive was used, then verify that appropriate directories exist,



                            !mdkir -p /content/drive






                            share|improve this answer


























                              0












                              0








                              0







                              If mounting does not work even if absolute path /content/drive was used, then verify that appropriate directories exist,



                              !mdkir -p /content/drive






                              share|improve this answer













                              If mounting does not work even if absolute path /content/drive was used, then verify that appropriate directories exist,



                              !mdkir -p /content/drive







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Jan 18 at 14:42









                              azdobylakazdobylak

                              11




                              11























                                  0














                                  Replace drive.mount('/content/drive/') by drive.mount('/content/drive')






                                  share|improve this answer




























                                    0














                                    Replace drive.mount('/content/drive/') by drive.mount('/content/drive')






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      Replace drive.mount('/content/drive/') by drive.mount('/content/drive')






                                      share|improve this answer













                                      Replace drive.mount('/content/drive/') by drive.mount('/content/drive')







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jan 19 at 18:34









                                      Endy Bermúdez REndy Bermúdez R

                                      62




                                      62






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Stack Overflow!


                                          • 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%2fstackoverflow.com%2fquestions%2f54230871%2fgoogle-colab-valueerror-mountpoint-must-be-in-a-directory-that-exists%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

                                          Liquibase includeAll doesn't find base path

                                          How to use setInterval in EJS file?

                                          Petrus Granier-Deferre