The only thing I do notice is that it takes a little longer (3 seconds)
to mount which could be the "mounting on access". But for me the issue
is negligible be it mount on boot up or mount on access. In a production
environment or where the drive is being used to store data that is
required by
Hi Tim,
> After a lot of testing, re-reading of web pages I have managed to get
> the nas to auto-mount on boot up. I found this page had the right info
> to get a working configuration:
>
> https://www.linuxtechi.com/automount-nfs-share-in-linux-using-autofs/
>
> Particularly sections 2 & 3
Glad
After a lot of testing, re-reading of web pages I have managed to get
the nas to auto-mount on boot up. I found this page had the right info
to get a working configuration:
https://www.linuxtechi.com/automount-nfs-share-in-linux-using-autofs/
Particularly sections 2 & 3
Hope it helps somebody
Hi,
Here's Tim's output without Thunderbird's corruption for those playing
along at home.
The lines which aren't ‘loaded active mounted’ look interesting.
-.mount
loaded activemounted Root Mount
dev-hugepages.m
Here is the output from the command (below)
Within Mint there was not configuration, just added the line to fstab
and it worked. There is no authenication required to login into the NAS
mit@mit-ThinkPad-T530:~$ systemctl list-units --all | grep -w mount
-.mount loaded active mounted Roo
Hi Tim,
> 192.168.18.150:/volume1/Data /media/nas nfs x-systemd.automount 0 0
>
> Made no difference (this is line I had in Linux Mint which worked Perfectly)
Given https://wiki.archlinux.org/title/Fstab#Tips_and_tricks
3.1.2 Remote file system
The same applies to remote file syste
Hi Bob
It makes no difference, changed it to:
192.168.18.150:/volume1/Data /media/nas nfs x-systemd.automount
0 0
Made no difference (this is line I had in Linux Mint which worked Perfectly)
Tim H
On 12/12/2024 20:37, Bob Dunlop wrote:
Okay another guess,
Try replacing "defaul
Okay another guess,
Try replacing "defaults" with "defaults,auto" I'd expect auto to be part
of the normal defaults set for an NFS entry but you never know.
On Thu, Dec 12 at 05:33, Tim wrote:
> Hi Bob,
>
> Having spent ages looking at the that line I had not noticed the missing
> "/" but it
Hi Tim,
So "sudo mount -a" mounts it? Strange that it doesn't mount on boot then, if
the fstab entry is correct. Maybe it's trying to mount before the networking is
set up?
Best,
Hamish
On 12 December 2024 17:48:31 GMT, Tim wrote:
>Hi Ralph
>
>Mount on booting, if I want to mount it I have to
Hi Ralph
Mount on booting, if I want to mount it I have to run sudo mount -a or
something like sudo mount 192.168.18.150:/ /media/nas/data/volume1
Tim H
On 12/12/2024 17:42, Ralph Corderoy wrote:
Hi Tim,
it still does not auto mount.
By that, do you mean mount on booting or mount on fir
Hi Tim,
> it still does not auto mount.
By that, do you mean mount on booting or mount on first access to the
mountpoint?
--
Cheers, Ralph.
--
Next meeting: Online, Jitsi, Tuesday, 2025-01-07 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.u
Hi Bob,
Having spent ages looking at the that line I had not noticed the missing
"/" but it would still mount manually without it and respond correctly
to the other commands I passed against the NFS. Unfortunately adding
the missing forward slash has made no difference to the non-mounting, it
Hi,
Just a small observation but in the fstabs in my MX-linux and Linux Mint
machines that NFS mount from a Gentoo server. The line would read:
192.168.18.150:/volume1/Data /media/nas nfs defaults 0 0
Note the addition of / before volume1.
On Wed, Dec 11 at 05:55, Tim wrote:
...
>
Hi Tim,
> This is the fstab line from Linux Mint which worked perfectly but not
> in Xubuntu
You may find https://wiki.archlinux.org/title/NFS#Client_configuration
worth a look to understand the various line syntaxes and what pays
attention to them.
--
Cheers, Ralph.
--
Next meeting: Online
14 matches
Mail list logo
