Migrated to SSD, now Samba share doesnt work

Configuration
1

Hello,

i migrated my home assistant to a SSD, and used a snapshot i made just before that to restore it.
Its running on a pi4 which is connected via ethernet, and i use a windows 10 pc to interact with it.
Before the snapshot it all worked perfectly but now no longer.

Duckdns also stopped working but i fixed that by making a new domain name. Esphome also stopped working but a re-install fixed that. But now samba share is refusing to work even after a re-install. My pi also doesnt show up on my network either but other devices do.

The log shows the following:

INTERNAL ERROR: open_sockets_smbd() failed in pid 32801 (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 32801): open_sockets_smbd() failed 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
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]"
interpret_interface: Can't find address for eth0
WARNING: no network interfaces found
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
open_sockets_smbd: No sockets available to bind to.

Does anyone experience the same, or ran into this issue aswell?
any input would be appreciated

2

Can you show your SAMBA addon config?

3 
workgroup: WORKGROUP
username: homeassistant
password: xxxxxxx
allow_hosts:
  - 192.168.178.0/16
  - 192.168.178.75                  #ip of adress my pi#
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false
4

moving to an SSD shouldn’t really affect you IP or other settings at all, so this is a bit weird. I would however suggest you hop over to Discord channel #homeassistant_os https://discord.gg/BdMG8W2W (that is, assuming you are running homeassistant_os of course, otherwise pick the correct channel for your install method.)

5

Your config mostly looks ok. Not sure why you have this:

The problem is that the addon cant find the network adaptor:

6

i just added that in here too clarify that ip number in case it was helpfull in some way.

7

I has been fixed, by probably a combination of removing the internal ip adress that was set to a duckdns one (for google cast to work), and a shut down host + unplug combination.