I really don’t understand your case. Please explain. If you need to write to a NAS from a PC do it directly why use HA?
I am trying to write files from my PC to sambaNAS running on HA. But I can ´t do it because windows shows “disk is protected against writing”. Sorry I am not good in explaining.
I’ve just found out about Samba NAS and have installed the add-on. Prior to this, I have been using Samba Share. Since the NAS still able to access the regular folders as the Share does, I am sticking with this version instead.
Now, I wish to access a remote media drive that is still within the same network as HA, but is not connected physically to HA. How do I input the line in samba NAS config file? From Windows, I am able to access it via \192.168.1.25\www\MUSIC. I want to share this folder within HA.
You can’t. There is an open architectural discussion about mount network share on HA (RFC: Mount Manager · Issue #2564 · home-assistant/supervisor · GitHub). This addon allow to mount disk that are physically attached to ha ( usb/sata etc ). The only remote possible with this addon ( but never tested! ) are the iscsi and USBoE protocols but you need a customized hassos image so is more simple to customize the image to have samba client on host level and mount disk via fstab.
My SambaNAS can’t connect to SSH, I got this message in log:
ssh: connect to host my HA ip port 22222: Connection refused
What could be wrong?
Have you set the SSH host connection? From your PC/MAC you can connect to HA Host on port 22222?
ok. I have installed a new sata3 drive into a mini pc before formatting. Under all hardware, HA sees the drive. Is it possible to format the drive within HA without physically removing the drive to format??
If you are on hassos you can try on host if there are fsutil ( fdisk, mkfs etc etc). I think the best way is to boot with gparded live or other live Linux from usb, make partitions and format ( also set a label on partition is useful ).
L.
I’ve just updated to 10.0.0 and addon unable to start. Getting this error.
Update: I figured it out. The below needs to be set to false if you have nothing to mount. I have no drive to mount atm.
automount: false
–
Log:
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
-----------------------------------------------------------
Add-on: Samba NAS
Expose Home Assistant disc with SMB/CIFS
-----------------------------------------------------------
Add-on version: 10.0.0-nas5
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / generic-x86-64)
Home Assistant Core: 2023.2.0
Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
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
[05:37:24] INFO: Protection Mode is false
[05:37:24] INFO: MoreDisk or Automount option found!
modprobe: module ntfs3 not found in modules.dep
s6-rc: warning: unable to start service init-automount: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
supervisor log:
23-02-02 05:29:07 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Samba NAS
23-02-02 05:29:10 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Samba NAS
23-02-02 05:29:11 INFO (MainThread) [supervisor.store] Loading add-ons from store: 150 all - 0 new - 0 remove
23-02-02 05:29:11 INFO (MainThread) [supervisor.store] Loading add-ons from store: 150 all - 0 new - 0 remove
23-02-02 05:30:21 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
23-02-02 05:30:21 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2023.2.0
23-02-02 05:30:21 INFO (SyncWorker_2) [supervisor.docker.interface] Cleanup images: ['ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.1.7']
23-02-02 05:30:45 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:30:46 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
23-02-02 05:32:36 WARNING (SyncWorker_2) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
23-02-02 05:32:36 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_1a32f091_sambanas application
23-02-02 05:32:37 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on dianlight/amd64-addon-sambanas with version 10.0.0-nas5
23-02-02 05:32:57 ERROR (SyncWorker_0) [supervisor.docker.interface] Container addon_1a32f091_sambanas is not running
23-02-02 05:34:00 WARNING (SyncWorker_1) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
23-02-02 05:34:00 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_1a32f091_sambanas application
23-02-02 05:34:01 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on dianlight/amd64-addon-sambanas with version 10.0.0-nas5
23-02-02 05:34:33 ERROR (SyncWorker_5) [supervisor.docker.interface] Container addon_1a32f091_sambanas is not running
23-02-02 05:35:24 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:35:24 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
23-02-02 05:37:22 WARNING (SyncWorker_0) [supervisor.docker.addon] Samba NAS running with disabled protected mode!
23-02-02 05:37:22 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_1a32f091_sambanas application
23-02-02 05:37:23 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on dianlight/amd64-addon-sambanas with version 10.0.0-nas5
23-02-02 05:40:09 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:40:10 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
23-02-02 05:41:03 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-02-02 05:45:18 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:45:18 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
23-02-02 05:50:49 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:50:49 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
23-02-02 05:55:38 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqttuser'
23-02-02 05:55:38 INFO (MainThread) [supervisor.auth] Successful login for 'mqttuser'
Is it very demanding for the Raspberry Pi 4 (4GB) to use this addon? I only want it to do two things:
- Act as a backup solution for Time Machine to backup my Mac Mini.
- Share files so I can serve them to Infuse on Apple TV 4K. No transcoding.
Many people recommend a NAS from Synology but the Synology hardware for their 2 bay NAS seems worse than RPi4 and the NAS costs $210 for me.
Would the RPi4 be enough for the two things above?
Thanks!
I started with a rpi3. Than rpi4. Although rpi4 is great, but if you are going to tinker with Ha for long term and start installing more devices down the road, it will eventually choke. I recently purchased a mini pc, Beelink U59 Pro. Now I can install what I want and even have the history db running along side whereas before it would be on a separate device. No more worry about the sd card going bad if you are still using sd card for your rpi4. Much, much faster when I reboot ha now.
So are you saying that using RPi4 for simple serving of files and occasional Time Machine backup is a bad idea because it’s very taxing on the hardware?
I already have Home Assistant on an SSD and have been using it for a long time for my large house with many, many devices without issues or the slightest feeling that I would need better hardware.
No. It should be fine. What I was getting at is when you start adding on more devices later on, you will feel a lag on your rpi4.
Now I’m getting this error:
Warning: Permanently added ‘[“my ip”]:22222’ (ED25519) to the list of known hosts.
Load key “/root/.ssh/id_rsa”: error in libcrypto
root@“my ip”: Permission denied (publickey).
In the ssh_private_key part I need to paste all of the text of the id_rsa?
Yes all the content of your private key file (also header and footer).
But now I suggest you to regenerate your key because exposing your private key on a public post is very dangerous for your ha security.
L.
2 Likes
RPi4 is enough. I created the addon to replace my old NAS that was my tm target and my media disk for plex. In my config I have an rpi4-8gb with a 128gb ssd (from an old 2010 mbp ) for hassos, a RAID1 2tb hd connected with usb3 for tm, and a hub with 3 old hdd ( 1tb + 2tb x2) for plex.
Now is the tm target for 2 mbp and the bk target for a w11 pc. All with hourly policy without problem.
Obviously the ha is my controller for home with many integration and automations, the bridge/border for Zigbee, mysensor etc.
The rpi4 is enough but remember to use a right thermal control for cpu temperature.
L.
Thank you for that reply!
It seems to me that the RPi4 with 4GB is both a cheaper and a much more powerful device than Synology’s DS220j ($220 for me) and even DS418 ($465).
Synology looks much better than having 2-4 external drives on an RPi4 but I wouldn’t want either to be visible anyway.
I generated a new one right after that, but thank you for the tip.
Should I create the ssh key in the computer hosting home assistant or any computer?
– Edit 2
Finally!
But now I’m having trouble to connect to the samba from other computers.
I’ve tried using the \\ip-adress\ is there any other thing to configure?
Is there any recommendation for which file system I should format disks to?
I will have one drive used exclusively for Time Machine backups. All other drives will only have video files to serve to Infuse (no transcoding).
Check the workgroup and allow_hosts.
Also the user and password. You should be able to see ha in your network browser on the client machine.
L