Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Cannot Upgrade LEM - Mount error (13)

Cannot Upgrade LEM - Mount error (13)

Updated February 18, 2019

Overview

 

You are trying to upgrade your LEM appliance from 6.2.X to 6.3.x and receive the error 

Mount error (13) Permission denied 

while trying to mount a Windows network share (CIFS) located either on Client or Server Windows OS.

Environment

  • LEM version 6.1 and earlier
  • Windows 2012 R2 with enforced NTLM v2 authentication 

 

Cause 

LEM does not support NTLM v2 authentication prior to LEM v6.2.  Mount error (13) originated from Windows. Windows has issues with multi-layer paths. 

Resolution

 

  1. The command that LEM is running (behind the scenes).

    mount -t cifs //yourserver/yourshare /tmp/smb -o user=youruser,domain=yourdomain,password=yourpassword

    mount.cifs has known issues with multi-layer share paths. 

  2. For example, if your LEM 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 the 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

    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.

If the above still fails, then it is most likely that SMBv1 is disabled in your Windows environment.

 

 

 

Last modified

Tags

Classifications

Public