• NFS not working after upgrade to 6.8


    hema
    • Minor

    After I upgraded the system I cannot mount any of Unraid NFS shares from debian client.

     

    It seems that NFS is not working at all, not even locally. 

     

    I have no way of replicating my findings and I only use NFS, not SMB.

    Anybody else, have you seen this?

     

     

    from client: 

     

    [tykki] showmount -e tower
    rpc mount export: RPC: Timed out

     

     [tykki] rpcinfo -p  tower
       program vers proto   port  service
        100000    4   tcp    111  portmapper
        100000    3   tcp    111  portmapper
        100000    2   tcp    111  portmapper
        100000    4   udp    111  portmapper
        100000    3   udp    111  portmapper
        100000    2   udp    111  portmapper
        100024    1   udp  48360  status
        100024    1   tcp  43585  status
        100003    3   tcp   2049  nfs
        100003    3   udp   2049  nfs
        100021    1   udp  40414  nlockmgr
        100021    3   udp  40414  nlockmgr
        100021    4   udp  40414  nlockmgr
        100021    1   tcp  33355  nlockmgr
        100021    3   tcp  33355  nlockmgr
        100021    4   tcp  33355  nlockmgr
        100005    1   udp  38496  mountd
        100005    1   tcp  45369  mountd
        100005    2   udp  58422  mountd
        100005    2   tcp  58399  mountd
        100005    3   udp  34615  mountd
        100005    3   tcp  49991  mountd

     

    On server 

     

    root@Tower:/etc/rc.d# showmount -e localhost
    rpc mount export: RPC: Timed out

      

    syslog:

    Dec 18 06:25:56 Tower rpcbind[42978]: connect from tykki to getport/addr(portmapper)
    Dec 18 06:25:56 Tower rpcbind[42979]: connect from tykki to dump()
    Dec 18 06:26:58 Tower rpcbind[48650]: connect from tykki to getport/addr(mountd)

     

     

     




    User Feedback

    Recommended Comments

    You have a problem with your unassigned devices share not mounting

    Dec 16 22:17:55 Tower rpc.mountd[14263]: refused mount request from 192.168.255.84 for /mnt/user/kamera/Dome (/mnt/user/kamera/Dome): unmatched host

    It results in numerous authentication failures.

    Dec 19 21:12:09 Tower rpc.mountd[29539]: authenticated mount request from PTZ-N4425IH-DE20180703AAWRC33159201W.local:626 for /mnt/user/kamera/Dome (/mnt/user/kamera)
    Dec 19 21:12:10 Tower kernel: sd 2:0:1:0: task abort: SUCCESS scmd(00000000ca7c1b57)

    Does it still exist?

     

    Link to comment

    That share did exist and is was not on an Unassigned Device but on the main array.

    I removed the mount from the IP camera and it did nothing to help the main problem:

    Debian (.255.197) not mounting ANY of the NFS mounts on Unraid.

     

    There is a manually shared ZFS-share too on the system but that did work perfectly before and removing it does not seem to influence the NFS mount problem

     

    NFS just refuses to work after upgrade. Did work well for years with pretty static config.

    For what it is worth my ESXi (.255.30) seems to be able to mount NFS-datastores but linux-based NFS3 clients CoreElec and Debian are not.

     

    Again, without anything else changed but the version on Unraid.

     

    I do not consider the case solved. The array is unmountable.

    Unraid has some nice features which I appreciate but if the main function is not met I think it is back to Solaris 11.

    Edited by hema
    Link to comment
    1 hour ago, hema said:

    I do not consider the case solved. The array is unmountable.

    Can you try to start your system in safe mode (without plugins) and see if that makes a difference.

    Link to comment

    It made no difference in maintenance mode.

     

    Seems that it is not dependent on the array at all. Before starting the array after reboot I tried to export manually a directory with no success. 

     

    I am running out of ideas.

     

    [tykki] rpcinfo -m  192.168.255.13
    PORTMAP (version 2) statistics
    NULL    SET     UNSET   GETPORT DUMP    CALLIT  
    1       0/0     0/0     16/19   0       0/0     
    
    PMAP_GETPORT call statistics
    prog            vers    netid     success       failure
    mountd          3       tcp       4             0
    555555555       1       tcp       0             2
    mountd          3       udp       6             0
    nfs             3       tcp       6             0
    status          1       udp       0             1
    
    RPCBIND (version 3) statistics
    NULL    SET     UNSET   GETADDR DUMP    CALLIT  TIME    U2T     T2U     
    0       16/16   4/4     0/0     0       0/0     0       0       0       
    
    RPCBIND (version 4) statistics
    NULL    SET     UNSET   GETADDR DUMP    CALLIT  TIME    U2T     T2U     
    1       16/16   4/4     0/0     0       0/0     0       0       0       
    VERADDR INDRECT GETLIST GETSTAT 
    0       0       0       1       
    [tykki] rpcinfo -s  192.168.255.13                                                                       
       program version(s) netid(s)                         service     owner
        100000  2,3,4     local,udp,tcp,udp6,tcp6          portmapper  superuser
        100024  1         tcp6,udp6,tcp,udp                status      32
        100003  3         udp6,tcp6,udp,tcp                nfs         superuser
        100021  4,3,1     tcp6,udp6,tcp,udp                nlockmgr    superuser
        100005  3,2,1     tcp6,udp6,tcp,udp                mountd      superuser
    [tykki] sudo mount -va                                                                 
    /                        : ignored
    /boot/efi                : already mounted
    mount.nfs: timeout set for Fri Dec 20 16:37:05 2019
    mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.255.13'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.255.13 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.255.13 prog 100005 vers 3 prot UDP port 58814
    ^C

          

    Link to comment
    37 minutes ago, hema said:

    It made no difference in maintenance mode.

    This is not the same thing as "safe mode"

     

    See Main -> Flash -> Syslinux Configuration.

    Select the "Safe mode" (3rd) section and reboot your system

    Link to comment

    Hi,

       I'm suffering the same problem, I upgraded to 6.8 and now nfs seems to have stopped (using it as a backup destination for a seperate proxmox server) my logs were full of connection spam from the proxmox server so I restarted the array.

    I don't appear to get a refused mount etc.

    lspace-diagnostics-20191223-1117.zip

     

    Edited by Rebel
    Link to comment

    my log also full of similar logs,  in kodi,  when you click a movie trying to play it, sometimes it says the file is not there, but sometimes it will work for the same movie,  on such issue on 6.72, it would be better to upgrade NFS to supoort V3

     

    Dec 27 17:33:18 Tower rpcbind[10637]: connect from 192.168.2.21 to getport/addr(nfs)
    Dec 27 18:26:20 Tower rpcbind[3941]: connect from 192.168.2.21 to dump()
    Dec 27 18:26:20 Tower rpcbind[3942]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:27 Tower rpcbind[4226]: connect from 192.168.2.21 to dump()
    Dec 27 18:26:27 Tower rpcbind[4227]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:31 Tower rpcbind[4387]: connect from 192.168.2.21 to dump()
    Dec 27 18:26:31 Tower rpcbind[4388]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:36 Tower rpcbind[4549]: connect from 192.168.2.21 to dump()
    Dec 27 18:26:36 Tower rpcbind[4550]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:37 Tower rpcbind[4590]: connect from 192.168.2.21 to dump()
    Dec 27 18:26:37 Tower rpcbind[4591]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:38 Tower rpcbind[4592]: connect from 192.168.2.21 to getport/addr(mountd)
    Dec 27 18:26:38 Tower rpc.mountd[5447]: authenticated mount request from 192.168.2.21:668 for /mnt/user/media

    Link to comment
    On 12/20/2019 at 5:22 PM, bonienl said:

    This is not the same thing as "safe mode"

     

    See Main -> Flash -> Syslinux Configuration.

    Select the "Safe mode" (3rd) section and reboot your system

    I suffered a drive failure during holidays and was not able to attend to this issue but now that I started to figure out the safe mode I realize that as my array is encrypted I do no want to boot in such a mode that does require magic spells to start. I do know linux but what I did find from the forum about browserless start is just too much hassle.

     

    Edit: I just understood the difference between GUI and WebUI... I shall try the safe mode next.

     

    It seems that sometimes some of the UDP NFSv3 mounts are succeeding but they are painfully slow.

     

    [tykki] sudo mount -vvv  192.168.255.13:/mnt/user/Entertainment /media                                                     
    mount.nfs: timeout set for Sun Dec 29 19:11:31 2019
    mount.nfs: trying text-based options 'vers=4.2,addr=192.168.255.13,clientaddr=192.168.255.197'
    mount.nfs: mount(2): Protocol not supported
    mount.nfs: trying text-based options 'vers=4.1,addr=192.168.255.13,clientaddr=192.168.255.197'
    mount.nfs: mount(2): Protocol not supported
    mount.nfs: trying text-based options 'vers=4.0,addr=192.168.255.13,clientaddr=192.168.255.197'
    mount.nfs: mount(2): Protocol not supported
    mount.nfs: trying text-based options 'addr=192.168.255.13'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.255.13 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.255.13 prog 100005 vers 3 prot UDP port 33661

    Above manual mount goes thru after couple of minutes.

    "ls -lart" takes many seconds display anything. Everything seems almost frozen.

     

    My fstab mounts are NFSv3 TCP and that seems to be the reason they did not function after the upgrade.

     

    Is there something that has changed on the NFS in the latest version of Unraid ?

     

     

    H

     

    Edited by hema
    Link to comment
    On 12/20/2019 at 5:22 PM, bonienl said:

    This is not the same thing as "safe mode"

     

    See Main -> Flash -> Syslinux Configuration.

    Select the "Safe mode" (3rd) section and reboot your system

    Made no difference. Still not mounting properly as it did before upgrade.

     

    Do you guys have a clean procedure for downgrade ?

     

     

    H

    Link to comment
    15 minutes ago, hema said:

    Do you guys have a clean procedure for downgra

    You can downgrade (or upgrade) to any release by downloading the zip file for the release from the Limetech site and extract all the bz* type files over-writing those on the flash drive.

    Link to comment
    On 1/3/2020 at 5:31 AM, Rebel said:

    Damn, I think I have links..... this needs some working around.

     

    Note that symlinks (soft links) are fine, it's hard links which present a problem.

    Link to comment

     

    On 12/29/2019 at 9:26 PM, itimpi said:

    You can downgrade (or upgrade) to any release by downloading the zip file for the release from the Limetech site and extract all the bz* type files over-writing those on the flash drive.

    I did downgrade to 6.7.2 an year ago and have been running it since. No problems nor headaches.

     

    But, is there any reports or testing on 6.9 beta regarding this NFS issue that made 6.8.x unusable for us linux-users?

    I would appreciate the many new features available in newer releasers but if upgrading again makes my NAS not able to share NFS it is not worth it.

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.