Colab cannot mount the Google Drive of the account I need

[SZ-STEPHEN]

Describe the current behavior
A clear and concise explanation of what is currently happening.

I am a Colab Pro user, and I need to mount Google Drive to process my data. Today, when I use the code

"From google.colab import drive
drive.mount('/content/drive')"

To mount the Google Drive where I store data, it no longer asks me to fill in the verification code as usual, but goes to another page to log in to the account. When I log in to the Google Drive of my other account (not the account using the Colab), an error has occurred and it cannot be mounted. The specific situation is shown in the figures below

Describe the expected behavior

I hope to solve the problem as soon as possible, so that everyone can successfully mount the Google Drive of other accounts, thank you very much

What web browser you are using
Chrome

Additional context
Link to a minimal, public, self-contained notebook that reproduces this issue.

• Share the file using your GitHub account using File > Save a copy as a GitHub Gist.
• or Share Drive notebooks using the Share button then 'Get Shareable Link'.

[SawanKumar28]

I am facing the same issue. I hope this is resolved as soon as possible.

[morg1649]

similar problem

[morg1649]

Google, please, return the disk connection to notepad as it was before (with code input)

[ShamimAlMahmud]

I'm also facing the same problem from this morning

[yaryaryar]

i solved this problem.when i see the code in colab,i find two different functions.

One is the

def mount(mountpoint,
force_remount=False,
timeout_ms=120000,
use_metadata_server=None):

The other one is

def _mount(mountpoint,

force_remount=False,

timeout_ms=120000,

use_metadata_server=None):

if you use the _mount you can get the link.So i think this is a update for colab.

finally,try running this code:

from google.colab import drive

drive._mount('/content/drive')

[SZ-STEPHEN]

i solved this problem.when i see the code in colab,i find two different functions.

One is the

def mount(mountpoint,
force_remount=False,
timeout_ms=120000,
use_metadata_server=None):

The other one is

def _mount(mountpoint,

force_remount=False,

timeout_ms=120000,

use_metadata_server=None):

if you use the _mount you can get the link.So i think this is a update for colab.

finally,try running this code:

from google.colab import drive

drive._mount('/content/drive')

Thanks a lot! It works!

[Rajarshi07]

i solved this problem.when i see the code in colab,i find two different functions.

One is the

def mount(mountpoint,
force_remount=False,
timeout_ms=120000,
use_metadata_server=None):

The other one is

def _mount(mountpoint,

force_remount=False,

timeout_ms=120000,

use_metadata_server=None):

if you use the _mount you can get the link.So i think this is a update for colab.

finally,try running this code:

from google.colab import drive

drive._mount('/content/drive')

THANK YOU

[cperry-goog]

We've rolled out a new, more secure method to mount Google Drive. This requires using the same account to mount Google Drive as you use for notebook code execution. Let us know if you have any issues mounting Google Drive and executing code from the same account.

Any workarounds for connecting other accounts will eventually cease to succeed, so know that you will need to migrate at some point in the near future.

[Huy-LichHoang]

it no longer run well

[ananda1996ai]

We've rolled out a new, more secure method to mount Google Drive. This requires using the same account to mount Google Drive as you use for notebook code execution. Let us know if you have any issues mounting Google Drive and executing code from the same account.

Any workarounds for connecting other accounts will eventually cease to succeed, so know that you will need to migrate at some point in the near future.

Why on earth would you do this! This makes sharing code so much harder which is supposed to be the very purpose of "Colab"!! The functionality to mount different drives should have been kept as is. This is just stupid.

[tian1327]

We've rolled out a new, more secure method to mount Google Drive. This requires using the same account to mount Google Drive as you use for notebook code execution. Let us know if you have any issues mounting Google Drive and executing code from the same account.
Any workarounds for connecting other accounts will eventually cease to succeed, so know that you will need to migrate at some point in the near future.

Why on earth would you do this! This makes sharing code so much harder which is supposed to be the very purpose of "Colab"!! The functionality to mount different drives should have been kept as is. This is just stupid.

I believe they are trying to prevent people from combining resources under different gmail account. For example, I used to mount my personal colab with my university google drive since student account has unlimited storage for google drive. Now they found this bug and fixed it.

Also, I remember they announced that student account can no longer mount their drive to colab. SAD!!!

[PratikStar]

@tian1327 This is exactly how I was using this mounting function. Sadly not possible now :(

[bryastring]

It is frustrating that they won't let people do this any more. All they're going to do is force people to look into using different platforms that are better and more user and collaboration friendly. Kind of ironic that they would name the product colab then make it so difficult to collaborate.