ErrNo 13 errors when accessing Samba share on NAS

Support for the Debian/Ubuntu package, created by JCFP.
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
gaijinboricua
Newbie
Newbie
Posts: 1
Joined: March 6th, 2014, 11:59 am

ErrNo 13 errors when accessing Samba share on NAS

Post by gaijinboricua »

Hello everyone, I am encountering a problem that my Google-Fu skills can't find a solution to.

I am running Sabnzbd on a raspberry pi on Raspbian. So far the installation works and I can access the web gui with no problems. The only problem I am finding is that Sabnzbd is not downloading, upon inspecting the lgos I noticed that I am getting a lot of ErrNo 13 errors when accessing my samba shares on my NAS. Oddly enough I can access, write and delete from these shares under the terminal window (command line). I have not created any other users, only the default user that comes in raspbian.

My configuration is as follows:
+Sabnzb config file has USER=pi
+Samba drives located at 192.168.2.2 and mounted using the following command: sudo mount -t cifs -o user=<nas_user>,password=<nasuserpassword>,sec=ntlmv2 //192.168.2.2/<sharedfolder> /home/pi/<sharename>
+mount works fine for Deluge when downloading torrents.


<nas_user> is the user in the NAS with read/write rights to the share
<nasuserpassword> is the password for this user
<sharedfolder> is the folder name in the NAS, no spaces on the name
<sharename> is the name of the mount on linux, no spaces on the name


I am thinking of changing the <sec=ntlmv2> part to <rw,file_mode=0777,dir_mode=0777>, but not sure if this will cause any unexpected security issues or break this mount.


I am not sure if I am missing something. Any help is greatly appreciated.
Post Reply