Samba: mount error(5): Input/output error
Samba: mount error(5): Input/output error
I keep getting this error message with Samba. I've rebooted both servers and double checked everything.. why?
Samba Server:
yum install samba cifs-utils -y
systemctl restart smb; systemctl enable smb
vi /etc/samba/smb.conf
[documents]
comment = documents
path = /new
valid users = victoria
write list = victoria
victoria is part of an LDAP domain
smbpasswd -a victoria
Password1
ll -Zd /new
drwxrwxrwx. victoria victoria unconfined_u:object_r:samba_share_t:s0 /new
Samba Client:
yum install cifs-utils -y
vi /etc/fstab
//192.168.50.31/documents /one/two cifs credentials=/root/samba 0 0
vi /root/samba
username=victoria
password=Password1
mount -a
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Samba Server:
yum install samba cifs-utils -y
systemctl restart smb; systemctl enable smb
vi /etc/samba/smb.conf
[documents]
comment = documents
path = /new
valid users = victoria
write list = victoria
victoria is part of an LDAP domain
smbpasswd -a victoria
Password1
ll -Zd /new
drwxrwxrwx. victoria victoria unconfined_u:object_r:samba_share_t:s0 /new
Samba Client:
yum install cifs-utils -y
vi /etc/fstab
//192.168.50.31/documents /one/two cifs credentials=/root/samba 0 0
vi /root/samba
username=victoria
password=Password1
mount -a
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
-
- Posts: 2019
- Joined: 2015/02/17 15:14:33
- Location: Bulgaria
- Contact:
Re: Samba: mount error(5): Input/output error
Can you mount the share manually via 'mount -vvv' to check if you are able to access the share at a all?
Re: Samba: mount error(5): Input/output error
no go, I set selinux to permissive and stopped firewalld on 192.168.50.31.
[root@net2 ~]# mount -vvv -o username=victoria //192.168.50.31/documents /one/two
Password for victoria@//192.168.50.31/documents: *********
mount.cifs kernel mount options: ip=192.168.50.31,unc=\\192.168.50.31\documents,user=victoria,pass=********
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@net2 ~]# ping 192.168.50.31
PING 192.168.50.31 (192.168.50.31) 56(84) bytes of data.
64 bytes from 192.168.50.31: icmp_seq=1 ttl=64 time=0.307 ms
64 bytes from 192.168.50.31: icmp_seq=2 ttl=64 time=0.408 ms
^C
--- 192.168.50.31 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.307/0.357/0.408/0.053 ms
[root@net2 ~]# mount -vvv -o username=victoria //192.168.50.31/documents /one/two
Password for victoria@//192.168.50.31/documents: *********
mount.cifs kernel mount options: ip=192.168.50.31,unc=\\192.168.50.31\documents,user=victoria,pass=********
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@net2 ~]# ping 192.168.50.31
PING 192.168.50.31 (192.168.50.31) 56(84) bytes of data.
64 bytes from 192.168.50.31: icmp_seq=1 ttl=64 time=0.307 ms
64 bytes from 192.168.50.31: icmp_seq=2 ttl=64 time=0.408 ms
^C
--- 192.168.50.31 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.307/0.357/0.408/0.053 ms
Re: Samba: mount error(5): Input/output error
Getting all sorts of errors with samba-4.8.3-4.el7.x86_64. I'm on CentOS Linux release 7.6.1810.
One showing:
Unable to find suitable address.
With this in the logs:
[349596.178431] CIFS VFS: Error connecting to socket. Aborting operation.
[349596.180187] CIFS VFS: cifs_mount failed w/return code = -113
[349628.143690] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349628.144530] CIFS VFS: Error connecting to socket. Aborting operation.
[349628.146224] CIFS VFS: cifs_mount failed w/return code = -113
[349794.878070] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349794.879430] CIFS VFS: Error connecting to socket. Aborting operation.
[349794.881970] CIFS VFS: cifs_mount failed w/return code = -113
[349828.237042] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349828.237765] CIFS VFS: Error connecting to socket. Aborting operation.
[349828.238756] CIFS VFS: cifs_mount failed w/return code = -113
The other showing:
mount error(5): Input/output error
showing this in the logs:
[ 520.302866] CIFS VFS: Send error in SessSetup = -5
[ 520.303733] CIFS VFS: cifs_mount failed w/return code = -5
[ 711.140148] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 711.140164] CIFS VFS: Send error in SessSetup = -5
[ 711.141790] CIFS VFS: cifs_mount failed w/return code = -5
[ 884.960839] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 884.960845] CIFS VFS: Send error in SessSetup = -5
[ 884.961913] CIFS VFS: cifs_mount failed w/return code = -5
[ 890.526495] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 890.526505] CIFS VFS: Send error in SessSetup = -5
[ 890.527805] CIFS VFS: cifs_mount failed w/return code = -5
[ 894.524696] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 894.524710] CIFS VFS: Send error in SessSetup = -5
[ 894.525715] CIFS VFS: cifs_mount failed w/return code = -5
I've triple checked my configurations. I'm going to try and provision two new test servers to see if these are simply borked.
One showing:
Unable to find suitable address.
With this in the logs:
[349596.178431] CIFS VFS: Error connecting to socket. Aborting operation.
[349596.180187] CIFS VFS: cifs_mount failed w/return code = -113
[349628.143690] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349628.144530] CIFS VFS: Error connecting to socket. Aborting operation.
[349628.146224] CIFS VFS: cifs_mount failed w/return code = -113
[349794.878070] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349794.879430] CIFS VFS: Error connecting to socket. Aborting operation.
[349794.881970] CIFS VFS: cifs_mount failed w/return code = -113
[349828.237042] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[349828.237765] CIFS VFS: Error connecting to socket. Aborting operation.
[349828.238756] CIFS VFS: cifs_mount failed w/return code = -113
The other showing:
mount error(5): Input/output error
showing this in the logs:
[ 520.302866] CIFS VFS: Send error in SessSetup = -5
[ 520.303733] CIFS VFS: cifs_mount failed w/return code = -5
[ 711.140148] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 711.140164] CIFS VFS: Send error in SessSetup = -5
[ 711.141790] CIFS VFS: cifs_mount failed w/return code = -5
[ 884.960839] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 884.960845] CIFS VFS: Send error in SessSetup = -5
[ 884.961913] CIFS VFS: cifs_mount failed w/return code = -5
[ 890.526495] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 890.526505] CIFS VFS: Send error in SessSetup = -5
[ 890.527805] CIFS VFS: cifs_mount failed w/return code = -5
[ 894.524696] Status code returned 0xc0000001 STATUS_UNSUCCESSFUL
[ 894.524710] CIFS VFS: Send error in SessSetup = -5
[ 894.525715] CIFS VFS: cifs_mount failed w/return code = -5
I've triple checked my configurations. I'm going to try and provision two new test servers to see if these are simply borked.
Re: Samba: mount error(5): Input/output error
Did you do what it told you to do? This is not just a CentOS or even a samba change, SMB1 is highly insecure and has been disabled by Microsoft on pretty much everything.Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
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
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
Re: Samba: mount error(5): Input/output error
I never had to specify version in fstab. Regardless to what I set it to, it still shows the input/output error. I did try 1.0 for kicks just to see if it would work, it did not.
Re: Samba: mount error(5): Input/output error
Various software updates on both Linux and Windows have progressively got more and more aggressive about disabling SMB1. There was a particularly bad bug that was trivially exploitable on Windows where the only solution was disable SMB1 and that's been more and more the case since then. Since you're running samba 4.8 then you already have those changes.
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
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
Re: Samba: mount error(5): Input/output error
Ok, thanks for the response. I've started a new VM with Centos. I'll see if I encounter the same issues.
Re: Samba: mount error(5): Input/output error
Still receiving this error code with the latest version of CentOS:
Mar 15 14:14:23 localhost kernel: CIFS VFS: validate protocol negotiate failed: -13
Mar 15 14:14:23 localhost kernel: CIFS VFS: cifs_mount failed w/return code = -5
I'm sure it's a bug.
Mar 15 14:14:23 localhost kernel: CIFS VFS: validate protocol negotiate failed: -13
Mar 15 14:14:23 localhost kernel: CIFS VFS: cifs_mount failed w/return code = -5
I'm sure it's a bug.