Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Unable to mount Unraid NAS share

  1. #1
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Unable to mount Unraid NAS share

    I am using Ubuntu 24.04 and have nfs-utils installed.

    I have built a NAS and am trying to access a share on it.

    Code:
    makem@makem-22:~$ sudo mount -t nfs4 192.168.1.249/data /media/nas-media
    [sudo] password for makem: 
    mount: /media/nas-media: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.
           dmesg(1) may have more information after failed mount system call.
    makem@makem-22:~$
    I am not sure what to look for in dmesg.

    Edit: Installed nfs-common:

    Code:
    sudo mount -t nfs4 192.168.1.249/data /media/nas-media
    mount.nfs4: remote share not in 'host:dir' format
    The share is exported in the NAS but under the SMB SECURITY SETTINGS

    Does that mean only SMB sharing?
    Last edited by makem2; September 27th, 2024 at 02:10 PM. Reason: installed nfs-common and result

  2. #2
    Join Date
    Mar 2010
    Location
    Been there, meh.
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to mount Unraid NAS share

    I know nothing at all about Unraid. I do know NFS.

    nfs4 is wrong. Use nfs instead. The client and server will negotiate the version supported. The command it missing a ':' as well.

    To be clear,
    Code:
    sudo      mount        -t nfs      192.168.1.249:/data     /media/nas-media
    This assumes that
    Code:
    showmount -e 192.168.1.249
    shows 192.168.1.249:/data as being exported
    AND
    it assumes that /media/nas-media directory exists already.

    I am a bit worried that the IP is being provided via DHCP. Servers need static IPs, which are typically under .20 in a home environment. Using DHCP with a server is asking for problems. It will happen eventually.

  3. #3
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Unable to mount Unraid NAS share

    Quote Originally Posted by TheFu View Post
    I know nothing at all about Unraid. I do know NFS.

    nfs4 is wrong. Use nfs instead. The client and server will negotiate the version supported. The command it missing a ':' as well.

    To be clear,
    Code:
    sudo      mount        -t nfs      192.168.1.249:/data     /media/nas-media
    This assumes that
    Code:
    showmount -e 192.168.1.249
    shows 192.168.1.249:/data as being exported
    AND
    it assumes that /media/nas-media directory exists already.

    I am a bit worried that the IP is being provided via DHCP. Servers need static IPs, which are typically under .20 in a home environment. Using DHCP with a server is asking for problems. It will happen eventually.
    Code:
    makem@makem-22:~$ sudo mount -t nfs 192.168.1.249:/data /media/nas-media
    [sudo] password for makem: 
    Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
    Above did not finish.

    Code:
    makem@makem-22:~$showmount -e 192.168.1.249clnt_create: RPC: Unable to receive
    makem@makem-22:~$
    The IP address is static, being set in the router. Typo ':' as I was aware that should be there.

    I will have to find how Unraid exports - surely not just Windows when its Linux based.

    Thank you for your time (I was aware of your NFS knowledge and preference)

    Edit: /media/nas-media directory exists.
    Last edited by makem2; September 27th, 2024 at 04:17 PM. Reason: Added /media/nas-media directory exists

  4. #4
    Join Date
    Mar 2010
    Location
    Been there, meh.
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to mount Unraid NAS share

    Ah ... the dreaded RPC boot-timing issue. So, NFS is dependent on a few other services that need to work BEFORE it can work. I don't have them memorized, sorry. In general, the easiest solution is to reboot the server (your NAS) and reboot the NFS client. That fixes this issue 90% of the time. If it doesn't you'll need to dig into each depend service looking at log files (or journalctl) to figure out which isn't starting up, determine the issue and fix that. A few months ago, one of my NFS servers had the rpc.service refuse to start - no NFS workie. I don't recall the exact issue now, but something like /var/ had gotten full is typical. There's no way anyone here would know to ask those things, so you'll need to figure out why a service that nfs depends on isn't starting.

    https://docs.redhat.com/en/documenta...e_guide/ch-nfs says this, which I didn't know:
    NFSv4 has no interaction with portmapper, rpc.mountd, rpc.lockd, and rpc.statd, since they have been rolled into the kernel. NFSv4 listens on the well known TCP port 2049.
    NFS is the same on all Linux systems, so don't worry that the link is for RH. On my 20.04 NFS servers, rpcbind.service is still required to work. The rpc-statd.service is not, though is is running to support NFSv3 clients.

    Also, there are a few firewall ports that need to be open on the NFS server. I force 111, 2049 and 13025 ports to be allowed in from my NFS client systems to the server. 13025 is non-standard. I configured that port separately for some reason I don't recall now.

    Is your "NAS" a commercial product that would not be a generic Linux distro?
    Last edited by TheFu; September 27th, 2024 at 04:21 PM.

  5. #5
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Unable to mount Unraid NAS share

    Quote Originally Posted by TheFu View Post
    Ah ... the dreaded RPC boot-timing issue. So, NFS is dependent on a few other services that need to work BEFORE it can work. I don't have them memorized, sorry. In general, the easiest solution is to reboot the server (your NAS) and reboot the NFS client. That fixes this issue 90% of the time. If it doesn't you'll need to dig into each depend service looking at log files (or journalctl) to figure out which isn't starting up, determine the issue and fix that. A few months ago, one of my NFS servers had the rpc.service refuse to start - no NFS workie. I don't recall the exact issue now, but something like /var/ had gotten full is typical. There's no way anyone here would know to ask those things, so you'll need to figure out why a service that nfs depends on isn't starting.

    https://docs.redhat.com/en/documenta...e_guide/ch-nfs says this, which I didn't know:

    NFS is the same on all Linux systems, so don't worry that the link is for RH. On my 20.04 NFS servers, rpcbind.service is still required to work. The rpc-statd.service is not, though is is running to support NFSv3 clients.

    Edit: https://unraid.net/

    Also, there are a few firewall ports that need to be open on the NFS server. I force 111, 2049 and 13025 ports to be allowed in from my NFS client systems to the server. 13025 is non-standard. I configured that port separately for some reason I don't recall now.

    Is your "NAS" a commercial product that would not be a generic Linux distro?
    Wow, that is a lot to digest. No, I personally built it from scratch and the OS is on an SD card which must be present as it is loaded into ram on every boot.

    I will reboot with crossed fingers and report back.
    Last edited by makem2; September 27th, 2024 at 04:40 PM. Reason: added url

  6. #6
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Unable to mount Unraid NAS share

    I am getting this error now:

    Code:
    makem@makem-22:~$ sudo mount -t nfs 192.168.1.249:/data /media/nas-media
    [sudo] password for makem: 
    mount.nfs: access denied by server while mounting 192.168.1.249:/data
    makem@makem-22:~$
    My son set up Unraid and I remember although I usually use makem as username he asked me to use makem1. I have a makem1 account accessible by makem.

    I think I will leave well alone as I am so close until he returns next week.

    Edit: May be of interest as 2 errors mentioned:

    Code:
    makem@makem-22:~$ sudo mount -t nfs 192.168.1.249:/data /media/nas-media
    [sudo] password for makem: 
    mount.nfs: access denied by server while mounting 192.168.1.249:/data
    makem@makem-22:~$ sudo mount -t nfs -vvv 192.168.1.249:/data /media/nas-media
    mount.nfs: timeout set for Fri Sep 27 17:01:01 2024
    mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.249,clientaddr=192.168.1.59'
    mount.nfs: mount(2): No such file or directory
    mount.nfs: trying text-based options 'addr=192.168.1.249'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.249 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.1.249 prog 100005 vers 3 prot UDP port 50462
    mount.nfs: mount(2): Permission denied
    mount.nfs: access denied by server while mounting 192.168.1.249:/data
    makem@makem-22:~$
    On the NAS:

    Code:
    root@nas:~# showmount -e
    Export list for nas:
    /mnt/user/data *
    root@nas:~#
    My previous showmount was on the client without the nas IP

    On the NAS:

    /etc/exports shows:

    "/mnt/user/data" -fsid=100,async,no_subtree_check *(rw,sec=sys,insecure,anongid=100,anonuid=99,all_s quash)
    Last edited by makem2; September 27th, 2024 at 05:20 PM. Reason: added showmount nas result

  7. #7
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Unable to mount Unraid NAS share

    @TheFu, Reading https://docs.redhat.com/en/documenta...nfs#s1-nfs-how

    I find that the NAS does not have an /etc/exports directory to determine whether the client is allowed to access any of the exported file systems. As mentioned in the above url.



  8. #8
    Join Date
    Mar 2010
    Location
    Been there, meh.
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to mount Unraid NAS share

    Quote Originally Posted by makem2 View Post
    Code:
    makem@makem-22:~$ sudo mount -t nfs 192.168.1.249:/data /media/nas-media
    [sudo] password for makem: 
    mount.nfs: access denied by server while mounting 192.168.1.249:/data
    makem@makem-22:~$ sudo mount -t nfs -vvv 192.168.1.249:/data /media/nas-media
    mount.nfs: timeout set for Fri Sep 27 17:01:01 2024
    mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.249,clientaddr=192.168.1.59'
    mount.nfs: mount(2): No such file or directory
    mount.nfs: trying text-based options 'addr=192.168.1.249'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.249 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.1.249 prog 100005 vers 3 prot UDP port 50462
    mount.nfs: mount(2): Permission denied
    mount.nfs: access denied by server while mounting 192.168.1.249:/data
    makem@makem-22:~$
    On the NAS:

    Code:
    root@nas:~# showmount -e
    Export list for nas:
    /mnt/user/data *
    root@nas:~#
    My previous showmount was on the client without the nas IP

    On the NAS:

    /etc/exports shows:

    Code:
    /mnt/user/data -fsid=100,async,no_subtree_check *(rw,sec=sys,insecure,anongid=100,anonuid=99,all_squash)
    Has some options I've never seen before. I suspect they aren't necessary. An export on one of my NFS servers, converted for your situation (but with the wrong subnet) has this:
    Code:
    /mnt/user/data    172.22.22.0/24(fsid=4,rw,async,no_subtree_check)
    The main difference is that I restrict the allowed client subnet to one of my subnets. I think you have 3 fields when there should only be 2 fields. A field is separated by one or more whitespace characters. I'm amazed it ever worked before, if it did.

    For another NFS server, I have 1 export line for each client to each exported file system. That exports file has 63 lines (a bit cumbersome, I agree).
    Code:
    /d/D1           deneb(rw,async,root_squash,no_subtree_check,fsid=1)
    /d/D1           posc(rw,async,root_squash,no_subtree_check,fsid=1)
    Because I run a LAN DNS server, the hostnames map to specific IPs, but that is hidden. Most people would just have 1 line and use something like 192.168.24.0/24 as their network limiting option.

  9. #9
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Unable to mount Unraid NAS share

    Quote Originally Posted by TheFu View Post
    Has some options I've never seen before. I suspect they aren't necessary. An export on one of my NFS servers, converted for your situation (but with the wrong subnet) has this:
    Code:
    /mnt/user/data    172.22.22.0/24(fsid=4,rw,async,no_subtree_check)
    The main difference is that I restrict the allowed client subnet to one of my subnets. I think you have 3 fields when there should only be 2 fields. A field is separated by one or more whitespace characters. I'm amazed it ever worked before, if it did.

    For another NFS server, I have 1 export line for each client to each exported file system. That exports file has 63 lines (a bit cumbersome, I agree).
    Code:
    /d/D1           deneb(rw,async,root_squash,no_subtree_check,fsid=1)
    /d/D1           posc(rw,async,root_squash,no_subtree_check,fsid=1)
    Because I run a LAN DNS server, the hostnames map to specific IPs, but that is hidden. Most people would just have 1 line and use something like 192.168.24.0/24 as their network limiting option.
    'I think you have 3 fields when there should only be 2 fields. A field is separated by one or more whitespace characters.'

    I don't understand that but I think lets leave it until my son returns. I find he has put a 'data' directory in as a user! So it looks like I may have to set it up again from scratch with the proper paths layout. He is a Windows user.

  10. #10
    Join Date
    Mar 2010
    Location
    Been there, meh.
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Unable to mount Unraid NAS share

    MS-Windows users aren't gonna help you with Unix problems. Whatever. Good luck. The way that an MS-Windows user looks at storage is very, very, different from how Unix sees it.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •