mount issue

[shadowempire]

Hi,
I am trying to mount a share (ext4 formatted usb disk shared via smb on ubuntu).
I am in a plex jail and have no success.

I have created /mnt/mymedia in my jail.

My /etc/samba/smb. conf (on my ubuntu machine):
[mymedia]
path = /mnt/mymedia
public = yes
writeable = yes
comment = mymedia

I can connect to the share from my windows 10 pc, but my jail has problems:

root@plex:/mnt # mount //192.168.1.158/mymedia /mnt/mymedia
mount: /192.168.1.158/mymedia: Operation not permitted


Any ideas?
thx

 

[GBillR]

Hi,
I am trying to mount a share (ext4 formatted usb disk shared via smb on ubuntu).
I am in a plex jail and have no success.
Any ideas?

Sounds like a networking issue. You have not provided details on the network configuration. Can you ping the server with the share from inside the jail? Are all of the machines on the same subnet and switch? Is there a router/firewall in the way?

 

[shadowempire]

Sounds like a networking issue. You have not provided details on the network configuration. Can you ping the server with the share from inside the jail? Are all of the machines on the same subnet and switch? Is there a router/firewall in the way?

I am quite sure that the network is fine.
I can ping my ubuntu server:

root@plex:~ # mount 192.168.1.158/mymedia /mnt/mymedia
mount: 192.168.1.158/mymedia: Operation not permitted
root@plex:~ # ping 192.168.1.158
PING 192.168.1.158 (192.168.1.158): 56 data bytes
64 bytes from 192.168.1.158: icmp_seq=0 ttl=64 time=0.492 ms
64 bytes from 192.168.1.158: icmp_seq=1 ttl=64 time=0.587 ms
64 bytes from 192.168.1.158: icmp_seq=2 ttl=64 time=0.530 ms
--- 192.168.1.158 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.492/0.536/0.587/0.039 ms

root@plex:~ # mount 192.168.1.158/mymedia /mnt/mymediaxxxxxxx
mount: /mnt/mymediaxxxxxxx: No such file or directory

Trying to connect to an invalid share gives the correct error... see above

 

[GBillR]

I am quite sure that the network is fine.
I can ping my ubuntu server:

root@plex:~ # mount 192.168.1.158/mymedia /mnt/mymedia
mount: 192.168.1.158/mymedia: Operation not permitted
root@plex:~ # ping 192.168.1.158
PING 192.168.1.158 (192.168.1.158): 56 data bytes
64 bytes from 192.168.1.158: icmp_seq=0 ttl=64 time=0.492 ms
64 bytes from 192.168.1.158: icmp_seq=1 ttl=64 time=0.587 ms
64 bytes from 192.168.1.158: icmp_seq=2 ttl=64 time=0.530 ms
--- 192.168.1.158 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.492/0.536/0.587/0.039 ms

root@plex:~ # mount 192.168.1.158/mymedia /mnt/mymediaxxxxxxx
mount: /mnt/mymediaxxxxxxx: No such file or directory

Trying to connect to an invalid share gives the correct error... see above

This is usefull information. Can you share the entire smaba config from the ubuntu side? Or is the entire config already in your first post? Are you able to connect the jail to a samba share on the TrueNAS server or some other Samba share on a different server?

My experience with jails is limited, so if it turns out to be a jail config issue, I will have to defer to others more knowledgeable than me...

 

[shadowempire]

I am able to connect to local mounted disks in my jail.

actually it is a default config, just added the 3 shares at the bottom.

root@bolt:# cat /etc/samba/smb.conf
#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin


[mounts]
path = /mnt
valid users = plex
read only = no

[backup]
path = /mnt/NAS4/Backups
public = yes
writable = yes
comment = smb share
printable = no
guest ok = no

[mymedia]
path = /mnt/mymedia
public = yes
writeable = yes
comment = mymedia

 

[GBillR]

Looking at this now, I suspect a permissions issue. You have shared the /mnt/mymedia as a guest, which is a subfolder of the /mnt directory, which you only allow user plex to mount. Your cofig does not have a guest account specified, so I am not sure what might be happening on the ubuntu side when guest tries to mount that share. What do the permissions on the /mnt and subfolders look like on the ubuntu server?

Also, just a note, I am not sure what the "best practices" might be, but I normally reserve the /mnt folder for mounts to shares on other servers. If your media files are located there (on the ubuntu server), I do not think it is a problem, but not sure it would align with typical setups. Unless you are sharing a share... which I guess might be possible, but I wouldn't want to try to figure that hot mess out.

Can you try mounting the share as user plex? You will have to ensure the UID is the same on both the ubuntu server and the jail. In my plex server (not a jail, but a ESXi VM), when mounting a samba share I had to add credentials to the fstab entry to properly mount the share. Ultimately, I decided to switch to nfs for my shares with plex since it seemed easier to configure...

Sorry I may not be much more help... my experience has always been similar to yours, and then once I get it working I do not do a great job of documenting what I did to get it working.

 

[shadowempire]

thx for your answers.
still no luck...

I changed my smb config to only have:

[mymedia]
path = /mnt/mymedia
public = yes
writeable = yes
comment = mymedia
guest ok = yes

Under Windows I just enter \\192.168.1.158\mymedia and it connects at once.
I have also tested the config with another sharename and it is working under windows.

And I tested to mount it on another Linux machine (raspberry pi 4 debian) and it works.

root@omv:/mnt# mount //192.168.1.158/mymedia2 /mnt/tmp3
Password for root@//192.168.1.158/mymedia2:
root@omv:/mnt/tmp3# ls tmp3
Datashare5TB aquota.group aquota.user docker lost+found