Comment 4 for bug 1544480

D (darkduck) wrote :

I have the same problem.
CIFS drive does not mount at boot, but works OK after sudo mount -a.
After checking the dmesg output, found the following:
[ 21.401090] IPv6: ADDRCONF(NETDEV_UP): enp14s0: link is not ready
[ 21.409315] r8169 0000:0e:00.0 enp14s0: link down
[ 21.409391] IPv6: ADDRCONF(NETDEV_UP): enp14s0: link is not ready
[ 21.426414] IPv6: ADDRCONF(NETDEV_UP): wlp20s0: link is not ready
[ 21.576880] IPv6: ADDRCONF(NETDEV_UP): wlp20s0: link is not ready
[ 21.784873] IPv6: ADDRCONF(NETDEV_UP): wlp20s0: link is not ready
[ 27.087515] FS-Cache: Loaded
[ 27.113285] FS-Cache: Netfs 'cifs' registered for caching
[ 27.113434] Key type cifs.spnego registered
[ 27.113445] Key type cifs.idmap registered
[ 27.125723] CIFS VFS: Error connecting to socket. Aborting operation.
[ 27.125812] CIFS VFS: cifs_mount failed w/return code = -101
[ 27.440130] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[ 37.997256] wlp20s0: authenticate with 8c:10:d4:61:7b:8c
[ 38.016336] wlp20s0: send auth to 8c:10:d4:61:7b:8c (try 1/3)
[ 38.120061] wlp20s0: send auth to 8c:10:d4:61:7b:8c (try 2/3)
[ 38.121720] wlp20s0: authenticated
[ 38.124072] wlp20s0: associate with 8c:10:d4:61:7b:8c (try 1/3)
[ 38.127684] wlp20s0: RX AssocResp from 8c:10:d4:61:7b:8c (capab=0x411 status=0 aid=2)
[ 38.129296] wlp20s0: associated

If I understand that correctly, CIFS tries to mount the partition while the network is still down.

Would be happy if that helps.