You are not logged in.

Pages: 1

#1 2018-03-16 09:32:00

jackydacky
Member
Registered: 2018-01-16
Posts: 8

fstab fails to mount cifs shares during start up

Hey everyone!

I hope everyone is having a great day. I seem to have gotten myself into awkward situation where my fstab fails to mount cifs shares during start up. After starting up I've noticed that the directory where the mounts were suppose to be on are empty. I've tried performing the following command, which was able to remount those cifs shares back.

# mount -a

Looking through journalctl I also did notice this

 
Mar 17 07:24:50 MAIN-PC kernel: r8169 0000:03:00.0 enp3s0: link up
Mar 17 07:24:50 MAIN-PC kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Mar 17 07:24:50 MAIN-PC systemd[1]: Started A basic static ethernet connection.
Mar 17 07:24:50 MAIN-PC systemd[1]: Reached target Network.
Mar 17 07:24:50 MAIN-PC systemd[1]: Starting Network Time Service...
Mar 17 07:24:50 MAIN-PC systemd[1]: Started OpenSSH Daemon.
Mar 17 07:24:50 MAIN-PC systemd[1]: Starting Samba NetBIOS name server...
Mar 17 07:24:50 MAIN-PC systemd[1]: Starting Samba AD Daemon...
Mar 17 07:24:50 MAIN-PC systemd[1]: Reached target Network is Online.
Mar 17 07:24:50 MAIN-PC systemd[1]: Mounting /mnt/Downloads...
Mar 17 07:24:50 MAIN-PC systemd[1]: Mounting /home/bob/Videos/Anime...
Mar 17 07:24:50 MAIN-PC systemd[1]: Mounting /home/bob/Music...
Mar 17 07:24:50 MAIN-PC systemd[1]: Mounting /home/bob/Videos/Movies...
Mar 17 07:24:50 MAIN-PC ntpd[465]: ntpd 4.2.8p11@1.3728-o Wed Mar  7 18:48:03 UTC 2018 (1): Starting
Mar 17 07:24:50 MAIN-PC ntpd[465]: Command line: /usr/bin/ntpd -g -u ntp:ntp
Mar 17 07:24:50 MAIN-PC systemd[1]: Started Network Time Service.
Mar 17 07:24:50 MAIN-PC kernel: FS-Cache: Loaded
Mar 17 07:24:50 MAIN-PC ntpd[487]: proto: precision = 0.059 usec (-24)
Mar 17 07:24:50 MAIN-PC kernel: Key type dns_resolver registered
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listen and drop on 0 v6wildcard [::]:123
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listen normally on 2 lo 127.0.0.1:123
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listen normally on 3 enp3s0 192.168.10.4:123
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listen normally on 4 lo [::1]:123
Mar 17 07:24:50 MAIN-PC ntpd[487]: bind(21) AF_INET6 fe80::76d4:35ff:fe83:f98d%2#123 flags 0x11 failed: Cannot assign requested address
Mar 17 07:24:50 MAIN-PC ntpd[487]: unable to create socket on enp3s0 (5) for fe80::76d4:35ff:fe83:f98d%2#123
Mar 17 07:24:50 MAIN-PC ntpd[487]: failed to init interface for address fe80::76d4:35ff:fe83:f98d%2
Mar 17 07:24:50 MAIN-PC ntpd[487]: Listening on routing socket on fd #21 for interface updates
Mar 17 07:24:50 MAIN-PC sshd[466]: Server listening on 192.168.10.4 port 22.
Mar 17 07:24:50 MAIN-PC network[404]: Started network profile 'default'
Mar 17 07:24:50 MAIN-PC kernel: FS-Cache: Netfs 'cifs' registered for caching
Mar 17 07:24:50 MAIN-PC kernel: Key type cifs.spnego registered
Mar 17 07:24:50 MAIN-PC kernel: Key type cifs.idmap registered
Mar 17 07:24:50 MAIN-PC samba[468]: [2018/03/17 07:24:50.986819,  0] ../source4/smbd/server.c:448(binary_smbd_main)
Mar 17 07:24:50 MAIN-PC samba[468]:   samba version 4.7.6 started.
Mar 17 07:24:50 MAIN-PC samba[468]:   Copyright Andrew Tridgell and the Samba Team 1992-2017
Mar 17 07:24:50 MAIN-PC systemd[1]: Started Samba AD Daemon.
Mar 17 07:24:50 MAIN-PC systemd[1]: Started Samba NetBIOS name server.
Mar 17 07:24:50 MAIN-PC systemd[1]: Starting Samba SMB/CIFS server...
Mar 17 07:24:50 MAIN-PC nmbd[540]: [2018/03/17 07:24:50.993370,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Mar 17 07:24:50 MAIN-PC nmbd[540]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Mar 17 07:24:51 MAIN-PC samba[539]: [2018/03/17 07:24:51.033539,  0] ../source4/smbd/server.c:600(binary_smbd_main)
Mar 17 07:24:51 MAIN-PC samba[539]:   At this time the 'samba' binary should only be used for either:
Mar 17 07:24:51 MAIN-PC samba[539]:   'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
Mar 17 07:24:51 MAIN-PC samba[539]:   You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
Mar 17 07:24:51 MAIN-PC samba[539]: [2018/03/17 07:24:51.033610,  0] ../lib/util/become_daemon.c:111(exit_daemon)
Mar 17 07:24:51 MAIN-PC samba[539]:   STATUS=daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code 22
Mar 17 07:24:51 MAIN-PC systemd[1]: samba.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 07:24:51 MAIN-PC systemd[1]: samba.service: Failed with result 'exit-code'.
Mar 17 07:24:51 MAIN-PC systemd[1]: Started Samba SMB/CIFS server.
Mar 17 07:24:51 MAIN-PC smbd[543]: [2018/03/17 07:24:51.061580,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Mar 17 07:24:51 MAIN-PC smbd[543]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Mar 17 07:24:51 MAIN-PC dbus-daemon[399]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.6' (uid=0 pid=543 comm="/usr/bin/smbd -D ")
Mar 17 07:24:51 MAIN-PC dbus-daemon[399]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Mar 17 07:24:51 MAIN-PC ntpd[487]: bind(24) AF_INET6 fe80::76d4:35ff:fe83:f98d%2#123 flags 0x11 failed: Cannot assign requested address
Mar 17 07:24:51 MAIN-PC ntpd[487]: unable to create socket on enp3s0 (6) for fe80::76d4:35ff:fe83:f98d%2#123
Mar 17 07:24:51 MAIN-PC ntpd[487]: failed to init interface for address fe80::76d4:35ff:fe83:f98d%2
Mar 17 07:24:53 MAIN-PC ntpd[487]: Listen normally on 7 enp3s0 [fe80::76d4:35ff:fe83:f98d%2]:123
Mar 17 07:24:53 MAIN-PC ntpd[487]: new interface(s) found: waking up resolver
Mar 17 07:24:57 MAIN-PC mount[477]: Unable to find suitable address.
Mar 17 07:24:57 MAIN-PC mount[471]: Unable to find suitable address.
Mar 17 07:24:57 MAIN-PC mount[475]: Unable to find suitable address.
Mar 17 07:24:57 MAIN-PC mount[469]: Unable to find suitable address.
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Videos-Anime.mount: Mount process exited, code=exited status=32
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 07:24:57 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Videos-Anime.mount: Failed with result 'exit-code'.
Mar 17 07:24:57 MAIN-PC systemd[1]: Failed to mount /home/bob/Videos/Anime.
Mar 17 07:24:57 MAIN-PC systemd[1]: Dependency failed for Remote File Systems.
Mar 17 07:24:57 MAIN-PC systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Mar 17 07:24:57 MAIN-PC systemd[1]: mnt-Downloads.mount: Mount process exited, code=exited status=32
Mar 17 07:24:57 MAIN-PC systemd[1]: mnt-Downloads.mount: Failed with result 'exit-code'.
Mar 17 07:24:57 MAIN-PC systemd[1]: Failed to mount /mnt/Downloads.
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Music.mount: Mount process exited, code=exited status=32
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Music.mount: Failed with result 'exit-code'.
Mar 17 07:24:57 MAIN-PC systemd[1]: Failed to mount /home/bob/Music.
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Videos-Movies.mount: Mount process exited, code=exited status=32
Mar 17 07:24:57 MAIN-PC systemd[1]: home-bob-Videos-Movies.mount: Failed with result 'exit-code'.
Mar 17 07:24:57 MAIN-PC systemd[1]: Failed to mount /home/bob/Videos/Movies.

Initially, things were fine until when I tried to tether my phone's network to the machine by following this wiki: https://wiki.archlinux.org/index.php/android_tethering . I don't know if this has anything to do with the problem. My assumption was that it's got something to do with the NIC failing during startup but eventually becomes successful afterwards as the cifs drives were able to be mounted with the command above. The obvious work around to this would be to have the command run during each startup. But, would prefer to actually fix this than cover it. Any suggestions and help would be greatly appreciated.

Again sorry for any of newbieness. I'm still learning smile

PS: I've also tried updating and upgrading via pacman -Su and -Syy as well.

Last edited by jackydacky (2018-03-16 09:33:40)

Offline

#2 2018-03-16 10:36:52

robg
Member
Registered: 2015-03-05
Posts: 225

Re: fstab fails to mount cifs shares during start up

This

Mar 17 07:24:57 MAIN-PC systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Mar 17 07:24:57 MAIN-PC systemd[1]: mnt-Downloads.mount: Mount process exited, code=exited status=32

may suggest that the network is not yet ready when the samba shares should be mounted. The wiki states:

Samba#Automatic mounting wrote:

Note: You may need to enable systemd-networkd-wait-online.service or NetworkManager-wait-online.service (depending on your setup) to proper enable booting on start-up.

Have you tried this?

Offline

#3 2018-03-16 17:43:00

jackydacky
Member
Registered: 2018-01-16
Posts: 8

Re: fstab fails to mount cifs shares during start up

I've tried both systemd-networkd-wait-online.service and netctl-wait-online.service as I'm using a netctl profile defined in /etc/netctl/default. Here's my netctl for reference.

Description='A basic static ethernet connection'
Interface=enp3s0
Connection=ethernet
IP=static
Address=('192.168.10.8/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.10.1'
DNS=('192.168.10.1')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'

Unfortunately the suggestions didn't work. However, what I did noticed at the end of my journalctl was this

Mar 17 04:28:41 MAIN-PC at-spi-bus-launcher[858]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 17 04:28:46 MAIN-PC nmbd[540]: [2018/03/17 04:28:46.974128,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Mar 17 04:28:46 MAIN-PC nmbd[540]:   *****
Mar 17 04:28:46 MAIN-PC nmbd[540]:   
Mar 17 04:28:46 MAIN-PC nmbd[540]:   Samba name server MAIN-PC is now a local master browser for workgroup WORKGROUP on subnet 192.168.10.8
Mar 17 04:28:46 MAIN-PC nmbd[540]:   
Mar 17 04:28:46 MAIN-PC nmbd[540]:   *****
Mar 17 04:28:58 MAIN-PC dhcpcd[431]: enp3s0: offered 192.168.10.212 from 192.168.10.1
Mar 17 04:28:58 MAIN-PC dhcpcd[431]: enp3s0: probing address 192.168.10.212/24
Mar 17 04:28:59 MAIN-PC sudo[967]:      bob : TTY=pts/0 ; PWD=/home/bob ; USER=root ; COMMAND=/usr/bin/journalctl
Mar 17 04:28:59 MAIN-PC sudo[967]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 17 04:29:03 MAIN-PC dhcpcd[431]: enp3s0: leased 192.168.10.212 for 43200 seconds
Mar 17 04:29:03 MAIN-PC dhcpcd[431]: enp3s0: adding route to 192.168.10.0/24
Mar 17 04:29:03 MAIN-PC dhcpcd[431]: enp3s0: adding default route via 192.168.10.1
Mar 17 04:29:04 MAIN-PC ntpd[496]: Listen normally on 8 enp3s0 192.168.10.212:123
Mar 17 04:29:04 MAIN-PC ntpd[496]: new interface(s) found: waking up resolver

Looks like dhcpcd is trying to do something despite the fact I have static IP configured in netctl. I even tried to reinstall dhcpcd and recreated a new netctl profile and reenabled it. This came up before Samba's initiation

ar 17 04:28:29 MAIN-PC dhcpcd[431]: enp3s0: DHCP lease expired
Mar 17 04:28:29 MAIN-PC dhcpcd[431]: enp3s0: soliciting a DHCP lease
Mar 17 04:28:30 MAIN-PC mount[562]: Unable to find suitable address.
Mar 17 04:28:30 MAIN-PC mount[564]: Unable to find suitable address.
Mar 17 04:28:30 MAIN-PC mount[561]: Unable to find suitable address.
Mar 17 04:28:30 MAIN-PC mount[566]: Unable to find suitable address.
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 04:28:30 MAIN-PC kernel: CIFS VFS: cifs_mount failed w/return code = -113
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Music.mount: Mount process exited, code=exited status=32
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Music.mount: Failed with result 'exit-code'.
Mar 17 04:28:30 MAIN-PC systemd[1]: Failed to mount /home/bob/Music.
Mar 17 04:28:30 MAIN-PC systemd[1]: Dependency failed for Remote File Systems.
Mar 17 04:28:30 MAIN-PC systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Videos-Anime.mount: Mount process exited, code=exited status=32
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Videos-Anime.mount: Failed with result 'exit-code'.
Mar 17 04:28:30 MAIN-PC systemd[1]: Failed to mount /home/bob/Videos/Anime.
Mar 17 04:28:30 MAIN-PC systemd[1]: mnt-Downloads.mount: Mount process exited, code=exited status=32
Mar 17 04:28:30 MAIN-PC systemd[1]: mnt-Downloads.mount: Failed with result 'exit-code'.
Mar 17 04:28:30 MAIN-PC systemd[1]: Failed to mount /mnt/Downloads.
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Videos-Movies.mount: Mount process exited, code=exited status=32
Mar 17 04:28:30 MAIN-PC systemd[1]: home-bob-Videos-Movies.mount: Failed with result 'exit-code'.
Mar 17 04:28:30 MAIN-PC systemd[1]: Failed to mount /home/bob/Videos/Movies.

Offline

#4 2018-03-16 18:12:57

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: fstab fails to mount cifs shares during start up

What's the output of...

systemctl list-unit-files --state=enabled

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#5 2018-03-17 00:05:12

jackydacky
Member
Registered: 2018-01-16
Posts: 8

Re: fstab fails to mount cifs shares during start up

Here's the output

UNIT FILE                  STATE  
autovt@.service            enabled
dhcpcd.service             enabled
getty@.service             enabled
libvirtd.service           enabled
netctl-wait-online.service enabled
netctl@default.service     enabled
nmbd.service               enabled
ntpd.service               enabled
samba.service              enabled
smbd.service               enabled
sshd.service               enabled
virtlockd.socket           enabled
virtlogd.socket            enabled
remote-fs.target           enabled

14 unit files listed.

Last edited by jackydacky (2018-03-17 00:27:36)

Offline

#6 2018-03-17 00:30:46

jackydacky
Member
Registered: 2018-01-16
Posts: 8

Re: fstab fails to mount cifs shares during start up

Hey guys, Looks like I may have solved the problem. I think the problem really isn't Linux related but more of a Layer 2 and Layer 3 issue between my router and switch. I forgot I had the NIC connected to one of my Cisco Catalysts switches. When changing it back to my normal switch it works all fine.


Moreover I've had the router resetted as well.

Thanks all for the suggestions above

Offline

#7 2018-03-21 09:49:46

fettouhi
Member
Registered: 2007-05-07
Posts: 785

Re: fstab fails to mount cifs shares during start up

I have the same issue as well now with cifs and my freenas fileserver. If I look through journalctl I see this

mar 21 10:41:22 andre mount[690]: mount error(13): Permission denied
mar 21 10:41:22 andre mount[690]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mar 21 10:41:22 andre kernel: CIFS VFS: cifs_mount failed w/return code = -13
mar 21 10:41:22 andre systemd[1]: media-freenas.mount: Mount process exited, code=exited status=32
mar 21 10:41:22 andre systemd[1]: media-freenas.mount: Failed with result 'exit-code'.
mar 21 10:41:22 andre systemd[1]: Failed to mount /media/freenas.
mar 21 10:41:22 andre systemd[1]: Dependency failed for Remote File Systems.
mar 21 10:41:22 andre systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.

and the output from

systemctl list-unit-files --state=enabled

gives

EDIT: Ignore this post. My issue was caused by an update of FreeNAS that deleted the smb password database. Reverted back to the previous update of FreeNAS now cifs works again.

UNIT FILE                                   STATE  
org.cups.cupsd.path                         enabled
autovt@.service                             enabled
avahi-daemon.service                        enabled
cups-browsed.service                        enabled
dbus-org.freedesktop.Avahi.service          enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
getty@.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager-wait-online.service          enabled
NetworkManager.service                      enabled
ntpd.service                                enabled
org.cups.cupsd.service                      enabled
sddm.service                                enabled
ufw.service                                 enabled
avahi-daemon.socket                         enabled
org.cups.cupsd.socket                       enabled
remote-fs.target                            enabled
fstrim.timer                                enabled

everything was working fine until a few days ago.

Last edited by fettouhi (2018-03-21 13:51:58)

Offline

#8 2018-03-21 11:50:07

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,857

Re: fstab fails to mount cifs shares during start up

No, you do not
https://bbs.archlinux.org/viewtopic.php … 1#p1748021

please read error messages and search the forum (or the internet) - the "error" is all over the place since the default protocol version was changed.
Also fix your NAS - SMBv1 is to be considered "terrible".

Edit:
https://bbs.archlinux.org/viewtopic.php?id=230551
https://bbs.archlinux.org/viewtopic.php?id=230364
https://bbs.archlinux.org/viewtopic.php?id=233400
https://bbs.archlinux.org/viewtopic.php?id=233518

... for instances - there are far more.

Last edited by seth (2018-03-21 11:51:23)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2018-03-21 14:03:16

fettouhi
Member
Registered: 2007-05-07
Posts: 785

Re: fstab fails to mount cifs shares during start up

seth wrote:

No, you do not
https://bbs.archlinux.org/viewtopic.php … 1#p1748021

please read error messages and search the forum (or the internet) - the "error" is all over the place since the default protocol version was changed.
Also fix your NAS - SMBv1 is to be considered "terrible".

Edit:
https://bbs.archlinux.org/viewtopic.php?id=230551
https://bbs.archlinux.org/viewtopic.php?id=230364
https://bbs.archlinux.org/viewtopic.php?id=233400
https://bbs.archlinux.org/viewtopic.php?id=233518

... for instances - there are far more.

How can you see that my NAS is using SMBv1? Is that implied in the error code?

Offline

#10 2018-03-21 14:12:24

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,857

Re: fstab fails to mount cifs shares during start up

What I can say is that you get a permission error (13) and that this is typical for the protocol version mismatch and I know that this was a *very* common issue in recent times.
Ruling out individual issues, this is the error you'd most likely face (and it's certainly different from the OPs one)

How does this make sense, btw?

an update of FreeNAS that deleted the smb password database. Reverted back to the previous update of FreeNAS now cifs works again.

Did the revert undelete the passwords or is that just an estimation? Why not just restore the passwords?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2018-03-21 15:19:46

fettouhi
Member
Registered: 2007-05-07
Posts: 785

Re: fstab fails to mount cifs shares during start up

seth wrote:

What I can say is that you get a permission error (13) and that this is typical for the protocol version mismatch and I know that this was a *very* common issue in recent times.
Ruling out individual issues, this is the error you'd most likely face (and it's certainly different from the OPs one)

How does this make sense, btw?

an update of FreeNAS that deleted the smb password database. Reverted back to the previous update of FreeNAS now cifs works again.

Did the revert undelete the passwords or is that just an estimation? Why not just restore the passwords?

Reverting back made it work again other FreeNAS users have reported that restoring the password also works in some cases. I was advised to revert back as this is considered the safest option until a permantent fix is released.

Offline

Pages: 1

Board footer

Powered by FluxBB