NFS share not visible in Linux client after OMV reboot

greg77 · Aug 17th 2022

Hi all,

I have OMV running on RPI4. I have LUKS HDD connected to it. I have configured SMB and NFS shares (HDD root dir for both).

On Ubuntu clients (two very similar laptops) I occasionally have had issues with accessing NFS share after OMV restart. I think it was something to do with a cache or something as it usually came back after 48 hours or so.

Last time it didn't, so I need your help please.

OMV is IP 192.168.1.140 and hostname "rpi4". On my client machine an NFS part of /etc/fstab looks like that:

192.168.1.140:/export/shared /mnt/shared nfs auto,defaults,noatime,nodiratime,nolock,intr,tcp,actimeo=1800,_netdev,retry=3,nfsvers=3,rsize=65536,wsize=65536 0 0

Tried also with nfsvers=4

Or manually:

sudo mount -t nfs rpi4:/export/shared /mnt/shared

then

df -h

I can see a line:

192.168.1.140:/export/shared 30G 2.2G 26G 8% /mnt/shared

which looks like OMV root fs (2.2GB used of 32GB card), not my HDD with data.

Obviously /mnt/shared exists on both laptops.

The below command:

rpcinfo -p rpi4| grep nfs

give me below result:

100003 3 tcp 2049 nfs

100003 4 tcp 2049 nfs

100003 3 udp 2049 nfs

showmount -e rpi4

gives me:

Export list for rpi4:

/export 192.168.1.0/24

/export/shared 192.168.1.0/24

Also this:

showmount -a rpi4

gives me the result as below:

All mount points on rpi4:

192.168.1.111:/export/shared/backups/moode

192.168.1.111:/export/shared/mp3

192.168.1.196:/export/shared

192.168.1.63:/export/shared

Ubuntu laptops are IPs ...1.196 and ...1.63.

IP ...1.111 is my moOde RPI player (mp3 / online radio, etc), but it's down at the moment (SD card failed).

The SMB share works fine on Windows and Linux on two similar laptops

Any ideas how to make NFS to work too?

EDIT:

Managed to restore mo0de from a recent backup to a new SD card. It also has problems to connect to an NFS share with music.

I can see this in mo0de logs:

20220817 232028 sourceMount(): Mount error: (mount.nfs: mounting 192.168.1.140:/export/shared/mp3 failed, reason given by server: No such file or directory)

20220817 232028 sourceMount(): Mount error: (mount.nfs: mounting 192.168.1.140:/export/shared/backups/moode/ failed, reason given by server: No such file or directory)

EDIT 2:

Forgot to mention that currently I use latest OMV v6 (upgraded from v5, not a fresh install), but previously had the same issue with v5 as well if that helps.

greg77 · Aug 24th 2022

Anyone?

From what I could read seems like in OMV an NFS share list is not updated after a LUKS decryption. Looks like a pretty old problem (back from OMV 4.x).

A few links below from OMV git repo:

https://github.com/OpenMediaVa…-luksencryption/issues/13

https://github.com/openmediavault/openmediavault/issues/871

and one from this forum:

Thread

NFS shares appear as empty on client

While I was writing this up, I believe I figured out the cause of my issue, but alas, I have no clue how to fix it.

I had to reboot my Hypervisor, and so I did. And then I blindly booted up all of my VMs. I completely forgot that all of my drives in OMV are encrypted, so they are not initially available upon boot. So after my other VMs booted up, autofs worked like a charm, and they dutifully tried writing to the NFS shares. It appears that they created data in the /exports/ folder on OMV,…

andre1234

Jan 24th 2021

At the moment I've switched to SMB in Linux clients, but ideally would love to come back to NFS.

ryecoaaron · Aug 24th 2022

Does sudo systemctl restart nfs-server fix the issue after unlocking luks?

B3rnd · Aug 24th 2022

You called your sharedfoleder "shared"? It's sounds a little bit strange for me.

greg77 · Aug 24th 2022

Quote from ryecoaaron

Does sudo systemctl restart nfs-server fix the issue after unlocking luks?

Unfortunately it doesn't help.

Same issue. ls command shows empty directory, df command shows space available in OMV root filesystem.

Quote from B3rnd

You called your sharedfoleder "shared"? It's sounds a little bit strange for me.

Why? It is a network share between a few machine we have at home. It's like HDD with various data people called "data_files", etc :D.

Also calling it something different wouldn't solve my NFS problem :(.

ryecoaaron · Aug 25th 2022

Quote from greg77

Unfortunately it doesn't help.

Then you need to restart your bind mounts. I would have to see your fstab to help with that.

greg77 · Aug 25th 2022

Code

/etc/fstab


