The problem is probably that you are using a softlink to redirect the samba var folder to the other disk.
A softlink behaves somewhat differently than a real folder and could be not acceptable to the samba socket creation code.

What I would do in a setup like yours is put the entire /var filesystem on the other disk (or as a tmpfs) and simply mount it at boot-time.
Or, if you don't wan to go all the way, just create a tmpfs filesystem at boot and mount that at /var/lib/samba.

A mount-point should be OK. Otherwise no Linux system would ever be able to put /var on a different filesystem.

Answer from Tonny on Stack Exchange
🌐
Reddit
reddit.com › r/selfhosted › smb share only works in read-only
r/selfhosted on Reddit: SMB share only works in read-only
February 17, 2024 -

I am new to Linux and tried to make a Samba share, to access files on an external hard drive (ext4), mounted on my Linux system, from a mac and a PC. I followed the steps on Ubuntu's website, and I can navigate in the share, but only in read-only. I would like all my shares to work with read-write permissions to the designated users.

Here is my smb.conf file:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

#======================= Global Settings =======================

[global]

create mask = 0644
directory mask = 0755

## 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 = classic
# primary domain controller', 'server role = classic 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

[MOVIES]
    comment = MOVIES
    path = /media/MOVIES
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[DATA]
    comment = DATA
    path = /media/DATA
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[PUBLIC]
    comment = PUBLIC
    path = /media/DATA/PUBLIC
    read only = no
    browsable = yes
    valid users = admin, myusername, public
    write list = admin, myusername, public

🌐
Stack Exchange
unix.stackexchange.com › questions › 374201 › read-only-file-system-error-on-samba-share-alternative-share-with-identical-o
ubuntu - "Read-only file system error" on Samba share, alternative share with identical options working (Linux client) - Unix & Linux Stack Exchange
June 29, 2017 - Now the strange thing is that I can access both shares from my Linux client as ap but I only have write access on [temp]. When I try to create a folder or delete a file on [media], I get a "Read-only file system" error.
Discussions

