Rclone mount with gdrive keeps checking for changes on remote

What is the problem you are having with rclone?

i created a remote with a google drive using ssh on seedhost. When i try to mount it keeps giving a message "checking for changes on remote " and doesnt mount.

What is your rclone version (output from rclone version)

rclone v1.53.0

  • os/arch: linux/amd64
  • go version: go1.15

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

Linux

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)

rclone mount Test: ~/TestDrive/

The rclone config contents with secrets removed.

[Test]
type = drive
client_id = XXXXXXXXXXXXX-ejfri9c0vine0s1a29nl6p4sl7qlk9vt.apps.googleusercontent.com
client_secret = NJxuEbXXXXXXXXXCXjaH4
scope = drive
token = {"access_token":"ya29.XXXXXXXXXXXX3uJnx2U5qs-ESJH8eAyrQaL5uDIzX1C6i2ir0Sg4qh88Yz8l3yy6MNFuMxnqLLanvPH80kmB_xF3qncnPBPXfGXdVTCPPvVwwDcR1eyHoYrKD96cdeQMOkaZ_yQ3oBRZoE9TTxYwdfVBLfe8-3LsOpdekw","token_type":"Bearer","refresh_token":"1//XXXXXXXXXXRAAGAkSNwF-L9IrLcidBBXQ2gSAbufitnLLUau6K9o4R-x_S8F_XlhlNMxiGkaX82_V0GM-9vCWQ7t23Tk","expiry":"2020-09-09T19:26:37.845490412+02:00"}

A log from the command with the -vv flag

rclone mount Test: ~/TestDrive/ -vv
DEBUG : rclone: Version "v1.53.0" starting with parameters ["rclone" "mount" "Test:" "/home28/XXXXXXXX/TestDrive/" "-vv"]
DEBUG : Creating backend with remote "Test:"
DEBUG : Using config file from "/home28/XXXXXXXX/.config/rclone/rclone.conf"
DEBUG : Google drive root '': root_folder_id = "XXXXXXXXf5Uk9PVA" - save this in the config to speed up startup
DEBUG : Google drive root '': Mounting on "/home28/XXXXXXXX/TestDrive/"
DEBUG : : Root:
DEBUG : : >Root: node=/, err=<nil>
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote
DEBUG : Google drive root '': Checking for changes on remote

It looks mounted. Those messages just mean it's checking Google for changes. Why do you think it's not mounted?

when i run ls /TestDrive/ it doesnt show the files so it looks like it hasnt been mounted properly

try addiing

      --allow-other                            Allow access to other users.

its a shared seedbox from seedhost. it doesnt allow to the use of --allow-other.
(i am getting an error and this is something others have also mentioned on this forum) :frowning:

can you post the command and error?

This is a seedbox issue. Permission issue. You should talk to your provider. Who is it?

I am using Seedhost.eu

rclone mount --allow-other Test: ~/TestDrive/

mount helper error: fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf
Fatal error : failed to mount FUSE fs: fusermount: exit status 1

edit that file and add this text
user_allow_other

Tried . it says i dont have permission to edit the fuse.conf file.

try this
sudo nano /etc/fuse.conf

Says my account is not in sudoers file.

if you can post the error message text, not just summarize it.

i also, have a seedbox, and i am able to edit that file

~$ sudo nano /etc/fuse.conf
[sudo] password for xxxxxxx:
xxxxxxxx is not in the sudoers file.  This incident will be reported.

contact tech support

some seedboxes allow root and some do not.

as per their website, it seems only dedicated seedboxes have root.
that is a lot of money to get root account.

Yeah , that is what i had seen others mention as well.

Will take it up with them and see.

Thanks for your time, guys. :slightly_smiling_face:

Why the tilde in the mount command? Are you trying to use tilde expansion to mount this in your home directory? what happens if you use the explicit path instead?

Also, --allow-other will allow any user on the seedbox to access the mounted filesystem. I think this is a bad idea, since this is a shared seedbox.

hi,
do you think that we can tweak other mount settings such as --uid as a work around?

Its the same even if i give the full path