I'm running HassOS 4.8, Supervisor v225, on an Intel NUC.

I'm running the add-on with protection mode turned off, but it still fails to mount my exfat USB drive.

[19:11:17] INFO: Hostname: homeassistant
[19:11:17] INFO: More Disks mounting.. wd-drive
[19:11:17] INFO: Mount wd-drive
FUSE exfat 1.3.0
WARN: volume was not unmounted cleanly.
fuse: device not found, try 'modprobe fuse' first
[19:11:17] WARNING: Protection mode is ON. Unable to mount external drivers!

workgroup: WORKGROUP
username: homeassistant
password: 'mypassword'
interface: ''
moredisks:
  - wd-drive
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 192.168.1.1/16
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes

If I use Portainer to open a console inside the add-on, I can see my drive:

bash-5.0# ls /dev_/disk/by-label/
EFI             hassos-boot     hassos-data     hassos-kernel   hassos-overlay  wd-drive

Trying to mount it there, throws the same error:

bash-5.0# mount -t auto /dev_/disk/by-label/wd-drive /wd-drive -o nosuid,relatime,noexec
FUSE exfat 1.3.0
WARN: volume was not unmounted cleanly.
fuse: device not found, try 'modprobe fuse' first
bash-5.0# modprobe fuse
modprobe: FATAL: Module fuse not found in directory /lib/modules/5.4.43

Any ideas on how to get it working?

Hi!
I'm running hassos on raspberry pi 4 4gb from an ssd drive and trying to connect another ext4 hdd for media and plex content.
I've tried samba share addon and it works fine for the config files, but doesn't show second drive.
Installed your addon and it won't start with either one or two drives - I get an error "500 Server Error: Internal Server Error ("error creating overlay mount to mnt/data/docker/overlay2/a0c502c5395b9367e77c8c44f99d56d36769b40a272430d28d5144ed287554e0-init/merged: too many levels of symbolic links")" starting an add-on.
Is there any way to make it work with two drives?

I'm trying to backup my MacBook with an External HDD with the ext4 format connected to a Raspberry Pi 3B+ with Hassio OS.
I managed to install and start the SAMBA NAS add-on and I also my mac recognize successfully the HDD but wen I try to make the backup I get a message that says "Try again when homeassistant is available"
Moved a 387.4MB file to the disk and back via smb and verified the files with checksum and there was no problem
I have my raspberry pi connected to my router via cable.

Here is the log of the add-on

`[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing...
[13:38:41] INFO: Protection Mode is false
[13:38:42] WARNING: MoreDisk option found!
[13:38:42] INFO: More Disks mounting.. TimeMachine
[13:38:42] INFO: Mount TimeMachine
[13:38:42] INFO: Success!
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing...
[13:38:43] ERROR: Got unexpected response from the API: Service not enabled
[13:38:45] WARNING: No MQTT Server found. Homeassistant integration can't work!
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] samba.sh: executing...
[13:38:47] INFO: Hostname: homeassistant
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user homeassistant.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
nmbd version 4.12.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[services.d] done.
[13:38:48] INFO: Starting the AVAHI daemon for homeassistant...
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Waiting for daemon ...
smbd version 4.12.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
INFO: Profiling support unavailable in this build.
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[13:38:49] WARNING: No MQTT config.
Failed to fetch record!
pcap cache not loaded
Failed to fetch record!
pcap cache not loaded
error in mds_init_ctx for: /TimeMachine
_mdssvc_open: Couldn't create policy handle for TimeMachine

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.105

error in mds_init_ctx for: /TimeMachine
_mdssvc_open: Couldn't create policy handle for TimeMachine
fruit_pread_meta_stream: Removing [86ED7541-147C-5D9D-954B-81456388D056.sparsebundle:AFP_AfpInfo] after short read [0]
fruit_pread_meta_stream: Removing [86ED7541-147C-5D9D-954B-81456388D056.sparsebundle:AFP_AfpInfo] failed
Failed to fetch record!
pcap cache not loaded
Failed to fetch record!
pcap cache not loaded
[14:02:49] WARNING: No MQTT config.`

Here is my configuration:

`workgroup: WORKGROUP
username: homeassistant
password: 'xxxxxx'
interface: ''
allow_hosts:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16
• 'fe80::/10'
  moredisks:
• TimeMachine
  veto_files:
• ._*
• .DS_Store
• Thumbs.db
• icon?
• .Trashes
  compatibility_mode: false
  autodiscovery: {}`

Pelas help me, I don’t know what to do

