What is the problem you are having with rclone?
Trying to create an autostart/automount script, and when I manually mount via SSH it locks/freezes when I browse the folders. It takes a very long time to access/browse media content.
What is your rclone version (output from rclone version
)
rclone v1.45
-
os/arch: linux/arm
-
go version: go1.11.6
(Installed via sudo apt-get rclone install)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
OSMC on a Vero 4k +
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 crypt:media /home/osmc/gsuite --allow-non-empty --size-only --dir-cache-time=2m --fast-list --vfs-read-chunk-size=96M --vfs-cache-max-age 675h --vfs-read-chunk-size-limit=1G --buffer-size=48M
The rclone config contents with secrets removed.
[gsuite]
type = drive
client_id = x
client_secret = x
scope = drive
token = {"access_token":x
[crypt]
type = crypt
remote = gsuite:media
filename_encryption = standard
directory_name_encryption = true
password = x
A log from the command with the -vv
flag
[https://pastebin.com/ghj6sjTJ](https://pastebin.com/ghj6sjTJ)
I tried to follow these instructions:
cd /home/osmc
mkdir scripts
cd scripts
nano mountscript.sh
chmod +x mountscript.sh
mountscript.sh looks like this
$!/bin/bash
rclone mount crypt:media /home/osmc/gsuite --allow-non-empty size-only --dir-cache-time=2m --fast-list --vfs-read-chunk-size=96M --vfs-cache-max-age 675h --vfs-read-chunk-size-limit=1G --buffer-size=48M
Then I did:
*sudo nano /lib/systemd/system/test.service
and typed in:
[Unit]
Description=rclone_mount
After=network.target[Service]
ExecStart=/home/osmc/scripts/mountscript.sh[Install]
WantedBy=multi-user.target
and at last:
*sudo systemctl daemon-reload
*sudo systemctl enable test.service
*sudo systemctl start test.service
But it does not mount when I restart. (This is my first time trying such a script as this)
Output from this command:
*sudo systemctl start test.service
Failed to start test.service: Unit test.service has a bad unit file setting.
See system logs and ‘systemctl status test.service’ for details.
I haven’t found out how to see the system logs yet.