[SOLVED] Automount stopped working

3rensho · 12-10-2023, 01:48 AM

I have been using automounting of my NFS shares as per Tadgy's tutorial since he posted it and everything has worked fine. After the updates today I can no longer mount or access the nfs shares.

Code:

cd /nfs/Daily-1
bash: cd: /nfs/Daily-1: No such file or directory

Could that be due to the libxml update or is it probably unrelated? Worked fine yesterday however. Thanks for any advice.

pan64 · 12-10-2023, 04:55 AM

that is a missing directory. probably you need to create it (again).

3rensho · 12-10-2023, 05:24 AM

Quote:

Originally Posted by pan64

that is a missing directory. probably you need to create it (again).

Looks like it is there:

Code:

bash-5.2# pwd
/nfs
bash-5.2# ls -l
total 0
drwxr-xr-x 2 root root 0 Dec 10 12:12 D-Drive-1
drwxr-xr-x 2 root root 0 Dec 10 12:12 Daily-1
drwxr-xr-x 2 root root 0 Dec 10 12:12 Upgrade

The only thing to have changed between yesterday and today is the libxml2 update

henca · 12-10-2023, 05:38 AM

What do you get from:

Code:

cat /proc/filesystems | grep nfs

Are you using a huge kernel (with NFS support built in) or a generic kernel (which needs modules)?

Did the "updates of today" include an update of the kernel? If so, did you carefully read the following text from ChangeLog.txt:

Code:

  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.

Does the output from "uname -r" match the version number of a directory in /lib/modules?

regards Henrik

3rensho · 12-10-2023, 06:13 AM

Quote:

Originally Posted by henca

What do you get from:

Code:

cat /proc/filesystems | grep nfs

Are you using a huge kernel (with NFS support built in) or a generic kernel (which needs modules)?

Did the "updates of today" include an update of the kernel? If so, did you carefully read the following text from ChangeLog.txt:

Code:

  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.

Does the output from "uname -r" match the version number of a directory in /lib/modules?

regards Henrik

Code:

bash-5.2# cat /proc/filesystems | grep nfs
nodev   nfs
nodev   nfs4
nodev   nfsd

and

Code:

bash-5.2# cat /proc/filesystems | grep nfs
nodev   nfs
nodev   nfs4
nodev   nfsd
bash-5.2# uname -r
6.1.66
bash-5.2# ls -l /lib/modules
total 32
drwxr-xr-x 3 root root 4096 Nov 23 08:07 6.1.60
drwxr-xr-x 3 root root 4096 Dec  1 04:58 6.1.61
drwxr-xr-x 3 root root 4096 Nov 16 04:17 6.1.62
drwxr-xr-x 3 root root 4096 Dec  8 07:55 6.1.63
drwxr-xr-x 3 root root 4096 Dec  5 08:24 6.1.64
drwxr-xr-x 3 root root 4096 Dec  9 15:47 6.1.65
drwxr-xr-x 3 root root 4096 Dec  9 16:17 6.1.66
drwxr-xr-x 3 root root 4096 Dec  5 14:17 6.6.4

I'm running grub and after I build a new kernel I make a new initrd before booting. Thanks for the response

Tom

Petri Kaukasoina · 12-10-2023, 06:33 AM

Quote:

Originally Posted by 3rensho

I have been using automounting of my NFS shares as per Tadgy's tutorial since he posted it and everything has worked fine. After the updates today I can no longer mount or access the nfs shares.

Could that be due to the libxml update or is it probably unrelated? Worked fine yesterday however. Thanks for any advice.

/usr/sbin/automount does link against libxml2.so.2, so it would be a good idea to check it by downgrading it.

Quote:

I'm running grub and after I build a new kernel I make a new initrd before booting.

Try the previous kernel where automount worked?

Next I would make sure that an nfs share can be mounted manually.

Petri Kaukasoina · 12-10-2023, 06:51 AM

Quote:

Originally Posted by 3rensho

Code:

bash-5.2# uname -r
6.1.66

Are you connected via wifi? 6.1.66 wireless is broken. https://www.linuxquestions.org/quest...ml#post6469394

3rensho · 12-10-2023, 07:20 AM

Quote:

/usr/sbin/automount does link against libxml2.so.2, so it would be a good idea to check it by downgrading it

I have been looking for the previous version but haven't been able to locate a source for it.

My system is not on wifi.

MDKDIO · 12-10-2023, 07:45 AM

Quote:

Originally Posted by 3rensho

I have been looking for the previous version but haven't been able to locate a source for it.

My system is not on wifi.

Have you tried this?
https://slackware.uk/cumulative/

Current or 15.0, both found there...

3rensho · 12-10-2023, 08:14 AM

Quote:

Originally Posted by MDKDIO

Have you tried this?
https://slackware.uk/cumulative/

Current or 15.0, both found there...

Many thanks for the link. I downgraded to -1 but still no joy.

Petri Kaukasoina · 12-10-2023, 08:34 AM

Quote:

Originally Posted by 3rensho

I downgraded to -1 but still no joy.

Just to check, does -1 mean libxml2-2.9.14-x86_64-1? (There was also libxml2-2.12.2-x86_64-1 in testing for a few hours which probably wouldn't help at all.)

3rensho · 12-10-2023, 08:37 AM

Well, in the end the problem was down to dumbA$$ ME!! Overlooked the obvious and tried to find a solution to what was no problem. Color me RED Faced. I had taken my machine apart yesterday afternoon for a good cleaning from cat hair and dust and who knows what else.. When I reassembled it and plugged everything back in I plugged in the network to the wrong card. Of course I have my NAS access restricted to specific IP's. Ignored the obvious and looked for something more difficult. Maybe someday I will learn. Thank you everyone for help/suggestions and taking the time to respond.