What do the logs say? You can see the logs specific to the Samba share hass.io addon at the bottom of the Samba plugin page. You can also try resetting the add-on settings back to default.
Oh, I was able to get it to start now (?! - just added an interface and it restarted). But still can’t connect. This is the log:
Log
[INFO] Read hostname: null
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
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.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
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.
nmbd version 4.8.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2018
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface wlan0 ip=fdcc:23e:c5bd:1:c38b:a755:45b4:4b87 bcast= netmask=ffff:ffff:ffff:ffff::
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface wlan0 ip=192.168.0.48 bcast=192.168.0.255 netmask=255.255.255.0
making subnet name:192.168.0.48 Broadcast address:192.168.0.255 Subnet mask:255.255.255.0
making subnet name:172.30.32.1 Broadcast address:172.30.33.255 Subnet mask:255.255.254.0
making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.0
create_subnets: ignoring non IPv4 interface.
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
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.8.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2018
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]"
added interface wlan0 ip=fdcc:23e:c5bd:1:c38b:a755:45b4:4b87 bcast= netmask=ffff:ffff:ffff:ffff::
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface wlan0 ip=192.168.0.48 bcast=192.168.0.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.17.0.1
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.30.32.1
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 192.168.0.48
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.0.48
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.0.48
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.0.48
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.0.48
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.17.0.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.30.32.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.0.48
run_elections: >>> Won election for workgroup WORKGROUP on subnet 192.168.0.48 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 192.168.0.48
Man, this is driving me crazy. Can’t for the life of me work it out, and my automations won’t run until I can update them.
Edit: Hallelujah it’s working now… Not sure why. Basically reset everything (again), added the IP of my laptop as a host, and tried using cifs://hassio.local rather than smb://hassio
I’m glad you figured it out. Samba is pretty unreliable in general, though the add-on works for me. Sometimes I’ve had to use the IP address than \hassio to access the shares.
When I had problems with not being able to access the Samba shares but the cifs:// tip worked (at times), the problem turned out to be that I had filled up the disk and in the process corrupted some of the Samba internal databases.
This will of course not be the cause of everybody’s Samba problems, but may be worth checking.
Clearing disk space and getting databases regenerated by changing the username in the Hassio configuration unbroke things.
(I think that’s all I did - it happened a few months ago, but I just found this thread again.)
With me the same problem occured when i changed my host (ubuntu server) its hostname from “hahost” to “HuisOmgeving” here the screenshot of the problem