You are not logged in.

#1 2021-06-26 19:40:59

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

[SOLVED]cannot mount newly installed Lithium

I have installed BL-Lithium on several of my laptops and have been using NFS. On my most recent install on the host 'roe', I can not mount the /home file system from any of my other computers.

Running the following:

mount -V

from any of my hosts, yields:

mount from util-linux 2.33.1 (libmount 2.33.1: selinux, smack, btrfs, namespaces, assert, debug)


When I run:

mount -t nfs roe:/home /mnt/roe

I get the following output:

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


and when I run:

mount -vvvv -t nfs roe:/home /mnt/roe

I get the following output:

mount.nfs: mount(2): Connection refused
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported
mount.nfs: timeout set for Sat Jun 26 15:18:50 2021
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.235,clientaddr=192.168.1.237'
mount.nfs: trying text-based options 'addr=192.168.1.235'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: prog 100003, trying vers=3, prot=17

The error messages seem to indicate an NFS version problem. All the hosts involved are running BL-Lithium.

Can anyone provide guidance on how to get this new host integrated with the other hosts on my local area network?

Jim A.

Last edited by jjanderson5 (2021-06-28 13:27:06)

Offline

#2 2021-06-26 21:15:24

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,082

Re: [SOLVED]cannot mount newly installed Lithium

jjanderson5 wrote:

Can anyone provide guidance on how to get this new host integrated with the other hosts on my local area network?

Package nfs-kernel-server in buster support both NFSv3 and NFSv4.

I prefer to setup the nfs-share in /etc/fstab, with flags "user,noauto", so I can mount when needed. See https://linuxconfig.org/how-to-set-up-a … -10-buster.

You don't write anything about /etc/exports. Do you export to your lan segment or named hosts?


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#3 2021-06-27 12:51:35

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

Re: [SOLVED]cannot mount newly installed Lithium

I have several points to cover and I'm going to post each separately and number them. In responses to my questions/issues it will help to include a reference number.

Item 1

Looking back on my notes, I see that I install the nfs-server using:

apt-get install nfs-server

and not:

apt-get install nfs-kernel-server

As far as I can tell, this does not matter. Each command appears to give the same result. As I am reading the documentation, I will be looking see if this is explained.

Offline

#4 2021-06-27 12:54:29

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

Re: [SOLVED]cannot mount newly installed Lithium

Item 2

The /etc/exports file on the nfs serving host has the following:

/home 192.168.1.254(rw,no_subtree_check)
/home 192.168.1.253(rw,no_subtree_check)
  .
  .
  .
/home 192.168.1.230(rw,no_subtree_check)
  .
  .
  .
/home 192.168.1.115(rw,no_subtree_check)
  .
  .
  .
/home 192.168.1.100(rw,no_subtree_check)
  .
  .
  .
/home 192.168.1.50(rw,no_subtree_check)
  .
  .
  .
/home 192.168.1.10(rw,no_subtree_check)

This supports ip addresses ending from 254 down to 230, 115 down to 100, and 50 down to 10.

Many of these are not used at any given time, but over the years the actual addresses used have changed for various reasons. With this set of addresses, I can use the same /etc/exports file on my new installations.

Last edited by jjanderson5 (2021-06-27 13:03:57)

Offline

#5 2021-06-27 13:19:24

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

Re: [SOLVED]cannot mount newly installed Lithium

Item 3

I removed the  nfs-server and nfs-common packages on the host which I am having the problem with. When I re-installed I got errors, which I am guessing that I likely had on the initial installation, but I did not see the errors. When I re-installed nfs-kernel-server, I got errors. I'm sorry to post the entire output, but any or all of it could be useful.

The line numbers were inserted by my vim and are not part of the actual file.

Note that lines 21, 28 and 29 indicate failure.

1 apt-get install nfs-kernel-server
  2 Reading package lists... Done
  3 Building dependency tree
  4 Reading state information... Done
  5 The following NEW packages will be installed:
  6   nfs-kernel-server
  7 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
  8 Need to get 0 B/124 kB of archives.
  9 After this operation, 353 kB of additional disk space will be used.
10 Selecting previously unselected package nfs-kernel-server.
11 (Reading database ... 183036 files and directories currently installed.)
12 Preparing to unpack .../nfs-kernel-server_1%3a1.3.4-2.5+deb10u1_amd64.deb ...
13 Unpacking nfs-kernel-server (1:1.3.4-2.5+deb10u1) ...
14 Setting up nfs-kernel-server (1:1.3.4-2.5+deb10u1) ...
15 Job for nfs-server.service canceled.
16 Job for nfs-server.service canceled.
17 invoke-rc.d: initscript nfs-kernel-server, action "restart" failed.
18 ● nfs-server.service - NFS server and services
19    Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
20    Active: failed (Result: exit-code) since Sun 2021-06-27 08:29:38 EDT; 5ms ago
21   Process: 652 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
22   Process: 653 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
23   Process: 655 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
24
25 Jun 27 08:29:37 roe systemd[1]: Starting NFS server and services...
26 Jun 27 08:29:37 roe exportfs[652]: exportfs: duplicated export entries:
27 Jun 27 08:29:37 roe exportfs[652]: exportfs:         192.168.1.23:/home
28 Jun 27 08:29:37 roe systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
29 Jun 27 08:29:38 roe systemd[1]: nfs-server.service: Failed with result 'exit-code'.
30 Jun 27 08:29:38 roe systemd[1]: Stopped NFS server and services.
31 Failed to restart nfs-kernel-server, ignoring.
32 Processing triggers for man-db (2.8.5-2) ...

