Samba share not automounted

[Kósa Lajos]

Since updated to kernel 4.18.0-16 from 4.18.0-15, samba shares are not automounted, however I can do it manually. When booting with the older kernel, automount works.

Here is the excerpt of /etc/fstab:

//fritz.box/FRITZ.NAS/WD-Elements25A2-01 /mnt/NAS/WD-Elements25A2-01 cifs credentials=/work/smbcredentials.txt,uid=kosal,gid=users,iocharset=utf8,file_mode=0640,dir_mode=0750,nounix,vers=1.0,user 0 0

#4TB external
//fritz.box/FRITZ.NAS/Verbatim-DesktopHDD3-0-01 /mnt/NAS/Verbatim-DesktopHDD3-0-01 cifs credentials=/work/smbcredentials.txt,uid=kosal,gid=users,iocharset=utf8,file_mode=0640,dir_mode=0750,nounix,vers=1.0,user 0 0

With new kernel, commands from terminal 'mount /mnt/NAS/WD-Elements25A2-01' and '/mnt/NAS/Verbatim-DesktopHDD3-0-01' both work.

/var/log:

with older kernel:

[ OK ] Mounted /mnt/NAS/Verbatim-DesktopHDD3-0-01.
[ OK ] Mounted /mnt/NAS/WD-Elements25A2-01.
[ OK ] Reached target Remote File Systems.

with newer kernel:

         Mounting /mnt/NAS/Verbatim-DesktopHDD3-0-01...
         Mounting /mnt/NAS/WD-Elements25A2-01...
[FAILED] Failed to mount /mnt/NAS/Verbatim-DesktopHDD3-0-01.
See 'systemctl status "mnt-NAS-Verbatim\\x2dDesktopHDD3\\x2d0\\x2d01.mount"' for details.
[DEPEND] Dependency failed for Remote File Systems.
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Start/Stop Eaton - Intelligent Power Protector service....
         Starting LSB: lsyncd daemon init script...
         Starting LSB: Starts AOLserver web daemon...
         Starting Permit User Sessions...
         Starting LSB: minidlna server...
         Starting LSB: automatic crash report generation...
         Starting Tool to automatically collect and submit kernel crash signatures...
[FAILED] Failed to mount /mnt/NAS/WD-Elements25A2-01.
See 'systemctl status "mnt-NAS-WD\\x2dElements25A2\\x2d01.mount"' for details.

[Kósa Lajos (lajos-p)]

with new kernel:

kosal@kosal-pc:~$ systemctl status "mnt-NAS-WD\\x2dElements25A2\\x2d01.mount"
● mnt-NAS-WD\x2dElements25A2\x2d01.mount - /mnt/NAS/WD-Elements25A2-01
   Loaded: loaded (/etc/fstab; generated)
   Active: failed (Result: exit-code) since Thu 2019-03-14 13:13:10 CET; 53s ago
    Where: /mnt/NAS/WD-Elements25A2-01
     What: //fritz.box/FRITZ.NAS/WD-Elements25A2-01
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)

márc 14 13:13:10 kosal-pc systemd[1]: Mounting /mnt/NAS/WD-Elements25A2-01...
márc 14 13:13:10 kosal-pc mount[1524]: mount error: could not resolve address for fritz.box: Unknown error
márc 14 13:13:10 kosal-pc systemd[1]: mnt-NAS-WD\x2dElements25A2\x2d01.mount: Mount process exited, code=exited status=1
márc 14 13:13:10 kosal-pc systemd[1]: mnt-NAS-WD\x2dElements25A2\x2d01.mount: Failed with result 'exit-code'.
márc 14 13:13:10 kosal-pc systemd[1]: Failed to mount /mnt/NAS/WD-Elements25A2-01.

[Kósa Lajos (lajos-p)]

A new resolve package with today's update solved the problem; apparently it was an issue with name resolving.

[Morten Kjeldgaard (mok0)]

Please add information on what Ubuntu distribution you experienced this problem, and what "resolve package" and version that solved it. Thanks!

[Kósa Lajos (lajos-p)]

Ubuntu 18.10. My resolvconf package is currently 1.79ubuntu10.18.10.3, and with this it works. What the version number was that solved it I don't know, but it was the one released around the day I reported the bug solved.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]