This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Up to now I have used my ReadyNAS 104 (firmware 6.10.0) from Windows. I have now rebuilt one of my machines with Linux Mint 22 and will do the same with my nother machines after I have worked through the teething problems.
The current teething problem is accessing my NAS from Linux. I had thought that CIFS was the way to do this but have just been told that NFS is the way to go.
I'm already on a fairly steep learning curve and clearly this question is part of that curve. However, can anyone tell me how I might go about enabling NFS on the ReadyNAS (without affecting my existing shares and data).
The current teething problem is accessing my NAS from Linux. I had thought that CIFS was the way to do this but have just been told that NFS is the way to go.
CIFS (SMB 1) is very old and being deprecated. SMB 3 is well supported on Linux, so there is no reason not to use it.
But if you want NFS for some reason, you can just enable it in system->settings and for each share. The default settings on the NAS should be fine.
The current teething problem is accessing my NAS from Linux. I had thought that CIFS was the way to do this but have just been told that NFS is the way to go.
CIFS (SMB 1) is very old and being deprecated. SMB 3 is well supported on Linux, so there is no reason not to use it.
But if you want NFS for some reason, you can just enable it in system->settings and for each share. The default settings on the NAS should be fine.
Probably nothing. Though you might find you get better performance if you reduce the number of threads to 4. The RN100 series doesn't have a lot of memory, and 4 threads would require fewer resources.
Just something to keep in mind if the performance seems sluggish.
Once you have enabled NFS on the Settings page and individually for each share you need to access, you will need to map the shares to a directory on your Linux system. I have a Pro2 dedicated to running OwnCloud and have several directories on my main NAS mapped in Read Only mode to that machine. That way, uploads can only go to the Pro2 but I can give access to shares on my main NAS for download. I decided to go with NFS instead of Samba for the mapping because it retains the Linux permissions.
Just Google how to map drives in Linux. You can do so temporarily via the command line or put them in fstab to make them automatic. Since I don't use any Linux system with a GUI on a regular basis, I don't know how to do it there, but I suspect there is a way.
Found some tutorials on mounting NFS shares on YouTube and wrote down the set of commands I was going to try. First up was to move my mount points from /mnt to /media, which I did (although in the tutorial video I was watching, he moved them to below his home directory):
Then install nfs-common...
sudo apt install nfs-common
That seemed to run ok but as often happens, a thought pinged to me - "What would I see if I viewed my NAS within Files right now?" In fact, I see this:
So next, I tried to click into the Music directory and was prompted for creds.
I wasn't expecting that as the tutorial I had been watching had stated that Linux wouldn't normally require user authentication on each share.
BTW - I see that '.local' has been appended onto the end of my NAS name. Will I need to take account of that when I come to actually issuing a mount command?
If I was to manually issue a mount command of the Backup share right now, would it look like this?
sudo mount -t nfs 192.168.1.41:/backup /media/nfs_backup
EDIT: I guess not, as typing that yielded:
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: access denied by server while mounting 192.168.1.41:/backup
Anyway, I went back into the NAS again to look at the share setup. It looks like this:
and
and
and
and
Does anyone have further wisdom for me in terms of getting this up and running?
Yes I did. Also did for the 4 or 5 other directories that I am trying to share to my Linux machine. Actually, I mis-named the directory initially - it's actually nas_backup and nas_music etc
You shouldn't have to open it that widly. But you blurred out the user names on the NAS, so that's the only recommendation I could make. Now that I see your Linux system is trying to connect as julian, is julian set up to access that share?
If you add users or permissions, you do usually have to go reset permissions so all existing files and folders have their permissions updated. So, try that next.
julian is indeed the logged-in linux user. But no, that user does not have permissions on those shares.
I'm probably going to oversimplify this massively now, but if I was to add julian as a user on the NAS and add that user to those shares, would linux then just assume that because the name is the same then that linux julian is the same as the NAS user julian?
If the above is true, then I would have thought that my previous addition of "Everyone" to the share would have enabled the linux user julian to access them?
But having said all that, you have suggested "resetting" permissions. So I have to see how to do that. I don't recall seeing that option so far.
Reset is on the share's File Access tab. It resets all files' and folders' permissions in that share to the current ones. It does so in the background, so you do need to give it time to complete.
OK, I did some more checking. SMB will only allow mounting for all users, which uses the ReayNAS Everybody permissions. It's a limitation of NFS, not the ReadyNAS specifically. You also need to specify the entire path, so 192.168.1.41:/data/music, assuming your data volume is named data.
If you don't want to set the permissions on the NAS to Everyone, you'll need to mount using SMB (cifs).
sudo mount -t cifs -o vers=3.0,username=authorizeduser //192.168.1.41.music /media/nas_music
Where authorizeduser has permissions to the share. This will prompt for authorizeduser's NAS password. vers=3.0 tells it to use SMB3 even though cifs is usually SMB1. Of course, SMB1 will also work on a ReadyNAS unless you've turned it off with SMBPlus, but SMB3 is more secure.
You can also include the password in the mount command:
sudo mount -t cifs -o vers=3.0,username=authorizeduser,password=userpass //192.168.1.41.music /media/nas_music
Then I performed the reset on both the Music and Pictures shares. Here are the success messages.
One thing I notice is that the shares are referred to as data\Music and data\Pictures. Also the word 'data' appears top left in the Shares screen. I'm not too sure what that refers to, but it has made me wonder: when I am trying to mount the share, should I be including data in the share path?
Also, I notice that if I now look at the permissions for the Music share, while it shows user julian to have read/write for SMB, it is not possible to assign any permission for that user when the protocol selected is NFS. As soon as I select NFS in the drop down, the user changes to Anyhost.
Further to that, if I go to Settings->Network access, julian has read/write, but in Settings->File access, read/write is not an option for user julian.
I did try to mount those two shares again but the same error is returned.
I tried adding data into the path but get the same error:
sudo mount -t nfs 192.168.1.41:/data/music /media/nas_music [sudo] password for julian: mount.nfs: access denied by server while mounting 192.168.1.41:/data/music
I think I'm fine staying with NFS and having 'Everyone' with access. However, if I go to Network access screen and select NFS, I am unable to add Everyone:
I can't help thinking I'm missing something fundamental here as it seems like providing open access to everyone should be pretty simple.
