BeagleBone Black - Ubuntu 18.04 - NFS Server issue


#1

As i am learning something new each day while working with my Beaglebone Black, i have decided to create a small cluster of BBB to allow me the opportunity to learn and experiment with different programming methods used for distributive computing. as a part of this setup i am installing the NFS kernel server for sharing the mpiuser home directory as many different guides suggest doing so. however it seams i have run into a snag,

Using the latest release https://rcn-ee.com/rootfs/2018-09-11/flasher/
for the BBB i am unable to get the NFS server running and it crashes during install with a dependency issues.

Using an older version here https://rcn-ee.com/rootfs/2018-08-10/flasher/
again a clean install before doing any upgrading to the system if i do a simple apt update and install the nfs-kernel–server every thing will install properly and the server will start and run as intended.

however as soon as i do the apt upgrade to bring the rest of the system up to date followed by a reboot the nfs server will no longer start and reports a dependency issue.

on my home computer running Ubuntu 18.04 and after running sudo apt update && sudo apt upgrade i install the nfs server in the exact same fashion as i done with the BBB all works fine so this is telling me perhaps there is an issue with one of the arm upgrades that is braking the nfs server … as i am no expert in this manor and i am a bit hesitant in posting here, i have exhausted all other resources and google seams to provide little to no help in fixing the dependency issue.

any help or ideas will be greatly appreciated… below is the exact commands and error along with the journal output of the error. Thank you for your time reading this.

sudo service nfs-kernel-server start

“A dependency job for nfs-server.service failed. See ‘journalctl -xe’ for details.”

and the journalctl results

-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: Dependency failed for NFS Mount Daemon.
-- Subject: Unit nfs-mountd.service has failed
-- Defined-By: systemd
-- Support: XXX://www.ubuntu.com/support
-- 
-- Unit nfs-mountd.service has failed.
-- 
-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: nfs-mountd.service: Job nfs-mountd.service/sta
Nov 20 07:37:36 Bone0 systemd[1]: Dependency failed for NFSv4 ID-name mapping se
-- Subject: Unit nfs-idmapd.service has failed
-- Defined-By: systemd
-- Support: XXX://www.ubuntu.com/support
-- 
-- Unit nfs-idmapd.service has failed.
-- 
-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: nfs-idmapd.service: Job nfs-idmapd.service/sta
Nov 20 07:37:36 Bone0 systemd[1]: nfs-server.service: Job nfs-server.service/sta
Nov 20 07:37:36 Bone0 sudo[1909]: pam_unix(sudo:session): session closed for use
Nov 20 07:38:06 Bone0 sudo[1937]: morpheus : TTY=pts/0 ; PWD=/home/morpheus ; US
Nov 20 07:38:06 Bone0 sudo[1937]: pam_unix(sudo:session): session opened for use
lines 2954-2976/2976 (END)
-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: Dependency failed for NFS Mount Daemon.
-- Subject: Unit nfs-mountd.service has failed
-- Defined-By: systemd
-- Support: XXX://www.ubuntu.com/support
-- 
-- Unit nfs-mountd.service has failed.
-- 
-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start failed with result 'dependency'.
Nov 20 07:37:36 Bone0 systemd[1]: Dependency failed for NFSv4 ID-name mapping service.
-- Subject: Unit nfs-idmapd.service has failed
-- Defined-By: systemd
-- Support: XXX://www.ubuntu.com/support
-- 
-- Unit nfs-idmapd.service has failed.
-- 
-- The result is RESULT.
Nov 20 07:37:36 Bone0 systemd[1]: nfs-idmapd.service: Job nfs-idmapd.service/start failed with result 'dependency'.
Nov 20 07:37:36 Bone0 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.
Nov 20 07:37:36 Bone0 sudo[1909]: pam_unix(sudo:session): session closed for user root
Nov 20 07:38:06 Bone0 sudo[1937]: morpheus : TTY=pts/0 ; PWD=/home/morpheus ; USER=root ; COMMAND=/bin/journalctl -xe
Nov 20 07:38:06 Bone0 sudo[1937]: pam_unix(sudo:session): session opened for user root by morpheus(uid=0)

#2

