9
4
I am getting mount error (5):
Input output error on mounting to cifs windows share.
Command executed:
sudo /bin/mount -t cifs //server/folder /mnt/folder/ -o username="domain/username",password=password
Error returned:
mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
The ams command worked on RHEL 32 .
Abdul Jaleel
Posted 2014-12-09T07:46:56.863
Reputation: 106
17
When setting up a share on a Windows 2012 server, I had to use:
sudo mount.cifs //server/folder /path/to/folder/ -o user=username,password=pass,vers=3.0
Note the vers=3.0.
Based on the suggestions below, you may need to try vers=2.0. The vers parameter is the key.
JebaDaHut
Posted 2014-12-09T07:46:56.863
Reputation: 271
3Thank you. vers=2.0 was definitely the key for me in mounting, as was the case with -m SMB2 when listing shares with smbclient -L (client max protocol = SMB2 in smb.conf, for permanent setting). – None – 2017-10-22T22:30:56.430
Adding <code>vers=2.0</code> to the options solved our issue with this error. Thanks for the suggestion! – Kentgrav – 2017-10-23T21:56:04.833
1This answer has worked for me in Linux with the mount command. I had been using the mount command without the vers option for over 2 years and then, suddenly, the mounting was not working anymore – although I could connect on terminal with smbclient. Apparently there has been a change in software version somewhere so that now vers=3.0 option is needed, so that the remote drive is mounted. – loved.by.Jesus – 2018-01-15T13:32:36.180
Mine worked with vers=2.1 sudo mount -t cifs -o username=myUser,password=myPassword,vers=2.1 //1.2.3.4/folderA/folderB /foo/bar --verbose which is weird because the version says 2.23 on my Amazon Linux 1 EC2-Instance [ec2-user@ip-1-2-3-4 ~]$ sudo mount --version mount from util-linux 2.23.2 (libmount 2.23.0: selinux, debug, assert) – Kyle Bridenstine – 2018-08-01T13:22:41.940
1vers=2.0 was the solution for me too. – YoMismo – 2019-02-11T15:47:46.803
2
For me the problem was a different one when trying to mount a share from a NAS device from a more recent GNU/Linux desktop. Specifying -o nounix to disable Unix extensions worked for me.
In the end what helped me was to look into the output of dmesg which told me:
[160169.609325] CIFS VFS: Send error in SETFSUnixInfo = -5
[160169.609327] CIFS VFS: Negotiating Unix capabilities with the server failed. Consider mounting with the Unix Extensions disabled if problems are found by specifying the nounix mount option.
[160169.620877] CIFS VFS: Malformed FILE_UNIX_BASIC_INFO response. Unix Extensions can be disabled on mount by specifying the nosfu mount option.
[160169.620888] CIFS VFS: cifs_read_super: get root inode failed
okurz
Posted 2014-12-09T07:46:56.863
Reputation: 121
2
Check the domain account isn't locked out
Paul
Posted 2014-12-09T07:46:56.863
Reputation: 203
1Bingo! After much frustration regarding error(5), it occurred to me to check dmesg on the GNU/Linux side, only to find Status code returned 0xc0000234 STATUS_ACCOUNT_LOCKED_OUT. So, I checked the properties of the account in question, which is a local Windows 10 account, and sure enough, Account is locked out was checked. (This probably occurred as a result of too many failed logins when I was fiddling with the overall share configuration earlier.) – Ben Johnson – 2018-11-29T14:49:28.907
I think i'd had the same top level error, solved it, but had seen this question in my research so popped back long enough to post.. :) – Paul – 2018-12-03T12:38:32.727
Please refer the below link and follow SEC http://askubuntu.com/questions/491297/permanent-windows-share-mounting
– vembutech – 2014-12-09T07:51:14.037Still giving the same error after adding sec=ntlm – Abdul Jaleel – 2014-12-09T08:23:33.467