Security Compliance

SEM SMB Mount error (13)

This article provides brief information and steps to resolve the following error: Mount error (13) Permission denied. or Error: Cannot mount any SMB version

First published date

10/8/2018 7:37 PM

Last published date

9/9/2022 12:25 AM

Overview

While upgrading your SEM(Formerly LEM) appliance OR during scheduled daily backups you may see following error(s)

Mount error (13) Permission denied.

OR

image.png
And in mgrconfig.log on the SEM appliance

2020-12-21 17:10:02 [Backup.pm:113 #2297] SolarWinds normalized-db-backup : OK, continue in backup
2020-12-21 17:10:02 [SmbMount.pm:246 #2297] trying mount smb versions: autoNegotiate, 3.11, 2.0, 1.0
2020-12-21 17:10:02 [SmbMount.pm:262 #2297] smb version 'autoNegotiate' failed: smb error: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) at /etc/perl/Lem/SmbMount.pm line 284.
2020-12-21 17:10:02 [SmbMount.pm:262 #2297] smb version '3.11' failed: smb error: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) at /etc/perl/Lem/SmbMount.pm line 284.
2020-12-21 17:10:02 [SmbMount.pm:262 #2297] smb version '2.0' failed: smb error: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) at /etc/perl/Lem/SmbMount.pm line 284.
2020-12-21 17:10:02 [SmbMount.pm:262 #2297] smb version '1.0' failed: smb error: mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) at /etc/perl/Lem/SmbMount.pm line 284.
2020-12-21 17:10:02 [sysconfig:47 #2297] cannot mount any SMB version at /etc/perl/Lem/SmbMount.pm line 270

 

Product section

Security Event Manager

Cause

  1.  Mount error (13) originated from Windows. Windows has issues with multi-layer paths. 
  2. Permissions problem on the SMB/CIFS share

Resolution

Solution 1: 
- Verify network share permissions

Solution 2:
  1. The command that SEM is running (behind the scenes)  
    mount -t cifs //yourserver/yourshare /tmp/smb -o user=youruser,domain=yourdomain,password=yourpassword

    Note: mount.cifs has known issues with multi-layer share paths (up to certain version needs validation)

  2. For example, if your SEM network share is \\yourserver\yourshare\a\folder\way\down\the\line\lem\backups, mount.cifs will likely fail.
  3. As LEM will try to connect to \\yourserver\yourshare only and skips the rest of the path.
  4. If it is a requirement for you to keep the backup/upgrade package in .\lem\backups folder, it should share it directly so you can use shorter path \\yourserver\backups at the command prompt or at worst you can use \\yourserver\lem\backups.
  5. The mount.cifs command wants to mount an actual share and struggles when the share path is buried more than 2/3 levels deep . 

For example, the share is \\abc-server.domain.com\ABC, that's where the upgrade folders should be copied to.

So, at the upgrade command prompt you would enter: "//abc-server.domain.com/ABC"

And your upgrade folders are located under : //abc-server.domain.com/ABC/upgrade 
 

Note: 
  • Error 13 suggests, that you've entered a bad username/password, but this can be misleading and often manifests as a result of an overly complex path or permissions
  • If the above still fails, then it is most likely that SMBv1 is disabled in your Windows environment (which was requirements for LEM 6.2 EOL) But starting with SEM 6.4 and higher SEM supports SMB v2 and v3 in SEM 2020.