[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 28/12/17 16:28, mr meowski wrote:
Yes it is, but you'll be pleased to know that since the last outing with the NFS shares I have pared down the options so now all I have in the fstab is:On 24/12/17 22:22, Julian Hall wrote:The upgrade procedure was pretty basic: I installed 4.13.. keeping the previous version as always (in this case 4.11) and rebooted. The NFS shares failed to load. I haven't done any other updates today and it was fine up to that point. So I followed your advice and in Grub I chose the 4.11 kernel from the Advanced Options, and the NFS shares loaded straight away. It does seem to be a problem with this kernel as others have posted on forums, albeit with Samba not NFS for all of them, so it seems to be a general network share issue.Is this still an issue by the way? I had a look around the mint forums and my money is on your super-sketchy NFS automount configuration being the culprit. There is a lot of complex interplay between the kernel, networking subsystems and systemd in bringing up network shares and it's easy to fall afoul of configuration tweaks and best practices as things upgrade over time.
# automount CASSIOPEIA on NAS 192.168.1.3:/volume1/CASSIOPEIA /media/julian/CASSIOPEIA nfs # automount DIANA on NAS 192.168.1.3:/volume1/DIANA /media/julian/DIANA nfs # automount PERSEPHONE on NAS 192.168.1.3:/volume1/PERSEPHONE /media/julian/PERSEPHONE nfs Very little option for any screwups, I would hope.
Actually no, I'm being stubborn and sticking with 4.13 even though having to manually mount them through the terminal on every boot is a pain.Knowing you you'll probably just stick with the 4.11 kernel because it works* but you're going to have to roll with the punches and upgrade at some point.
Interesting. I upgraded from 18.2 to 18.3 but this problem didn't crop up immediately. It sounds as if some file used by systemd has the wrong version left in place if an upgrade is done, but a full reinstall installs the right version.Automounting via systemd is the way to go on current Mint (and most other systemd equipped distros now): from reading between the lines on Mint forums it looks as if this is yet another known bit of Mint stupidity as plenty of others are having the same problems, mostly when upgrading from 18.2 to 18.3. Fresh 18.3 installs on the other hand have been working fine.
Again interesting. I'm sure you saw as I did some comments on the forums that the system may not be waiting for the network to be up before trying to mount the shares, then failing and not trying again. That seems bone-headed to me but entirely possible. I'll try with the options the Wiki suggests and report back...Meaning of course that Mint have introduced another one of their typical clumsy mistakes into the upstream Ubuntu base which didn't have the same problem. And they of course got it from Debian, who also didn't have this problem. Mint however DOES have this problem, because it really isn't a very good distro unfortunately. As usual Arch has some solid documentation available: https://wiki.archlinux.org/index.php/NFS#Client Have a look particularly at the "Mount using /etc/fstab with systemd" section for how it should be done.
*A few reboots later*Hmm.. that works but it messes up the desktop putting two icons on instead of just the share and moves the others around - http://www.kaotic.co.uk/initboot.jpg . Then after 30 seconds the duplicates disappear leaving this - http://www.kaotic.co.uk/initboot2.jpg
Kind regards, Julian -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq