Cannot start add-ons after migrating to NVME

Hello,

I have migrated with the help of a full backup to an NVME Drive. Unfortunatly after restore I see that all add-ons are greyed out. When trying to start them, nothing happens. If I click on the add-on start page on the left menu and the screen says that the add-on is not started.
I have installed the following add-ons:

  • Mosquitto Broker
  • Zigbee2MQTT
  • ESPHome
  • Samba Share
  • Log Viewer
  • Home Assistant Google Drive Backup
  • Terminal & SSH
  • File Editor

The logs for ESPHome are the following:

[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] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: ESPHome
 ESPHome add-on for intelligently managing all your ESP8266/ESP32 devices
-----------------------------------------------------------
 Add-on version: 2021.12.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.8.4
 Home Assistant Supervisor: 2022.08.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 20-nginx.sh: executing... 
[cont-init.d] 20-nginx.sh: exited 0.
[cont-init.d] 30-dirs.sh: executing... 
[cont-init.d] 30-dirs.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:33:18] INFO: Waiting for dashboard to come up...
[16:33:19] INFO: Starting ESPHome dashboard...
2022-08-15 16:33:20,104 INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome...
[16:33:20] INFO: Starting NGINX...

The strange thing is that the frontend of the plugin is saying that it is not the working, the backend seems working. I have installed Mosquito Add-on and the broker is working. Other automation tools use it (NodeRED).
The logs for Mosquitto Broker are the following:

[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] mosquitto.sh: executing... 
[16:01:29] INFO: Setting up user Charel_MQTT
[16:01:30] INFO: SSL is not enabled
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:01:31] INFO: Starting NGINX for authentication handling...
[16:01:31] INFO: Starting mosquitto MQTT broker...
1660572091: Warning: Mosquitto should not be run as root/administrator.
[16:01:32] INFO: Successfully send discovery information to Home Assistant.
[16:01:33] INFO: Successfully send service information to the Supervisor.
1660572091: mosquitto version 2.0.11 starting
1660572091: Config loaded from /etc/mosquitto/mosquitto.conf.
1660572091: Loading plugin: /usr/share/mosquitto/go-auth.so
1660572091:  ├── Username/password checking enabled.
1660572091:  ├── TLS-PSK checking enabled.
1660572091:  └── Extended authentication not enabled.
1660572091: Opening ipv4 listen socket on port 1883.
1660572091: Opening ipv6 listen socket on port 1883.
1660572091: Opening websockets listen socket on port 1884.
1660572091: mosquitto version 2.0.11 running
1660572091: New connection from 127.0.0.1:48482 on port 1883.
1660572091: Client <unknown> closed its connection.
1660572106: New connection from 192.168.178.47:37258 on port 1883.
1660572106: New connection from 192.168.178.47:37260 on port 1883.
1660572106: New connection from 192.168.178.47:37262 on port 1883.
1660572106: New client connected from 192.168.178.47:37258 as nodered_a5f3fe315fa2af6b (p2, c1, k60, u'Charel_MQTT').
1660572106: New client connected from 192.168.178.47:37260 as nodered_2e39cc8a462e7811 (p2, c1, k60, u'Charel_MQTT').
1660572106: New client connected from 192.168.178.47:37262 as nodered_52d9302b21f262e6 (p2, c1, k60, u'Charel_MQTT').
1660572131: New connection from 192.168.178.50:51914 on port 1883.
1660572131: New client connected from 192.168.178.50:51914 as DVES_7DDDD8 (p2, c1, k30, u'Charel_MQTT').
1660572131: New connection from 192.168.178.47:55055 on port 1883.
1660572131: New client connected from 192.168.178.47:55055 as 7cdBelARDVxVA1NXZXi9hk (p1, c1, k60, u'Charel_MQTT').
1660572135: Client DVES_7DDDD8 closed its connection.
1660572180: New connection from 192.168.178.28:56454 on port 1883.
1660572180: New client connected from 192.168.178.28:56454 as DVES_B3A6E4 (p2, c1, k30, u'Charel_MQTT').
1660572180: New connection from 192.168.178.51:56459 on port 1883.
1660572180: New client connected from 192.168.178.51:56459 as DVES_780420 (p2, c1, k30, u'Charel_MQTT').
1660572218: New connection from 172.30.32.1:55766 on port 1883.
1660572218: New client connected from 172.30.32.1:55766 as mqttjs_db81e16d (p2, c1, k60, u'Charel_MQTT').
1660572256: New connection from 192.168.178.50:51915 on port 1883.
1660572256: New client connected from 192.168.178.50:51915 as DVES_7DDDD8 (p2, c1, k30, u'Charel_MQTT').
1660572286: New connection from 172.30.32.1:34217 on port 1883.
1660572286: New client connected from 172.30.32.1:34217 as 1zbw7yLzukbNFxUvLEW89v (p2, c1, k60, u'homeassistant').
1660572301: New connection from 192.168.178.42:55145 on port 1883.
1660572301: New client connected from 192.168.178.42:55145 as DVES_73E8B1 (p2, c1, k30, u'Charel_MQTT').
1660573639: Client 1zbw7yLzukbNFxUvLEW89v closed its connection.
1660573666: New connection from 172.30.32.1:39131 on port 1883.
1660573666: New client connected from 172.30.32.1:39131 as 4rn6LA5J1hHNTKl4g10mmO (p2, c1, k60, u'homeassistant').
1660573892: Saving in-memory database to /data//mosquitto.db.
1660574414: New connection from 192.168.178.51:52981 on port 1883.
1660574414: Client DVES_780420 already connected, closing old connection.
1660574414: New client connected from 192.168.178.51:52981 as DVES_780420 (p2, c1, k30, u'Charel_MQTT').
1660574419: Client nodered_a5f3fe315fa2af6b has exceeded timeout, disconnecting.
1660574419: Client nodered_2e39cc8a462e7811 has exceeded timeout, disconnecting.
1660574419: Client nodered_52d9302b21f262e6 has exceeded timeout, disconnecting.
1660574422: New connection from 192.168.178.42:51506 on port 1883.
1660574422: Client DVES_73E8B1 already connected, closing old connection.
1660574422: New client connected from 192.168.178.42:51506 as DVES_73E8B1 (p2, c1, k30, u'Charel_MQTT').
1660574423: New connection from 192.168.178.28:64984 on port 1883.
1660574423: Client DVES_B3A6E4 already connected, closing old connection.
1660574423: New client connected from 192.168.178.28:64984 as DVES_B3A6E4 (p2, c1, k30, u'Charel_MQTT').
1660574427: Client DVES_7DDDD8 closed its connection.
1660574437: New connection from 192.168.178.50:51917 on port 1883.

Does anyone has an idea how to solve this?

having same issue after a an upgrade to a faster processer and using a restore snapshot. All my addons are grey out but seems to be working in backend. Did you figure the fix??

Update: A full reboot of system and not just a restart is the fix as suggested buy this user.