Mount remote smb share on hassio

[dmnmes163 (DM)]

How do I find out what the HA system-user is? I tried creating a user called homeassistant on the Synology and gave it explicit permissions to everything, and using those credentials still results in a return code 111.

[boheme61]

HA’s os is root, HA uses root + you “your-user/login name”, samba is samba-user … what user did you use to mount-on hassio ?

[dmnmes163 (DM)]

Sorry if this is a really basic question, but does that depend on how I connected to run it? I used putty to connect to the ssh that I configured in the Terminal & SSH Add-on.

[boheme61]

I guess you then logged into Ha, with your HA username, so you should have the right “credentials” then “Administrator” in HA, root in terminal/SSH … easiest way is to login through ssh again and type “whoami”

@dmnmes163

I have the PASSWORD in ''s as it contains a ) and I ran into an error due to that. I’m not sure if putting the password in ''s is the solution for that?

…and this sounds like “greek” to me and “escape special characters” ? … don’t use them if it’s not supported

[boheme61]

PS: Have you read/tried any of the examples above ?, on howto Mount … or maybe some other “half” official guide

[dmnmes163 (DM)]

Ah, TIL, thank you. I know whoami works in a windows command line, didn’t even think to try that.

@boheme61

…and this sounds like “greek” to me and “escape special characters” ? … don’t use them if it’s not supported

I think I butchered that. I meant that putting them in ''s would indicate it’s a string, like in SQL. I just tried to replicate and I’m not seeing the error I did before, so there must have been something else going on. At any rate, removing the ''s has the same effect. Shouldn’t one of them return an error for a bad password? I did enable debug but the only mention of homeassistant.components.shell_command in the log is it with a bunch of other components.

[dmnmes163 (DM)]

@boheme61

PS: Have you read/tried any of the examples above ?, on howto Mount … or maybe some other “half” official guide

This is the first method I have tried. Honestly I wasn’t sure which of the other methods applied to me, and figured I should ask for advice on what to try. If you know of a guide that I could take a look at that would be awesome. I’ll also keep looking.

[boheme61]

is it a windows “partitioned(ntfs)” disk you try to share ? … if so , i wouldn’t even try to do that, but feel free to read “backwards” from here, post by post, and even try “other” search terms along your “learning-steps”, might be other Topics , with a solution for you …, beside reading post/topics gets you additional knowledge about your own system Linux/window/samba/network etc

[dmnmes163 (DM)]

@boheme61

is it a windows “partitioned(ntfs)” disk you try to share ?

I don’t believe so. To my understanding the Synology DSM is a heavily modified Debian distro. Does that mean that I should be using a different method to mount the drive? Sorry, I haven’t had a lot of exposure to linux so am trying to learn about that in addition to how to get HA to do what I want.

Thank you for the advise. I did find another thread along these lines but it talked a lot about portainer which apparently is discontinued. I will keep digging through it to see if I can glean anything.

[dmnmes163 (DM)]

I just looked in the Storage manager for the Synology and it looks like it’s a btrfs. I suppose that’s going to be a completely different method.

[boheme61]

dont use username or password with “space” or other special characters, unless you are sure that all device, OS, Software that should communicate with eachother supports this,

[boheme61]

@dmnmes163

Shouldn’t one of them return an error for a bad password?

i suppose so, but it’s the mount that seems wrong , i don’t know anything about synology

But you get a " Connection refused", so either you don’t have right user/passwd, or not enabled samba on your nas, or wrong path
… thats why i asked about the “disk” … user “guest” ?, i would never have used this, but same user as either HA or samba, and in regards to the path, i obviously can’t say anything as i dont know your system … but i try to be “generic”, so if a mount a disk in linux, i use same file-system/cluster size on the disk,i even have an extra disk for files, configs/backups etc, same file system … why complicate things or “create” additional" fault points ?, various techs is complicated enough … and don’t forget to make sure you use supported nfs version

PS: and don’t for get to change this … Don’t use “special characters” you don’t even know if supported

@boheme61

“escape special characters” ? … don’t use them if it’s not supported

[dmnmes163 (DM)]

So I tried to take the Synology out of the picture and just share a folder on my win10 laptop, changed security to give “Everyone” access, and I’m still getting permission denied errors, when trying both nfs and cifs. I did temporarily turn off Windows firewall so I don’t think it’s a port issue, unless my router is doing something weird. I think I’m going to walk away from this one and maybe come back fresh another day. Thanks for your help @boheme61

[boheme61]

Which integration/ADD-Onn are you using ? and how does your settings look like there ?

[boheme61]

@dmnmes163

Here is what I have listed in my configuration.yaml:

homeassistant:
  media_dirs:
    media: /media
    synologynas: /media/syno

Are you sure you have followed the “Installation” guide for your Samba ? as i don’t use configuration.yaml but th ADD-Onn to configure the Samba, above looks pretty “simple” as there is no “allow_hosts:” etc. , and as i mention before " Don’t use username/password with space or other “special” characters

[carsten_h (Carsten Friehe)]

@boheme61

as i don’t use configuration.yaml but th ADD-Onn to configure the Samba

I think you are in the wrong thread.
This thread is about mounting an external samba share from a samba server not about using Home Assistant as a samba server!

[boheme61]

ok, yes it seems so when going through all posts from scratch, didn’t even know that HA was able to “talk” samba, without an Add-On or Integration … but maybe that’s not needed, when trying to authenticate to the external samba-server

[boheme61]

So at-least i can try to give a “Final” hint, if it’s helpful …

@insajd

yes,

1. go to http://homeassistant.local:8123/hassio/store (Add-on Store)
2. Install Portainer (after install, disable Protection mode checkbox)
3. Portainer → Settings → Hidden containers. Delete the listed hidden labels
4. Open Containers section, open homeassistant container, click Console
5. Connect as root (that’s the default).
6. Check that folder was created

cd /mnt
ls -la
#here configrm that media2 is here

7. Execute

mount -t cifs -o username=anonymous,domain=WORKGROUP //192.168.1.121/Movies /mnt/media2

8. If no errors, go into (cd /mnt/media2) folder and check that the files are there (ls -la)

• Probably issue would be with username/domain combo. anonymous/WORKGROUP is what I use
• It might be that SMB is configured to allow only 192.168.1.* IP addresses, this docker container has internal IP that is looking something like 172.30.32.2 - that’s also possible culprit

@tachikoma1373

Getting somewhere but its now 1:30am and I have work tomorrow Will update later today - thank you so much.

EDIT:

so I got it working with the following config.

homeassistant:
  media_dirs:
    music: /mnt/media2

shell_command:
  mount_music_folder: mkdir -p /mnt/media2;mount -t cifs -o vers=1.0,noserverino,username=<username>,domain=WORKGROUP //192.168.1.121/music /mnt/media2

You were right about the spacing - my bad. My WDis old, a version 1 hardware/firmware and the key point seems to be specifying the “vers=1.0,noserverino,”. Using the same principles I was able to mount other shares as well.

Thanks again for the assistance and the education.

From: below, thou seems like various solution for Supervised vs HassOS

Point media_dirs: at NAS share?

Thanks a lot. I’m having some issues getting this working. I’m running on a proxmox box and here’s the system info: |arch|x86_64| |---|---| |chassis|vm| |dev|false| |docker|true| |docker_version|19.03.11| |hassio|true| |host_os|HassOS 4.13| |installation_type|Home Assistant OS| |os_name|Linux| |os_version|5.4.63| |python_version|3.8.5| |supervisor|245| |timezone|Europe/London| |version|0.115.2| |virtualenv|false| So there is already a “media” directory in place as part of the install. I’m tr…

[boheme61]

… And some more from Reddit:

level 2

eruisi

Op · 4 mo. ago

I tried to config NFS in QNAP NFS and mount from regular linux host, but got connection refused:

mount -t nfs 192.168.1.200:/Download /mnt/download
mount: mounting 192.168.1.200:/Download on /mnt/download failed: Connection refused

2

Continue this thread

level 1

DopeBoogie

· 4 mo. ago

Impossible? Not exactly.

Difficult/next-to-impossible? Yeah pretty much.

You have the right general idea, though I believe only NFS is possible and it’s extremely picky about versions/configuration.

You will also need to run these commands from outside of the home assistant container though, which means that it can’t be done through the HA terminal or ssh add-on. You’ll need to use the debug-mode ssh to access the host system in order to run the mount commands.

This involves using a USB flash drive to import an ssh key (password is not an option, you’ll have to use keys) and once successful you can ssh into :2222 to access the host system.

[jacktux]

OK, so managed to get into Debug (on 22222) but I dont have the cifs.utils installed. What package manager is being used, or how can I install the cifs and nfs utils for mount?