NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

wagb4's avatar
wagb4
Aspirant
Sep 07, 2014

Can't Use NFS to Access Home Shares

ReadyNAS model 102, Firmware version 6.1.8 - Tried to mount (on Linux) via entry in fstab a user's home folder and I get the error: mount.nfs: access denied by server while mounting <IP address / user's name>

I changed the share to mount in fstab to "/data/Pictures" and that worked. And yes the Home folders is enabled and the allow NFS access is enabled for Home shares; and the NFS service is enabled.

I tried with and without the volume name "data".

I was trying to get a NFS mount command to work for a Home folder and can not, so I tried the fstab route. This is implying that NFS is really not enabled for the Home folders. I can mount home folders using SMB, but that doesn't give me file permissions.

I want to mount NAS shares and retain Linux file permissions. How do I do that. A related problem is whenever I mount the NAS the owner comes up as root. Why cannot the NAS administrator see Home folders - shouldn't admin be able to see everything on the NAS?

Any suggestions or ideas where to look would be helpful.

Thanks.

17 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Does specifying the type of the connection make any difference? e.g.

    sudo mount -t nfs 192.168.XXX.XXX:/home /mnt/NFS


    What version of nfs-common do you have installed?
  • No, specifying the protocol (-t nfs) in the mount command does not change a thing.

    nfs-common verson is 1:1.2.5-3ubuntu3.1 on my Linux Mint vesion 13.
    nfs-common verson is 1.1.2.8-6ubuntu1.1 on a Linux Mint version 17.

    Both Linux Mint systems give the same results. Good thought! Thanks for the idea.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    If you download your logs (System > Logs > Download Logs), what does your initrd.log look like?
  • initrd.log seems to only include actions performed during original setup of the NAS.

    [2014/09/03 19:39:18] Factory default initiated due to new disks (no RAID, no partitions)!
    [2014/09/03 19:39:23] Defaulting to X-RAID2 mode, RAID level 1
    [2014/09/03 19:39:50] Factory default initiated on ReadyNASOS 6.0.4.
    [2014/09/03 12:19:46] Updated from ReadyNASOS 6.0.4 (1364529349) to 6.1.8 (1398980083).
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    That's a big firmware jump.

    Have you loaded much data on yet?

    Can you try backing up your data, doing a factory default (wipes all data, settings, everything) and restoring your data from backup?
  • The NAS is only a week old and that jump in firmware versions was when I checked for updates during the intial setup. There is no data on the NAS that I care about. I have been reluctant to copy files to the NAS until I understand how it works and how I should organize files on the NAS. And most importantly how I can access it on the LAN.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Yes, well the last factory default (in this case on initial setup) and the subsequent firmware updates and OS Re-installs are logged in initrd.log

    Seeing you haven't put data on yet, I would suggest you do a factory default e.g. via System > Settings > Update > Perform Factory Default in the Dashboard.

    This will give you a clean setup on 6.1.8. After doing that can you enable NFS for your home shares and see if it works any better for you?

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More