oh also i have noticed another thing that i forgot to mention earlier… after doing the apt update && apt upgrade the power button no longer shuts down the bone… i actually have to press and hold the power button for several seconds to get it to power off… also i have several BBB and have tried the above on many of then thinking i may have a defected bone only to have the same ending results with the nfs server and the power button.


#3

@milesbdyson, With that same image, I can’t seem fully replicate this.

sudo apt update ; sudo apt install nfs-kernel-server 

Works for me, i’ve also set it up as a nfs server and nfs mount, both work. I do get a nfs has failed state in systemd:

Nov 20 16:00:10 arm systemd[1]: Started NFS status monitor for NFSv2/3 locking..
-- Subject: Unit rpc-statd.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit rpc-statd.service has finished starting up.
-- 
-- The start-up result is RESULT.
Nov 20 16:00:10 arm mount[1122]: mount.nfs: Network is unreachable
Nov 20 16:00:11 arm dbus-daemon[1028]: [system] Successfully activated service 'org.freedesktop.hostname1'
Nov 20 16:00:11 arm set-cpufreq[1049]: Setting ondemand scheduler for all CPUs
Nov 20 16:00:11 arm systemd[1]: opt-builder.mount: Mount process exited, code=exited status=32
Nov 20 16:00:11 arm systemd[1]: opt-builder.mount: Failed with result 'exit-code'.
Nov 20 16:00:11 arm systemd[1]: Failed to mount /opt/builder.
-- Subject: Unit opt-builder.mount has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit opt-builder.mount has failed.
-- 
-- The result is RESULT.
Nov 20 16:00:11 arm systemd[1]: Dependency failed for Remote File Systems.
-- Subject: Unit remote-fs.target has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit remote-fs.target has failed.
-- 
-- The result is RESULT.

BUT, i tried to load BEFORE connman, thus no network was available, then once connman loads everything works after i reload fstab:

ubuntu@arm:~$ mount | grep nfs
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
ubuntu@arm:~$ sudo mount -a
ubuntu@arm:~$ mount | grep nfs
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
192.168.0.12:/opt/builder on /opt/builder type nfs (rw,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.12,mountvers=3,mountport=35538,mountproto=udp,local_lock=none,addr=192.168.0.12)

So the nfs service needs to be patched to wait for connman.

Regards,


#4

@milesbdyson, that is strange, that issue should be fixed. Please run this script for comparsion:

sudo /opt/scripts/tools/version.sh
sudo /opt/scripts/tools/version.sh 
git:/opt/scripts/:[0aa8fd09a1821f6f9197aada6ec69e9746e91f67]
eeprom:[A335BNLT000C1823BBBG1273]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[rcn-ee.net console Ubuntu Image 2018-09-11]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.67-ti-r74]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20180803.0-0rcnee0~bionic+20180804]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~bionic+20180517]
pkg:[kmod]:[24-1ubuntu3rcnee0~bionic+20180515]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
groups:[ubuntu : ubuntu adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable]
dmesg | grep pinctrl-single
[    1.256954] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[    1.269059] gpio-of-helper ocp:cape-universal: ready
END

#5

Thank you for your reply, here is the output of the script you asked for…

$ sudo /opt/scripts/tools/version.sh

git:/opt/scripts/:[4a61888e8e27158bcbb0ca70531038d225a8d7af]
eeprom:[A335BNLT000C1316BBBK1338]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[rcn-ee.net console Ubuntu Image 2018-08-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.03-00002-gac9cce7c6a]:[location: dd MBR]
kernel:[4.14.62-ti-r69]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~bionic+20181110]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~bionic+20180517]
pkg:[kmod]:[24-1ubuntu3.1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
groups:[ubuntu : ubuntu adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable]
dmesg | grep pinctrl-single
[ 1.205167] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 1.217220] gpio-of-helper ocp:cape-universal: ready
END


#6

Thanks @milesbdyson, BeagleBone Black with eeprom 000C, that should have no issues with power down. Just remember the power button, needs to be read by systemd, which systemd then triggers the shutdown routine… If you hold it for 8 seconds, it just shuts down the power rail.

Regards,


#7

as you are unable to replicate this issue …

i began to wonder if i was possibly creating my micro-sd card incorrectly, after trying a few different way, from the img.xz and from .img file …

