Mount rClone on reboot (MAC OS X)

Help and Support
1

What is the problem you are having with rclone?
I can't get rClone to mount automatically when rebooting

What is your rclone version (output from rclone version)
rclone v1.57.0

  • os/version: darwin 11.5.2 (64 bit)
  • os/kernel: 20.6.0 (x86_64)
  • os/type: darwin
  • os/arch: amd64
  • go/version: go1.17.2
  • go/linking: dynamic
  • go/tags: cmount

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

I'm actually connecting my remote seedbox to my local Mac (FTP)

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

////usr/local/bin/rclone cmount T5Drive:/files/downloads /Volumes/"Samsung T5/BitTorrent"

The rclone config contents with secrets removed.

remote> 1

[T5Drive]

type = ftp

host = xxx.xxx.xxx.xxx

user = username

pass = *** ENCRYPTED ***

explicit_tls = true

no_check_certificate = true

encoding = Slash,BackSlash,Del,Ctl,RightSpace,Dot,SquareBracket

I have created a file with Textmate called rclonemount.command with the following inside it - /usr/local/bin/rclone cmount T5Drive:/files/downloads /Volumes/"Samsung T5/BitTorrent" and made it executable.

It is now in my LOGIN ITEMS on my Mac, but when the Mac reboots, it throws me an error.

/Users/username/Documents/rclonemount.command ; exit;

username@MacMinii7 ~ % /Users/username/Documents/rclonemount.command ; exit;

2021/11/17 06:32:05 Failed to create file system for "T5Drive:/files/downloads": NewFs: dial tcp 185.38.14.210:21: i/o timeout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

After the Mac has booted, if I double click to run the rclonemount.command file, then it mounts perfectly well. It just doesn't work on booting.

2

You might want to add a log-file flag so you can generate a log to see more what's going on.

That error looks like a firewall blocking a connection or your network isn't up yet.

3

Many thanks for the reply.

It seems that the network not being up was the likely issue.

I added a sleep command for 30 seconds, and it seems ok now.

Thanks again for the reply.

4

I'd still super suggest adding a log file even with just hardly any info.

That'll give you some idea if something goes wrong and at normal logging, it won't take much space either.

5

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