NFS not working after upgrade to omv6

  • Hello All,


    I recently noticed that NFS wasn't working anymore on my omv server, I think it happend after upgrade to OMV 6, didn't notice any errors after update but when I tried to add a nfs-share on webinterface, I couldn't apply changes , keeps giving big error messages.

    when I try to start nfs-server from cl, I get depency error;


    root@jacksbox3:~# systemctl start nfs-server.service

    A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    root@jacksbox3:~# journalctl -xe

    Jul 20 13:53:05 jacksbox3 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.

    ░░ Subject: A start job for unit rpc-svcgssd.service has finished successfully

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit rpc-svcgssd.service has finished successfully.

    ░░

    ░░ The job identifier is 6025.

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: /usr/sbin/rpc.mountd: bad version number: 0

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: Usage: /usr/sbin/rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-o num|--descriptors num]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-p|--port port] [-V version|--nfs-version version]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-N version|--no-nfs-version version] [-n|--no-tcp]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-H prog |--ha-callout prog] [-r |--reverse-lookup]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-s|--state-directory-path path] [-g|--manage-gids]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-t num|--num-threads=num] [-u|--no-udp]

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=1/FAILURE

    ░░ Subject: Unit process exited

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ An ExecStart= process belonging to unit nfs-mountd.service has exited.

    ░░

    ░░ The process' exit code is 'exited' and its exit status is 1.

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

    ░░ Subject: Unit failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ The unit nfs-mountd.service has entered the 'failed' state with result 'exit-code'.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Failed to start NFS Mount Daemon.

    ░░ Subject: A start job for unit nfs-mountd.service has failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit nfs-mountd.service has finished with a failure.

    ░░

    ░░ The job identifier is 6009 and the job result is failed.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Dependency failed for NFS server and services.

    ░░ Subject: A start job for unit nfs-server.service has failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit nfs-server.service has finished with a failure.

    ░░

    ░░ The job identifier is 6005 and the job result is dependency.

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    root@jacksbox3:~# systemctl list-dependencies nfs-server

    nfs-server.service

    ● ├─auth-rpcgss-module.service

    ● ├─nfs-config.service

    ● ├─nfs-idmapd.service

    ● ├─nfs-mountd.service

    ● ├─proc-fs-nfsd.mount

    ● ├─rpc-statd.service

    ● ├─rpc-svcgssd.service

    ● ├─rpcbind.socket

    ● ├─system.slice

    ● └─network.target

    root@jacksbox3:~# systemctl status nfs-mountd.service

    ● nfs-mountd.service - NFS Mount Daemon

         Loaded: loaded (/lib/systemd/system/nfs-mountd.service; static)

    Active: failed (Result: exit-code) since Thu 2023-07-20 13:53:05 CEST; 1min 56s ago

    Process: 26593 ExecStart=/usr/sbin/rpc.mountd $RPCMOUNTDARGS (code=exited, status=1/FAILURE)

            CPU: 3ms

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: Usage: /usr/sbin/rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-o num|--descriptors num]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-p|--port port] [-V version|--nfs-version version]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-N version|--no-nfs-version version] [-n|--no-tcp]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-H prog |--ha-callout prog] [-r |--reverse-lookup]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-s|--state-directory-path path] [-g|--manage-gids]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-t num|--num-threads=num] [-u|--no-udp]

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=1/FAILURE

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Failed to start NFS Mount Daemon.

    root@jacksbox3:~# 

    seems nfs-mountd is the problem, search all the forums but couldn't find a fix,

    has anybody here an idea?

    thanks.

    • Offizieller Beitrag

    Same issue here- RE: Error When Apply NFS Configuration


    Can you post the output of the command I asked for on that thread?

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • votdev

    Hat das Label OMV 6.x hinzugefügt.
  • [tt][

    root@jacksbox3:~# cat /proc/fs/nfsd/versions

    +2 +3 +4 +4.1 +4.2

    root@jacksbox3:~# cat /etc/default/nfs-kernel-server

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    # Number of servers to start up

    RPCNFSDCOUNT="8"


    # Runtime priority of server (see nice(1))

    RPCNFSDPRIORITY="0"


    # Options for rpc.nfsd.

    RPCNFSDOPTS="--no-nfs-version 2 --nfs-version --nfs-version 3 --nfs-version 4 --nfs-version 4.1 --nfs-version 4.2 "


    # Options for rpc.mountd.

    RPCMOUNTDOPTS="--no-nfs-version 2 --nfs-version 0 --nfs-version 3 --nfs-version 4 --manage-gids"


    # Do you want to start the svcgssd daemon? It is only required for Kerberos

    # exports.

    NEED_SVCGSSD=


    # Options for rpc.svcgssd.

    RPCSVCGSSDOPTS=""

    root@jacksbox3:~# cat /etc/default/nfs-common

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    # Do you want to start the statd daemon? It is not needed for NFSv4.

    NEED_STATD="yes"


    # Options for rpc.statd.

    # Should rpc.statd listen on a specific port? This is especially useful

    # when you have a port-based firewall. To use a fixed port, set this

    # this variable to a statd argument like: "--port 4000 --outgoing-port 4001".

    # For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS

    STATDOPTS=""


    # Do you want to start the idmapd daemon? It is only needed for NFSv4.

    NEED_IDMAPD="yes"


    # Do you want to start the gssd daemon? It is required for Kerberos mounts.

    NEED_GSSD=

    root@jacksbox3:~# omv-confdbadm read --prettify conf.service.nfs

    {

    "enable": true,

    "shares": {

    "share": []

    },

    "versions": ",3,4,4.1,4.2"

    }



    /tt]

    • Offizieller Beitrag

    ctrl-shift-R

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • ctrl-shift-R?


    I did search the omv and debian 11 forums and read throw very many topic related to nfs-server not starting but did't find a fix for my situation , so thats why I started a new thread here.


    root@jacksbox3:~# cat /proc/fs/nfsd/versions +2 +3 +4 +4.1 +4.2 root@jacksbox3:~# awk '{ for (i=1; i<=NF; i++) if ($i > 0) printf "%s,", $i }' /proc/fs/nfsd/versions | sed -e 's/+//g' -e 's/,$//' 2,3,4,4.1,4.2root@jacksbox3:~#

  • votdev

    Hat das Label gelöst hinzugefügt.
    • Offizieller Beitrag

    ctrl-shift-R?

    Your window wasn't showing the nfs versions dropdown. You needed to refresh your browser cache and ctrl-shift-R does that.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • NFF wasn't working after upgrade to OMV 6.5.7-1 (from 6.5.6.1) anymore. I did some iterative testing by unabeling one nfs version after the other in Services>NFS>Settings>Versions(pulldown menue).


    The second NFSv3 was successfull. Unchecking it gave me the opprtunity to diable nfs and enable it again without NFSv3.


    Now I only have NFSv2, NFSv4, NFSv4.1, NFSv4.2. Do I run into problems now? I have no clue if I need V3?

    heinso


    OMV 5.6.25-1 (Usul) upgraded to currently 6.9.15-2(Shaitan), 64bit, on my ASRock Celeron J4105 NAS Build (10W TDP ;) ), 150WPicoPSU, Raid 5 Array: 4x WD Red 2TB, 250 GB NVMe SSD on PCIe V1, 2x 4GB RAM SO-DIMM 2400, [read/write 950/850 Mb/s over GE (84 GB-file with i5 8th Gen, NVMe SSD as exchange partner)].

    • Offizieller Beitrag
  • Thanx a lot. You are rigth. When I enabled NFSv3 again it reconfigured in status GREEN again ; ))

    heinso


    OMV 5.6.25-1 (Usul) upgraded to currently 6.9.15-2(Shaitan), 64bit, on my ASRock Celeron J4105 NAS Build (10W TDP ;) ), 150WPicoPSU, Raid 5 Array: 4x WD Red 2TB, 250 GB NVMe SSD on PCIe V1, 2x 4GB RAM SO-DIMM 2400, [read/write 950/850 Mb/s over GE (84 GB-file with i5 8th Gen, NVMe SSD as exchange partner)].

    • Offizieller Beitrag

    Do I run into problems now? I have no clue if I need V3?

    Depends on if any of your nfs clients are v3 only. I don't know that answer. On my network, I really only need v3.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I think V3 is used by the good old Dreamboxes (TV Receivers) which are run by newnigma². So in my case it should remain in place. The boxes dont' know the nfsstat -c but this is OT here.

    heinso


    OMV 5.6.25-1 (Usul) upgraded to currently 6.9.15-2(Shaitan), 64bit, on my ASRock Celeron J4105 NAS Build (10W TDP ;) ), 150WPicoPSU, Raid 5 Array: 4x WD Red 2TB, 250 GB NVMe SSD on PCIe V1, 2x 4GB RAM SO-DIMM 2400, [read/write 950/850 Mb/s over GE (84 GB-file with i5 8th Gen, NVMe SSD as exchange partner)].

    Einmal editiert, zuletzt von heinso ()

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!