hello,
I have been trying to mount a windows network drive to a machine. I am receiving this error.
Please help:


mount command (not the real inputs):
mount -t cifs -o username=user,password=pw //10.10.10.10/alf /mnt/alfr

Error received:
[root@monkey]/mnt/alfr/$ ls
ls: reading directory .: Input/output error

show that it is mount:
[root@monkey]/root/$ mount -v
//10.10.10.10/alf on /mnt/alfr type cifs (rw)


fsck:

[root@monkey]/root/$ fsck.ext4 -v /mnt/alfr
e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Is a directory while trying to open /mnt/alfr

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

dmesg:
CIFS VFS: Error connecting to socket. Aborting operation
CIFS VFS: cifs_mount failed w/return code = -110
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
CIFS VFS: cifs_mount failed w/return code = -22
CIFS VFS: cifs_mount failed w/return code = -22
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13
CIFS: Unknown mount option Cusername
CIFS VFS: No username specified
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts
SELinux: initialized (dev cifs, type cifs), uses genfs_contexts

Hi Nojenk - Welcome to LQ.

I was able to find quite a few references when Googling errors 22 and 13 for CIFS mounts - you could start there. A couple of suggestions that came up fairly often:

- Use IP address of Windows machine and not its machine name (you are already doing this, though)

- Make sure you have cifs-utils installed on your linux box with which you are trying to connect

- Try either sec=ntlm or sec=ntlmv2 as options in your mount command.

Cheers !

I have added cifs-utils and I have tried doing it in fstab. Also did sec=ntlmv2 inside the mount statement. I am still receiving CIFS VFS errors. This is the newest one.
CIFS VFS: signing required but server lacks support
CIFS VFS: cifs_mount failed w/return code = -95

In this case, assume that messages about "superblocks" and so-forth are red herrings: the problem is that the two servers are not properly connecting. And, you probably need to look in the Event Viewer (Administrative Tools) on the Windows machine to which you are trying to connect. It should have recorded information about the failed event which Linux might not see, but which will prove essential in understanding the root cause of the problem.

As a matter of course, I always start my investigations with tcpdump or WireShark: "are the messages going in both directions between the two machines?" I want to see, preferably on both sides, that messages and corresponding replies, initiated from both sides, are in fact successfully making the round-trip. (It doesn't matter if they are encrypted, as they probably are.)

I've run into a lot of "bogus message" situations that turned out to be fundamental TCP/IP communication issues, and nothing more.

1 members found this post helpful.