I have mounted USB disk with FAT32 FS.
`
workgroup: WORKGROUP
username: homeassistant
password: ***
interface: ''
allow_hosts:

• XXX.XXX.0.0/24
  moredisks:
• KINGSTON
  veto_files:
• .DS_Store
• '*.zip'
  compatibility_mode: false
  autodiscovery: {}
  `

I can write into any folder shared by SMB, but no way to write *.ZIP file. Also there is a problem to write the file with national characters into KINGSTON share

Hi mate!

Found your Samba NAS while searching how to mount external hard drives into Home Assistant. Nice work! For what I understood, I can use it to mount to /share/ folder and use it in other addons. My usage would be setting up Transmission + Plex to read from folders at external hard drives.

I see that it only supports ext3/4 and fat for the moment, and also you plan to support NTFS and others for the future. Did you start any work already? Willing to help 😉

I try sharing a drive which already mount on the host system but getting error below

[cont-init.d] automount.sh: executing...
[00:59:43] WARNING: MoreDisk option found!
[00:59:44] INFO: More Disks mounting.. Seagate
[00:59:44] INFO: Mount Seagate
mount: /Seagate: /dev_/sdb1 already mounted or mount point busy.
[00:59:44] WARNING: Protection mode is ON. Unable to mount external drivers!

Anyway to support mount bind or just share the file system.

Hi @dianlight ,
first thanks for this nice addon.
At the moment all MQTT entities are shown in 1 device in HomeAssistant.
In my opinion it would be better if each share/directory will be displayed in a seperate device.

Also the default home assistant shares/directories (addons, backup, config, media, share, ssl) are probably always on the same disk.
So they will show always the same values.
Maybe it would be better to merge them to one device and also merge their sensors.

Moved from [https://community.home-assistant.io/t/new-addon-samba-nas-mount-external-disk-and-share-it/172193/221?u=pnstewart]

Error message:

[cont-init.d] automount.sh: executing... 
[14:15:55] INFO: Protection Mode is false
[14:15:56] INFO: MoreDisk option found!
[14:15:56] INFO: MediaLibrary option found!
Warning: Permanently added '[192.168.100.2]:22222' (ECDSA) to the list of known hosts.
Tue Nov  2 14:15:57 CET 2021
[14:15:57] INFO: SSH connection to 192.168.100.2:22222 OK
[14:15:57] INFO: Available Disk Labels:
 External
[14:15:57] INFO: More Disks mounting.. External
[14:15:57] INFO: Mount External
mount: mounting /dev/disk/by-label/External on /mnt/data/supervisor/media/External failed: No such file or directory
[14:15:57] WARNING: Host Mount Fail!
[14:16:33] INFO: Success!
[cont-init.d] automount.sh: exited 0.

If the directory is manually created and permissions set to 777 then the error changes to "Permission denied"

Configuration:

workgroup: WORKGROUP
username: <removed>
password: <removed>
allow_hosts:
  - 192.168.100.0/16
moredisks:
  - External
medialibrary:
  enable: true
  ssh_private_key: |
    -----BEGIN OPENSSH PRIVATE KEY-----
    
    -----END OPENSSH PRIVATE KEY-----
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
compatibility_mode: false
autodiscovery: {}

This is running on a Pi4 with Hassos 6.6, Supervisor 2021.10.8, and Core 2021.10.7 (latest).
The disc is an SSD connected via USB3 to the Pi and formatted in ext4.

Any help would be greatly appreciated

The problem appeared about 2 months ago after some of the homeassistant updates.
There was no time to ask and I thought that during this time someone also had a similar problem ...
Protected mode disabled.

log:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing...
curl: (7) Couldn't connect to server
[20:53:15] ERROR: Something went wrong contacting the API
[20:53:15] INFO: Protection Mode is
[20:53:15] WARNING: MoreDisk ignored because ADDON in Protected Mode!
[20:53:15] WARNING:
[20:53:15] WARNING: A recommended add-on configuration option is not set.
[20:53:15] WARNING:
[20:53:15] WARNING: The configuration key 'protected' seems to be empty.
[20:53:15] WARNING:
[20:53:15] WARNING:
[20:53:15] WARNING: Consider configuring this because:
[20:53:15] WARNING: moredisk only work when Protection mode is disabled
[20:53:15] WARNING: Check the add-on manual for more information.
[20:53:15] WARNING:
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing...
curl: (7) Couldn't connect to server
[20:53:15] ERROR: Something went wrong contacting the API
[20:53:17] WARNING: No MQTT Server found. Homeassistant integration can't work!
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] samba.sh: executing...
curl: (7) Couldn't connect to server
[20:53:18] ERROR: Something went wrong contacting the API
[20:53:18] WARNING: Can't read hostname, using default.
[20:53:18] INFO: Hostname: hassio
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user homeassistant.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.12.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
open_socket_in(): socket() call failed: Permission denied
[20:53:19] INFO: Starting the AVAHI daemon for ...
Bad number of arguments
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing...
/usr/lib/bashio/config.sh: line 49: printf: write error: Broken pipe
[20:53:19] INFO: MQTT cleanup.
Error: Permission denied
[cont-finish.d] mqtt.sh: exited 1.
[cont-finish.d] umount.sh: executing...
[20:53:19] INFO: Unmount drivers.
umount: /dev: target is busy.
[cont-finish.d] umount.sh: exited 32.
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/s6-fdholderd: Read-only file system
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Samba NAS
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 0.banner.sh: executing...

/ | __ _ _ __ ___ | | __ | \ | | __ _ ___
_ \ / | '_ _ | ' \ / | \| |/ _ / __|
) | (| | | | | | | |) | (| | |\ | (| __
|/ _,|| || ||./ _,|| _|_,|/

                          Version 9.5.1-nas4

[cont-init.d] 0.banner.sh: exited 0.
[cont-init.d] automount.sh: executing...
[19:07:37] INFO: Protection Mode is false
[19:07:37] INFO: MoreDisk option found!
[19:07:37] INFO: MediaLibrary option found!
ssh: connect to host 192.168.178.22 port 22222: Connection refused
[cont-init.d] automount.sh: exited 255.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing...
[19:07:38] INFO: MQTT cleanup.
s6-maximumtime: warning: unable to wait for child process: Operation timed out
[cont-finish.d] mqtt.sh: exited 99.
[cont-finish.d] umount.sh: executing...
[19:07:43] INFO: Done.
[cont-finish.d] umount.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

workgroup: WORKGROUP
username: *******
password: ******
allow_hosts:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16
• fe80::/10
  moredisks:
• exthd
  available_disks_log: true
  medialibrary:
  enable: true
  ssh_private_key:
  veto_files:
• ._*
• .DS_Store
• Thumbs.db
• icon?
• .Trashes
  compatibility_mode: false
  autodiscovery: {}

Hi @Lucio_Tarantino, since upgrading to Core 2021.2.3, the mount by labels stops with an error. I am using Home Assistant OS on Rpi3b+ 32 bits with OS 5.11.

I've double-checked the partition name with terminal and it is correct (Typing in portainerv "ls -l /dev/disk/by-label" shows: "NAS -> ../../sda1"). However, I can mount the disk manually using /dev/sda1 in my own addon (which uses a custom apparmor.txt). In your own addon, "mount /dev/sda1 /zzz" results in "cannot mount /dev/sda1 read-only".

I confirm that by adding a apparmor.txt such as this one to your addon, mounting is done properly again https://raw.githubusercontent.com/alexbelgium/hassio-addons-1/master/sambanas/apparmor.txt

I wonder if this pull from the official addon could be the cause : home-assistant/addons#1825

BTW, thanks very much for this addon!

Here is the log:

[cont-init.d] automount.sh: executing... 
[22:01:40] INFO: Protection Mode is false
[22:01:41] WARNING: MoreDisk option found!
mount: /dev_: cannot mount devtmpfs read-only.
[22:01:43] WARNING: Unable to mount external drivers!
[cont-init.d] automount.sh: exited 0.

Supervisor log is OK:

21-02-19 22:00:22 WARNING (SyncWorker_1) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
21-02-19 22:00:24 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on dianlight/armv7-addon-sambanas with version 9.3.0-nas6
21-02-19 22:00:51 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-02-19 22:00:51 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-02-19 22:00:54 INFO (SyncWorker_6) [supervisor.docker.interface] Stopping addon_1a32f091_sambanas application

Just installed Samba NAS and after I start it it shuts down. Log is below

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing...
[17:35:10] INFO: Protection Mode is false
[17:35:11] WARNING: MoreDisk option found!
[17:35:11] INFO: More Disks mounting.. ExternalHD
[17:35:11] INFO: Mount ExternalHD
[17:35:15] INFO: Success!
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing...
[17:35:16] ERROR: Got unexpected response from the API: Service not enabled
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] samba.sh: executing...
[17:35:20] INFO: Hostname: homeassistant
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user XXXX.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[17:35:24] INFO: Starting the MQTT daemon for disks info...
[17:35:24] INFO: Starting the AVAHI daemon for homeassistant...
nmbd version 4.12.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Server version: avahi 0.7; Host name: homeassistant.local
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.12.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
INFO: Profiling support unavailable in this build.
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Established under name 'homeassistant'
[17:35:26] INFO: Sending MQTT autodiscovery...
Error: -h argument given but no host specified.
Use 'mosquitto_pub --help' to see usage.
Got SIGTERM: going down...
Got SIGTERM, quitting.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing...
[17:35:27] INFO: MQTT cleanup.
Error: -h argument given but no host specified.
Use 'mosquitto_sub --help' to see usage.
[cont-finish.d] mqtt.sh: exited 1.
[cont-finish.d] umount.sh: executing...
[17:35:28] INFO: Unmount drivers.
umount: /dev: target is busy.
[cont-finish.d] umount.sh: exited 32.
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/s6-fdholderd: Read-only file system
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Upon attempting to add this repo to HACS, I get Repostitory structure for master is not compliant.

HACS version 1.10.1

Hi, searching for a way to add simply nas functionality to Hassbian, i tried, unsuccessfully, to download your addon "sambanas". I have no experience at all in this kind of things; here, the output from sistem log:

20-04-20 08:28:15 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/dianlight/hassio-addons repository: Cmd('git') failed due to: exit code(1) cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/dianlight/hassio-addons /data/addons/git/1a32f091 stderr: 'Cloning into '/data/addons/git/1a32f091'... POST git-upload-pack (192 bytes) POST git-upload-pack (201 bytes) Submodule 'addon-plex' (https://github.com/dianlight/addon-plex) registered for path 'addon-plex' Cloning into '/data/addons/git/1a32f091/addon-plex'... fatal: remote error: upload-pack: not our ref 24175c1cd0cbae5ab83a4b1157c7fa1e8cb64daf fatal: the remote end hung up unexpectedly Fetched in submodule path 'addon-plex', but it did not contain 24175c1cd0cbae5ab83a4b1157c7fa1e8cb64daf. Direct fetching of that commit failed. '. 20-04-20 08:28:15 ERROR (MainThread) [supervisor.store] Can't load from repository https://github.com/dianlight/hassio-addons

Problem/Motivation

First of all, thank you for your work. I am a very grateful user of Samba NAS and Plex Media Server with NAS addons.

I am running in an issue with Plex Media Server with NAS. The addon can't mount a network disk anymore. It worked well before. As far as I can tell, this problem started appearing with the Core 2021.2.3.

Expected behavior

[12:45:00] INFO: Starting the Plex Media Server...
[12:45:00] INFO: Network Disks mounting.. //192.168**/pms
[12:45:00] INFO: Mount //192.168**/pms
[12:45:00] INFO: Success!

Actual behavior

[12:45:00] INFO: Starting the Plex Media Server...
[12:45:00] INFO: Network Disks mounting.. //192.168**/pms
[12:45:00] INFO: Mount //192.168**/pms
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[12:45:00] WARNING: Protection mode is ON. Unable to mount external drivers!

Steps to reproduce

Start the addon with a networkdisks set up. The //192.168**/pms is mounted using your SambaNAS addon.

claim_code: **
webtools: true
networkdisks: - //192.168**/pms
cifsusername: **
cifspassword: **
cifsversion: '3.0'

Proposed changes

I used docker exec -it addon_**_plex /bin/bash to investigate the problem:

• The folder /192.168**/pms is correctly created and the permissions are correctly set up.
• I tried to execute the mount request and ran into the same problem, even when trying to use a different directory.

The same request (mkdir -p /192.168**/pms && chown -R root:root /192.168**/pms && mount -t cifs -o username='**',password='**',vers=3.0 //192.168**/pms /192.168**/pms) runs perfectly in the homeassistant container. This makes me think that the problem comes from the docker container running the addon missing some permissions or capabilities.

Same as with the Samba NAS addon problem you solved by adding a apparmor.txt, my guess would be to add something similar so the mount capability is added to the docker container running plex.

EDIT : I tried this in a fork and I testify that it works. Thus I created a pull request for you to review : #41

Context (Environment)

Rpi4
Core Version: core-2021.2.3
Supervisor Version: supervisor-2021.02.11
Operating System: Home Assistant OS 5.11
Addon version : 2.4.2-dht2
EDIT : I tried the apparmor correction on both Home Assistant OS 5.11 and Home Assistant OS 5.12. It worked in both cases.

Hi,

would it be possible to add an option to install a backup client (e.g. Jottacloud) into this fantastic add-on ?

or an SSH access to the image, so we can install it ?

Hi Man,
First of all, thanks for you plugin it's really handy

I've seen that your usage percentage is set with unit_of_measurement % but in the value of the sensor it cames with the symbol as well, that transform the result in a string blocking us to use it on graphics

I've by pass it by creating my own sensor, but I think that you could have a look on it.

Cheers !

Are you interested in getting this change upstream?

After updating to 9.3.0-nas5 from 9.3.0-nas4, the addon won't start.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] automount.sh: executing... [19:13:20] INFO: Protection Mode is false [19:13:20] WARNING: MoreDisk option found! [19:13:20] INFO: More Disks mounting.. NAS [19:13:20] INFO: Mount NAS [19:13:22] INFO: Success! [cont-init.d] automount.sh: exited 0. [cont-init.d] mqtt.sh: executing... [19:13:23] ERROR: Got unexpected response from the API: Service not enabled /var/run/s6/etc/cont-init.d/mqtt.sh: line 22: bashio::log.warn: command not found [cont-init.d] mqtt.sh: exited 127. [cont-finish.d] executing container finish scripts... [cont-finish.d] mqtt.sh: executing... [19:13:25] INFO: MQTT cleanup. Error: Connection refused [cont-finish.d] mqtt.sh: exited 1. [cont-finish.d] umount.sh: executing... [19:13:26] INFO: Unmount drivers. umount: /dev: target is busy. [cont-finish.d] umount.sh: exited 32. [cont-finish.d] done. [s6-finish] waiting for services. s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/s6-fdholderd: Read-only file system [s6-finish] sending all processes the TERM signal.

To my knowledge there's no way of knowing the remaining storage on the mounted disk. Would it be possible to add a sensor that could add support for this? This way I can prevent myself from accidentally filling up the storage of my external HDD.

what am I doing unevenly? formatted the flash drive to ext4, put the usb label. but nothing appears either in the logs or on the network (((

Hey, this addon provides the exact functionality im looking for! Im currently using a rpi 4 and an external 2tb hdd (wd) formatted as ext4.

I managed to setup everything and i got the share working on windows, macos and ios (infuse). However, after i copied my files over and forgot about it for a few hours, now i can no longer see any file from any OS. i can see that the drive is 98% full but no files.

Log from the addon:

Failed to fetch record!
pcap cache not loaded
np_open: 'ping.txt' is not a registered pipe!
np_open: 'ping.txt' is not a registered pipe!
np_open: 'ping.txt' is not a registered pipe!
reply_ulogoffX: ulogoff, vuser id 177 does not map to user.
np_open: 'ping.txt' is not a registered pipe!
Failed to fetch record!
pcap cache not loaded
error in mds_init_ctx for: /2TBPi
_mdssvc_open: Couldn't create policy handle for 2TBPi
reply_ulogoffX: ulogoff, vuser id 18629 does not map to user.
Failed to fetch record!
pcap cache not loaded
reply_ulogoffX: ulogoff, vuser id 21952 does not map to user.
np_open: 'ping.txt' is not a registered pipe!
Failed to fetch record!
pcap cache not loaded
reply_ulogoffX: ulogoff, vuser id 35508 does not map to user.
np_open: 'ping.txt' is not a registered pipe!
np_open: 'ping.txt' is not a registered pipe!

Current config (nothing changed since i set it up and worked):

workgroup: WORKGROUP
username: Radu
password: <pass>
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 'fe80::/10'
moredisks:
  - 2TBPi
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: true
autodiscovery: {}
mqtt_enable: false

@dianlight any clue what's going on?
thanks a ton!

Problem/Motivation

Access to files stored on NAS only with SMB 1 possible
With SMB 1 deactivated on NAS console reports “error opening file” … “stale file handle (116)”

Expected behavior
Use cifsversion according to setting in configuration - e.g. cifsversion: ‘3.0’

Actual behavior
Access to files on NAS only with SMB 1 activated on NAS possible.
Looks like Addon is set to SMB 1 permanently.

Steps to reproduce
see above

Proposed changes (If you have a proposed change, workaround or fix, describe the rationale behind it)

My environment:
Add-on version: 2.4.2-dht3
You are running the latest version of this add-on.
System: Home Assistant OS 5.12 (armv7 / raspberrypi3)
Home Assistant Core: 2021.3.4
Home Assistant Supervisor: 2021.03.6
NAS: Firtzbox AVM 7490 latest firmware

I'm getting lost off error's (at least i think they are) in my logfile.

query_name_response: Multiple (2) responses received for a query on subnet 192.168.2.203 for name WORKGROUP<1d>.
This response was from IP 192.168.2.200, reporting an IP address of 192.168.2.200.

IP 192.168.2.203 is hassio
IP 192.168.2.200 is a PC with Ubuntu with als Samba on it

I even think that i makes the plugin stop

Are they error's or can i leave them?

--edit--

sorry i missed a part

daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
query_name_response: Multiple (2) responses received for a query on subnet 192.168.2.203 for name WORKGROUP<1d>.
This response was from IP 192.168.2.200, reporting an IP address of 192.168.2.200.
Failed to fetch record!
pcap cache not loaded
Failed to fetch record!
pcap cache not loaded
Failed to fetch record!
pcap cache not loaded

Hi,

Like the title states, I would love to be able to spin down my NAS hard drive after being idle for a preset time (30 minutes or 1 hour), as I probably access it only a few hours per day.

This would reduce noise and wear on the hard drive.

Thanks for the great add-on and keep up the good work!

[22:18:18] INFO: MQTT cleanup.
Error: -h argument given but no host specified.
Use 'mosquitto_sub --help' to see usage.
[cont-finish.d] mqtt.sh: exited 1.
[cont-finish.d] umount.sh: executing...
[22:18:18] INFO: Unmount drivers.
umount: /dev: target is busy.
[cont-finish.d] umount.sh: exited 32.
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/nmbd: Read-only file system
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

What might be the issue

Unable to mount usb:

Would be awesome to custom choose which folders are exposed on the share. Personally I would like not to share /config. Also, it could be nice to have multiple users with different permissions like in the original samba for linux.

Great work!

Hi @dianlight
First of all, great job.. it's a very handy addon.

I've a improvement request, could you add the ability to allow more than 1 user under the authentication process.
As far I could understand, I'm only able to connect using 1 par of user/pwd.

When starting the Plex Media Server with NAS addon, my log gives the error: "WARNING: Protection mode is ON. Unable to mount external drivers!" despite having protection mode toggled off.

I'm getting the following error dialog after updating the add-on and hitting Start:

Failed to start addon

500 Server Error: Internal Server Error ("error while creating mount source path '/sys/firmware/devicetree/base': mkdir /sys/firmware/devicetree: operation not permitted")

Supervisor log:

20-10-23 17:13:08 INFO (MainThread) [supervisor.addons] Add-on '1a32f091_sambanas' successfully updated
20-10-23 17:13:08 WARNING (SyncWorker_4) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
20-10-23 17:13:08 ERROR (SyncWorker_4) [supervisor.docker] Can't start addon_1a32f091_sambanas: 500 Server Error: Internal Server Error ("error while creating mount source path '/sys/firmware/devicetree/base': mkdir /sys/firmware/devicetree: operation not permitted")
20-10-23 17:13:10 WARNING (SyncWorker_1) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
20-10-23 17:13:10 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_1a32f091_sambanas application
20-10-23 17:13:10 ERROR (SyncWorker_1) [supervisor.docker] Can't start addon_1a32f091_sambanas: 500 Server Error: Internal Server Error ("error while creating mount source path '/sys/firmware/devicetree/base': mkdir /sys/firmware/devicetree: operation not permitted")
20-10-23 17:15:30 INFO (MainThread) [supervisor.snapshots] Found 2 snapshot files

If I restore my snapshot of 9.3.0-nas2 it starts normally, so I think something got broken on the update.
Here's by 9.3.0-nas2 log:

Here's my add-on config:

workgroup: WORKGROUP
username: homeassistant
password: 'my-secret-password'
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 192.168.1.1/16
  - 'fe80::/10'
moredisks:
  - wd-drive
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
autodiscovery: {}

I'm running HassOS.
Supervisor: 249
HassOS 4.15
Home Assistant 0.116.4

Please let me know if you need more info.

I'm trying to run the Samba add-on but it appear to stop shortly after starting, with the error

s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/s6-fdholderd: Read-only file system

I'm running the latest HAOS (Home Assistant OS 5.10) on a Raspberry Pi 3B, and I moved the data partition to an external SSD (following these instructions). I assume this might be related to the issue I'm seeing, as it's mentioned in the link above:

this partition can be moved off of the SD card onto an externally connected drive, leaving the rest of the read-only system on the SD.

Here are the add-on logs:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing... 
[11:32:17] INFO: Protection Mode is false
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing... 
[11:32:19] ERROR: Got unexpected response from the API: Service not enabled
/var/run/s6/etc/cont-init.d/mqtt.sh: line 22: bashio::log.warn: command not found
[cont-init.d] mqtt.sh: exited 127.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing... 
[11:32:21] INFO: MQTT cleanup.
Error: Connection refused
[cont-finish.d] mqtt.sh: exited 1.
[cont-finish.d] umount.sh: executing... 
[11:32:21] INFO: Unmount drivers.
umount: /dev: target is busy.
[cont-finish.d] umount.sh: exited 32.
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: unable to subscribe to events for /var/run/s6/services/s6-fdholderd: Read-only file system
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

and my config:

workgroup: WORKGROUP
username: myuser
password: mypassword
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 'fe80::/10'
moredisks: []
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
autodiscovery: {}

I have mounted an ext4 USB drive using the addon. works perfectly.

Only problem is with the entities that are created in home assistant for the drive.
sambanas Available
sambanas Used
sambanas Use%
sambanas Size

They all stay with a status Unknown.

Here is my setup:
Raspberry Pi 4
Hassos core : core-2021.10.7
Supervisor : 2021.10.8
Addon: 9.5.1-nas3
Drive : 3TB USB drive

workgroup: WORKGROUP
username: *****
password: *****
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - fe80::/10
moredisks:
  - Drive-1
medialibrary:
  enable: false
  ssh_private_key: *****
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
autodiscovery: {}

Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing... 
[12:45:06] INFO: Protection Mode is false
[12:45:06] INFO: MoreDisk option found!
[12:45:06] INFO: MediaLibrary disabled in config. Disk are mounted only for this addon!
[12:45:06] INFO: Available Disk Labels:
 Drive-1
[12:45:07] INFO: More Disks mounting.. Drive-1
[12:45:07] INFO: Mount Drive-1
[12:45:07] INFO: Success!
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing... 
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] samba.sh: executing... 
[12:45:11] INFO: Using hostname=homeassistant interface=eth0
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user pihub.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[12:45:12] INFO: Starting the MQTT daemon for disks info...
[12:45:12] INFO: Starting the AVAHI daemon for homeassistant...
nmbd version 4.13.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.13.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Waiting for daemon ...
INFO: Profiling support unavailable in this build.
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[12:45:13] INFO: Sending MQTT autodiscovery...
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.55
*****

\192.168.0.132\PlexDrive is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

A device attached to the system is not functioning.

username: <Username from Samba Share>
password: <Password from Samba Share>
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 'fe80::/10'
moredisks:
  - PlexDrive
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
autodiscovery: {}

Edit: Every once in a while it's letting me through, which is just extra weird.

Edit 2: Didn't mean to close this. Reopened.

Hello
After update from version 9.5.1-nas2 my drives were not available - currently cured by reinstallung the backup.

I have Plex NAS set up, and when I go to Plex, it says: "You are currently running version 1.21.1.3876 on the server "Home Assistant". Version 1.21.3.4021 is now available. This update will need to be installed manually after download."

What is the easiest way to install updates?

It would be convenient to support adding more than one user in the config, and letting those users access their home directories.

Would you accept a PR that would add support for that?

Hello,

I use Home Assistant OS.

I would like to know if this is the good ssh format for the privatee key (I deleted the BEGIN and END lines):

I used HassOS SSH port 22222 Configurator to set the public key, and then it asked me to reboot and unistall it.

The public key in Configurator and in your sammbanas addon corresponds.

I still get this error when enable is set to true (I know it was false in the first screen):

I want to mount my external WD drive with ext4 filesystem.

Subsystem:
block
Device path:
/dev/sda1
ID:
/dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_QBJP861T-part1
Attributes:
DEVLINKS: >-
  /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_QBJP861T-part1
  /dev/disk/by-id/wwn-0x5000cca2a3e5d990-part1
  /dev/disk/by-partuuid/86ff932c-c63b-8e4f-88d8-8e20cf40168a
  /dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2.2.3:1.0-scsi-0:0:0:0-part1
  /dev/disk/by-uuid/3eda72a0-552e-4ff1-8b67-e0d3563f2750
DEVNAME: /dev/sda1
DEVPATH: >-
  /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2.2/2-2.2.3/2-2.2.3:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
DEVTYPE: partition
ID_ATA: '1'
ID_ATA_DOWNLOAD_MICROCODE: '1'
ID_ATA_FEATURE_SET_APM: '1'
ID_ATA_FEATURE_SET_APM_CURRENT_VALUE: '164'
ID_ATA_FEATURE_SET_APM_ENABLED: '1'
ID_ATA_FEATURE_SET_HPA: '1'
ID_ATA_FEATURE_SET_HPA_ENABLED: '1'
ID_ATA_FEATURE_SET_PM: '1'
ID_ATA_FEATURE_SET_PM_ENABLED: '1'
ID_ATA_FEATURE_SET_PUIS: '1'
ID_ATA_FEATURE_SET_PUIS_ENABLED: '0'
ID_ATA_FEATURE_SET_SECURITY: '1'
ID_ATA_FEATURE_SET_SECURITY_ENABLED: '0'
ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN: '66850'
ID_ATA_FEATURE_SET_SMART: '1'
ID_ATA_FEATURE_SET_SMART_ENABLED: '1'
ID_ATA_ROTATION_RATE_RPM: '5400'
ID_ATA_SATA: '1'
ID_ATA_SATA_SIGNAL_RATE_GEN1: '1'
ID_ATA_SATA_SIGNAL_RATE_GEN2: '1'
ID_ATA_WRITE_CACHE: '1'
ID_ATA_WRITE_CACHE_ENABLED: '1'
ID_BUS: ata
ID_FS_TYPE: ext4
ID_FS_USAGE: filesystem
ID_FS_UUID: 3eda72a0-552e-4ff1-8b67-e0d3563f2750
ID_FS_UUID_ENC: 3eda72a0-552e-4ff1-8b67-e0d3563f2750
ID_FS_VERSION: '1.0'
ID_MODEL: WDC_WD140EFFX-68VBXN0
ID_MODEL_ENC: >-
  WDC\x20WD140EFFX-68VBXN0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
ID_PART_ENTRY_DISK: '8:0'
ID_PART_ENTRY_NUMBER: '1'
ID_PART_ENTRY_OFFSET: '2048'
ID_PART_ENTRY_SCHEME: gpt
ID_PART_ENTRY_SIZE: '27344701407'
ID_PART_ENTRY_TYPE: 0fc63daf-8483-4772-8e79-3d69d8477de4
ID_PART_ENTRY_UUID: 86ff932c-c63b-8e4f-88d8-8e20cf40168a
ID_PART_TABLE_TYPE: gpt
ID_PART_TABLE_UUID: a4da3f4a-7609-11eb-afd7-f40669525f7a
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2.2.3:1.0-scsi-0:0:0:0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_2_2_3_1_0-scsi-0_0_0_0
ID_REVISION: 81.00A81
ID_SERIAL: WDC_WD140EFFX-68VBXN0_QBJP861T
ID_SERIAL_SHORT: QBJP861T
ID_TYPE: disk
ID_WWN: '0x5000cca2a3e5d990'
ID_WWN_WITH_EXTENSION: '0x5000cca2a3e5d990'
MAJOR: '8'
MINOR: '1'
PARTN: '1'
SUBSYSTEM: block
TAGS: ':systemd:'
USEC_INITIALIZED: '11485807066'

What should I do? Can I create a label for this disk from the Home Assistant somehow?

This is what I get:
[cont-init.d] automount.sh: exited 0.
[cont-init.d] mqtt.sh: executing...
[17:20:19] ERROR: Got unexpected response from the API: Service not enabled
[17:20:19] INFO: Sending MQTT autodiscovery...
Error: -h argument given but no host specified.

No explanation on what I should install or change to fix that
The config is almost exactly like the regular Samba add-on

Cheers... i guess i'm too stupid to add your rep :(

Here with the official add-on store:

Here trying while using HACs:

What i'm doing wrong?!

My config never changed and after updating the addon will only mount one drive, often mounting a drive under the wrong name.
According to the logs both mount successfully but only one ever shows and it's always the smaller drive. I am able to mount them both seperately but only one at a time, if I go to mount them both the small one claims the larger drives name and doesn't mount under it's own name.
Example:
Library 4 tb and Internal 1 tb both mounted,
Both will mount successfully then only Library will be available but it will be the Internal disk labelled as 1 tb.

Hi
when want to create a directory or a file in smb share on external HD. I have "access denied smb: " error
I have full access on sd card.
The hardisk is formated in Ntfs.

Ignore this.

When I try to access a folder shared with the Samba NAS add-on...

....I get this error (original file/subject not found):

This is the log from the add-on

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] automount.sh: executing... 
[10:33:30] WARNING: MoreDisk option found!
[10:33:30] INFO: More Disks mounting.. MyPassport500GB
[10:33:30] INFO: Mount MyPassport500GB
[10:33:31] INFO: Success!
[cont-init.d] automount.sh: exited 0.
[cont-init.d] samba.sh: executing... 
[10:33:36] INFO: Hostname: homeassistant
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
Added user homeassistant.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:33:40] INFO: Starting the AVAHI daemon for homeassistant...
nmbd version 4.11.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Server version: avahi 0.7; Host name: homeassistant.local
smbd version 4.11.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
INFO: Profiling support unavailable in this build.
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Established under name 'homeassistant'
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1
*****
*****
Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.3.6
*****
Failed to fetch record!
pcap cache not loaded

When I am trying to import the customer repo into my home assistance it throwing "Repostitory structure for master is not compliant"

it's so good

Hi,

After upgrading to 9.5.1, the mqtt reporting of disksize is missing

I have a "sensor.sambanas_available_datadisk" setup unde 9.3.1, it was working, but after the upgrade it just report 0