Mounted Folder is Empty After Update to Rclone 1.15

What is the problem you are having with rclone?

After the update to the version 1.15 all the mounted folders are empty.

What is your rclone version (output from rclone version)

rclone v1.51.0

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Synology DSM 6

  • os/arch: linux/amd64

  • go version: go1.13.7

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

Google Drive (GSuite)

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

rclone mount GDrive: /volume1/Media\ Library --dir-cache-time 672h --vfs-cache-max-age 675h --vfs-read-chunk-size 64M --vfs-read-chunk-size-limit 1G --buffer-size 32M --allow-non-empty --log-file=/volume1/Downloads/rclone.log

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

2020/03/03 16:38:54 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "mount" "GDrive:" "/volume1/Media Library" "--dir-cache-time" "672h" "--vfs-cache-max-age" "675h" "--vfs-read-chunk-size" "64M" "--vfs-read-chunk-size-limit" "1G" "--buffer-size" "32M" "--allow-non-empty" "--log-file=/volume1/Downloads/rclone.log" "-vv"]
2020/03/03 16:38:54 DEBUG : Using config file from "/var/services/homes/Mattia Costa/.config/rclone/rclone.conf"
2020/03/03 16:38:54 DEBUG : Google drive root '': Mounting on "/volume1/Media Library"
2020/03/03 16:38:54 DEBUG : GDrive: Loaded invalid token from config file - ignoring
2020/03/03 16:38:54 NOTICE: Time may be set wrong - time from "oauth2.googleapis.com" is 8m47.480012361s different from this computer
2020/03/03 16:38:54 DEBUG : GDrive: Saved new token in config file
2020/03/03 16:38:54 NOTICE: Time may be set wrong - time from "www.googleapis.com" is 8m47.692928819s different from this computer
2020/03/03 16:38:54 DEBUG : Adding path "vfs/forget" to remote control registry
2020/03/03 16:38:54 DEBUG : Adding path "vfs/refresh" to remote control registry
2020/03/03 16:38:54 DEBUG : Adding path "vfs/poll-interval" to remote control registry
2020/03/03 16:38:54 DEBUG : : Root:
2020/03/03 16:38:54 DEBUG : : >Root: node=/, err=

hello and welcome to the forum,

not sure that these suggestion are the problem:

/volume1/Media\ Library is that correct?

in your log there are a couple of debug messages, perhaps set the time correctly
Time may be set wrong

Yeah that's the path of where my rclone need to mount the drive.
The time of my server it's actually correct... I don't know why is that but I'll double check, it should not be the issue right?

The time on the server is 8 minutes off so you'd need to fix that.

Fixed now, but the problem persist...

Consider that everything was working fine with the old version of rclone, the mount script is the same, but after the update nothing worked anymore

that path has two different slashes, forward slash and backslash.

if you path has space character in it, you should enclose it with quotes.

after you fixed the time, did you kill the mount and restart it?

Do you have a new debug log?

Is really bad to use as it allows for over mounting. I would remove that.

"/volume1/Media Library" Like this?

that is correct

1 Like

this is the new log

2020/03/03 17:01:16 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "--config" "/var/services/homes/Mattia Costa/.config/rclone/rclone.conf" "mount" "GDrive:" "/volume1/Media Library" "--dir-cache-time" "672h" "--vfs-cache-max-age" "675h" "--vfs-read-chunk-size" "64M" "--vfs-read-chunk-size-limit" "1G" "--buffer-size" "32M" "--allow-non-empty" "--log-file=/volume1/Downloads/rclone.log" "-vv"]

2020/03/03 17:01:16 DEBUG : Using config file from "/var/services/homes/Mattia Costa/.config/rclone/rclone.conf"
2020/03/03 17:01:16 DEBUG : Google drive root '': Mounting on "/volume1/Media Library"
2020/03/03 17:01:16 DEBUG : Adding path "vfs/forget" to remote control registry
2020/03/03 17:01:16 DEBUG : Adding path "vfs/refresh" to remote control registry
2020/03/03 17:01:16 DEBUG : Adding path "vfs/poll-interval" to remote control registry
2020/03/03 17:01:16 DEBUG : : Root:
2020/03/03 17:01:16 DEBUG : : >Root: node=/, err=

as per @Animosity022, you should remove that flag, unless you know for sure you need it.

is the mount working now?

Nope, the share is still empty

did you remove that flag, and then kill and restart the mount?

Let me try now, in the debug the only log is this:
2020/03/03 17:06:19 DEBUG : Google drive root '': Checking for changes on remote
2020/03/03 17:07:19 DEBUG : Google drive root '': Checking for changes on remote

I can read the file correctly via terminal using the command rclone ls GDrive but still is invisible on the operating system of the NAS, I think it might be a permission issue now... ill double check

How do I kill all the mounts in one go? there Is a command for that?

Can you share the full debug log?

You can use 3 backtics before and after to keep it as a code block

Like

this
with the tics

You can:

ps -ef | grep rclone
kill process id

or you can use fusermount -uz /mountpoint

Done and yes now it's working correctly, the share is not visible inside the NAS File explorer, but that's an issue with Synology!

Thanks!!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.