Recent Update Causes CIFS Mount Failure

General support questions
Post Reply
gw1500se
Posts: 222
Joined: 2012/05/07 13:53:35

Recent Update Causes CIFS Mount Failure

Post by gw1500se » 2019/01/15 16:23:23

I recently did an update and there were many packages updated. My NAS has been successfully mounting for eons via cifs. However something in the update is now causing the mount to fail with an invalid error:
bash-4.2$ sudo mount --verbose /mnt/dap003
mount.cifs kernel mount options: ip=192.168.0.5,unc=\\dap003\Public,file_mode=0775,dir_mode=0775,gid=100,user= dap,pass=********
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
The host is clearly not down as I can ping it and it is mountable on other OS's. What changed and how can I debug/fix this? TIA.

lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Recent Update Causes CIFS Mount Failure

Post by lightman47 » 2019/01/15 17:12:54

May it be referring to the cifs portion on your host? Is the service running, authenticating properly, etc.? - perhaps the protocol requirements have changed?

just a thought

gw1500se
Posts: 222
Joined: 2012/05/07 13:53:35

Re: Recent Update Causes CIFS Mount Failure

Post by gw1500se » 2019/01/15 17:27:49

I'm not sure what to check but samba service is running:
smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-01-15 11:10:34 EST; 1h 15min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 4632 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4
CGroup: /system.slice/smb.service
├─4632 /usr/sbin/smbd --foreground --no-process-group
├─6011 /usr/sbin/smbd --foreground --no-process-group
├─6012 /usr/sbin/smbd --foreground --no-process-group
└─6170 /usr/sbin/smbd --foreground --no-process-group

Jan 15 11:10:26 dap002 systemd[1]: Starting Samba SMB Daemon...
Jan 15 11:10:34 dap002 systemd[1]: Started Samba SMB Daemon.
Jan 15 11:10:36 dap002 smbd[4632]: [2019/01/15 11:10:34.935375, 0] ../lib/...y)
Jan 15 11:10:36 dap002 smbd[4632]: daemon_ready: STATUS=daemon 'smbd' fin...ns
Hint: Some lines were ellipsized, use -l to show in full.

tonybKDE
Posts: 16
Joined: 2018/12/06 01:52:48

Re: Recent Update Causes CIFS Mount Failure

Post by tonybKDE » 2019/01/15 17:58:03

I and at least one other poster here had to add

vers=3.0

to our mount command lines after the update to CentOS 7.6. Separate it from other arguments with a comma.

Rocketrrt
Posts: 51
Joined: 2016/09/15 16:51:31

Re: Recent Update Causes CIFS Mount Failure

Post by Rocketrrt » 2019/01/15 19:23:20

I had same problem but I to use vers=2.0

gw1500se
Posts: 222
Joined: 2012/05/07 13:53:35

Re: Recent Update Causes CIFS Mount Failure

Post by gw1500se » 2019/01/15 19:26:29

Thanks but no joy. I did discover that mnbd is not running. When I query the status, I get:
bash-4.2$ sudo service nmbd status
Redirecting to /bin/systemctl status nmbd.service
Unit nmbd.service could not be found.

lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Recent Update Causes CIFS Mount Failure

Post by lightman47 » 2019/01/15 19:47:35

Isn't it 'nmb' for the user name service?

gw1500se
Posts: 222
Joined: 2012/05/07 13:53:35

Re: Recent Update Causes CIFS Mount Failure

Post by gw1500se » 2019/01/17 15:45:30

I tried vers=2.0 and that did not help either. I'm not sure what the significance of nmbd not being present is or if that is the root of my problem. In any case nothing so far has worked.

gw1500se
Posts: 222
Joined: 2012/05/07 13:53:35

Re: Recent Update Causes CIFS Mount Failure

Post by gw1500se » 2019/01/17 15:49:55

Well, I found the solution. Although the default protocol used to be 1.0, apparently that is no longer the case with this update. I had to specify vers=1.0 to get it to work.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Recent Update Causes CIFS Mount Failure

Post by TrevorH » 2019/01/17 16:00:02

SMB1 is hideously insecure and has been disabled by Microsoft on recent versions of windows.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Post Reply