NFS kernel mounting NO WORKIE

    I am attempting to update my trusty old x86 HTPC from an ancient version of OpenELEC that I've been running forever because it just worked and it was sufficient for my needs. Now however I'm trying to move to the latest LibreELEC (legacy PC edition) and I'm just not able to get NFS mounts to work following the instructions on this LibreELEC Wiki page:

    Mount Network Share

    I have noted that (in the case of NFS, at least) these are still the identical old instructions that I used on OpenELEC, years ago, to have the kernel mount my NFS volumes. So in theory this should all still work, but it ain't working. Here are the errors I'm getting:

    Apr 27 03:42:03 LibreELEC systemd[1]: Mounting storage-y.mount...

    Apr 27 03:42:03 LibreELEC mount[1420]: mount.nfs: rpc.statd is not running but is required for remote locking.

    Apr 27 03:42:03 LibreELEC mount[1420]: mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

    Apr 27 03:42:03 LibreELEC mount[1420]: mount.nfs: an incorrect mount option was specified for /storage/y

    Apr 27 03:42:03 LibreELEC systemd[1]: storage-y.mount: Mount process exited, code=exited, status=32/n/a

    Apr 27 03:42:03 LibreELEC systemd[1]: storage-y.mount: Failed with result 'exit-code'.

    Apr 27 03:42:03 LibreELEC systemd[1]: Failed to mount storage-y.mount.


    (The above errors are in the systemd log, of course.)

    I've tried all of the obvious solutions to fix this problem and nothing is working, so I'm asking for guidance. Specifically I've tried "systemctl start rpc-statd" but that only produced the error "Failed to start rpc-statd.service: Unit rpc-statd.service not found.". Of course I also tried adding "-o nolock" to the Options= line in my storage-y.mount file, and that still produced errors & failure when I did "systemctl start storage-y.mount".

    I am at a loss and at an impasse. Any & all suggestions that might allow me to move forward would be appreciated.

    P.S. Just for context I should mention that, back in the day I actually did go to the trouble of actually measuring the performance of (a) SMB shares (they really suck, performance-wise) and (b) the in-built Kodi NFS client (not bad, but not great), and (c) kernel mounted NFS shares. Kernel mounted NFS outperformed the Kodi in-built NFS client by a significant margin, which is why I most definitely want to stick with them and get them working on a current LibreELEC release.

    Investigate manual mounting of an NFS share from the console. Once you have that working .. translate the working config into the required systemd mount file options. Pay particular care to the NFS protocol versions being used because modern kernels (client) might make assumptions on infrastructure (server) supporting equally modern versions of NFS, and if SMB is unperformant you probably have old server hardware running old server software. In my experience SMB works fine unless the underlying network environment is poor, and the cure for that is always fixing the environment not swapping protocols /shrug