My config for Google Drive remote no longer works

What is the problem you are having with rclone?

After system upgrade from Ubuntu 22.04 to 24.04, rclone remote to a Google Drive folder no longer works.
This has been working more or less flawlessly since November 2024 until I upgraded the system. Upon upgrade, it did work for a few days.

Now it doesn't.

I can no longer access the file that my remote is supposed to be connected to on Google Drive. It is there, I can see it on my Google Drive. But I can't see it in my local rclone remote.

Run the command 'rclone version' and share the full output of the command.

$ rclone version
rclone v1.69.1
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.0-58-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.0
- go/linking: static
- go/tags: none

I should mention that the this command previously returned the following, which I noticed, and then upgraded to the above from a download:

$ rclone version
rclone v1.60.1-DEV
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.0-58-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.2
- go/linking: dynamic
- go/tags: none

All that follows is with the upgraded version.

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

No command line command. The folder created by the config is there but the file from Google Drive is missing.

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

$ rclone config redacted
[wopa]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
root_folder_id = XXX
token = XXX
team_drive = 


A log from the command that you were trying to run with the -vv flag

I ran no command. I tried to run it from systemctl as I always have. I guess the command would be what is in the service file, so I try that:



The console hangs at this point, but we can see that the file 871204.xxxx is not found. Yet I can find it on my Google Drive.

$ /usr/bin/rclone -vv  --config=/home/xxxxxx/.config/rclone/rclone.conf         mount wopa: /home/xxxxxx/wopa
2025/04/20 16:02:28 DEBUG : rclone: Version "v1.69.1" starting with parameters ["/usr/bin/rclone" "-vv" "--config=/home/xxxxxx/.config/rclone/rclone.conf" "mount" "wopa:" "/home/xxxxxx/wopa"]
2025/04/20 16:02:28 DEBUG : Creating backend with remote "wopa:"
2025/04/20 16:02:28 DEBUG : Using config file from "/home/xxxxxx/.config/rclone/rclone.conf"
2025/04/20 16:02:28 DEBUG : Google drive root '': Mounting on "/home/xxxxxx/wopa"
2025/04/20 16:02:28 DEBUG : : Root: 
2025/04/20 16:02:28 DEBUG : : >Root: node=/, err=<nil>
2025/04/20 16:02:28 DEBUG : /: Lookup: name=".Trash"
2025/04/20 16:02:28 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
2025/04/20 16:02:28 DEBUG : /: Lookup: name=".Trash-1001"
2025/04/20 16:02:28 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
2025/04/20 16:02:49 DEBUG : /: Attr: 
2025/04/20 16:02:49 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=<nil>
2025/04/20 16:02:49 DEBUG : /: Lookup: name=".Trash"
2025/04/20 16:02:49 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
2025/04/20 16:02:49 DEBUG : /: Lookup: name=".Trash-1001"
2025/04/20 16:02:49 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
2025/04/20 16:02:49 DEBUG : /: ReadDirAll: 
2025/04/20 16:02:49 DEBUG : /: >ReadDirAll: item=3, err=<nil>
2025/04/20 16:02:49 DEBUG : /: Lookup: name="871204.xxxx"
2025/04/20 16:02:49 DEBUG : /: >Lookup: node=871204.xxxx, err=<nil>
2025/04/20 16:02:49 DEBUG : 871204.xxxx: Attr: 
2025/04/20 16:02:49 DEBUG : 871204.xxxx: >Attr: a=valid=1s ino=0 size=147911 mode=-rw-rw-r--, err=<nil>
2025/04/20 16:02:49 DEBUG : /: Lookup: name=".hidden"
2025/04/20 16:02:49 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
2025/04/20 16:02:49 DEBUG : /: Attr: 
2025/04/20 16:02:49 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=<nil>

based on having used a many years old, custom compiled version rclone, i suggest:

  1. create a new gdrive remote from scratch.
  2. make sure rclone ls sees that file you mentioned.
  3. rclone mount ...

New just on the rclone end or on the google drive end too?

i would follow the rclone docs.

Ok, but interestingly enough, before creating a new remote:

~$ rclone ls wopa:
   147911 871204.xxxx

IOW, rclone sees the file but my local file system does not.

Actually, even this:

$ ls wopa
871204.xxxx

But the Ubuntu Files application does not see it.

Uhhh, never mind the whole thing. Refreshing the Files app now shows the file as well.

well, that same file is in the mount debug log
871204.xxxx: >Attr: a=valid=1s ino=0 size=147911


not sure what you need help with??

see my edit above. Case closed.

I think all I needed to do was upgrade the rclone and reconfigure.