well, looks like that rclone mount itself is not crashing but you have the same errors as before.
as @Animosity022 uses dropbox, i will give him the pleasure to respond to you.
I have never had any issues till now. It was working fine I unmounted and then when I tried to remount it started issue.
add back --daemon --daemon-timeout=5m and test.
rclone mount Dropbox3: /home/ilovemymac/PLEX --daemon --daemon-timeout=5m --buffer-size=64M --dir-cache-time=64h --vfs-cache-mode=full --vfs-read-chunk-size 100M --vfs-read-chunk-size-limit 0 --vfs-cache-max-age=6h
2022/01/04 21:23:05 Fatal error: mount not ready
so we have narrowed this down to some issue with --daemon --daemon-timeout=5m
i suggest trying just --daemon and see what happens.
or maybe the mount is not killed correctly,
might need to run fusermount -uz /home/ilovemymac/PLEX, before running rclone mount
oh wait, no worries, @ivandeex is about to join us!
rclone mount Dropbox3: /home/ilovemymac/PLEX --daemon --buffer-size=64M --dir-cache-time=64h --vfs-cache-mode=full --vfs-read-chunk-size 100M --vfs-read-chunk-size-limit 0 --vfs-cache-max-age=6h
2022/01/04 21:29:35 Fatal error: mount not ready
fusermount -uz /home/ilovemymac/PLEX
fusermount: entry for /mnt/mpathad/ilovemymac/PLEX not found in /etc/mtab
Very good was the troubleshooting advice to remove --daemon temporarily. Technically --daemon runs another background process to do the mount but has no access to its message log, so it can only report mount not ready if the daemon deadlocks or fails. Removing --daemon lets you see the core reason for error.
Next... The name --daemon-timeout is rather misleading and the flag is only relevant on MacOS for some their stuff. In a general case, if you expect that your cloud storage just responds too slowly and you want to give the --daemon process more time to setup, you should use --daemon-wait=5m.
To get to the core you should remove --daemon, add -vv --log-file=debug.log and thoroughly analyze the log.
Thanks
1 Like
It has never had an issue before. I use the same set up each time and no issues. But today its as though it doesn't want to mount.
Same error even without the timeout
I'd imagine it's because the maintainer has an older version which daemon is busted since it updated a few days back which is why we don't support custom builds.
Please, please don't use repo's.
Please refrain from repeating "I did not have the problem before". This tells nothing. Recall that I probably live on another continent, another time zone, never seen your system. The only thing that exists for me and all other volunteers here is YOUR LOG.
Restart your command without --daemon, with -vv --log-file=debug.log and send the log here. I know you and your system solely through the log.
I second this.
@Stream_One If you installed version from a repo, please talk to the repo maintainer. They don't report to us. We don't know what they did with code. To get support here you must install code compiled by us.
Again I have no choice. I am on a shared server I do not have root privileges to it to install a new rclone. I did not install it to begin with on the server. Whatbox has it preinstalled and updates it across all servers.
As allot of these server companies seem to do I have noticed.
You told me to download a linux version but im on personally here a Mac OS. The server is linux which again I do not have access to. I have installed the latest Mac OS rclone locally.
that is very interesting, as i noticed that the OP version used go1.17.5
i thought that all versions of rclone use the same version of go?
3rd time. You don't need root to install rclone.
felix@gemini:~/test$ wget https://downloads.rclone.org/v1.57.0/rclone-v1.57.0-linux-amd64.zip
--2022-01-04 16:51:29-- https://downloads.rclone.org/v1.57.0/rclone-v1.57.0-linux-amd64.zip
Resolving downloads.rclone.org (downloads.rclone.org)... 5.153.250.7, 2a02:24e0:8:61f9::1
Connecting to downloads.rclone.org (downloads.rclone.org)|5.153.250.7|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14409443 (14M) [application/zip]
Saving to: ‘rclone-v1.57.0-linux-amd64.zip’
rclone-v1.57.0-linux-amd64.zip 100%[================================================================================================================>] 13.74M 15.7MB/s in 0.9s n
2022-01-04 16:51:30 (15.7 MB/s) - ‘rclone-v1.57.0-linux-amd64.zip’ saved [14409443/14409443]
felix@gemini:~/test$ unzip rclone-v1.57.0-linux-amd64.zip
Archive: rclone-v1.57.0-linux-amd64.zip
creating: rclone-v1.57.0-linux-amd64/
inflating: rclone-v1.57.0-linux-amd64/README.txt
inflating: rclone-v1.57.0-linux-amd64/git-log.txt
inflating: rclone-v1.57.0-linux-amd64/rclone.1
inflating: rclone-v1.57.0-linux-amd64/README.html
inflating: rclone-v1.57.0-linux-amd64/rclone
felix@gemini:~/test$ cd rclone-v1.57.0-linux-amd64/
felix@gemini:~/test/rclone-v1.57.0-linux-amd64$ ./rclone version
rclone v1.57.0
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.11.0-43-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17.2
- go/linking: static
- go/tags: none
felix@gemini:~/test/rclone-v1.57.0-linux-amd64$ id
uid=1000(felix) gid=1000(felix) groups=1000(felix),4(adm),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),109(render),116(lxd)
1 Like
It's however you compile it. A maintainer can do whatever they want, compile whatever they want, change whatever they want.
Gentoo's beauty is that everything is compiled/built. I used it for a bit.
After following your directions above I get this
rclone v1.57.0-DEV
- os/version: gentoo 2.7 (64 bit)
- os/kernel: 5.10.27-gentoo-whatbox (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17.5
- go/linking: dynamic
- go/tags: none
This still produces the error of Mount not ready
You ran the old binary.
You need to use the full path to wherever you unzipped it.
felix@gemini:~/test/rclone-v1.57.0-linux-amd64$ pwd
/home/felix/test/rclone-v1.57.0-linux-amd64
felix@gemini:~/test/rclone-v1.57.0-linux-amd64$ /home/felix/test/rclone-v1.57.0-linux-amd64/rclone version
rclone v1.57.0
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.11.0-43-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17.2
- go/linking: static
- go/tags: none