[SOLVED] Unable to mount cifs volume

cbo77 · 2018-01-09 12:05:25

Hello archforums, I recently changed my uni computer over from Mint to Arch, and I can't get the network drive to mount.

sudo mount //hostname/share -t cifs /home/chris/network/idrive -o credentials=/etc/cred/uni

Results in:

mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

The same command worked on mint previously. The share is definitely online, I can ping the host etc.

I have read the suggested man page and couldn't see what could help. I have googled the problem but only relevant results I could find were from ~2014 ([1] [2]). Still, I tried the fixes suggested (setting mount options 'sec=krb5', or 'vers=2.0') but to no avail.

I have cifs-utils installed and the driver is loaded.

Any ideas? Any other relevant info I'm missing here?

Last edited by cbo77 (2018-01-10 13:17:35)

lo1 · 2018-01-09 12:30:26

I've never used my linux laptop as a client, perhaps you'd need this?

exad · 2018-01-09 13:16:32

mount -t  cifs -o credentials=/etc/cred/uni,uid=1000,gid=1000 //hostname/share /home/chris/network/idrive

cbo77 · 2018-01-09 15:41:46

Thanks for the replies.

lo1:-
I installed samba and tried with the winbindd service on, but no change. I don't think its a domain resolution problem. If I ping hostname, it translates it to an IP correctly and everything.

exad:-
Didn't work either Same error code as before.

seth · 2018-01-09 16:12:51

stat /home/chris/network/idrive

Do you literally pass "//hostname/share"?

cbo77 · 2018-01-09 16:32:34

seth:-

Output from stat:

  File: /home/chris/network/idrive
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 803h/2051d	Inode: 25428679    Links: 2
Access: (0755/drwxr-xr-x)  Uid: ( 1000/   chris)   Gid: (  992/   users)
Access: 2018-01-09 10:10:48.923971968 +0000
Modify: 2017-12-21 17:14:06.583466509 +0000
Change: 2017-12-21 17:14:06.583466509 +0000
 Birth: -

No, I'm passing the actual doman and share names, I just didn't want to post them online.

seth · 2018-01-10 12:59:27

Connection problem then.
If the server is not reachable across the internet, but a local hostname on a local server, you can safely (ok, maybe not if it's "pornhub" or so ;-) post it.

For the most prominent recent change, try to mount it with "vers=1.0" (wannacry situation)
If that works, fix the server if you can. If not, it would be good to know more about the server (windows/samba; version; non-private parts of smb.conf)

The credentials are aligned and the file is readable? Check your journal and the server logs (if you can) on errors here.

cbo77 · 2018-01-10 13:16:54

seth:-

Setting vers=1.0 worked! Thank you!

According to the man page, this is the default? Why did setting this work?

vers=
           SMB protocol version. Allowed values are:

           ·   1.0 - The classic CIFS/SMBv1 protocol. This is the default.

seth · 2018-01-10 13:19:51

It's not, rushed move - the manpage is probably dated.

The reason is the wannacry disaster. If you missed it, google it up and tell the server admin (in doubt yourself) to fix this.
Most notably if this is a publically accesible server, running it on SMBv1 is no way acceptable.

Arch Linux

#1 2018-01-09 12:05:25

[SOLVED] Unable to mount cifs volume

#2 2018-01-09 12:30:26

Re: [SOLVED] Unable to mount cifs volume

#3 2018-01-09 13:16:32

Re: [SOLVED] Unable to mount cifs volume

#4 2018-01-09 15:41:46

Re: [SOLVED] Unable to mount cifs volume

#5 2018-01-09 16:12:51

Re: [SOLVED] Unable to mount cifs volume

#6 2018-01-09 16:32:34

Re: [SOLVED] Unable to mount cifs volume

#7 2018-01-10 12:59:27

Re: [SOLVED] Unable to mount cifs volume

#8 2018-01-10 13:16:54

Re: [SOLVED] Unable to mount cifs volume

#9 2018-01-10 13:19:51

Re: [SOLVED] Unable to mount cifs volume

Board footer