It is clear that something has gone wrong here and the error messages seem to imply that the nfs-server will not be working. I'm not sure how to interpret the error messages, nor how to fix it.

Offline

#6 2021-06-27 13:55:03

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

Re: [SOLVED]cannot mount newly installed Lithium

Item 4 - nfs version??

rhb said:

Package nfs-kernel-server in buster support both NFSv3 and NFSv4.

When I run:

mount -V

I get:

mount from util-linux 2.33.1 (libmount 2.33.1: selinux, smack, btrfs, namespaces, assert, debug)

This command tells me the version of 'mount'. Having run this command with the same results on each of the relevant hosts, I know the each of the hosts should be supporting the same version(s) of NFS.

If I look further at the mount manpage, it shows that the -t option is used to specify the type of mount. Interestingly, 'nfs' is documented, but 'nfs3' and 'nfs4' are not.

My question is how do I actually verify the NFS version supported by mount? Reading the document that 'rhb' referred me to, it looks like the current version of Debian supports nfs3 and nfs4 and a command like like:

$ sudo mount -t nfs4 192.168.1.110:/media/nfs /media/share

is acceptable.  My opinion is that the manpage should document this. I plan to enter a defect report with Debian, asking that the manpage be more specific as to which version(s) of nfs are support and how the NFS version should be specified.

Does this seem reasonable, or did I misinterpret the documention?

Last edited by jjanderson5 (2021-06-27 13:55:27)

Offline

#7 2021-06-27 19:16:27

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,082

Re: [SOLVED]cannot mount newly installed Lithium

jjanderson5 wrote:

I have several points to cover and I'm going to post each separately and number them. In responses to my questions/issues it will help to include a reference number.

To splitt the thread in multiple threads, only makes the communication more fragmented..,

Item 1

Looking back on my notes, I see that I install the nfs-server using:

apt-get install nfs-server

and not:

apt-get install nfs-kernel-server

As far as I can tell, this does not matter. Each command appears to give the same result. As I am reading the documentation, I will be looking see if this is explained.

I can not find package nfs-server in stable, oldstable or oldoldstable. So, it does make a difference. Package "nfs-server" is not installable.


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#8 2021-06-27 19:45:34

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,082

Re: [SOLVED]cannot mount newly installed Lithium

jjanderson5 wrote:

Item 3

I removed the  nfs-server and nfs-common packages on the host which I am having the problem with. When I re-installed I got errors, which I am guessing that I likely had on the initial installation, but I did not see the errors. When I re-installed nfs-kernel-server, I got errors. I'm sorry to post the entire output, but any or all of it could be useful.

The line numbers were inserted by my vim and are not part of the actual file.

Note that lines 21, 28 and 29 indicate failure.

The first error was in line 17:
"invoke-rc.d: initscript nfs-kernel-server, action "restart" failed."

1 apt-get install nfs-kernel-server
[...]
25 Jun 27 08:29:37 roe systemd[1]: Starting NFS server and services...
26 Jun 27 08:29:37 roe exportfs[652]: exportfs: duplicated export entries:
27 Jun 27 08:29:37 roe exportfs[652]: exportfs:         192.168.1.23:/home

you can not have duplicate entries like above error says. That will set your nfs-service unavailable and give you the errors you have encountered.
Remove the duplicateline , restart nfs-server and it will work ok.

Instead of exporting to a long list of computers, you can export to your lan. Makes the list shorter, easier to spot misstakes.

To restart nfs-server:

$ sudo systemctl restart nfs-server.service

To se status of nfs-server:

$ sudo systemctl status nfs-server.service

// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#9 2021-06-28 13:25:45

jjanderson5
Member
Registered: 2016-05-10
Posts: 106

Re: [SOLVED]cannot mount newly installed Lithium

@rbh

First, thank you. It was your help that got me through this.

A brief explanation. I was reading the duplicate address as 192.168.1.123, not 192.168.1.23 as was clearly stated. It was only after I ran "sort exports > a" and "sort exports | uniq > b" and "diff a b" that erroneous reading became clear.

Offline

#10 2021-06-28 16:21:09

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,082

Re: [SOLVED]cannot mount newly installed Lithium

Good you solved it.

Maybe you should edit subject line and change it from "cannot mount newly installed Lithium" to: "Unable to mount NFS-export", so the solution is easyer for others with duplicate export-lines to find the solution.


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

Board footer

Powered by FluxBB