Add Network Storage Fails for samba share

Configuration
1

Hi,
I have my HA running on machine 1 (Debian) and Frigate running on another machine 2 (Debian). As Frigate stores all recordings on the local disk of machine 2 , I want to add that to the media storage in HA.
I am running Samba share as a docker container on machine 2 to expose the frigate folder. I am able to browse that share very well from machine 1 via the smbclient but when I try to configure it via “Add Network Storage” in HA , it fails with an error Excess arguments. . Can someone tell me what’s wrong here?

$  systemd unit usr-share-hassio-mounts-frigate.mount
Excess arguments.

The settings on the add storage network screen are as in the screenshot.

IMG 2058
IMG 2058631×877 85.6 KB

image
image615×879 32.9 KB

Successful connection to the share from the HA machine via smbclient:

~$ smbclient //192.168.1.104/frigate -U ha_samba
Enter WORKGROUP\ha_samba's password:
Try "help" to get a list of possible commands.
smb: \> ls
  .                                   D        0  Sun Oct 15 16:07:50 2023
  ..                                  D        0  Wed Oct 18 10:02:25 2023
  frigate.db-shm                      N    32768  Tue Oct 17 21:21:04 2023
  recordings                          D        0  Tue Oct 17 06:16:53 2023
  clips                               D        0  Tue Oct 17 21:15:51 2023
  frigate.db-wal                      N  4165352  Tue Oct 17 21:21:04 2023
  frigate.db                          N  1093632  Tue Oct 17 12:12:39 2023
2

change your smbversion to 2.0 it should work.

3

Oh I tried that, it still results in the same error.

4

did you enable compatibility_mode on the plugin ?
and how old is your storage device ?

5

Can you pl elaborate where is the compatibility_mode , and on which plugin?
My storage device is a inbuilt SSD hard disk - local on a laptop.

6

you said u exposed the frigate folder with your samba plugin,
so if u go there u see this, enable it and restart, and play with the smbversion, it should work :slight_smile:

image
image1143×706 25.4 KB

7

oh , but that’s on the samba add on. I dont think that has to do anything with the samba share which is on the other machine (Machine 2 running Frigate). I anyway enabled the compatibility mode and I still get the same error.
But then these two arent related , isnt it? One is samba add on on HA , the media share is on another machine which runs samba as a docker container.

8

aaaah i thought you was using the samba plug-in.

hehe my bad, well if u using the samba share installed on some machine there need to be more configurations available like that mode, to let it be compatible with older versions.
but it needs to be enabled first.

i did found this:

9

ok, will read through it, but then I am running the latest version of samba on the docker container, I am not sure why should there be any compatibility issues between HA and samba. Although I don’t know which protocol does the container dperson/samba work with.

10

found your problem, i checked the github from that link u posted.

image
image905×147 7.7 KB

try than and it should be ok, be sure to use smb2

11

ah that seems promising, I have to now figure out how to pass on this command in the docker compose file … let me do some digging.

12

Although I am still intrigued by the error message I get irrespective of the protocol i use ,“excess arguments” which somehow points to the fact that HA is not able to pass the right arguments to connect to the server.

13

nope, this doesnt seems to be an issue, I verified the smb.conf within my container and it is already set to the right values:

   client max protocol = SMB3
   client min protocol = SMB2_10
   server max protocol = SMB3
   server min protocol = SMB2_10
14

yes i know, for me it fixed changing the protocol.

but i have a nas that’s different.
i really don’t know what could be the problem…

15

sure, thanks for looking into it, I hope someone else is able to shed more light on what could be an issue.

16

no problem, but what u can do is use an other share and try again, or try it with a nas or something. just to rule out its not a problem with samba.

regards

17

I dont have anything else to try with. Have opened a bug in HA OS , lets see if someone is able to confirm this being an issue. #2840

18

no worries, i hope it gets solved soon.
regards