Another "Failed to create file system for" thread, pretty sure no typos

What is the problem you are having with rclone?

When running my rclone systemd service copied from an existing working machine to a new Ubuntu server minimal system, I'm now encountering "Failed to create file system for "secret:data/media": didn't find section in config file

I've searched the forums and triple checked my configs but can't find the source of the problem. The exact same commands and configs (with only the mount point changed) run perfectly fine on my other system. I've double checked all folder permissions as well and everything this service touches is r/w for administrator:administrator

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

rclone v1.62.2

  • os/version: ubuntu 22.04 (64 bit)
  • os/kernel: 5.15.0-72-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.20.2
  • go/linking: static
  • go/tags: none

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

Google drive, enterprise workspace

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

systemd rclone.service

Description=GMedia Rclone Service systemd-networkd-wait-online.service rclone-precache.service

; Create mount point target
ExecStartPre=+/bin/mkdir -p /mnt/nas/media-cloud
ExecStartPre=+/bin/chown administrator:administrator /mnt/nas/media-cloud

ExecStart=/usr/bin/rclone mount secret:data/media /mnt/nas/media-cloud \
--allow-other \
--allow-non-empty \
--buffer-size 32M \
--use-mmap \
--dir-cache-time 5000h \
--log-file /mnt/nas/logs/rclone/rclone_mount.log \
--log-level DEBUG \
--poll-interval 10s \
--umask 002 \
--user-agent rclonedrive \
--rc \
--rc-addr [::]:5572 \
--rc-no-auth \
--cache-dir=/mnt/nas/media-cache \
--drive-pacer-min-sleep 10ms \
--drive-pacer-burst 200 \
--vfs-cache-mode full \
--vfs-cache-max-size 4000G \
--vfs-cache-max-age 5000h \
--vfs-cache-poll-interval 5m \
--bwlimit-file 100M \
--config /home/administrator/.config/rclone/rclone.conf

ExecReload=/bin/kill -USR1 $MAINPID
ExecStop=/bin/fusermount -uz /mnt/nas/media-cloud


The rclone config contents with secrets removed.

[BlueWillows Google Workspace]
type = drive
client_id = REDACTED
client_secret = REDACTED
scope = drive
token = REDACTED
team_drive = 

type = crypt
remote = BlueWillows Google Workspace:server-01
password = REDACTED
password2 = REDACTED

A log from the command with the -vv flag

quick additional info, data/media does exist on the remote and mounts correctly on my other system using the same systemd service with the mount point being in the administrator home directory instead of /mnt

can you post

rclone listremotes --config /home/administrator/.config/rclone/rclone.conf

command result?

1 Like

Thanks for your quick response!

administrator@rclonemergerfs:~$ rclone listremotes --config /home/administrator/.config/rclone/rclone.conf
BlueWillows Google Workspace:

I also updated the log with a pastebin. for some reason the log includes tons of erroneous "<0x00>"

Does simple cmd mount work?

/usr/bin/rclone mount secret:data/media /mnt/nas/media-cloud --config /home/administrator/.config/rclone/rclone.conf

hello and welcome to the fourm,

at first rclone.service is happy with Creating backend with remote "secret:data/media"
only after vfs/refresh, the problem starts.
then rclone.service is happy again with Google drive root '...': Checking for changes on remote

so i would look at rclone-precache.service
can you post that service file?

1 Like

running it now with -vv and so far im not seeing the failure. but that said there is about 96TB on this remote and it takes roughly 20 minutes to fully mount.

I think you're onto something there,

Description=rclone precache


ExecStart=/usr/bin/rclone rc vfs/refresh recursive=true --rc-addr



I think you have a general logic error.

You want the preache in your mount service file, but you can't run the precache until the mount is going.

I use an execpost command as that generally makes more sense and is easier and it runs async so it fires and forgets so the mount is ready sooner.

1 Like

ok, just do what you did with GMedia Rclone Service
--config /home/administrator/.config/rclone/rclone.conf

or follow the example at
ExecStartPost=/usr/bin/rclone rc vfs/refresh recursive=true --url _async=true

1 Like

OOOOOHhhhhhhh.... ok. so let me remove the precache service, ill add it as the post exec instead and now im running again to test

so this is interesting. I stopped the systemd services for rclone, the precache and mergerfs then disabled all of them and rebooted. now the log file I listed is still getting these entries:

2023/05/26 08:57:44 Failed to create file system for "secret:data/media": didn't find section in config file
2023/05/26 08:57:49 NOTICE: Serving remote control on http://[::]:5572/

when I do

sudo ps aux | grep rclone

all i see is the grep process

administrator@rclonemergerfs:~$ ps aux | grep rclone
adminis+     914  0.0  0.0   4020  2048 pts/0    S+   14:03   0:00 grep --color=auto rclone

I'm too scatterbrained. now that I've had coffee, the log was being populated by another VM trying to run the rclone service. After disabling that one, the log is no longer populated.

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