Question

2

CIFS mounting fails in Ubuntu 13.10 tried with sec=ntlm and sec=ntlmv2

rated 0 times [ 2] [ 0] / answers: 1 / hits: 16465 / 1 Year ago, mon, february 13, 2023, 1:33:18

I have read just about every cifs mount question and sadly cannot get a cifs share to mount.

The command I am using works from a redhat machine but not from Ubuntu 13.10 ( kernel 3.11.0-15-generic)

The command I use is

sudo mount -t cifs //server01.mycompany.com/archive$/StructuralBiology/RAW-Data /home/rawdata2 -o user=hari.lastname,rw,soft,nosuid,uid=1000,gid=1000

I have tried this with sec=ntlm , sec=ntlmv2 and it still does not work.

The cifs command fails with :

mount error(13): Permission denied

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

And dmesg has a message:

[169895.357046] CIFS VFS: cifs_mount failed w/return code = -13

[170370.733123] CIFS VFS: cifs_read_super: get root inode failed

I have spend days trying to find an answer and cannot : any help or pointers will be greatly appreciated.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

theurn

Add To Favorites

Follow

Total Points: 30

Total Questions: 110

Total Answers: 111

Location: Bahrain

Member since Fri, Sep 16, 2022

2 Years ago

theurn questions

1 How to change a folder's permissions and owners?

Tue, Apr 5, 22, 14:18, 2 Years ago

1 Cant mount Window's partition on bootable ubuntu 20.04

Mon, Feb 14, 22, 16:29, 2 Years ago

1 select positional argument in xargs

Sat, Apr 8, 23, 05:26, 1 Year ago

1 Refresh rate not working on login screen

Tue, Jan 10, 23, 23:59, 1 Year ago

1 Chromium does not start after update on 20.04

Fri, Apr 8, 22, 01:36, 2 Years ago

View All

answered 1 Year ago igeonlothe · Accepted Answer

So it seems that the Linux kernels in Ubuntu 13.10 may have different defaults for the mount.cifs program.

I was reading the cifs documentation and it had the text:

vers=

           SMB protocol version. Allowed values are:



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



           ·   2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and

               Windows Server 2008. Note that the initial release version of Windows Vista spoke a slightly different

               dialect (2.000) that is not supported.



           ·   2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.



           ·   3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.

So I assumed that the archive$ was a Microsoft Windows 7 and Windows Server 2008R2 based server.

So finally I got this command ( old command with vers=2.1 added) to mount the share

alias mountr2='sudo mount -t cifs //server01.mycompany.com/archive$/StructuralBiology/RAW-Data /home/rawdata2 -o user=hari.lastname,rw,soft,nosuid,uid=1000,gid=1000,vers=2.1

The share then mounted just as before with full read and write permissions.
Sadly this took me a long while ( two plus months) to figure out.

Hoping the cifs module and mount.cifs program could spit out more useful and meaningful error messages to not make this process such a blackbox.