I actually got it to work! For others with a Intel NUC and for future me in 10-20 years if I make it that long attached are the Configuration setting that worked on my system and a screenshot of the actual mapped drive. I think the main thing that got it going was deleting the mountoptions* (nosuid, relatime, noexec, X) that came preloaded with the Addon. Thank you Lucio for this great addon!
Great Addon!
After fixing all problems (gpt, label) my disc is recognized perfectly.
I want to use my second disk for frigate addon recordings. But frigate is pointing on /root/media/frigate with lower case. Samba NAS is creating /root/media/FRIGATE with upper case.
Label of file systems is āfrigateā.
Any idea to solve that?
I already tried to set a symbolic link with āln -sā. But I figured out that symbolic links to smb shares are not supported.
Is there any mount option like āeverything in lower caseā?
Hello, what about speed? Are there any config options or future updates to speedup connection to the drive slightly?
I know Samba is not the fastest way of sharing files but still I know that
You can have more speed in Samba share inside OMV.
socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
read raw = yes
write raw = yes
max xmit = 65535
dead time = 15
getwd cache = yes
Can we somehow use it in our addon?
Did you ever get the drive to spin-down correctly? I have a 5TB Seagate that never spins down when connected to my Intel NUC but spins down when I connect it to my Asus router.
Hi, thank you for this great addon 
.
I just started to use it as m my pi3/openmediavault does not boot anymore
It works fine with my two usb ntfs disk on my fanless mini Pc with haos.
Iāhave seen that ntfs is experimental in the starting log.
For me and all the readers information , what are the possible issues please ?
Thank you so much for this addon. I have it working on a 1TB HDD, and I recently purchased a 10TB to replace it, but am struggling to get it loaded into Samba NAS and need some assistance troubleshooting.
I deleted all partitions from the drive, created a single ext4 partition that fills as much of the drive as possible labeled āfrigateā, and I get the below error when loading up Samba NAS. It correctly finds āfrigateā earlier on in the logs, and I can see the USB device under the hardware tab so I know itās being read. None of my Samba NAS configuration settings changed when I swapped over from the old HDD. Iāve also tried partitioning the drive using Gparted and Minitool Partition Wizard with similar results.
Am I supposed to leave a small portion of the HDD unallocated or something?
[07:14:17] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:17] WARNING: Retry 1/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
[07:14:18] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:18] WARNING: Retry 2/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
[07:14:19] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:19] WARNING: Retry 3/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
Here are the logs from Host:
2024-10-12 11:14:11.587 homeassistant kernel: audit: type=1334 audit(1728731651.585:7385): prog-id=1615 op=UNLOAD
2024-10-12 11:14:12.641 homeassistant kernel: EXT4-fs (sdb1): mounted filesystem 30cde37a-1a36-b541-8d56-22e68e076cc0 r/w with ordered data mode. Quota mode: none.
2024-10-12 11:14:17.614 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:17.615 homeassistant mount[2559291]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:17.617 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:17.617 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:17.617 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
2024-10-12 11:14:18.734 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:18.742 homeassistant mount[2559306]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:18.746 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:18.746 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:18.747 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
2024-10-12 11:14:19.863 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:19.868 homeassistant mount[2559321]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:19.870 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:19.870 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:19.871 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
Any help would be greatly appreciated!
EDIT: I spent an entire night trying to figure this out, and 10 minutes after posting this, I learned that I had to physically power cycle the host machine by pressing the power button on my NUC. Frustrating when the fix is that simple, but boy is it satisfying to have this back up and running! Thank you for this contribution to the community!!
My Home Assistant runs on a Raspberry Pi 3 with HAOS. Everything is updated to the last version. I havenāt been able to update Samba NAS from 12.2.0-nas2 to 12.3.2-nas, since I keep getting this error:
Canāt install dianlight/armv7-addon-sambanas:12.3.2-nas: 404 Client Error for http+docker://localhost/v1.47/images/create?tag=12.3.2-nas&fromImage=dianlight%2Farmv7-addon-sambanas&platform=linux%2Farm%2Fv7: Not Found (āmanifest for dianlight/armv7-addon-sambanas:12.3.2-nas not found: manifest unknown: manifest unknownā)
I read on dianlight GitHub that some users had a similar problem with the previous version and solved by stopping NGINX. I tried the same with no results. Any ideas?
Iāve got exactly this on Raspberry Pi 4 too. Anyone know the solution?
It was working but nagging to update. I thought Iād uninstall and install afresh to get around the issue but it still reports the manifest issue so it no longer works at all for me. Doh!
I forgot to update this message! On the project github the owner wrote itās a known issue and it only applies to armv7 architecture, it will be solved by SambaNASās next official update and he jsut suggests to skip this update:
https://github.com/dianlight/hassio-addons/issues/203
Hi big fan of this addon. Iāve been using it for sometime to allow a basic NAS function in my home network.
Iāve recently experimented with the new automatic backup feature in the latest HA release. I select the SambaNAS shared drive in the backup configuration and set this as backup drive. I add the username and password and it works fine. Automatic backups will now run and are stored on the SambaNAS drive.
If I reboot home assistant however the drive is still shared from SambaNAS addon but it is no longer available in the backup options as a storage option. I need to enter my username and password again for it to be used as storage option for automatic backups.
Hope that makes sense. Is there a way to keep the SambaNAS drive available after a HA restart ?
Hi thank you for the nice addon.
Just for my understanding. Is it possible to use several addons to mount the same drive?
I use the rsync local plugin to succesfully mount and use my SSD under /dev/sda1
Now i wanted to use samba nas. Tried with Label name and uuid but it does not find my Drive. Even when rsync local is stopped or is a complete restart necessary?
Also restart could not fix it. Thatās strange because NFTS device was found but it was bugged and only worked sometimes. Now i formatted ext4 and rsync local works without bugs but Samba NAS is completely unable to find the device:
-----------------------------------------------------------
Add-on: Samba NAS
Expose Home Assistant disc with SMB/CIFS
-----------------------------------------------------------
Add-on version: 12.3.2-nas
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2025.1.2
Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-automount: starting
[11:30:20] INFO: Protection Mode is false
[11:30:20] INFO: MoreDisk or Automount option found!
---------------------------------------------------
Supported fs: ext3 ext2 ext4 squashfs vfat msdos f2fs erofs fuseblk ntfs3 exfat btrfs xfs
Supported fusefs: apfs
---------------------------------------------------
[11:30:20] INFO: MediaLibrary disabled in config. Disk are mounted only for this addon!
---------------------------------------------------
[11:30:23] INFO: No Disk with labels.
---------------------------------------------------
[11:30:23] INFO: MoreDisks to mount:
data
/dev/sda1
id:24504j4a6401
24504j4a6401
[11:30:24] WARNING: Disk with label data not found.
[11:30:24] WARNING: Disk with label /dev/sda1 not found.
[11:30:24] WARNING: Disk with id 24504j4a6401 not found.
[11:30:24] WARNING: Disk with label 24504j4a6401 not found.
s6-rc: info: service init-automount successfully started
s6-rc: info: service init-smartd: starting
s6-rc: info: service init-samba: starting
s6-rc: info: service hd-idle: starting
s6-rc: info: service hd-idle successfully started
[11:30:24] INFO: Hostname: homeassistant
[11:30:24] INFO: Interfaces: wlan0 end0
[11:30:24] INFO: Enabling S.M.A.R.T for /dev/sda
[11:30:24] INFO: Docker Interface: hassio 172.30.32.0/23
s6-rc: info: service init-smartd successfully started
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.
---------------------------------------------------
[11:30:25] INFO: Exposed Disks Summary:
[CONFIG] path = /homeassistant # TM:false US:homeassistant #
[ADDONS] path = /addons # TM:false US:homeassistant #
[SSL] path = /ssl # TM:false US:homeassistant #
[SHARE] path = /share # TM:false US:homeassistant #
[BACKUP] path = /backup # TM:false US:homeassistant #
[MEDIA] path = /media # TM:false US:homeassistant #
[ADDON_CONFIGS] path = /addon_configs # TM:false US:homeassistant #
---------------------------------------------------
label is data. checked again under gparted. anything i can try to do?
Interessingly my drive is exposed by MQTT
* SambaNas Physical Disk /dev/sda sambanas device.name /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_device_name_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-device-name/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
0 zuletzt empfangene NachrichtenTransmitted messages:
* SambaNas Physical Disk /dev/sda sambanas device.type /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_device_type_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-device-type/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
0 zuletzt empfangene NachrichtenTransmitted messages:
* SambaNas Physical Disk /dev/sda sambanas device.protocol /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_device_protocol_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-device-protocol/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
0 zuletzt empfangene NachrichtenTransmitted messages:
* SambaNas Physical Disk /dev/sda sambanas power_on_time.hours /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_power_on_time_hours_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-power_on_time-hours/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
0 zuletzt empfangene NachrichtenTransmitted messages:
* SambaNas Physical Disk /dev/sda sambanas power_cycle_count /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_power_cycle_count_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-power_cycle_count/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
0 zuletzt empfangene NachrichtenTransmitted messages:
* SambaNas Physical Disk /dev/sda sambanas temperature.current /dev/sda [USB NVMe Realtek] (`sensor.sambanas_physical_disk_dev_sda_sambanas_temperature_current_dev_sda_usb_nvme_realtek`)
MQTT discovery data:
* Topic: `homeassistant/sensor/sambanas/471001011184711510097-temperature-current/config`
* PayloadSubscribed topics:
* `sambanas/devsda/state`
I have a large SSD disk on the RPI. Is it possible to share a custom local folder ex. /personal thru this addon? I donāt want the folder to be inside the homeassistant default folders. Thanx in advance
Hello
I have this message with my config.
Whatās the problem?
Thanks
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
curl: (7) Failed to connect to supervisor port 80 after 0 ms: Could not connect to server
[14:33:17] ERROR: Something went wrong contacting the API
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
curl: (7) Failed to connect to supervisor port 80 after 0 ms: Could not connect to server
[14:33:17] ERROR: Something went wrong contacting the API
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-automount: starting
curl: (7) Failed to connect to supervisor port 80 after 0 ms: Could not connect to server
[14:33:18] ERROR: Something went wrong contacting the API
[14:33:18] WARNING: Your operating system is not supported!
Ā±-----------------------------------------------------------------+
| THIS ADDON IS DESIGNED FOR HOME ASSISTANT OPERATING SYSTEM ONLY! |
| THIS ADDON IS DESIGNED FOR HOME ASSISTANT OPERATING SYSTEM ONLY! |
| THIS ADDON IS DESIGNED FOR HOME ASSISTANT OPERATING SYSTEM ONLY! |
| THIS ADDON IS DESIGNED FOR HOME ASSISTANT OPERATING SYSTEM ONLY! |
| THIS ADDON IS DESIGNED FOR HOME ASSISTANT OPERATING SYSTEM ONLY! |
Ā±-----------------------------------------------------------------+
[14:33:18] FATAL: You can force this addon to run only if you known the meaning of life!
!!
1 Like
How do you Run Home assistant? Home assistant OS or Something else? Should be Home assistant OS to use this addon i guess
Hi there! Iām trying to use Twingate for connecting remotely using Samba NAS. I canāt find which port is being exposeā¦ trying with 445 but no luck. I trying using ps on the pi console but no luck and neither by inspecting the docker ps. Also read the documentation but found nothing there.
@Lucio_Tarantino I installed the script. Formatted an usb stick on ex4. It is recognised. But how do I point the other addons to the stick?
I want for example the Qbittorrent addon be able to write files to the stick, then EMBY to read from it (movies etc).
It does not see the usb stick in the mount directory when I point to it in Emby or qBittorrent.
Depends on addon but generally you need to enable the medialibrary feature o manually mount the share on ha as media and then you see the mounted disk inside the /media path in every addon.
Good morning everyone,
I use Samba Nas and it works great.
Several times a day in Supervisor an attention notification appears that I canāt find the cause of.
Can anyone give me some advice?
Thanks
1 Like
I have a question on how to mount, I have an ext4 drive called Files. I can only see it if I disable Protection Mode, Iām not sure yhow to make it visible with protection mode enabled.
Under more disks, I put the name of the drive Files and restart but it doesnāt show up
Thanks for your help
Hi I need some help, I got a usb SABRENT USB 3.0 to SATA External Hard Drive Lay-Flat Docking Station, formatted my 18tb drive to ext4. I put some media on there, and everything works fine for a few hours, but then I just canāt connect to the drive anymore using windows or my apple tv.
Looks like the logs dont say much either a bunch of hello and resolve and a bye messages.