Plop Linux PXE -> NFS does not mount, Error "mount.nfs: Protocol not supported"

[The_Raven]

Hello

I try to load Plop over PXE. It starts normally but then it can not mount the NFS-Share.
It shows "mount.nfs: Protocol not supported".
Then i have tried to mount it on the busybox-console. Same error.
I have also tried with options "vers=3" and "nfsvers=3" but without success. 
If i mount this share from a LinuxMint client it is working fine.
The only parameter i use is "nolock". This seems to be mandatory.

Any idea why the "protocol" is not supported? 
Is only NFSv4 supported by plop?

[Elmar]

Hello,

NFSv3 and v4 is supported. What OS do you use as server? Maybe I can reproduce the problem.

Elmar

[The_Raven]

Maybe this is the "problem". Server is a (very old!) opensuse 10.2.
Unfortunately i can not update this server. 
I have also checked the log from the server, but i don't find anything interesting.
Yesterday i tested it with another (temporary) test-server (linux mint 17.2) and with this it has worked!
So it must be a combination of client and server that causes this problem.
Opensuse-Server has kernel "2.6.18.2-34-default" (brrr, very old). I don't know how to find the version of the installed nfs-server. The version of "nfsstat" is 1.0.10.

[Elmar]

What happens when you try to mount the share from a Plop Linux booted from USB or DVD?

[The_Raven]

Good idea!
This works! 
If i run it with "-v" i see that it tries first to mount with vers=4. But this does not work, error "Operation not permitted" (don't know why), then it switches to vers=3 and this is working.

So now the question:
Why is it working if plop is bootet but not during the boot process? 

[Elmar]

Please post the full output of -v

[The_Raven]

From the working (bootet from usb) or from the non working (pxe)?

[Elmar]

If possible from both.

A smartphone photo would be good enough.

[The_Raven]

Ok, here they are.
As you can see, the option "nolock" is mandatory.
The only difference i see is "protocol not supported".
Hope you have an idea.
Looks still strange to me! 

[Elmar]

Are you able to ping the PXE server in the busybox shell?

[The_Raven]

Yes, ping works but mount not (tested again).
And, if i change the NFS-Server to another host (test-system) the mount works.
So it must be the combination of "busybox" and "nfs-server" from opensuse.

[Elmar]

Busybox is not the problem. Next week i finalize everything for the new Plop Linux release. I will also try to reproduce the problem. Maybe I can fix it easily for the new version.

[The_Raven]

Sounds good, hope you find a solution.
If you need any help, just let me know (if i can help...). 

[Elmar]

hello,

can you try the test version? ~670MB, it comes without opt.sqfs
https://download.plop.at/tmp/ploplinux-4.3.1-x86_64-raven.tar.gz

Regards
Elmar

[The_Raven]

Yes, but it takes a little bit. Not much time ATM.   

Edit: Tested but same error "protocol not supported". 

[alexo]

Hello,
I'm facing the same issues.
When I try to boot the latest plop linux version over NFS it fails to auto mount it.
But at the busybox shell I can mount with   mount.ntfs -o nolock,nfsvers=4  xxxxxx /media
It mounts just fine and then when I exit the busybox shell,  Plop resumes fine.

The question is:
How to pass the nolock and the nfsvers=4 options to the llinux kerner during boot?
I have tried with nfrsroot=xxxxxxx,nolock,nfsvers4  in my pxe config files but it doesn't work 

Thank you!

[Elmar]

Hello,

Hello,
The question is:
How to pass the nolock and the nfsvers=4 options to the llinux kerner during boot?
I have tried with nfrsroot=xxxxxxx,nolock,nfsvers4  in my pxe config files but it doesn't work 

see this example how to add parameters. You add it after a pipe |

Example: nfsmount=10.0.0.1:/tftpboot/ploplinux-netboot|rsize=2048,wsize=2048,nolock,vers=2,hard,intr

Regards
Elmar

[alexo]

Thanks, it works now. I thought I need to use comma and not pipe. Thanks again.

[The_Raven]

I have again a strange problem with booting pxe and mounting NFS share.
Tried with plop 19.4 and 20.1.
It has begun with an error "shared library libnsl.so.2 not found".
So ok, i made a symlink in the initrd:

Code Select Expand

ln -s libnsl-2.30.so libnsl.so.2
Now this error is gone, but i get error "nolock" is needed.
So i added the option "nolock".
Then i get "mount.nfs: Protocol is not supported". 
So i tried mounting with "nfsver=3", "vers=3" and always get  "mount.nfs: Protocol is not supported".
If i try with "vers=4" then i get "mounting failed, reason given by server: No such file or directory" what is correct because it is a NFS3 share.
When mountin it directly on the debian server all is ok, when mounting on LinuxMint all is ok...

What is wrong here? I am running out of ideas... 

Edit: Ok, switching to NFSv4 seemse to solve the problem. But it looks like plop can not mount NFSv3.

[Elmar]

Booting from NFS3 server is fixed.

Fix: I added the missing files netconfig, protocols and services to the initrd etc.

Please try the 21.1 test version.
https://www.plop.at/en/ploplinux/upcoming/index.html

[The_Raven]

Tested with 21.2 and it works!

Thank you