Lost Samba Share (Hassio) after upgrade to Samba v8.1 Windows 10

JSCSJSCS · June 25, 2019, 4:31pm

Decided to upgrade Samba to V8.1 from Windows 10 v1903 from Samba v4. Looks like a lot has changed. I set this up so long ago that I don’t remember what things mean anymore. I got an error in the Samba configuration that I could not figure out so i set it to defaults… On save, I got another error. The defaults don’t have quotes around null in the password setting I discovered. I should think the defaults should not give an error.

I could not remember what username and password are supposed to be set to? Hass.io web page credentials? I tired those. No errors in the Config area of Samba, but no share available either. By the way, my home network uses workgroup name “JSCS”, so that is why it is showing.

Any help appreciated.

Current Config:

{
  "workgroup": "JSCS",
  "username": "hass.io login admin username?",
  "password": "hass.io login password?",
  "interface": "wlan0",
  "allow_hosts": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/16"
  ]
}

Here is the Samba log:
[INFO] Read hostname: hassio
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




Here is the supervisor log:
19-06-25 16:06:10 INFO (MainThread) [__main__] Initialize Hass.io setup
19-06-25 16:06:10 INFO (MainThread) [__main__] Setup HassIO
19-06-25 16:06:10 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armhf-hassio-supervisor with version 166
19-06-25 16:06:10 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /
19-06-25 16:06:11 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n'
19-06-25 16:06:11 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc
19-06-25 16:06:11 INFO (MainThread) [hassio.host.info] Update local host information
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-06-25 16:06:11 INFO (MainThread) [hassio.host.services] Update service information
19-06-25 16:06:11 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-06-25 16:06:12 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
19-06-25 16:06:12 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
19-06-25 16:06:12 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/raspberrypi3-homeassistant with version 0.79.3
19-06-25 16:06:13 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-06-25 16:06:13 INFO (MainThread) [hassio.store] Load add-ons from store: 19 all - 19 new - 0 remove
19-06-25 16:06:13 INFO (MainThread) [hassio.addons] Found 4 installed add-ons
19-06-25 16:06:13 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/armv7-addon-samba with version 8.1
19-06-25 16:06:13 INFO (SyncWorker_5) [hassio.docker.interface] Attach to homeassistant/armhf-addon-duckdns with version 1.0
19-06-25 16:06:13 INFO (SyncWorker_0) [hassio.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 5.6
19-06-25 16:06:13 INFO (SyncWorker_4) [hassio.docker.interface] Attach to homeassistant/armhf-addon-mosquitto with version 4
19-06-25 16:06:13 INFO (MainThread) [hassio.updater] Fetch update data from https://s3.amazonaws.com/hassio-version/stable.json
19-06-25 16:06:14 INFO (MainThread) [hassio.snapshots] Found 16 snapshot files
19-06-25 16:06:14 INFO (MainThread) [hassio.discovery] Load 1 messages
19-06-25 16:06:14 INFO (MainThread) [hassio.ingress] Load 0 ingress session
19-06-25 16:06:14 INFO (MainThread) [__main__] Run Hass.io
19-06-25 16:06:14 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons
19-06-25 16:06:14 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
19-06-25 16:06:14 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
19-06-25 16:06:14 INFO (MainThread) [hassio.addons] Phase 'system' start 1 add-ons
19-06-25 16:06:14 WARNING (MainThread) [hassio.addons.validate] Unknown options plain
19-06-25 16:06:14 WARNING (MainThread) [hassio.addons.validate] Unknown options ssl
19-06-25 16:06:28 INFO (SyncWorker_3) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-mosquitto with version 4
19-06-25 16:06:29 INFO (MainThread) [hassio.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
19-06-25 16:06:29 INFO (MainThread) [hassio.discovery] Duplicate discovery message from core_mosquitto
19-06-25 16:06:33 INFO (MainThread) [hassio.addons] Phase 'services' start 3 add-ons
19-06-25 16:06:54 INFO (SyncWorker_17) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-duckdns with version 1.0
19-06-25 16:06:58 INFO (SyncWorker_8) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 8.1
19-06-25 16:06:59 INFO (SyncWorker_11) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-ssh with version 5.6
19-06-25 16:07:04 INFO (SyncWorker_18) [hassio.docker.interface] Start homeassistant/raspberrypi3-homeassistant
19-06-25 16:07:58 INFO (MainThread) [hassio.api.security] /homeassistant/restart access from core_ssh
19-06-25 16:07:58 ERROR (MainThread) [hassio.utils] Can't execute restart while a task is in progress
19-06-25 16:08:23 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-06-25 16:08:23 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
19-06-25 16:08:23 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-06-25 16:08:23 INFO (MainThread) [hassio.core] Hass.io is up and running
19-06-25 16:08:24 INFO (MainThread) [hassio.api.security] /homeassistant/restart access from core_ssh
19-06-25 16:08:24 INFO (SyncWorker_8) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant
19-06-25 16:10:14 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance

petro · June 25, 2019, 4:37pm

It’s null because it forces users to put in a password.

It’s whatever you want it to be. They are the username and password for things (like a windows desktop) connecting to your home assistant. Not the other way around. So you could set it equal to your Windows username and password.

Because you have to browse to the Hostname and enter your credentials.

JSCSJSCS · June 25, 2019, 4:53pm

Thanks for responding. I’m slow. Previously, the Hassio samba share just showed up in the network explorer. I clicked on it and got to things like my configuration.yaml file.

Now it does not show up and I don’t know how to get to it anymore.

You say I have to browse to the hostname and enter my credentials. I’m not use how to do that.

petro · June 25, 2019, 4:56pm

Yes, browse to it like any other network drive inside a window

//hostname

After pressing enter, credentials will appear

JSCSJSCS · June 25, 2019, 5:04pm

I enter //HASSIO into the explorer and nothing happens, then after s short time, a browser window opens to http://hassio/ and gives an error.

How does one determine the hostname for hassio installation? I used to see HASSIO in my explorer. Of course it is no longer there.

JSCSJSCS · June 25, 2019, 5:23pm

Progress: I used \HASSIO instead of //HASSIO and got a credentials login screen. Then I was able to accesss the samba share.

Do you know how I get it to just show up in the explorer withouot me having to remember what the share name is? Just like it used to do.

petro · June 25, 2019, 7:17pm

Sorry, I’m not a networking guru. This has to do with your windows setup, not samba. I have the same issue but i’ve never bothered looking into it. The reason it worked ‘seemlessly’ before is because the component used the guest network as a loophole to get around security. That loophole was fixed.

msaponaro · July 2, 2020, 6:29pm

in windows i think that you must habilitate in Windows features (SMB 1.0 / CIFS file sharing Support)