Hi Guys,
I need a bit help on this because my OpenLDAP and AD, so i can not configure Samba to do a test.
Currently working on a NS8 server for a friend which AD installes, but i want to install Samba but with the share on a 2nd disk which is mounted
Is it easy to link all the samba share to this disk or do i need to perform so manual actions?
Manual actions are needed, see this thread.
Another way would be to install the samba app on the new disk, see Disk usage — NS8 documentation
You could use some virtualization for testing.
Thanks MrMarkuz,
I was hoping NS8 was a bit further than this old thread.
Maybe a UI setting would be great
Thanks and Yes i can use VM, but i need to seed up a good test VM some day
I’ve setup an VMtest NS8 and add the AD and Samba
The test share is visible in windows, so that part went well.
Only i have tried to understand the posts but i can get to the 2nd disk linked so all the samba share are stored on this.
For the home it may keep as it is. I want only large storage share
How can i mount this 2ns disk to this share ?
i’ve manage to get it working, but no sure it is proper way and holds updates??
I mount the 2nd disk to the podman folder
/dev/sdb1 /home/samba2/.local/share/containers/storage/volumes/shares/_data none bind 0 0
Then change owner to samba and the net folder are stored there now
I think updates are working.
The alternative method is to mount it from the samba “shares” volume like explained here
How should this be for samba.
Like this ?
mount /dev/sdb1 /mnt/disk00
runagent -m samba1 podman volume create --opt=device=/mnt/disk00/ --opt=type=bind samba1
To check the available volumes:
[root@node ~]# runagent -m dokuwiki1 podman volume ls
DRIVER VOLUME NAME
local dokuwiki-data
[root@node ~]# runagent -m samba1 podman volume ls
DRIVER VOLUME NAME
local homes
local shares
local data
local config
local timescaledb
In the case of the samba shares, it’s the shares volume so the command should be
runagent -m samba1 podman volume create --opt=device=/mnt/disk00/ --opt=type=bind shares
Am i doing something wrong?
runagent -m samba2 podman volume create --opt=device=/mnt/disk00/ --opt=type=bind shares
Error: volume with name shares already exists: volume already exists
What does “runagent -m samba2 podman volume ls” tell you? Previously it was samba1, so are you trying to mount an already mounted share on samba1 also on samba2?
DRIVER VOLUME NAME
local homes
local shares
local data
local config
i’ve no samba 1.
It is a test VM server so only Samba2
You need to create the volume before it is created by the samba app itself.
Remove the user domain and reinstall it. Before finally configuring samba (enter admin user/password etc), go through following steps:
Prepare the mountpoint:
chown samba3:samba3 /mnt/disk00
chmod 700 /mnt/disk00/
Create the shares volume:
runagent -m samba3 podman volume create --opt=device=/mnt/disk00/ --opt=type=bind shares
Now you can finish configuring samba and the created shares should be visible in /mnt/disk00
Thanks
So basically you can not at an extra disk once samba has been installed and the docker/podman has been created
I tried to install samba shares, but i’m unable to do this
Samba has been installed as LDAP, but i can not see the Samba File share menu
It seems you didn’t set the local interface as the screenshot shows the wireguard IP 10.5.4.1 instead of some private LAN address. In this mode the samba file server isn’t shown in the app drawer.