i also tried on another bone fresh out of its sealed package without any jumpers or circuits attached to the headers and connected by wired network…

on the morcro-sd card created from the .img file the sudo apt update / sudo apt install nfs-kernel-server the server does install and start correctly, then after sudo apt upgrade the server is still up and running however after a reboot the server does not start with a status of (dead) and the journalctl command still reports the same as above with the dependency issue

nothing reported about network unreachable like what you are showing in yours… can you possible confirm that the nfs kernel server does in fact start after rebooting ?

not sure if perhaps there is an issue farther down the line, maybe in the kernel it self… i plan to test this without updating the kernel to try and understand what update is causing this issue for me…

but one thing for sure i definitely am able to reproduce this over and over again.

thank you for your time and help .


#8

@milesbdyson, okay that’s one thing i didn’t test… sudo apt upgrade to see if ubuntu broke anything…

First boot after installing nfs-kernel-server

added to /etc/fstab:

httphost:/var/www/html/farm /mnt/farm nfs rw,nfsvers=3,rsize=8192,wsize=8192 0 0
ubuntu@arm:~$ mount | grep nfs
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
httphost:/var/www/html/farm on /mnt/farm type nfs (rw,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.98,mountvers=3,mountport=33692,mountproto=udp,local_lock=none,addr=192.168.1.98)

● arm
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Wed 2018-11-21 01:27:32 UTC; 1min 12s ago
   CGroup: /
           ├─user.slice
           │ └─user-1000.slice
           │   ├─user@1000.service
           │   │ └─init.scope
           │   │   ├─1566 /lib/systemd/systemd --user
           │   │   └─1568 (sd-pam)
           │   └─session-1.scope
           │     ├─1233 /bin/login -p --
           │     ├─1584 -bash
           │     ├─2021 systemctl status
           │     └─2022 /usr/bin/python3 /usr/bin/pastebinit
           ├─init.scope
           │ └─1 /sbin/init
           └─system.slice
             ├─nfs-idmapd.service
             │ └─986 /usr/sbin/rpc.idmapd
             ├─nfs-mountd.service
             │ └─1110 /usr/sbin/rpc.mountd --manage-gids
             ├─systemd-timesyncd.service
             │ └─1008 /lib/systemd/systemd-timesyncd
             ├─nginx.service
             │ ├─1157 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
             │ └─1158 nginx: worker process
             ├─dbus.service
             │ └─1034 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
             ├─ssh.service
             │ └─1106 /usr/sbin/sshd -D
             ├─dnsmasq.service
             │ └─1210 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service
             ├─avahi-daemon.service
             │ ├─1058 avahi-daemon: running [arm.local]
             │ └─1070 avahi-daemon: chroot helper
             ├─system-serial\x2dgetty.slice
             │ └─serial-getty@ttyGS0.service
             │   └─1998 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyGS0 vt220
             ├─system-getty.slice
             │ └─getty@tty1.service
             │   └─1240 /sbin/agetty -o -p -- \u --noclear tty1 linux
             ├─wpa_supplicant.service
             │ └─1062 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
             ├─connman.service
             │ └─1050 /usr/sbin/connmand -n --nodnsproxy
             ├─networkd-dispatcher.service
             │ └─1027 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
             ├─rpcbind.service
             │ └─999 /sbin/rpcbind -f -w
             ├─nfs-blkmap.service
             │ └─941 /usr/sbin/blkmapd
             ├─systemd-logind.service
             │ └─1019 /lib/systemd/systemd-logind
             ├─cron.service
             │ └─1052 /usr/sbin/cron -f
             ├─systemd-udevd.service
             │ └─951 /lib/systemd/systemd-udevd
             ├─rpc-statd.service
             │ └─1223 /sbin/rpc.statd --no-notify
             ├─rsyslog.service
             │ └─1056 /usr/sbin/rsyslogd -n
             ├─ofono.service
             │ └─1051 /usr/sbin/ofonod -P ril --nodetach
             ├─systemd-journald.service
             │ └─927 /lib/systemd/systemd-journald
             └─haveged.service
               └─1004 /usr/sbin/haveged --Foreground --verbose=1 -w 1024

Now running:

