[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 06/05/17 02:46, Julian Hall wrote:
On 05/05/17 23:18, mr meowski wrote:That worked with no errors and I was able to just browse it from the desktop icon Cinnamon puts up for any mounted drives.On 05/05/17 22:51, Julian Hall wrote:fstab commented out and boots in under ten seconds - / is on an SSD.As expected - systemd isn't timing out waiting for whatever's wrong with the NFS mount any more. Of course, the NAS isn't mounted either. What happens if you mount the share the good old fashioned way: mkdir ~/NFSMNT sudo mount -t nfs 1.2.3.4:/$share ~/NFSMNT Replace 1.2.3.4 and $share with whatever the values should be for your NAS of course. Report back any errors and don't forget to check dmesg if anything doesn't work. You should also be able to point a Thunar window at ~/NFSMNT and browse around as per normal. CheersJulian
Hi,I've been looking at the different NFS mount options, and wondered if this would work:
192.168.1.3:/volume1/Hera /media/julian/HERA nfs rsize=8192,wsize=8192,timeo=70,intr
I sort of understand what those options do, and the timeo one is interesting as I've noticed the Wired Network connection only seems available a second or so after the desktop appears, so if I tell it to wait a bit before failing that should stop system.d failing?
This is the original line:192.168.1.3:/volume1/Hera /media/julian/HERA nfs noauto,x-systemd.automount,nouser,rsize=8192,wsize=8192,atime,rw,dev,exec,suid 0
In short the behaviour I would like is what it used to before I upgraded; that is boot the system and the NAS mounts automatically so I can use it just as any other local drive.
Both the above lines are commented out in the fstab btw. 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