[SOLVED] nfs-kernel-server absolutely will not start

[alexskysilk]

and here I thought I've seen everything.

I wake up this morning to a box that houses my pbs, mirror, and various other system services with nfs off. odd- but nothing that systemctl restart wouldnt fix- or so I thought.

[root@store64 /]$ systemctl status nfs-kernel-server.service
● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
     Active: inactive (dead)

Dec 20 09:45:38 store64 systemd[1]: Dependency failed for NFS server and services.
Dec 20 09:55:39 store64 systemd[1]: Dependency failed for NFS server and services.

wha?!

[root@store64 /]$ systemctl list-dependencies nfs-kernel-server
nfs-kernel-server.service
● ├─auth-rpcgss-module.service
● ├─nfs-config.service
● ├─nfs-ganesha-lock.service
● ├─nfs-idmapd.service
● ├─nfs-mountd.service
● ├─proc-fs-nfsd.mount (RED)
● ├─rpc-svcgssd.service
● ├─rpcbind.socket
● ├─system.slice
● ├─zfs-share.service
● └─network.target

[root@store64 /]$ systemctl status proc-fs-nfsd.mount
● proc-fs-nfsd.mount - NFSD configuration filesystem
     Loaded: loaded (/lib/systemd/system/proc-fs-nfsd.mount; static)
     Active: failed (Result: exit-code) since Tue 2022-12-20 10:09:02 PST; 21min ago
      Where: /proc/fs/nfsd
       What: nfsd
        CPU: 4ms

Dec 20 10:09:02 store64 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'.
Dec 20 10:09:02 store64 systemd[1]: Failed to mount NFSD configuration filesystem.

what the actual f***?

[root@store64 /]$ journalctl -u proc-fs-nfsd.mount
Dec 20 09:55:39 store64 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'.
Dec 20 09:55:39 store64 systemd[1]: Failed to mount NFSD configuration filesystem.

I disabled my zfs sharenfs and make a static entry in my exports. no help. I honestly have no idea what to do next short of reinstalling the whole thing, which would be a pita.

help?

 

[cheiss]

Can you run mount -v -t nfsd nfsd /proc/fs/nfsd and see what that puts out?

This is basically what the proc-fs-nfsd.mount is doing, but should hopefully provide some more information about why it fails.

 

[alexskysilk]

Can you run mount -v -t nfsd nfsd /proc/fs/nfsd and see what that puts out?

mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'.

what? where's the nfsd modu.... oh dear. I'm a moron.

This system was previously set up for ganesha. which requires the nfsd module blacklisted.

problem solved. Thank you for shoving my nose in it

 

[Serhioromano]

I have absolutely the same problem. But my result is Permission denied for mounting proc.

User and usergroup for this folder is nobody

root@nas /proc/fs# ls -la
total 0
dr-xr-xr-x   7 nobody nogroup 0 Jun 25 11:30 .
dr-xr-xr-x 503 nobody nogroup 0 Jun 25 11:30 ..
dr-xr-xr-x   7 nobody nogroup 0 Jun 25 11:35 ext4
dr-xr-xr-x   7 nobody nogroup 0 Jun 25 11:35 jbd2
dr-xr-xr-x   3 nobody nogroup 0 Jun 25 11:30 lockd
dr-xr-xr-x   3 nobody nogroup 0 Jun 25 11:35 nfs
dr-xr-xr-x   2 nobody nogroup 0 Jun 25 11:30 nfsd

When I try to chown command to root if fails because permissions also denied.

root@nas /proc/fs# chown root:root /proc/fs/nfsd
chown: changing ownership of '/proc/fs/nfsd': Operation not permitted

Before I was running privileged container, and all worked fine. Now after I've got an idea of the PVE I decided to setup everything the right way. I successfully created an unprivileged container and configured access to files and created SMB shares. But I cannot create NFS share now.

 

[Boerny41]

I got the same problem @Serhioromano has. Can unprivileged containers not create nfs shares?