raspbian - Samba share is read-only despite settings - Raspberry Pi Stack Exchange
I am running Samba on my Raspberry Pi, and have configured the smb.conf file as such, which should just be the default version with the following appended: [media] comment = Media path = /mnt/raid1/media valid users = @media force group = media create mask = 0660 directory mask = 0771 browseable = yes writable = yes read only ... More on raspberrypi.stackexchange.com
🌐 raspberrypi.stackexchange.com
permissions - Samba shares are read-only from both Windows and Linux - Unix & Linux Stack Exchange
I managed to connect both Linux ... only in read-only mode. I get Permission denied on all attempts to write, even though the permissions from ls show that I should be able to write. ... Here 1000 is the ID of myuserserv. I'd like to use this drive for purposes other than Samba sharing, so I didn't specify sambauser instead. sambaserv: Created sambauser by issuing these commands: useradd sambauser passwd sambauser pdbedit -a -u sambauser ... $ sudo testparm Load smb config files from ... More on unix.stackexchange.com
🌐 unix.stackexchange.com
June 2, 2015
read_only filesystem doesn't work
mkdir failed on directory /var/log/samba/cores: Read-only file system Failed to create /var/log/samba/cores for user 0 with mode 0700 Unable to setup corepath for smbd: Read-only file system smbd version 4.8.4 started. More on github.com
🌐 github.com
1
November 25, 2018
SMB shares suddenly read only [or how to troubleshoot samba?]
I created a new dataset, configured with user1 as owner: only read access. Created a new user, change the owner of the new dataset to this new user: write access. When accessing over SSH, on the different datasets, the owner is set correclty (user1 for existing datasets or new user for new dataset). So it appears that at system level (linux access rights) it works as expected, so it might be somewhere at samba ... More on truenas.com
🌐 truenas.com
4
August 16, 2020
🌐
Linux-training
linux-training.be › storage › ch19.html
Chapter 19. a read only file server
The share is called pubread and the path is set to our newly created directory. Everyone is allowed access (guest ok = yes) and security is set to read only. [pubread] path = /srv/samba/readonly comment = files to read read only = yes guest ok = yes
🌐
Raspberry Pi Forums
forums.raspberrypi.com › board index › projects › networking and servers
simple solution to run SAMBA on a read only file system - Raspberry Pi Forums
A better system would be to backup the domain (Samba provides the tool to do this) and then rebuild the domain if the DC is turned off and damaged (again Samba provides a too to restore a domain). ... Assuming you still want to do this and are using RPiOS, I think there is an even simpler way: Configure your Samba server as you would normally. Enable the read only overlay filesystemfor the root partition in raspi-copnfig.
🌐
Ask Ubuntu
askubuntu.com › questions › 1378952 › files-become-read-only-when-adding-files-to-a-samba-share-between-ubuntu-and-win
networking - Files become read-only when adding files to a Samba share between Ubuntu and Windows - Ask Ubuntu
December 3, 2021 - To be clear, you can write files to the Samba share on Ubuntu, but cannot read the files back to your Windows machine(s). Is this correct? Which version of Ubuntu are you using? How was the Samba share configured? ... @matigo I'll try to answer your questions as best I can but I might be misunderstanding. While in Ubuntu I can access everything with full permissions, but when using the windows machine I can only write to the first folder, any deeper and it becomes read only.
Find elsewhere
🌐
Arch Linux Forums
bbs.archlinux.org › viewtopic.php
[solved]samba share - read only file system error / Networking, Server, and Protection / Arch Linux Forums
May 4, 2010 - [global] workgroup = MEDIACENTER server string = Samba Server hosts allow = 192.168.1. 192.168.2. 127. load printers = no guest account = danny log file = /var/log/samba/%m.log max log size = 50 dns proxy = no [public] comment = Public Stuff path = / available = yes browsable = yes public = yes writable = no ... 2007 - Started using Arch Linux as my only/main OS - Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8Gb DDR3 ram - 700Gb HDD On board intel Graphics & Sound ... 2007 - Started using Arch Linux as my only/main OS - Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8Gb DDR3 ram - 700Gb HDD On board intel Graphics & Sound
🌐
Stack Exchange
unix.stackexchange.com › questions › 207068 › samba-shares-are-read-only-from-both-windows-and-linux
permissions - Samba shares are read-only from both Windows and Linux - Unix & Linux Stack Exchange
June 2, 2015 - File and share permissions are not related to each other and you need to set them individually. You need a line such as this in smb.conf to allow write access to the share: ... See smb.conf man page for the details. ... Doesn't work for me. However, what does work (as I have just discovered) is adding sambauser to the group of myuserserv (and restarting Samba daemon).
🌐
Openenergymonitor
openenergymonitor.github.io › forum-archive › node › 12124.html
Guide: How to enable Samba server on the Pi's read only file system | Archived Forum
Enabling Samba on the Raspberry Pi enables its files to be read easily in Windows, its very useful if like me your day to day work is from a Windows machine. To allow it to work with the read only file system requires a few extra steps which I'll detail below.
🌐
Raspberry Pi Forums
forums.raspberrypi.com › board index › projects › networking and servers
Samba & read only Filesystem - Raspberry Pi Forums
RPi B using Wheezy, Samba and transmission installed. Thanks for your guidance! ... I have logged in as root, and i still get "read only file system" Mount command details: /dev/root on / type ext4 (rw,noatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=216132k,nr_inodes...
🌐
GitHub
github.com › dperson › samba › issues › 174
read_only filesystem doesn't work · Issue #174 · dperson/samba
November 25, 2018 - I saw you updated your docker-compose, and noticed that you are doing a read_only filesystem. This does not work due to multiple file changes. usermod: /etc/passwd.9: Read-only file system usermod: cannot lock /etc/passwd; try again later. groupmod: /etc/group.10: Read-only file system groupmod: cannot lock /etc/group; try again later.
Author   dperson
🌐
TrueNAS Community
truenas.com › forums › archives › freenas (legacy software releases) › freenas help & support › sharing
SOLVED - SMB shares suddenly read only [or how to troubleshoot samba?] | TrueNAS Community
August 16, 2020 - I created a new dataset, configured with user1 as owner: only read access. Created a new user, change the owner of the new dataset to this new user: write access. When accessing over SSH, on the different datasets, the owner is set correclty (user1 for existing datasets or new user for new dataset). So it appears that at system level (linux access rights) it works as expected, so it might be somewhere at samba ...
🌐
Red Hat
access.redhat.com › solutions › 2058633
Samba read-only share is not working as expected. - Red Hat Customer Portal
samba read-only share is not working as expected. We created a Samba share, marking it as read-only (it's actually a read-only FS created with funionfs). When Windows users access that share via Windows Explorer and try to copy a file Windows ...
🌐
Super User
superuser.com › questions › 1247178 › samba-refuses-to-start-with-ro-rootfs
linux - Samba refuses to start with ro rootfs - Super User
September 4, 2017 - I configured Raspbian Stretch to mount rootfs in read-only mode. Basically I did the following: apt-get -y remove --purge triggerhappy logrotate dphys-swapfile apt-get -y install busybox-syslogd;...
🌐
LinuxQuestions.org
linuxquestions.org › questions › linux-networking-3 › samba-config-to-allow-windows-read-only-file-attribute-changes-38531
Samba config to allow Windows read-only file attribute changes
I am struggling with a client's accounting software (Daceasy version 10.5) where I have recently replaced a Win2k server with a Linux (e-Smith SME ver
🌐
Arch Linux Forums
bbs.archlinux.org › viewtopic.php
Samba guest (read only) requires write permission on file system / Networking, Server, and Protection / Arch Linux Forums
August 3, 2017 - [global] workgroup = WORKGROUP hosts allow = 127.0.0.1, 192.168.178.1/24 hosts deny = 0.0.0.0/0 log file = /var/log/samba/%m.log max log size = 50 security = user guest account = nobody encrypt passwords = true [RR-Videos] comment = Video Share path = /RR/Videos browseable = yes guest ok = yes read only = yes write list = @neutronst4r