[Resolved]Error when mounting a beryllium file system on a lithium

jjanderson5 · 2024-02-23 23:47:35

On my home network most of the PCs have older versions of Bunsenlabs running. Using the older releases, I have had some problems with some compatibility problems with applications and with the O/S's themselves. I decided that it is time to upgrade all the PC's on my network to boron.

I am currently running a PC (named 'sutton') with Lithium installed and I am trying to mount a file system located on a server (named 'wills') running Beryllium.

On each PC I run:

lsb_release -a

and on sutton get:

No LSB modules are available.
Distributor ID: Bunsenlabs
Description: BunsenLabs GNU/Linux 10.5 (Lithium)
Release: 10.5
Codename: buster

and on wills get:

No LSB modules are available.
Distributor ID: Bunsenlabs
Description: BunsenLabs GNU/Linux 11 (Beryllium)
Release: 11
Codename: bullseye

My problem: Using NFS, I am unable to mount on sutton a filesystem running on the server

On sutton, if I run:

mount -t nfs wills:/mnt/jjaLibrary2 /mnt/jjaLibrary2

I get the following error message:

mount.nfs: requested NFS version or transport protocol is not supported

I have seen that error message in the past. Stopping and restarting the NFS server has worked, but starting/stopping of the NFS server in this case does not help.

On sutton, I looked at /var/log/syslog and the end of the log showed:

2001 Feb 22 16:11:28 sutton kernel: [684385.333816] nfs4_renew_state: start
2002 Feb 22 16:11:28 sutton kernel: [684385.333832] <-- nfs41_proc_async_sequence status=0
2003 Feb 22 16:11:28 sutton kernel: [684385.333833] nfs4_renew_state: done
2004 Feb 22 16:11:28 sutton kernel: [684385.333845] --> nfs4_alloc_slot used_slots=0000 highest_used=4294967295 max_slots=31
2005 Feb 22 16:11:28 sutton kernel: [684385.333847] <-- nfs4_alloc_slot used_slots=0001 highest_used=0 slotid=0
2006 Feb 22 16:11:28 sutton kernel: [684385.333862] encode_sequence: sessionid=1550139165:1844415329:11:0 seqid=19470 slotid=0 ma x_slotid=0 cache_this=0
2007 Feb 22 16:11:28 sutton kernel: [684385.334146] --> nfs4_alloc_slot used_slots=0001 highest_used=0 max_slots=31
2008 Feb 22 16:11:28 sutton kernel: [684385.334148] <-- nfs4_alloc_slot used_slots=0003 highest_used=1 slotid=1
2009 Feb 22 16:11:28 sutton kernel: [684385.334150] nfs4_free_slot: slotid 1 highest_used_slotid 0
2010 Feb 22 16:11:28 sutton kernel: [684385.334152] nfs41_sequence_process: Error 0 free the slot
2011 Feb 22 16:11:28 sutton kernel: [684385.334153] nfs4_free_slot: slotid 0 highest_used_slotid 4294967295
2012 Feb 22 16:11:28 sutton kernel: [684385.334155] nfs41_sequence_call_done rpc_cred 00000000b762acb0
2013 Feb 22 16:11:28 sutton kernel: [684385.334156] <-- nfs41_sequence_call_done
2014 Feb 22 16:11:28 sutton kernel: [684385.334162] nfs4_schedule_state_renewal: requeueing work. Lease period = 60

NOTE THE LINE 2010, indicating an error. At least, is looks line an error message to me.

On wills, /var/log/syslog had no errors related to nfs.

Can any offer advise on how I can mount the desired file system?

Last edited by jjanderson5 (2024-03-09 16:35:19)

PackRat · 2024-02-24 00:37:47

You can try adding the option "vers=3" and some verbose flags to your mount command:

mount -vvvv -t nfs -o vers=3 wills:/mnt/jjaLibrary2 /mnt/jjaLibrary2

jjanderson5 · 2024-02-24 22:54:08

@PackRat

Thank you for the suggestion, but it did not work. I entered the mount as you suggested and got:

mount.nfs: timeout set for Sat Feb 24 17:49:48 2024
mount.nfs: trying text-based options 'vers=3,addr=192.168.1.220'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported

This is not meaningful to me. Does this give error output help?

PackRat · 2024-02-25 00:00:07

mount.nfs: portmap query failed: RPC: Program not registered

Follow up on that error.

Did you recently install/start a firewall?

Try mounting the nfs share using the ip address of the server instead of the server name. Drop the ver=3 option, but keep the verbose flags.

mount -vvvv -t nfs [SERVER IP]:/mnt/jjaLibrary2 /mnt/jjaLibrary2

Last edited by PackRat (2024-02-25 00:10:16)

jjanderson5 · 2024-02-26 23:00:01

No, I didn't install a firewall. I tried running the command that you suggested and got the following:

mount.nfs: timeout set for Mon Feb 26 17:57:58 2024
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.220,clientaddr=192.168.1.222'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'addr=192.168.1.220'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported

PackRat · 2024-02-26 23:54:48

You need to confirm that your server is enabled and that there are no errors in your /etc/exports file.

Like before -

https://forums.bunsenlabs.org/viewtopic.php?pid=116570

https://forums.bunsenlabs.org/viewtopic.php?id=7665

jjanderson5 · 2024-03-09 16:33:16

@PackRat

I finished up a project yesterday and finally got back to this. First thing I did was to retry your suggestion:

mount -vvvv -t nfs [SERVER IP]:/mnt/jjaLibrary2 /mnt/jjaLibrary2

and it worked. I have no clue why it worked now, but I'm happy that it did. I'm closing this issue, but thanks for your help.

#1 2024-02-23 23:47:35

[Resolved]Error when mounting a beryllium file system on a lithium

#2 2024-02-24 00:37:47

Re: [Resolved]Error when mounting a beryllium file system on a lithium

#3 2024-02-24 22:54:08

Re: [Resolved]Error when mounting a beryllium file system on a lithium

#4 2024-02-25 00:00:07

Re: [Resolved]Error when mounting a beryllium file system on a lithium

#5 2024-02-26 23:00:01

Re: [Resolved]Error when mounting a beryllium file system on a lithium

#6 2024-02-26 23:54:48

Re: [Resolved]Error when mounting a beryllium file system on a lithium

#7 2024-03-09 16:33:16

Re: [Resolved]Error when mounting a beryllium file system on a lithium

Board footer