My /etc/fstab contains some windows shares mounted with cifs.
Since the Dapper update of April 24th, these shares aren't mounted on boot.
Instead of that, the message is displayed:
Mounting remote filesystems...failed
But when I type
sudo mount -a
in a terminal, all shares are mounted immidiately without a problem!
This behaviour was reported by severall other users, too: http://www.ubuntuforums.org/showthread.php?t=163171
When I changed the mount type to smbfs for one share, this share wasn't mounted, too, as well as a NFS share I added.
As before: sudo mount -a in a terminal mounts them all without problem!
As a further information I can give:
A part of /var/log/dmesg:
My /etc/fstab contains some windows shares mounted with cifs.
Since the Dapper update of April 24th, these shares aren't mounted on boot.
Instead of that, the message is displayed:
Mounting remote filesystems. ..failed
But when I type www.ubuntuforum s.org/showthrea d.php?t= 163171
sudo mount -a
in a terminal, all shares are mounted immidiately without a problem!
This behaviour was reported by severall other users, too:
http://
When I changed the mount type to smbfs for one share, this share wasn't mounted, too, as well as a NFS share I added.
As before: sudo mount -a in a terminal mounts them all without problem!
As a further information I can give:
A part of /var/log/dmesg:
[4294697.572000] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[4294697.572000] CIFS VFS: cifs_mount failed w/return code = -101
(such a message occurs four times as I try to mount 4 shares. Similar messages are also in /var/log/syslog, /var/log/kern.log)
There are similar bugs reported here before, but they are a year old or older and "fixed", so I started this new one:
https:/ /launchpad. net/distros/ ubuntu/ +source/ udev/+bug/ 16381 /launchpad. net/distros/ ubuntu/ +source/ samba/+ bug/10474
https:/