Skip to content

Unable to use NFS V4.1 and V4.2 (CONFIG_NFS_V4_1 is not set) #4742

Open
Open
Unable to use NFS V4.1 and V4.2 (CONFIG_NFS_V4_1 is not set)#4742
@lejvin

Description

@lejvin
lejvin
opened on Jun 1, 2026

Describe the issue you are experiencing

Hello. NFS V4.1 and V4.2 are unavailable in the ova board release of HAOS. Mount will fail with invalid argument

This should be a somewhat easy fix. I see that some other boards have the following in their .config files:

CONFIG_NFS_V4=m
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y

I am however not a developer, so I will leave this to the professionals to handle.

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

17.3

Did the problem occur after upgrading the Operating System?

No

Hardware details

Virsh QEMU/KVM running on x64_64 host.
Host kernel: 6.12.90
QEMU emulator version 10.1.5

Steps to reproduce the issue

  1. Disable NFS V4.0 and NFS V3 on NFS server.
  2. Try to mount NFS Share.
  3. mount -v -t nfs will give you:
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.69,clientaddr=192.168.1.10'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.1.69,clientaddr=192.168.1.10'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.69,clientaddr=192.168.1.10'
192.168.1.69:/mnt/tank/ha-backup on /tmp/mnt2 type nfs (rw)

It will then freeze.

Anything in the Supervisor logs that might be useful for us?

2026-06-01 16:50:21.150 ERROR (MainThread) [supervisor.mounts.mount] Mounting new_new_new_backup did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-new_new_new_backup.mount for details.
2026-06-01 16:50:21.178 ERROR (MainThread) [supervisor.api.utils] Unexpected error during API call: Mounting new_new_new_backup did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-new_new_new_backup.mount for details.
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/api/utils.py", line 72, in wrap_api
    answer = await method(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/mounts.py", line 80, in create_mount
    await self.sys_mounts.create_mount(mount)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 307, in wrapper
    raise err
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 299, in wrapper
    return await method(obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/mounts/manager.py", line 209, in create_mount
    raise err
  File "/usr/src/supervisor/supervisor/mounts/manager.py", line 206, in create_mount
    await mount.load()
  File "/usr/src/supervisor/supervisor/mounts/mount.py", line 223, in load
    await self.mount()
  File "/usr/src/supervisor/supervisor/mounts/mount.py", line 390, in mount
    raise MountActivationError(
    ...<2 lines>...
    )
supervisor.exceptions.MountActivationError: Mounting new_new_new_backup did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-new_new_new_backup.mount for details.

Anything in the Host logs that might be useful for us?

2026-06-01 14:45:53.875 homeassistant systemd[1]: mnt-data-supervisor-mounts-new_new_backup.mount: Mount process exited, code=killed, status=15/TERM
2026-06-01 14:45:53.875 homeassistant systemd[1]: mnt-data-supervisor-mounts-new_new_backup.mount: Failed with result 'timeout'.
2026-06-01 14:45:53.876 homeassistant systemd[1]: Failed to mount Supervisor nfs mount: new_new_backup.
2026-06-01 14:49:46.014 homeassistant systemd[1]: Mounting Supervisor nfs mount: new_new_new_backup...
2026-06-01 14:50:21.124 homeassistant systemd[1]: mnt-data-supervisor-mounts-new_new_new_backup.mount: Mounting timed out. Terminating.
2026-06-01 14:50:21.125 homeassistant systemd[1]: mnt-data-supervisor-mounts-new_new_new_backup.mount: Mount process exited, code=killed, status=15/TERM
2026-06-01 14:50:21.125 homeassistant systemd[1]: mnt-data-supervisor-mounts-new_new_new_backup.mount: Failed with result 'timeout'.
2026-06-01 14:50:21.126 homeassistant systemd[1]: Failed to mount Supervisor nfs mount: new_new_new_backup.
2026-06-01 14:55:37.856 homeassistant systemd[1]: Mounting Supervisor nfs mount: backupafadf...
2026-06-01 14:56:12.875 homeassistant systemd[1]: mnt-data-supervisor-mounts-backupafadf.mount: Mounting timed out. Terminating.

System information

System Information

version core-2026.5.4
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.14.2
os_name Linux
os_version 6.12.85-haos
arch x86_64
timezone Europe/Stockholm
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 17.3
update_channel stable
supervisor_version supervisor-2026.05.1
agent_version 1.8.1
docker_version 29.3.1
disk_total 30.8 GB
disk_used 6.2 GB
nameservers 2001:2043:de16:6200::1, 192.168.1.1
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons File editor (6.0.0), Grafana (12.1.0)
Dashboards
dashboards 4
resources 0
views 1
mode storage
Network Configuration
adapters lo (disabled), enp1s0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth50db384 (disabled), vethffc0758 (disabled), veth900dbae (disabled), veth2332ee2 (disabled), veth9a917be (disabled), veth1c70be7 (disabled), veth9510a10 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp1s0 (192.168.1.10/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth50db384 (), vethffc0758 (), veth900dbae (), veth2332ee2 (), veth9a917be (), veth1c70be7 (), veth9510a10 ()
ipv6_addresses lo (::1/128), enp1s0 (2001:2043:de16:6200:d91c:5c62:a132:d12f/64, fe80::3f1:6bce:cb5:8b76/64), hassio (fd0c:ac1e:2100::1/48, fe80::d0c4:9fff:fe58:279e/64), docker0 (fe80::449c:d2ff:fe9e:7c3a/64), veth50db384 (fe80::18f5:56ff:fe5c:b6d9/64), vethffc0758 (fe80::f45f:ddff:fee3:ca35/64), veth900dbae (fe80::e468:2cff:fe8a:a8a9/64), veth2332ee2 (fe80::cca0:60ff:fe71:6f2/64), veth9a917be (fe80::4c1f:aaff:fe0b:ef2f/64), veth1c70be7 (fe80::9826:53ff:febe:1172/64), veth9510a10 (fe80::8cac:9fff:fec6:8121/64)
announce_addresses 192.168.1.10, 2001:2043:de16:6200:d91c:5c62:a132:d12f, fe80::3f1:6bce:cb5:8b76
Recorder
oldest_recorder_run May 11, 2026 at 15:49
current_recorder_run June 1, 2026 at 20:31
estimated_db_size 17.55 MiB
database_engine sqlite
database_version 3.49.2

Additional information

# zcat /proc/config.gz | grep -i "NFS\|SUNRPC\|BACKCHANNEL"
# CONFIG_USB_FUNCTIONFS is not set
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_KERNFS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V2 is not set
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_FSCACHE is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
# CONFIG_NFSD is not set
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_DEBUG is not set
# cat /etc/os-release
NAME="Home Assistant OS"
VERSION="17.3 (Open Virtual Appliance)"
ID=haos
VERSION_ID=17.3
PRETTY_NAME="Home Assistant OS 17.3"
CPE_NAME=cpe:2.3:o:home-assistant:haos:17.3:*::*:*:*:ova:*
HOME_URL=https://www.home-assistant.io/
VARIANT="Home Assistant OS Open Virtual Appliance"
VARIANT_ID=ova
SUPERVISOR_MACHINE=qemux86-64
SUPERVISOR_ARCH=amd64

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions