D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] system.d Mint18 automount NFS

 
On 25/03/17 21:36, mr meowski wrote:

On 25/03/17 19:27, Julian Hall via list wrote:

Hi All,

I have just upgraded from Mint 17.3 to 18, which uses system.d. As you
probably know this will not mount NFS shares properly which is a menace
as my NAS is NFS. In 17.3 it auto mounted so was available all the time.
Could you advise please as currently my system can't see the NAS no
matter what options I put into the fstab. The current entry is:

# automount synology nas
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

Any help gratefully received.

More than likely it's just NFS options changing between 17 & 18...
that's quite a fstab stanza as well, yikes. Before blaming systemd,

Hi mr meowski,
Thanks for the reply. I'm only blaming system.d as a few forums have said the change to system.d between 17 and 18 has caused this problem with many people. It's /sort of/ solved, except now I get two icons for the NAS when it's only mounted once. I followed your advice as below: 
what
does it have to say first?

journalctl -xn
-- Logs begin at Sat 2017-03-25 22:22:15 GMT, end at Sat 2017-03-25 22:26:03 GMT. -- Mar 25 22:23:03 Cerce ureadahead[348]: ureadahead:1118/cmdline: Ignored relative path Mar 25 22:23:03 Cerce ureadahead[348]: ureadahead:1119/stat: Ignored relative path Mar 25 22:23:03 Cerce ureadahead[348]: ureadahead:1119/cmdline: Ignored relative path Mar 25 22:23:03 Cerce ureadahead[348]: ureadahead:.ICEauthority: Ignored relative path 
Mar 25 22:23:03 Cerce ureadahead[348]: ureadahead:.: Ignored relative path
Mar 25 22:26:03 Cerce systemd[1]: ureadahead.service: State 'stop-sigterm' timed out. Killing. Mar 25 22:26:03 Cerce systemd[1]: ureadahead.service: Main process exited, code=killed, status=9/KILL 
Mar 25 22:26:03 Cerce systemd[1]: Stopped Read required files in advance.
-- Subject: Unit ureadahead.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ureadahead.service has finished shutting down.
Mar 25 22:26:03 Cerce systemd[1]: ureadahead.service: Unit entered failed state. Mar 25 22:26:03 Cerce systemd[1]: ureadahead.service: Failed with result 'signal'. 

I didn't understand any of that to be honest so then I followed:

And can you just mount the share manually, like this:

sudo mount -t nfs 192.168.1.3/volume1/Hera /media/julian/HERA
julian@Cerce ~ $ sudo mount -t nfs 192.168.1.3/volume1/Hera /media/julian/HERA 
[sudo] password for julian:
mount: wrong fs type, bad option, bad superblock on 192.168.1.3/volume1/Hera, 
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
Then I realised it /was/ partially my fault. It's so long since I did a clean install I forgot Mint doesn't install nfs-common by default. 'wrong fs type' was the clue so I installed it and tried again. However it still wouldn't mount:
julian@Cerce ~ $ sudo mount -t nfs 192.168.1.3/volume1/Hera /media/julian/HERA 
mount.nfs: remote share not in 'host:dir' format
So I tried julian@Cerce ~ $ sudo mount -t nfs 192.168.1.3:/volume1/Hera /media/julian/HERA as in the fstab
That mounted OK.. but then I saw I have two icons for the same mount point on the desktop. After a reboot it mounts automatically, but I still have two icons, one a normal drive icon and one a network drive. Any ideas why I have two please? 

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