Backup

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
ryem1340
Posts: 11
Joined: Fri Sep 20, 2019 5:34 am

Backup

Post by ryem1340 »

Hi All,

This query is regarding the Local Scheduled backup. We are trying to mount a network drive and use that as a repository.
SMBv1 is turned off on our storage and when we try to manually mount the network drive using mount.cifs it defaults to use SMBv1. We tried to force it to use by using the option vers=2.1 but no luck.

Any suggestions on how we can force it to use the later versions of SMBv2 or above.

Nagios XI- 5.7.1
Centos 6.8 (Final)
Kernel: 2.6.32-642.6.2.el6.x86_64 #1 SMP Wed Oct 26 06:52:09 UTC 2016

Thanks in advance.
User avatar
jdunitz
Posts: 235
Joined: Wed Feb 05, 2020 2:50 pm

Re: Backup

Post by jdunitz »

Do you get any kind of error when you try to specify the protocol version?
What version of cifs-utils do you have installed?

--Jeffrey
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
ryem1340
Posts: 11
Joined: Fri Sep 20, 2019 5:34 am

Re: Backup

Post by ryem1340 »

When I try to mount the drive using Vers=2.1 or above as an option. It gives an output that the there is an I/O error.
The verbose message shows that it by default uses ver=1 in the option.

cifs-utils - cifs-utils-4.8.1-20.el6.x86_64. Thats the latest one available for Centos 6.8 I believe.
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Backup

Post by ssax »

If you change Vers=2.1 to vers=2.1 (lowercase), does it work?

Please post the full sanitized command with verbose output turned on and we'll take a look.
ryem1340
Posts: 11
Joined: Fri Sep 20, 2019 5:34 am

Re: Backup

Post by ryem1340 »

Command I am using :

mount --verbos -t cifs //server/share/ /mountname --verbose -o vers=2.1,username=username,domain=domainname,sec=ntlm

Displays : final mount options: 'ver=2.1,username=username,domain=domain,sec=ntlm'
Prompts for the password : Enters the password

Output:

mount.cifs kernel mount options: ip=ipaddress,unc=\\server\share$,vers=2.1,sec=ntlm,ver=1,user=username,domain=domainname,pass=********
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

On the output it shows that it uses ver=1 also. Not sure if i am doing this wrong
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Backup

Post by ssax »

Is it already mounted? Unmount it first:

Code: Select all

mount | grep /mountname
umount /mountname
Just for testing, does it work if you put the password in there?

Code: Select all

mount --verbose -t cifs //server/share/ /mountname  -o username=username,domain=corpdom,password=XXXXXXXX,sec=ntlm
ryem1340
Posts: 11
Joined: Fri Sep 20, 2019 5:34 am

Re: Backup

Post by ryem1340 »

We have removed the mount earlier before trying to re mount it.
Just tried the Syntax mentioned by including the password but it throws the same error.
User avatar
mbellerue
Posts: 1403
Joined: Fri Jul 12, 2019 11:10 am

Re: Backup

Post by mbellerue »

Rather than sec=ntlm, try sec=ntlmv2, or just omitting the sec option and let CIFS try to figure it out.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
ryem1340
Posts: 11
Joined: Fri Sep 20, 2019 5:34 am

Re: Backup

Post by ryem1340 »

mbellerue wrote:Rather than sec=ntlm, try sec=ntlmv2, or just omitting the sec option and let CIFS try to figure it out.
We have tried that already. Tried various options. Looks like the CentOS 6.X might not support SMB Version 2 or above. Not sure.
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Backup

Post by ssax »

That may be the case:
Basic support for SMB 2.1 was added in kernel version 3.07
Taken from here:

https://wiki.samba.org/index.php/SMB3_kernel_status

What kernel are you running?

Code: Select all

uname -a
What version of samba are you running?

Code: Select all

rpm -qa | grep samba
This seems to indicate that samba4 may support it:

https://wiki.samba.org/index.php/Samba3/SMB2#SMB_2.1
Locked