Failed to create file system for encrypted remote

Help and Support
1

What is the problem you are having with rclone?

Cant sync with my encrypted remote.

What is your rclone version (output from rclone version)

rclone v1.54.1

  • os/arch: linux/arm
  • go version: go1.15.8

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Raspbian headless

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

Onedrive

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

Anything related to sending/syncing files using crypt remote.
FYI, everything is working fine with the onedrive remote (been syncing files with crontab for a few days).
So I set a crypt drive poiting to a specific location in onedrive.
Here is a example command :

   sudo rclone -vv copy /home/pi/rclone-upload.log drivecrypt:

The rclone config contents with secrets removed.

[Bitwarden]
type = onedrive
scope = onedrive
region = global
token = {"access_token"}
drive_id = blabla
drive_type = personal

[drivecrypt]
type = crypt
remote = Bitwarden:Utils/Saves/Bitwarden_volume/
filename_encryption = standard
directory_name_encryption = true
password = blabla
password2 = blabla

A log from the command with the -vv flag

2021/03/11 11:40:05 DEBUG : rclone: Version "v1.54.1" starting with parameters ["rclone" "-vv" "copy" "/home/pi/rclone-upload.log" "drivecrypt:"]
2021/03/11 11:40:05 DEBUG : Creating backend with remote "/home/pi/rclone-upload.log"
2021/03/11 11:40:05 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2021/03/11 11:40:05 DEBUG : fs cache: adding new entry for parent of "/home/pi/rclone-upload.log", "/home/pi"
2021/03/11 11:40:05 DEBUG : Creating backend with remote "drivecrypt:"
2021/03/11 11:40:05 Failed to create file system for "drivecrypt:": didn't find section in config file

By the way,

rclone -vv ls drivecrypt:

Looks to be working fine :slight_smile:

2021/03/11 11:43:43 DEBUG : rclone: Version "v1.54.1" starting with parameters ["rclone" "-vv" "ls" "drivecrypt:"]
2021/03/11 11:43:43 DEBUG : Using config file from "/home/pi/.config/rclone/rclone.conf"
2021/03/11 11:43:43 DEBUG : Creating backend with remote "drivecrypt:"
2021/03/11 11:43:43 DEBUG : Creating backend with remote "Bitwarden:Utils/Saves/Bitwarden_volume/"
2021/03/11 11:43:45 DEBUG : fs cache: renaming cache item "Bitwarden:Utils/Saves/Bitwarden_volume/" to be canonical "Bitwarden:Utils/Saves/Bitwarden_volume"
2021/03/11 11:43:46 DEBUG : lol: Skipping undecryptable dir name: illegal base32 data at input byte 3
2021/03/11 11:43:46 DEBUG : 5 go routines active

Help greatly appreciated !

2

hello and welcome to the forum,

each command is using a different rclone.conf file.
Using config file from "/root/.config/rclone/rclone.conf"
Using config file from "/home/pi/.config/rclone/rclone.conf"

the first time you use drivecrypt:, the folder should be empty.

3

Thank you for having a look. How can I solve this rclone.conf problem ?
Is there any way to force rclone to use the second one ?
Oh, is it because I did not use sudo for the second one ?

By the way, there is a document in the folder because I wanted to make sure that rclone "sees" inside this folder.

EDIT : oh man, rclone created two config file I get it...

Is there any way to force it to use the non root one ?

4

not a good idea to have non-crypted files inside a crypted remote, that is why rclone is complaining.

about the config file
https://rclone.org/docs/#config-config-file

5

Yes I am going to delete this file as soon as this is sorted.
Guess I have to start everything from scratch using sudo rclone config instead of rclone config.

EDIT : man I read this thing multiple times and didn't see this. Thanks a lot. Of course it's perfectly working now.

6

sure, glad you got it working.

7

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