sudo apt update ; sudo apt upgrade ; sudo apt dist-upgrade
Hit:1 http://repos.rcn-ee.com/ubuntu bionic InRelease
Hit:2 http://ports.ubuntu.com bionic InRelease     
Hit:3 http://ports.ubuntu.com bionic-updates InRelease
Reading package lists... Done                      
Building dependency tree       
Reading state information... Done
120 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  gpiod
The following packages will be upgraded:
  apt apt-utils bb-cape-overlays bb-customizations bind9-host binutils
  binutils-arm-linux-gnueabihf binutils-common bsdutils cpp cpp-7 cryptsetup
  cryptsetup-bin distro-info-data dpkg dpkg-dev fdisk g++ g++-7 gcc gcc-7
  gcc-7-base gcc-8-base gettext-base git git-man grub-common grub-efi-arm
  grub-efi-arm-bin grub2-common initramfs-tools initramfs-tools-bin
  initramfs-tools-core kmod libapparmor1 libapt-inst2.0 libapt-pkg5.0 libasan4
  libatomic1 libbind9-160 libbinutils libblkid1 libcc1-0 libcilkrts5
  libcryptsetup12 libcurl3-gnutls libdns-export1100 libdns1100 libdpkg-perl
  libfdisk1 libgcc-7-dev libgcc1 libglib2.0-0 libglib2.0-data libgomp1
  libisc-export169 libisc169 libisccc160 libisccfg160 libkmod2 libldap-2.4-2
  libldap-common liblwres160 libmount1 libnginx-mod-http-geoip
  libnginx-mod-http-image-filter libnginx-mod-http-xslt-filter
  libnginx-mod-mail libnginx-mod-stream libnss-systemd libpam-systemd
  libplymouth4 libpython2.7 libpython2.7-dev libpython2.7-minimal
  libpython2.7-stdlib libpython3-dev libpython3-stdlib libpython3.6
  libpython3.6-dev libpython3.6-minimal libpython3.6-stdlib libsmartcols1
  libstdc++-7-dev libstdc++6 libsystemd0 libubsan0 libudev1 libuuid1
  linux-firmware linux-libc-dev mount networkd-dispatcher nginx nginx-common
  nginx-core openssh-client openssh-server openssh-sftp-server plymouth
  plymouth-theme-ubuntu-text ppp python2.7 python2.7-dev python2.7-minimal
  python3 python3-dev python3-distutils python3-lib2to3 python3-minimal
  python3.6 python3.6-dev python3.6-minimal rfkill systemd systemd-sysv tzdata
  udev util-linux
119 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 193 MB of archives.
After this operation, 53.2 MB of additional disk space will be used.
Do you want to continue? [Y/n]

any upgrades just select: [keep the local version currently installed]

After reboot:

ubuntu@arm:~$ mount | grep nfs
httphost:/var/www/html/farm on /mnt/farm type nfs (rw,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.98,mountvers=3,mountport=33692,mountproto=udp,local_lock=none,addr=192.168.1.98)

But got one failed:

ubuntu@arm:~$ systemctl list-units --state=failed
  UNIT               LOAD   ACTIVE SUB    DESCRIPTION                  
● proc-fs-nfsd.mount loaded failed failed NFSD configuration filesystem

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

So other then the systemctl spam:

