after upgrade to 16.04 network drive not working; had to manually install cifs-util to get the drive to work

[Willem Hobers]

See: https://answers.launchpad.net/ubuntu/+question/284714

I upgraded from Xubuntu 14.04 to 16.04, because I would like to attribute to the testing.

After the upgrade my network drive does not mount.

fstab
//192.168.178.73/Thuis /media/Thuis cifs noserverino,guest,user=,nounix,_netdev,dir_mode=0777,file_mode=0777 0 0

This worked until the upgrade.

When trying to mount I get:

mount: wrong fs type, bad option, bad superblock on //192.168.178.73/Thuis,
       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.

And if I do dmesg | tail, it gives:

[ 21.141585] cgroup: new mount options do not match the existing superblock, will be ignored
[ 24.103109] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 24.103661] forcedeth 0000:00:07.0 eth1: MSI enabled
[ 31.195496] FS-Cache: Loaded
[ 31.232146] FS-Cache: Netfs 'cifs' registered for caching
[ 31.233761] Key type cifs.spnego registered
[ 31.233773] Key type cifs.idmap registered
[ 31.234020] CIFS VFS: No username specified
[ 327.314333] CIFS VFS: No username specified
[ 349.637971] CIFS VFS: No username specified

does any one know if I have to change the fstab after upgrading to 16.04?

Please also note that, in my case, the upgrade to 16.04 did not go smoothly: https://bugs.launchpad.net/ubuntu/+source/libutempter/+bug/1540493

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1544546/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

[Willem Hobers (whobers)]

Brian,

I am sorry: after experiencing this mounting problem I experienced many
other problems as well. Therefore I decided to do a clean install, which is
running as I type this.
I realise now that this is not helpful for this particular issue.
In short: I can't provide the log files as requested.
Sorry.
Op 11 feb. 2016 18:20 schreef "Brian Murray" <email address hidden>:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add the log files from '/var/log/dist-upgrade/'
> to this bug report as separate attachments? Thanks in advance.
>
> ** Changed in: cifs-utils (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1544546
>
> Title:
> after upgrade to 16.04 network drive not working; had to manually
> install cifs-util to get the drive to work
>
> Status in cifs-utils package in Ubuntu:
> Incomplete
>
> Bug description:
> See: https://answers.launchpad.net/ubuntu/+question/284714
>
> I upgraded from Xubuntu 14.04 to 16.04, because I would like to
> attribute to the testing.
>
> After the upgrade my network drive does not mount.
>
> fstab
> //192.168.178.73/Thuis /media/Thuis cifs
> noserverino,guest,user=,nounix,_netdev,dir_mode=0777,file_mode=0777 0 0
>
> This worked until the upgrade.
>
> When trying to mount I get:
>
> mount: wrong fs type, bad option, bad superblock on //
> 192.168.178.73/Thuis,
> 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.
>
> And if I do dmesg | tail, it gives:
>
> [ 21.141585] cgroup: new mount options do not match the existing
> superblock, will be ignored
> [ 24.103109] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 24.103661] forcedeth 0000:00:07.0 eth1: MSI enabled
> [ 31.195496] FS-Cache: Loaded
> [ 31.232146] FS-Cache: Netfs 'cifs' registered for caching
> [ 31.233761] Key type cifs.spnego registered
> [ 31.233773] Key type cifs.idmap registered
> [ 31.234020] CIFS VFS: No username specified
> [ 327.314333] CIFS VFS: No username specified
> [ 349.637971] CIFS VFS: No username specified
>
> does any one know if I have to change the fstab after upgrading to
> 16.04?
>
> Please also note that, in my case, the upgrade to 16.04 did not go
> smoothly:
> https://bugs.launchpad.net/ubuntu/+source/libutempter/+bug/1540493
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1544546/+subscriptions
>

[Launchpad Janitor (janitor)]

[Expired for cifs-utils (Ubuntu) because there has been no activity for 60 days.]

[Serge Stroobandt (serge-stroobandt)]

The following worked for me:

Add to each affected /etc/fsab line:

comment=systemd.automount

So, for example:
//192.168.1.100/shared /media/shared cifs comment=systemd.automount,credentials=…

Source:
http://lifeisabug.com/fix-debian-wheezy-mounting-cifs-smb-shares-boot-time/

Related bug:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1544480