proc            /proc           proc    defaults          0       0
PARTUUID=47d0ae8f-01  /boot           vfat    defaults          0       2
PARTUUID=47d0ae8f-02		/	ext4	noatime,nodiratime,defaults	0 1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
# >>> [openmediavault]
/dev/disk/by-uuid/9b905237-9d8a-4a60-b86a-8eab1bce9483		/srv/dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483	ext4	defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl	0 2
/srv/dev-disk-by-uuid-9b905237-9d8a-4a60-b86a-8eab1bce9483/		/export/shared	none	bind,nofail	0 0
# <<< [openmediavault]

Display More

and /etc/crypttab in case you want to see that too:

Code

# <target name>	<source device>		<key file>	<options>
# sda1-crypt	UUID=43bd41f4-9a09-46bd-b981-7810676f9008	/run/cryptsetup/keyfile-elements1	luks,nofail

ryecoaaron · Aug 26th 2022

I would try: sudo mount -o bind,rw,remount /export/shared

greg77 · Aug 26th 2022

Quote from ryecoaaron

I would try: sudo mount -o bind,rw,remount /export/shared

I get an error as below:

mount: /export/shared: mount point not mounted or bad option.

EDIT:

OK, the command worked without the "remount" part (that was the bad option which cause the previous error I guess). Now I ca list /export/shared and it shows the right content.

However in a Linux client when I try sudo mount -a it says:

mount.nfs: mounting 192.168.1.140:/export/shared failed, reason given by server: No such file or directory

EDIT2:

Just realized that it works on my other laptop which I use less and didn't change any fstab / nfs / smb settings recently.

Will come back to the old settings on my main laptop, but I guess this is the solution.

I don't restart OMV often, but it would be great to make it automated after OMV restart and unlocking LUKS.

Thanks again for the solution!

kamild1996 · Oct 1st 2022

I haven't had a chance to test the command yet (I choose not to restart my Odroid purposefully because of its strange issues with HDD detection), but I'll remember to try

Quote from greg77

I don't restart OMV often, but it would be great to make it automated after OMV restart and unlocking LUKS.

Untested, but here's what I'd try:

Login to the OMV's Linux shell
sudo nano /etc/systemd/system/remount-nfs-on-unlock.service
In the editor, paste this:

Code

[Unit]
Description=Remount NFS shares once LUKS volumes are unlocked
After=default.target

[Service]
ExecStart=/usr/local/bin/remount-nfs-on-unlock.sh

[Install]
WantedBy=default.target

sudo nano /usr/local/bin/remount-nfs-on-unlock.sh
In the editor, paste this: (you may need to refer to "Storage > Encryption" in OMV panel and replace the path in the 5th line of the script below with what you see in the "Decrypted Device" column)

Bash

#!/bin/sh
# remount-nfs-on-unlock.sh

while true; do
  if df | grep -q '/dev/mapper/md0-crypt';
  then
    echo "unlocked, remounting..."
    mount -o bind,rw /export/shared
    exit
  else
    echo "still locked, wait for 10 seconds and try again"
    sleep 10
fi
done

Display More

(thank you DimaKompot for this script)

sudo chmod a+x /usr/local/bin/remount-nfs-on-unlock.sh
sudo systemctl enable remount-nfs-on-unlock.service

greg77 · Oct 1st 2022

Thank you @kamild1996 for the solution. Will add it to the autostart and see if it works.

UKnau22 · Feb 18th 2025

Quote from kamild1996
I haven't had a chance to test the command yet (I choose not to restart my Odroid purposefully because of its strange issues with HDD detection), but I'll remember to try

Untested, but here's what I'd try:
Login to the OMV's Linux shell
sudo nano /etc/systemd/system/remount-nfs-on-unlock.service
In the editor, paste this:
Code
[Unit]
Description=Remount NFS shares once LUKS volumes are unlocked
After=default.target

[Service]
ExecStart=/usr/local/bin/remount-nfs-on-unlock.sh

[Install]
WantedBy=default.target
sudo nano /usr/local/bin/remount-nfs-on-unlock.sh
In the editor, paste this: (you may need to refer to "Storage > Encryption" in OMV panel and replace the path in the 5th line of the script below with what you see in the "Decrypted Device" column)
Bash
#!/bin/sh
# remount-nfs-on-unlock.sh

while true; do
  if df | grep -q '/dev/mapper/md0-crypt';
  then
    echo "unlocked, remounting..."
    mount -o bind,rw /export/shared
    exit
  else
    echo "still locked, wait for 10 seconds and try again"
    sleep 10
fi
done
Display More
(thank you DimaKompot for this script)
sudo chmod a+x /usr/local/bin/remount-nfs-on-unlock.sh
sudo systemctl enable remount-nfs-on-unlock.service

Great write-up! I just stumbled across the same issue and found this thread. Took 5 minutes to implement and works!!!

THANK YOU!

Participate now!