` if the file system is btrfs.
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [October 4, 2023, 9:02am UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/7 "2023-10-04T09:02:25Z")
Thanks, I think you’re right. I already moved root to an SSD; the only mount points showing as read-only are:
`ramfs on /run/credentials/systemd-sysctl.service`
`ramfs on /run/credentials/systemd-sysusers.service`
`ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service`
`ramfs on /run/credentials/systemd-tmpfiles-setup.service`
A reboot didn’t fix it so I’ll try swapping the SDcard when I get hold of a spare one!
---
### Author:  [@Sunil](https://discuss.freedombox.org/u/Sunil)
#### Post date: [October 4, 2023, 2:15pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/8 "2023-10-04T14:15:10Z")
Just focus on the physical filesystem mounted on ‘/’ holding your ‘/etc/’ file. Everything in /run is backed by RAM. Running `journalctl` will also show you the reason why the filesystem was mounted as read-only (likely disk errors).
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [October 4, 2023, 9:31pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/9 "2023-10-04T21:31:07Z")
“/” isn’t mounted read only. I found this error in `journalctl`:
```auto
Oct 04 17:32:58 freedombox kernel: BTRFS warning: duplicate device /dev/mmcblk0p2 devid 1 generation 7478 scanned by pool-udisksd (3507)
Oct 04 17:32:58 freedombox /usr/share/plinth/actions/actions[3502]: Error executing action: Command '['udisksctl', 'mount', '--block-device', '/dev/mmcblk0p2', '--no-user-interaction']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/usr/share/plinth/actions/actions", line 93, in _call
return_values = func(*arguments['args'], **arguments['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/plinth/modules/storage/privileged.py", line 218, in mount
subprocess.run([
File "/usr/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['udisksctl', 'mount', '--block-device', '/dev/mmcblk0p2', '--no-user-interaction']' returned non-zero exit status 1.
Oct 04 17:32:59 freedombox /usr/bin/plinth[560]: Mount operation failed: by-uuid-8bee72a3-2aa4-4bb7-a434-4ecf89057300 /dev/mmcblk0p2: Command '['udisksctl', 'mount', '--block-device', '/dev/mmcblk0p2', '--no-user-interaction']' returned non-zero exit status 1.
```
I copied the contents of the SD card to a new one and most of that error no longer shows in `journalctl` but the bit about “duplicate device” is still there and samba still isn’t working. I’m guessing it has something to do with when I originally moved root from the SD card to the SSD.
Tomorrow I will try deleting the second partition of `/dev/mmcblk0` and see what happens.
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [October 5, 2023, 1:36pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/10 "2023-10-05T13:36:39Z")
I’m still getting this error:
```auto
freedombox update-apparmor-samba-profile[5860]: /usr/share/samba/update-apparmor-samba-profile: line 59: /etc/apparmor.d/samba/smbd-shares.new: Read-only file system
```
I created a file in `/etc/apparmor.d/samba/` so it definitely isn’t read only. I’ve deleted the extra `/dev/mmcblk0p2` partition and reinstalled samba and apparmor. None of it seems to have made any difference. Anyone have any ideas?
---
### Author:  [@kopfkind](https://discuss.freedombox.org/u/kopfkind)
#### Post date: [October 5, 2023, 5:42pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/11 "2023-10-05T17:42:48Z")
This sounds really frustrating, and I am also running out of ideas. One more idea: How about trying to completely remove and reinstall apparmor. The error message refers to apparmor, and assuming something has gone wrong maybe purging the package may help? Unless you have customizations that you need to keep?
```
sudo apt remove --purge apparmor
```
Afterwards there should not be any `/etc/apparmor*` folders anymore.
If that solves the issue, you could try to bring it back with the default config afterwards by simple reinstalling.
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [October 5, 2023, 9:23pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/12 "2023-10-05T21:23:30Z")
No luck with that. I really appreciate the help anyway 🙂
I might try a clean install tomorrow.
---
### Author:  [@Sunil](https://discuss.freedombox.org/u/Sunil)
#### Post date: [October 5, 2023, 10:21pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/13 "2023-10-05T22:21:31Z")
> [@bella-north](#):
>
> I’m still getting this error:
>
> ```auto
> freedombox update-apparmor-samba-profile[5860]: /usr/share/samba/update-apparmor-samba-profile: line 59: /etc/apparmor.d/samba/smbd-shares.new: Read-only file system
>
> ```
>
> I created a file in `/etc/apparmor.d/samba/` so it definitely isn’t read only. I’ve deleted the extra `/dev/mmcblk0p2` partition and reinstalled samba and apparmor. None of it seems to have made any difference. Anyone have any ideas?
I checked the script `/usr/share/samba/update-apparmor-samba-profile`. It is a simple shell script that is executed just before starting `smbd.service`. In line 59 if this script, it tries to write to the file `/etc/apparmor.d/samba/smbd-shares.new`. Do you still see this error? Are you able to manually create a new file (as root) in the directory `/etc/apparmor.d/samba`?
Also the script successfully exists if it does not find the directory /etc/apparmor.d/samba. Try renaming that directory to `/etc/apparmor.d/samba.bak`.
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [October 6, 2023, 8:28am UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/14 "2023-10-06T08:28:46Z")
I was able to create the file `/etc/apparmor.d/samba/smbd-shares.new` using root. `nmbd` and `samba` remained inactive (after a restart). `smbd` was active but still showed these errors:
```auto
Oct 06 09:04:24 freedombox update-apparmor-samba-profile[9718]: grep: /etc/apparmor.d/samba/smbd-shares: No such file or directory
Oct 06 09:04:24 freedombox update-apparmor-samba-profile[9715]: /usr/share/samba/update-apparmor-samba-profile: line 59: /etc/apparmor.d/samba/smbd-shares.new: Read-only file system
Oct 06 09:04:24 freedombox update-apparmor-samba-profile[9719]: diff: /etc/apparmor.d/samba/smbd-shares: No such file or directory
Oct 06 09:04:24 freedombox update-apparmor-samba-profile[9720]: mv: cannot move '/etc/apparmor.d/samba/smbd-shares.new' to '/etc/apparmor.d/samba/smbd-shares': Read-only file system
```
After renaming the `/etc/apparmor.d/samba` dir those errors disappeared. But nmbd and samba services still wouldn’t run and I still couldn’t mount the share.
Looking at the script `/usr/share/samba/is-configured` (which I don’t think was in Bullseye), it seems that nmbd won’t start because of the setting `disable netbios = yes` in `/etc/samba/smb.conf`. Commenting that line out of the config allows nmbd to start properly but trying to mount the share still results in the error:
```auto
mount error(113): could not connect to 192.168.1.xxxUnable to find suitable address.
```
I don’t understand the script `/usr/share/samba/is-configured` well enough to see why it’s preventing the samba-ad-dc service from starting.
---
### Author:  [@bella-north](https://discuss.freedombox.org/u/bella-north)
#### Post date: [November 6, 2023, 10:44pm UTC](https://discuss.freedombox.org/t/nmbd-service-wont-start-samba-not-working/2752/15 "2023-11-06T22:44:50Z")
Well I’ve finally found a solution! I added my computer’s ip address as a source to the internal zone of firewalld:
`sudo firewall-cmd --permanent --zone=internal --add-source=[ip address]`
Don’t know what changed to make that necessary but I can now access the share again 😁