Unable to mount remote from existing rclone.conf file

Help and Support
1

What is the problem you are having with rclone?

I have been trying unsuccessfully to mount a Google Drive remote from my existing rclone.conf file using rclone on my PC.

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

rclone v1.64.2
- os/version: Microsoft Windows 10 Home Single Language 22H2 (64 bit)
- os/kernel: 10.0.19045.3570 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.3
- go/linking: static
- go/tags: cmount

This is the latest version available currently at: Rclone downloads

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 mydrive: Z: --config "C:\Users\Username\.config\rclone.conf"

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

[5d44cd8d-397c-4107-b79b-17f2b6a071e8]
type = alias
remote = /storage/emulated/0

[mydrive]
type = drive
scope = drive
token = XXX

[mydropbox]
type = dropbox
token = XXX

[mymega]
type = mega
user = XXX
pass = XXX

[myonedrive]
type = onedrive
region = global
token = XXX
drive_id = XXX
drive_type = personal
### Double check the config for sensitive info before posting publicly

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

2023/10/31 13:55:39 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "-vv" "--log-file=C:\\Users\\Username\\Desktop\\logfile.txt" "mount" "mydrive:" "Z:" "--config" "C:\\Users\\Username\\.config\\rclone.conf"]
2023/10/31 13:55:39 DEBUG : Creating backend with remote "mydrive:"
2023/10/31 13:55:39 DEBUG : Using config file from "C:\\Users\\Username\\.config\\rclone.conf"
2023/10/31 13:55:40 DEBUG : Google drive root '': 'root_folder_id = 0AF2Z4ovewR-YUk9PVA' - save this in the config to speed up startup
2023/10/31 13:55:40 DEBUG : Network mode mounting is disabled
2023/10/31 13:55:40 DEBUG : Mounting on "Z:" ("mydrive")
2023/10/31 13:55:40 DEBUG : Google drive root '': Mounting with options: ["-o" "attr_timeout=1" "-o" "uid=-1" "-o" "gid=-1" "--FileSystemName=rclone" "-o" "volname=mydrive"]
2023/10/31 13:55:40 DEBUG : Google drive root '': Init: 
2023/10/31 13:55:40 DEBUG : Google drive root '': >Init: 
2023/10/31 13:55:40 DEBUG : /: Statfs: 
2023/10/31 13:55:40 DEBUG : /: >Statfs: stat={Bsize:4096 Frsize:4096 Blocks:26843545600 Bfree:22577775846 Bavail:22577775846 Files:1000000000 Ffree:1000000000 Favail:0 Fsid:0 Flag:0 Namemax:255}, errc=0
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Readlink: 
2023/10/31 13:55:40 DEBUG : /: >Readlink: linkPath="", errc=-40
2023/10/31 13:55:40 DEBUG : /: Getxattr: name="non-existant-a11ec902d22f4ec49003af15282d3b00"
2023/10/31 13:55:40 DEBUG : /: >Getxattr: errc=-40, value=""
The service rclone has been started.
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Opendir: 
2023/10/31 13:55:40 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2023/10/31 13:55:40 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2023/10/31 13:55:40 DEBUG : /: >Opendir: errc=0, fh=0x0
2023/10/31 13:55:40 DEBUG : /: Statfs: 
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: >Statfs: stat={Bsize:4096 Frsize:4096 Blocks:26843545600 Bfree:22577775846 Bavail:22577775846 Files:1000000000 Ffree:1000000000 Favail:0 Fsid:0 Flag:0 Namemax:255}, errc=0
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Opendir: 
2023/10/31 13:55:40 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2023/10/31 13:55:40 DEBUG : /: Releasedir: fh=0x0
2023/10/31 13:55:40 DEBUG : /: >Releasedir: errc=0
2023/10/31 13:55:40 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2023/10/31 13:55:40 DEBUG : /: >Opendir: errc=0, fh=0x0
2023/10/31 13:55:40 DEBUG : /: Releasedir: fh=0x0
2023/10/31 13:55:40 DEBUG : /: >Releasedir: errc=0
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2023/10/31 13:55:40 DEBUG : /: >Getattr: errc=0
2023/10/31 13:55:40 DEBUG : /: Opendir: 
2023/10/31 13:55:40 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2023/10/31 13:55:40 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2023/10/31 13:55:40 DEBUG : /: >Opendir: errc=0, fh=0x0
2023/10/31 13:55:40 DEBUG : /: Releasedir: fh=0x0
2023/10/31 13:55:40 DEBUG : /: >Releasedir: errc=0
2023/10/31 13:56:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 13:57:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 13:58:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 13:59:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:00:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:01:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:02:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:03:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:04:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:05:40 DEBUG : : forgetting directory cache
2023/10/31 14:05:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:06:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:07:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:08:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:09:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:10:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:11:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:12:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:13:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:14:40 DEBUG : Google drive root '': Checking for changes on remote
2023/10/31 14:15:40 DEBUG : Google drive root '': Checking for changes on remote
The service rclone has been stopped.
2023/10/31 14:16:15 DEBUG : Google drive root '': Destroy: 
2023/10/31 14:16:15 DEBUG : Google drive root '': >Destroy: 
2023/10/31 14:16:15 DEBUG : Not calling host.Unmount as mount already Destroyed
2023/10/31 14:16:15 DEBUG : Unmounted successfully
2023/10/31 14:16:15 ERROR : Z:: Unmounted rclone mount
2023/10/31 14:16:15 DEBUG : rclone: Version "v1.64.2" finishing with parameters ["rclone" "-vv" "--log-file=C:\\Users\\Username\\Desktop\\logfile.txt" "mount" "mydrive:" "Z:" "--config" "C:\\Users\\Nomaan\\.config\\rclone.conf"]
2

What do you mean by "unsuccessfully"?

Your log shows that you mount it successfully...

3

Sorry for not being clearer in my post. By unsuccessfully, I mean that this process runs seemingly indefinitely with no new drive appearing in my Windows file explorer. I always have to CTRL+C the process because it never finishes processing the command to completion.

4

rclone mount runs indefinitely - this is how it works. When you press CTRL+C you terminate it (and destroy mount).

This is possible - especially on Windows when for example your cmd window runs as Administrator - have a look at docs.

Try to run your rclone mount command from non-elevated command prompt.

5

Oh! I can see the drive now but the process is still running in the command prompt. What should I do now? Quit the window?

6

If you quit the window you will stop the mount..... This rclone process has to run in order for mount to work.

You either keep this window open (you can minimize it) or configure rclone mount as a Windows service - read docs and you will find many examples on this forum.

I can see that a lot of people use https://nssm.cc/ to manage windows services. It makes it apparently easier. You can Google step by step examples easy, e.g.: Running Windows Rclone Mount as a Service – Storage Made Easy Blog

7

Thank you for all the help! But after following the tutorial you have linked I get this:
image

8

I am not a Windows user and not really familiar with all its peculiarities. But there are some Windows experts here:)

@asdffdsa - would you mind to have a look at this error message?

@rcloneforumuser - please provide more details - what is your service setup, command you run etc.

9

i always mount to a folder, not a drive letter. makes the mount visible to elevated and no-elevated processes.

fwiw, these days i tend to use windows built-in task scheduler instead of nssm.
have a nice gui and easy to use.

10

Would you mind explaining how you mount it to a folder?

Do you know of any resource where I can learn more about how to get rclone mount service running with the built-in task scheduler?

11

check rclone mount docs.
rclone mount remote: b:\path\to\folder

i have written about it a number of times in the forum.

12

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