NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS RN212 - Alerts Email, NFS and default shares
OS6.10.2 1) Setting up alerts - I have tried to confiugure the EMail alerts, but it fails on sending a test mail. The host I have as smtp.hosts.co.uk on port 465, the 'From' is my Email add...
steveTu wrote:
2) The default shares - Music, Pictures and Videos. I would like to create a mountable NFS share above those as 'media' (as my old ReadyNas Duo had) - so I can keep structures the same across the NASs. Can I just delete the existing shares and recreate them under a new 'media' share? Any implications?
You can delete the default shares, and create your own media share. That could have subfolders for Music, Pictures and Videos - or not, that is up to you.
You can't create shares within shares though (which couldn't be done on the Duo either).
The mount for NFS will be /data/media - unlike the Duo, the volume is included in the exported path.
steveTu wrote:
2) The default shares - Music, Pictures and Videos. I would like to create a mountable NFS share above those as 'media' (as my old ReadyNas Duo had) - so I can keep structures the same across the NASs. Can I just delete the existing shares and recreate them under a new 'media' share? Any implications?
You can delete the default shares, and create your own media share. That could have subfolders for Music, Pictures and Videos - or not, that is up to you.
You can't create shares within shares though (which couldn't be done on the Duo either).
The mount for NFS will be /data/media - unlike the Duo, the volume is included in the exported path.
I think there may be implications of changing Music,Pictures and Videos - which leads me to another question re ssh.
I am just prepping the 212 - copying across the data from the older DUO and mimicking the DUO's structure. I have had a couple of minor issues (as noted here) and on a couple of occasions have seen the suggestion of logging into the 212 via ssh. I had the SSH set up ok and had enabled SSH on my local 212 userid. I could log in as root ok, but I could not log in as my local user - that user got a simple 'Rejected' message.
My user on the 212 is set up in the primary group 'dev'. Am I right in then saying that SSH access to the 212 is restricted to users that belong to the admin group? If so, I can only see a way to set up my users primary group - is there a way to set up multiple groups for a user - ie can my user belong to admin and dev?
Then onto why I was wanted to log in - I couldn't see my music appearing on clients connected to the 212 - even though that data had been copied across. Looking at the /etc/minidlna.conf on the 212, the pointers are to the default /data/Music,Pictures and Videos shares. So the implication of changing the default shares is that minidlna does not appear to pick up the change in the config (even though the new 'media' share I created as the top level - ie /data/media/[Music|Pictures|Videos] - was set up at DLNA enabled.
So, am I also correct in thinking that if the default media folders are changed, then any configs HAVE to be modified via SSH - and if so - what does that do to the guarantee etc?
steveTu wrote:I think there may be implications of changing Music,Pictures and Videos ...
No, they are just shares. You can rename them or delete them.
steveTu wrote:
My user on the 212 is set up in the primary group 'dev'. Am I right in then saying that SSH access to the 212 is restricted to users that belong to the admin group? If so, I can only see a way to set up my users primary group - is there a way to set up multiple groups for a user - ie can my user belong to admin and dev?
If you are working in the OS partition (including /etc ), log in as root. Even logging in as admin can get you into trouble. But you can enable other users for ssh by going to their account settings, clicking on ssh, and then checking "allow shell access".
steveTu wrote:
Then onto why I was wanted to log in - I couldn't see my music appearing on clients connected to the 212 - even though that data had been copied across. Looking at the /etc/minidlna.conf on the 212, the pointers are to the default /data/Music,Pictures and Videos shares.
Hmmm. Mine has a full list of shares. Ones that have DLNA disabled are commented out.
For instance, with media:
- When DLNA is disabled I see #dashboard:available=0 media_dir=/data/media
- When DLNA is enabled I see media_dir=/data/media
This changes immediately when I change the DLNA setting for the share in the web ui. Did you set the media type to "all" when you enabled DLNA?
steveTu wrote:
So, am I also correct in thinking that if the default media folders are changed, then any configs HAVE to be modified via SSH - and if so - what does that do to the guarantee etc?
No, you shouldn't have to modify the configs with ssh.
As far as support implications, Netgear reserves the right to deny support if they believe your use of ssh caused damage.
OK - one bit at a time.
SSH - I think I saw an effect and assumed... my mistake.
I have my user 'stevet' - it has Shell Access on the Accounts->SSH -> Shell access option ticked. When I issue ssh -l stevet my.nas.addr from my linux terminal I get a simple:
Rejected
Connection to my.nas.addr closed
..no request for password.
So I tried ticking/unticking and applying the changes to stevet and still got the same result (looking at the screen now, if I untick the shell access and apply that change, the next time I go in the tick is back).
So I tried using root - and that worked fine with the admin password. So, I assumed (stupidly) that maybe the group was the problem - so set up another user 'nasadmin' in group admin - and ticked shell access for that user and it worked fine. So again I assumed my original thoughts on the group were correct.
I have then tried to log in via ssh with another user in a non-admin group and that works as you say - ie simply ticking the shell access box allows shell access irrespective of the group. So obviously my assumptions were wrong.
So my question should have just been - 'I have a user, that has shell access ticked, but when trying to access the NAS via ssh gets 'Rejected' before any password attempt. Any ideas as to why?' . The UID:GID is 1000:1000, I have two ssh keys loaded for that user as well (one per laptop) if that makes any difference.
steveTu wrote:
'I have a user, that has shell access ticked, but when trying to access the NAS via ssh gets 'Rejected' before any password attempt. Any ideas as to why?' . The UID:GID is 1000:1000, I have two ssh keys loaded for that user as well (one per laptop) if that makes any difference.
Just tested this on my own NAS with the same UID:GID, but without ssh keys. The log in worked with no problem.
I did find that I couldn't edit the group or ssh settings if I initially created a user with a weak password. That is a bug, but not directly related to your issue. JohnCM_S - can you log the bug I just found?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
