[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cifs boot time mounts fail after ugrading to Stretch

Le 2017-06-18 19:30, Guy Marcenac a écrit :

Hello,

I just upgraded from jesie to stretch, and everything went fine.
Except my network mounts from fstab fail at boot time.

If I
# mount -a
from the prompt it works.
I tried by adding one of the mounts as a systemd mount unit, and it fails too. 

Here are the entries from /etc/fstab:
//192.168.0.21/video/cine /root/cine/i580mt cifs
rw,credentials=/etc/cifspasswd,_netdev  0       0
//192.168.0.21/video/tv /root/tv/i580mt cifs
rw,credentials=/etc/cifspasswd  0       0

My syslog:
systemd[1]: Started OpenBSD Secure Shell server.
kernel: [    3.626226] FS-Cache: Netfs 'cifs' registered for caching
kernel: [    3.626273] Key type cifs.spnego registered
kernel: [    3.626277] Key type cifs.idmap registered
kernel: [ 3.630942] CIFS VFS: Error connecting to socket. Aborting operation. kernel: [ 3.630956] CIFS VFS: Error connecting to socket. Aborting operation. kernel: [ 3.631234] CIFS VFS: Error connecting to socket. Aborting operation. 
kernel: [    3.631987] CIFS VFS: cifs_mount failed w/return code = -101
kernel: [    3.631999] CIFS VFS: cifs_mount failed w/return code = -101
systemd[1]: root-tv-i580mt.mount: Mount process exited, code=exited status=32 kernel: [ 3.633183] CIFS VFS: Error connecting to socket. Aborting operation. kernel: [ 3.633275] CIFS VFS: Error connecting to socket. Aborting operation. 
kernel: [    3.633311] CIFS VFS: cifs_mount failed w/return code = -101
kernel: [    3.633866] CIFS VFS: cifs_mount failed w/return code = -101
kernel: [    3.634036] CIFS VFS: cifs_mount failed w/return code = -101
systemd[1]: Failed to mount /root/tv/i580mt.
systemd[1]: Dependency failed for Remote File Systems.
systemd[1]: remote-fs.target: Job remote-fs.target/start failed with
result 'dependency'.
systemd[1]: root-tv-i580mt.mount: Unit entered failed state.
The problem is that systemd does not wait for DHCP addresses to be obtained. Being new to systemd I could not succeed in finding the right parameters and dependencies in order to have the mounts wait till we have an IP address. I tried remote-fs.target, network-online.target, and other hacks with no success. This machine being keyboardless, I did not dare migrate to systemd/networkd in order to try systemd-networkd-wait-online. As a workaround, I ended up setting the shares to automount, which works fine, but I would prefer to have them mounted at the very beginning..... 

Any idea?

--
Guy
Reply to: