Hey, new here. My HASS install broke down, and I installed it again. There is no problem until this point. After I configured Samba and went to access the files, Windows can’t find the address that I asked it to search. Any possible ideas that can fix this or suggestion for another file server add-on because this keeps on not connecting EVERY SINGLE TIME. After some time, for whatever reason, it kills itself and restarts. Any idea why this happens?
Whare are your logs?
Furtermore:
- What kind of HA install?
- What kind of Samba install?
- What address are you using from Windows?
Fresh HASSIO install to RPi
Addon of Samba
I use this for an address: \ip.address.of.hass\ and use it on Windows Explorer
These are the 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] samba.sh: executing…
[15:09:54] INFO: Using hostname=homeassistant interface=eth0
addgroup: illegal character with code 32 at position 5
[cont-init.d] samba.sh: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
And this is my config (changed username and password for security and privacy reasons)
workgroup: WORKGROUP
username: user
password: XXXXXXXXXXXXXX
allow_hosts:
- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16
- fe80::/10
veto_files: - ._*
- .DS_Store
- Thumbs.db
compatibility_mode: false
guest: false
interface: eth0
No clue what the root issue is, but probably explains why samba is unreachable.
EDIT: looks like the addon doesn’t like your username, which, I guess, has some special character in it (a blank?).
addons/samba.sh at master · home-assistant/addons (github.com)
1 Like
two backslashes at the start!
\\ip.address.of.hass\
I also wrote 2 backslashes, but my keyboard hates me 
It has a special character, but even without a special character, it won’t connect
Please show the logs after you removed the special character from you username (I assume you restarted the addon after the change, here).
Now it won’t auto-restart, meaning half the issue solved, but there is the Windows can’t access hassio error. It will show up on Network under File Explorer, but it won’t connect.
[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] samba.sh: executing…
[11:54:06] INFO: Using hostname=homeassistant interface=eth0
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user hassio.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.13.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Registered MSG_REQ_POOL_USAGE
added interface eth0 ip=192.168.1.245 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.245 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
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
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section “[config]”
Processing section “[addons]”
Processing section “[ssl]”
Processing section “[share]”
Processing section “[backup]”
Processing section “[media]”
added interface eth0 ip=192.168.1.245 bcast=192.168.1.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
Registered MSG_REQ_POOL_USAGE
No builtin backend found, trying to load plugin
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
daemon_ready: daemon ‘smbd’ finished starting up and ready to serve connections
waiting for connections
Checking logs again, it gives panics and fatal errors when I try to connect to it again. Logs are as follows:
===============================================================
PANIC (pid 322): Signal 11: Segmentation fault in 4.13.8
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
Registered MSG_REQ_POOL_USAGE
check_ntlm_password: Authentication for user XXXXXXXXXX → XXXXXXXXXX FAILED with error NT_STATUS_NO_SUCH_USER, authoritative=1
Should I change my username and password to be the same as under my account? Or should I try to connect to it from another computer (I have that possibility)
I have the same problem:
Registered MSG_REQ_POOL_USAGE
check_ntlm_password: Authentication for user [XXXXXXXXXXXXXXXXXX] -> [XXXXXXXXXXXXXXXXXX] FAILED with error NT_STATUS_NO_SUCH_USER, authoritative=1
===============================================================
INTERNAL ERROR: Signal 11: Segmentation fault in pid 290 (4.13.8)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 290): Signal 11: Segmentation fault in 4.13.8
unable to produce a stack trace on this platform
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
I do not know why this error occurs now. Before this did not happen. A connection is also not possible!
Have you already fixed the problem?
Same problem, when I try to access:
INTERNAL ERROR: Signal 11: Segmentation fault in pid 290
… followed by PANIC.
It was working as recently as a week ago. Have tried reinstalling, restarting, accessing from other systems, accessing via IP, and a few other things. No luck.
@justin03 @jimh12345 Did you guys notice the error that leads up to this error? Specifically:
I.e. wrong username.
Found an answer that worked for me. I think this is the bug and the fix:
The problem is that Windows now starts by offering a Microsoft Accout user name (email address) and the samba server can’t parse it and crashes. The workaround is to create a Windows Credential for accessing the share with a proper user name; it gets looked at first.
4 Likes