Mounted (encrypted) drive stays empty

Something is going wrong in retrieving the contents from a mounted and encrypted acd drive.

The following works fine:

rclone ls encrypted-drive:
504639084 folder/folder/file.ext
2016/10/25 18:05:42 
Transferred:      0 Bytes (0 Bytes/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:        1.8s

Which gives me indication that everything is setup right. Uploading always work a-ok with the move command.

However, when I try to mount the drive it goes wrong:

sudo rclone mount encrypted-drive: /home/media --allow-other --dir-cache-time=2m --no-modtime &
[1] 907
ls -l media
total 0

Doesn’t really matter how long I wait, the folder will stay empty.

I am mounting with the sudo command, not sure if this can be overcome on my system. Interestingly enough though, when i login as root the clone ls encrypted-drive: command returns nothing:

su root
rclone ls encrypted-drive:
2016/10/25 18:14:29 
Transferred:      0 Bytes (0 Bytes/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:        1.7s

I am really unsure as to what is going on. Mounting the unencrypted drive works just fine.

Specs:

  • OpenVZ VPS (FUSE module enabled)
  • Latest rclone beta version (today)

in your first example you use encrypted-drive: but in your second and third you use crypt:.
if you run the mount command with encrypted-drive: as the source everything else should work.

Darn, that seems to be an edit mistake on my side. In reality the drive is called “crypt” indeed, but i figured i’d call it encrypted-drive for clarity sake in my examples. I’ve updated the OP and fixed the typo.

The problem remains, anyone encountered something like this before?

If you are using it as root and as a user then likely they are using different config files. ie /home/user/.rclone.conf and /root/.rclone.conf. Pass in the location of the config file explicitly with the --config flag and see if that helps.

1 Like

My next guess is that you run the first command as a normal user but the last two as root. This is making rclone use different configs. You should be able to run all rclone commands as nonroot, even mount. If you still have a problem try running rclone with -v for verbose.

1 Like

Those sound like probable causes, I will try them out later tonight and report back!

I have to mount as root because my normal user doesn’t have privileges to acces /etc/dev (I think it was that directory). I tried solving this but apparently it has a root (pun intended) cause in that the fuse module is shared between clients in OpenVZ and my host would need to give permissions to my normal user account. To say the least OpenVZ is not really suited for this but I managed to grab a good deal so I will have to deal with it :slight_smile:

Using the --config /home/user/.rclone.conf command fixed my problem! Many thanks for the support guys! Looking forward to all the exciting things to come in rclone!

1 Like

I am having the same issue as this but changing the config does nothing. I only have the one config file in root. /root/.config/rclone/rclone.conf

Drive drive
crypt crypt
gcrypt crypt
remote amazon cloud drive

crypt is my ACD and it is mounted with no issues.
I can mount Drive and I can see the folders and everything.

This is the code I am using.
rclone mount -v --allow-non-empty --allow-other --read-only gcrypt: /home/MYUSERNAME/CDrive &

Have also tried removing everything but allow-other

Here is running with -vv

2017/03/11 03:09:34 INFO : Encrypted Google drive root ‘files’: Modify window is 1ms
2017/03/11 03:09:34 DEBUG : Encrypted Google drive root ‘files’: Mounting on “/home/MYUSERNAME/CDrive”
2017/03/11 03:09:34 DEBUG : Encrypted Google drive root ‘files’: Root()
2017/03/11 03:12:10 DEBUG : : Dir.Attr valid=1m0s ino=0 size=0 mode=drwxr-xr-x
2017/03/11 03:12:10 DEBUG : : Dir.ReadDirAll
2017/03/11 03:12:10 DEBUG : : Reading directory
2017/03/11 03:12:10 DEBUG : Google drive root ‘files’: Reading “”
2017/03/11 03:12:10 DEBUG : knh54m6829202gq56sua5s: Not including undecryptable directory name: Bad PKCS#7 padding - too long
2017/03/11 03:12:10 DEBUG : bf64vicingijokrn7g2o78: Not including undecryptable directory name: Bad PKCS#7 padding - too long
2017/03/11 03:12:10 DEBUG : Google drive root ‘files’: Finished reading “”
2017/03/11 03:12:10 DEBUG : : Dir.ReadDirAll OK with 0 entries
2017/03/11 03:12:17 DEBUG : : Dir.ReadDirAll
2017/03/11 03:12:17 DEBUG : : Dir.ReadDirAll OK with 0 entries

Any help would be amazing.

*EDIT
I have solved the issue. I deleted the remote and renamed it gdrive. It may have been an issue because of capital letters. I had it as GDrive before. Now it mounts with no issue. :slight_smile:

I am running rclone v1.35-158-g4652db3β
(side note: I cannot delete the folders created when copying the new betas. I get a permissions denied error. (1:529)# rm -r “/root/rclone-v1.35-149-g5fba913?-linux-amd64/”
rm: cannot remove ‘/root/rclone-v1.35-149-g5fba913?-linux-amd64/’: No such file or directory
)

Thanks

Excellent - well done!