[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[DEPEND] Dependency failed for NFS Mount Daemon.
[DEPEND] Dependency failed for NFS server and services.
[DEPEND] Dependency failed for NFSv4 ID-name mapping service.

before the network is up, nfs does work:

ubuntu@arm:~$ mount | grep nfs
httphost:/var/www/html/farm on /mnt/farm type nfs (rw,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.98,mountvers=3,mountport=33692,mountproto=udp,local_lock=none,addr=192.168.1.98)

Found a similar bug: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799

ubuntu@arm:~$ cat /lib/systemd/system/proc-fs-nfsd.mount 
[Unit]
Description=NFSD configuration filesystem

[Mount]
What=nfsd
Where=/proc/fs/nfsd
Type=nfsd
ubuntu@arm:~$ ls -lha /proc/fs/nfs*
/proc/fs/nfsd:
total 0
dr-xr-xr-x 2 root root 0 Nov 21 02:03 .
dr-xr-xr-x 9 root root 0 Nov 21 01:52 ..

/proc/fs/nfsfs:
total 0
dr-xr-xr-x 2 root root  0 Nov 21 02:03 .
dr-xr-xr-x 9 root root  0 Nov 21 01:52 ..
lrwxrwxrwx 1 root root 23 Nov 21 02:03 servers -> ../../net/nfsfs/servers
lrwxrwxrwx 1 root root 23 Nov 21 02:03 volumes -> ../../net/nfsfs/volumes
ubuntu@arm:~$ zcat /proc/config.gz | grep NFSD
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
# CONFIG_NFSD_SCSILAYOUT is not set
# CONFIG_NFSD_FLEXFILELAYOUT is not set
CONFIG_NFSD_V4_SECURITY_LABEL=y
# CONFIG_NFSD_FAULT_INJECTION is not set

Wonder’s what if we build that in…

Building with:

diff --git a/patches/defconfig b/patches/defconfig
index 9c6e110..0dc2f4a 100644
--- a/patches/defconfig
+++ b/patches/defconfig
@@ -6149,7 +6149,7 @@ CONFIG_ROOT_NFS=y
 # CONFIG_NFS_USE_LEGACY_DNS is not set
 CONFIG_NFS_USE_KERNEL_DNS=y
 CONFIG_NFS_DEBUG=y
-CONFIG_NFSD=m
+CONFIG_NFSD=y
 CONFIG_NFSD_V2_ACL=y
 CONFIG_NFSD_V3=y
 CONFIG_NFSD_V3_ACL=y

okay that seems to have fixed everything:

ubuntu@arm:~$ ls -lha /proc/fs/nfs*
/proc/fs/nfs:
total 0
dr-xr-xr-x  2 root root 0 Nov 21 02:19 .
dr-xr-xr-x 10 root root 0 Nov 21 02:18 ..
-r--r--r--  1 root root 0 Nov 21 02:19 exports

/proc/fs/nfsd:
total 0
drwxr-xr-x  2 root root 0 Nov 21 02:18 .
dr-xr-xr-x 10 root root 0 Nov 21 02:18 ..
-r--r--r--  1 root root 0 Nov 21 02:18 export_features
-r--r--r--  1 root root 0 Nov 21 02:18 exports
-rw-------  1 root root 0 Nov 21 02:18 filehandle
-rw-r--r--  1 root root 0 Nov 21 02:18 max_block_size
-rw-r--r--  1 root root 0 Nov 21 02:18 max_connections
-rw-------  1 root root 0 Nov 21 02:18 nfsv4gracetime
-rw-------  1 root root 0 Nov 21 02:18 nfsv4leasetime
-rw-------  1 root root 0 Nov 21 02:18 nfsv4recoverydir
-r--r--r--  1 root root 0 Nov 21 02:18 pool_stats
-rw-------  1 root root 0 Nov 21 02:18 pool_threads
-rw-r--r--  1 root root 0 Nov 21 02:18 portlist
-r--r--r--  1 root root 0 Nov 21 02:18 reply_cache_stats
-r--r--r--  1 root root 0 Nov 21 02:18 supported_krb5_enctypes
-rw-------  1 root root 0 Nov 21 02:18 threads
-rw-------  1 root root 0 Nov 21 02:18 unlock_filesystem
-rw-------  1 root root 0 Nov 21 02:18 unlock_ip
-rw-r--r--  1 root root 0 Nov 21 02:18 v4_end_grace
-rw-------  1 root root 0 Nov 21 02:18 versions

ubuntu@arm:~$ systemctl list-units --state=failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

and pushed:

Regards,


#9

So the actual regression was just found…

package kmod is now fixed and pushed out…

Regards,


#10

Thank you very much for you hard work…

After running
sudo apt purge nfs-kernel-server nfs-common
sudo apt autoremove
sudo apt update && sudo apt upgrade -y
sudo apt install nfs-kernel-server

Every thing installed and the nfs-kernel-server is running, after a reboot the nfs-kernel-server starts up just fine …

I cant tell you how grateful i am for your time, my adventures in cluster computing may now continue … after i buy a new hair piece :slight_smile:


#11

oh ya and i forgot again … the power button is working now as well :slight_smile: