Unraid Version 6.12.13

 

Hi everyone! I'm new to unraid and this is my first time posting here so I'll keep it brief, and hopefully provide all required information.

 

Unraid: Everything works. I have mapped it as a network drive (Y:) and am happy with the results.

 

Rclone: I use it via CMD (on my pc) - having to go through all my files via cmd prompts is a pain.

 

Bright idea: Let's mount my rclone union onto my unraid, and access it as a mapped network drive!

 

What I've done:

 

I installed the rclone plugin on unraid (waseh 1.68.1) as well as user scripts.

 

Ultimately my goal is to:
1) Have a folder ("Cloud") on unraid, that I can access through "Y:"
2) This "Cloud" folder = my rclone union. The files exist on my unraid + in my rclone union

 

I tried using the mount command but the files don't show up. I followed spaceinvader's guide (https://www.youtube.com/watch?v=-b9Ow2iX2DQ)

 

Here's the code I used:

#local mount on unraid
mntpoint="/mnt/disks/rCloud"

#rclone union
remoteshare="thedrive:"

#---

mkdir -p $mntpoint

rclone mount --max-read-ahead 1024k --allow-other $remoteshare $mntpoint &

 

To clarify, when I run "rclone lsf thedrive:" (via the terminal on unraid) it shows my files, so I'm confident my unraid server can access rclone in the same way my computer can. I just can't get a visual mapped network drive folder to easily manage my files.

 

So... is mounting the right course of action and shall I attempt to make it work? Will it?

 

Perhaps I should instead copy the rclone union's files onto my NAS, and then schedule a SYNC via userscripts to run each night?

 

Image attached = my (hopefully) user experience.

If running on unraid I would advise not making a /mnt point i would make or use an existing share such as /mnt/user/system/ mount point
as /mnt is in ram and doesn't have free space....

 

Based on your explanation and the image provided, it seems like you're aiming to mount the rclone union to a directory on your Unraid server and access it visually as a mapped network drive. Let's troubleshoot and consider alternatives to achieve your desired outcome.

 

Summary:

Primary Solution: Mount the rclone union using the command with --vfs-cache-mode writes, make sure to add it as an Unraid share, and map it as a network drive.

Alternative Solution: Use rclone sync to copy files from the cloud to your NAS and keep them updated via scheduled scripts.

Issues and Recommendations:

 

1. Check the Mount Command Execution

Your current command looks mostly correct, but it might be missing some important options or running in an environment that doesn’t persist properly.

Consider adding --vfs-cache-mode writes to handle writing more smoothly

 

rclone mount --max-read-ahead 1024k --allow-other --vfs-cache-mode writes $remoteshare $mntpoint &

 

--vfs-cache-mode writes is needed to ensure smoother file browsing and interactions, especially when using it as a network share.

 

2. Mapping the Mount to the Network Drive

After you have mounted the rclone union at /mnt/disks/rCloud, make sure this path is shared through Unraid.

You can do this by going to your Unraid GUI:

Navigate to the “Shares” tab.

Add a new share and set the path to /mnt/disks/rCloud.

Set appropriate permissions for accessing the share on the network.

Once the share is configured, you should be able to map it in Windows as a network drive (e.g., Y:).

 

3. Persistent Mount

If your mount command isn’t persisting after reboots, you can use the User Scripts plugin to automate the mounting process:

#!/bin/bash
mntpoint="/mnt/disks/rCloud"
remoteshare="thedrive:"

mkdir -p $mntpoint
rclone mount --max-read-ahead 1024k --allow-other --vfs-cache-mode writes $remoteshare $mntpoint &

Set the script to run at startup so that the mount persists after reboots. -Unriad user script plugin at first array start...

 

Verifying File Visibility

After running the mount command, try listing the files in /mnt/disks/rCloud to verify they are accessible:

 

ls /mnt/disks/rCloud

 

If files appear in the command line but not through the network drive, it could be a permissions issue. Ensure that the permissions for /mnt/disks/rCloud allow read and write access for other users.

5. (Recommened) - Alternative Approach: Sync Instead of Mounting

If mounting continues to be problematic or if performance is not as expected, you could consider syncing the rclone union files to a folder on your NAS and accessing them locally.

You can set up a sync script using User Scripts
 

rclone sync thedrive: /mnt/user/Cloud --verbose

You could schedule this script to run at regular intervals (e.g., nightly). This way, your "Cloud" folder on the NAS will stay in sync with the remote.
cron daily: https://crontab.guru/every-day

custm cron: 0 0 * * *

 

Thank you so much for the detailed response. I am going to try this as soon as I get a chance.

I have followed the instructions and everything is working great. I'm able to see the shared files etc. The one thing I can't figure out is how to set the path of the share:

 

2. Mapping the Mount to the Network Drive

After you have mounted the rclone union at /mnt/disks/rCloud, make sure this path is shared through Unraid.

You can do this by going to your Unraid GUI:

Navigate to the “Shares” tab.

Add a new share and set the path to /mnt/disks/rCloud.

Set appropriate permissions for accessing the share on the network.

Once the share is configured, you should be able to map it in Windows as a network drive (e.g., Y:).

 

I can't see a field in the Share setup (see attached).

You will need to stop the array and add a share manual to SMB extra. since it not a standard share under /mnt/user

You can make a share beforehand and use that path for the mount. Since you have a mount directly to disk you will need to use samba smb conf option to add the disk share.

Unraid WebUi > Settings > SMB
SMB Extras

#example that should work:

[RCloud] 
        path = /mnt/disks/rCloud
        comment = Rclone Disk Share
        browseable = yes
        # Public
        public = yes
        writeable = yes
        case sensitive = auto
        preserve case = yes
        short preserve case = yes
        vfs objects = catia fruit streams_xattr
        fruit:encoding = native

you can cat/etc/samba/sbm-shares.conf
to see your other shares...

break down example to add a share:
 

[Shared]
   path = /srv/shared
   browseable = yes
   writable = yes
   guest ok = yes
   create mask = 0777
   directory mask = 0777

 

This configuration:

[Shared] is the name of the share as it will appear on the network.

path is the directory being shared.

browseable allows users to see the share when browsing.

writable allows users to write to the share.

guest ok allows guest access (no password required).

create mask and directory mask set default permissions for new files and directories.

I added the code to SMB extras and restarted the array. On the shares screen I still can't see the share.

 

 

You will never see the disk share in the share screen....
the share is now being shared via samba via the extra options... so if you go to you network share on unraid:



you will now see the Rcloud share.

I thank you for taking the time to help me. I really do appreciate it.

 

Unfortunately I do not see the share there:

 

Reboot unraid check again is the share there?

if your not seeing Rcloud you may need to restart samba.

otherwise your extra samba option may not be correct.

please confirm the share path.
/mnt/disks/rCloud

is correct. as i don't have your paths for the actual data and the path for "the drive"
 

Tried rebooting. Didn't change anything.

 

I'll clearly lay out everything I've done so far.

 

1) Set up unraid, created array called "SERVER" & a user w/ permission to access that.

2) Mapped SERVER to win11 PC. "\\192etc\SERVER"

3) Installed rclone plugin. Set up the config file of rclone (imported from my PC) with a union called "thedrive:" which is made of 4 onedrives.

4) Followed the steps you initially outlined, using the code verbatim to mount my rclone drive to unraid. [mntpoint="/mnt/disks/rCloud"
remoteshare="thedrive:"]

5) tested it using "ls /mnt/disks/rCloud" - I could see my files in the command (of unraid)

6) Pasted the supplied SMB code verbatim, into the extras area of SMB:

 

[RCloud] 
        path = /mnt/disks/rCloud
        comment = Rclone Disk Share
        browseable = yes
        # Public
        public = yes
        writeable = yes
        case sensitive = auto
        preserve case = yes
        short preserve case = yes
        vfs objects = catia fruit streams_xattr
        fruit:encoding = native

 

7) Restarted unraid.

ok, thanks for the clarifications

You will need to edit eh smb extra option to fix the samba share under smb extra...

at these steps

1) Set up unraid, created array called "SERVER" & a user w/ permission to access that.

2) Mapped SERVER to win11 PC. "\\192etc\SERVER"

you may have different samba share settings needed.

so cat

cat /etc/samba/smb-shares.conf

This is the share tab that you have for other shares. Find one that is working for you and fix the share setting to match that share settings change the top [something]
and set the path to /mnt/disks/rCloud
as in the example posted above...

then check the samba setting on unraid
 

testparm

 this will load the smb conf of what is currently running.

then check windows side if share exist if still no please post web UI tool > diag
at attached your diagnostic file.

Edited November 6, 20241 yr by bmartino1

IT WORKS! THANK YOU SO MUCH! I have learned a lot from this experience. I appreciate your assistance. Made a small donation via paypal. Not much, but a token of my appreciation nonetheless.

Edited November 6, 20241 yr by jtest

Okay, maybe I jumped the gun. It can only be read from my Win11 PC, but I can't modify.

 

 

I used the cmd (in unraid) to see if I could write from there, and it works. The copy command created a file in thedrive: which is reflected in the rCloud folder:

 

 

at this point, its all about make edits to your share.

you may need options like creat mask force mask and valid users

as your at the samba issue of who touched what where and who can touch what where.
Would need your share info to assist further.

as there are all kinds of options, you can have that you may need:

 

#guest account = nobody

read only=no
guest ok=yes
browseable=yes
writeable=yes
acl map full control=yes
acl allow execute always=yes
map archive=yes
map system=yes
map hidden=yes
force user=nobody
force group=nogroup
create mask=0777
directory mask=0777
force create mode = 0777
force directory mode = 0777

 as this appears to be a permission issue 

Normally unraid would have you write 777 "docker safe permission" to the folder...

Since this is rsync we may want to keep certain file permissions.
We need to know what user has access to the folder and either run
 

chmod 777 -R /mnt/disks/rCloud
chown nobody:user -R /mnt/disks/rCloud

to set read write permission...

Which will set permission to all files and folder that unraid will be able to use to touch the files... 

or edit samba to set the force user force group to what they are,

this is where I would open mc terminal and confirm who owns what. As I can't seem to remember/ forget the command to grab that data...

so type mc go to the folder.

file > advance crown

Example

 

as you can see, completedProject is 777 read write execute and the owner nobody and group users can touch and use the files.

Edited November 7, 20241 yr by bmartino1

ls -l /path/to/file_or_directory

Example Output:

-rwxr-xr-- 1 owner group 12345 Oct  6 10:00 /path/to/file_or_directory

 

Breakdown of the output:

-rwxr-xr--: The file permissions (read, write, execute for the owner, group, and others).

r = read, w = write, x = execute.

First set (owner), second set (group), third set (others).

1: The number of hard links to the file.

owner: The username of the file's owner.

group: The name of the group that owns the file.

12345: The file size in bytes.

Oct 6 10:00: The last modified date and time.

/path/to/file_or_directory: The file or directory path.