I just tried an update to hass.io through the web interface and it never came back up. Tried rebooting the raspberry Pi but no luck. The logo comes up on the HDMI port but that’s it. Can anything be done to recover without starting over? Is there a different way I should have updated it?
I’ll also add that the pi is still pingable and shows up on the network as “hassio” so it’s still somewhat booting at least
I decided to go back to Hassbian. Much easier to troubleshoot problems
1 Like
Since it was reachable, did you have a method of checking the logs? If so, did you find anything?
There was never anything to see through the HDMI port. You could have checked logs for a misconfig.
can you access it through SSH ?
If yes, try this:
curl -d '{"version": "0.68.1"}' http://hassio/homeassistant/update
Basically you’re doing a rollback to a previous version. Helped me already a lot in the past.
PS: obviously you can replace the 0.68.1 with any previous release ID
The problem is that I couldn’t access it through anything. All ports were closed. No ssh, samba or web
I’m also seeing this problem almost every single time I upgrade HASSIO to the new version. Only way I could recover in that case is reimage the SD card and restore my latest snapshot afterwards, which returns me to the previous version. The upgrade mostly works if I conduct it immediately after. I think it has something to do with DB-size or data that gets corrupted after some time, but I still wasn’t able to figure out the root cause.
Same here, after hassio update from 68.x to 69.1 no HTTP response on its ip adres. The rpi boots has network but no webserver response.
I followed these instructions to get SSH going:
https://developers.home-assistant.io/docs/en/hassio_debugging.html
The logs
root@hassio:/# journalctl -f -u resin-supervisor.service
-- Logs begin at Sun 2017-09-17 13:49:22 UTC. --
May 18 11:00:15 hassio systemd[1]: resin-supervisor.service: Service hold-off time over, scheduling restart.
May 18 11:00:15 hassio systemd[1]: Stopped Resin supervisor.
May 18 11:00:15 hassio systemd[1]: Starting Resin supervisor...
May 18 11:00:15 hassio docker[7678]: Error response from daemon: No such container: resin_supervisor
May 18 11:00:15 hassio systemd[1]: Started Resin supervisor.
May 18 11:00:16 hassio start-resin-supervisor[7689]: Error: No such object: homeassistant/armhf-hassio-supervisor
May 18 11:00:16 hassio systemd[1]: resin-supervisor.service: Main process exited, code=exited, status=1/FAILURE
May 18 11:00:16 hassio docker[7718]: Error response from daemon: No such container: resin_supervisor
May 18 11:00:16 hassio systemd[1]: resin-supervisor.service: Unit entered failed state.
May 18 11:00:16 hassio systemd[1]: resin-supervisor.service: Failed with result 'exit-code'.^C
root@hassio:/# docker logs resin_supervisor
Error response from daemon: No such container: resin_supervisor
root@hassio:/#
It seems everything is moved to lost+found
The configuration is in:
/mnt/data/lost+found/#16385/homeassistant/configuration.yaml
Now what? Any change to get this working again?
I gave up. Just going to copy the config files to a new hassio install.
What the f#*&.
resinos-hassio-1.3-raspberrypi3.img.bz2
The fresh installed V69.1 doesn’t respond to http…
I have set static ip, gw and 1 dns for eth0 in resin-sample.
The first 11 minutes the Preparing Hass.io(this can take up to 20 minutes) was displayed. After that no response on http
root@hassio:~# journalctl -f -u resin-supervisor.service
-- Logs begin at Sun 2017-09-17 13:49:22 UTC. --
May 18 12:40:07 hassio start-resin-supervisor[2008]: 18-05-18 12:40:07 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant
May 18 12:40:07 hassio start-resin-supervisor[2008]: 18-05-18 12:40:07 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.69.1.
May 18 12:52:36 hassio start-resin-supervisor[2008]: 18-05-18 12:52:36 INFO (SyncWorker_0) [hassio.docker.interface] Tag image homeassistant/raspberrypi3-homeassistant with version 0.69.1 as latest
May 18 12:52:36 hassio start-resin-supervisor[2008]: 18-05-18 12:52:36 INFO (MainThread) [hassio.homeassistant] HomeAssistant docker now installed
May 18 12:52:36 hassio start-resin-supervisor[2008]: 18-05-18 12:52:36 INFO (SyncWorker_5) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant docker application
May 18 12:52:40 hassio start-resin-supervisor[2008]: 18-05-18 12:52:40 INFO (SyncWorker_5) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
May 18 12:52:43 hassio start-resin-supervisor[2008]: 18-05-18 12:52:43 INFO (SyncWorker_5) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.69.1
May 18 13:02:44 hassio start-resin-supervisor[2008]: 18-05-18 13:02:44 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
May 18 13:02:44 hassio start-resin-supervisor[2008]: 18-05-18 13:02:44 INFO (SyncWorker_6) [hassio.docker.interface] Cleanup docker images: ['homeassistant/raspberrypi3-homeassistant:landingpage']
May 18 13:05:07 hassio start-resin-supervisor[2008]: 18-05-18 13:05:07 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home-Assistant
root@hassio:~# docker logs resin_supervisor
18-05-18 12:40:02 INFO (MainThread) [__main__] Initialize Hassio setup
18-05-18 12:40:02 INFO (MainThread) [__main__] Setup HassIO
18-05-18 12:40:03 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
18-05-18 12:40:03 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
18-05-18 12:40:03 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
18-05-18 12:40:03 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
18-05-18 12:40:03 INFO (MainThread) [hassio.host.info] Update local host information
18-05-18 12:40:03 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
18-05-18 12:40:03 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to supervisor homeassistant/armhf-hassio-supervisor with version 103.3
18-05-18 12:40:04 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup docker images: ['homeassistant/armhf-hassio-supervisor:0.96']
18-05-18 12:40:06 INFO (SyncWorker_1) [hassio.docker.interface] Attach to image homeassistant/raspberrypi3-homeassistant with version landingpage
18-05-18 12:40:06 INFO (MainThread) [hassio.addons.git] Load addon /data/addons/git/a0d7b954 repository
18-05-18 12:40:06 INFO (MainThread) [hassio.addons.git] Load addon /data/addons/core repository
18-05-18 12:40:06 INFO (MainThread) [hassio.addons] Load addons: 34 all - 34 new - 0 remove
18-05-18 12:40:06 INFO (MainThread) [hassio.updater] Fetch update data from https://raw.githubusercontent.com/home-assistant/hassio/master/version.json
18-05-18 12:40:07 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files
18-05-18 12:40:07 INFO (MainThread) [__main__] Run HassIO
18-05-18 12:40:07 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons
18-05-18 12:40:07 INFO (MainThread) [hassio.core] Ignore Hass.io auto updates on dev channel
18-05-18 12:40:07 INFO (MainThread) [hassio.core] Start API on 172.30.32.2
18-05-18 12:40:07 INFO (MainThread) [hassio.addons] Startup initialize run 0 addons
18-05-18 12:40:07 INFO (MainThread) [hassio.addons] Startup system run 0 addons
18-05-18 12:40:07 INFO (MainThread) [hassio.addons] Startup services run 0 addons
18-05-18 12:40:07 INFO (MainThread) [hassio.addons] Startup application run 0 addons
18-05-18 12:40:07 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
18-05-18 12:40:07 INFO (MainThread) [hassio.core] Hass.io is up and running
18-05-18 12:40:07 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant
18-05-18 12:40:07 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.69.1.
18-05-18 12:52:36 INFO (SyncWorker_0) [hassio.docker.interface] Tag image homeassistant/raspberrypi3-homeassistant with version 0.69.1 as latest
18-05-18 12:52:36 INFO (MainThread) [hassio.homeassistant] HomeAssistant docker now installed
18-05-18 12:52:36 INFO (SyncWorker_5) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant docker application
18-05-18 12:52:40 INFO (SyncWorker_5) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant docker application
18-05-18 12:52:43 INFO (SyncWorker_5) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.69.1
18-05-18 13:02:44 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home-Assistant startup!
18-05-18 13:02:44 INFO (SyncWorker_6) [hassio.docker.interface] Cleanup docker images: ['homeassistant/raspberrypi3-homeassistant:landingpage']
18-05-18 13:05:07 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home-Assistant
root@hassio:~# docker logs homeassistant
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=stop>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=restart>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=check_config>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=reload_core_config>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=create>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=dismiss>
2018-05-18 14:53:06 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded introduction from homeassistant.components.introduction
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.setup] Setting up introduction
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.components.introduction]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hello, and welcome to Home Assistant!
We'll hope that we can make all your dreams come true.
Here are some resources to get started:
- Configuring Home Assistant:
https://home-assistant.io/getting-started/configuration/
- Available components:
https://home-assistant.io/components/
- Troubleshooting your configuration:
https://home-assistant.io/getting-started/troubleshooting-configuration/
- Getting help:
https://home-assistant.io/help/
This message is generated by the introduction component. You can
disable it in configuration.yaml.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.setup] Setup of domain introduction took 0.0 seconds.
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=introduction>
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Welcome Home!, message=
Here are some resources to get started:
- [Configuring Home Assistant](https://home-assistant.io/getting-started/configuration/)
- [Available components](https://home-assistant.io/components/)
- [Troubleshooting your configuration](https://home-assistant.io/docs/configuration/troubleshooting/)
- [Getting help](https://home-assistant.io/help/)
To not see this card popup in the future, edit your config in
`configuration.yaml` and disable the `introduction` component.
, service_call_id=1962426032-1>
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.notification, old_state=None, new_state=<state persistent_notification.notification=notifying; title=Welcome Home!, message=Here are some resources to get started:
- [Configuring Home Assistant](https://home-assistant.io/getting-started/configuration/)
- [Available components](https://home-assistant.io/components/)
- [Troubleshooting your configuration](https://home-assistant.io/docs/configuration/troubleshooting/)
- [Getting help](https://home-assistant.io/help/)
To not see this card popup in the future, edit your config in
`configuration.yaml` and disable the `introduction` component. @ 2018-05-18T14:53:07.550387+02:00>>
2018-05-18 14:53:07 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1962426032-1>
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setting up http
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=http>
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setting up api
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setting up system_log
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=system_log, service=clear>
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=system_log, service=write>
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=system_log>
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2018-05-18 14:53:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=websocket_api>
2018-05-18 14:53:11 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.1 seconds.
2018-05-18 14:53:11 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=api>
2018-05-18 14:53:12 INFO (MainThread) [homeassistant.setup] Setting up recorder
2018-05-18 14:53:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=recorder, service=purge>
Exception in thread Recorder:
Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/usr/lib/python3.6/site-packages/homeassistant/components/recorder/__init__.py", line 187, in run
from .models import States, Events
File "/usr/lib/python3.6/site-packages/homeassistant/components/recorder/models.py", line 6, in <module>
from sqlalchemy import (
File "/usr/lib/python3.6/site-packages/sqlalchemy/__init__.py", line 9, in <module>
from .sql import (
File "/usr/lib/python3.6/site-packages/sqlalchemy/sql/__init__.py", line 8, in <module>
from .expression import (
File "/usr/lib/python3.6/site-packages/sqlalchemy/sql/expression.py", line 57, in <module>
from .dml import Insert, Update, Delete, UpdateBase, ValuesBase
File "<frozen importlib._bootstrap>", line 971, in _find_and_load
File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 674, in exec_module
File "<frozen importlib._bootstrap_external>", line 779, in get_code
File "<frozen importlib._bootstrap_external>", line 487, in _compile_bytecode
ValueError: bad marshal data (unknown type code)
2018-05-18 14:53:14 INFO (MainThread) [homeassistant.setup] Setting up frontend
2018-05-18 14:53:17 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 2.5 seconds.
2018-05-18 14:53:17 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=frontend>
2018-05-18 14:53:22 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
Reflashing and now only altering the image by installing an authorized keys file to the root for ssh access. No other changes are made. My DHCP server will fix the ip to 192.168.178.100.
Worked!
Setting the resin-sample file like this caused this problem:
[connection]
id=resin-sample
type=ethernet
interface-name=eth0
[ipv4]
address1=192.168.178.100/24,192.168.178.1
dns=8.8.8.8;
I am wondering if DB size has something to do with it too. My DB is already at 100 MB and it’s only been running for 4 days. Is that normal?
From my recent experience… had many of the same problems.
Replaced my microsd card with a brand new one, and they all went away.
I use the recorder component and don’t include anything by default, my DB stays very small. I only add entities to the recorder if I need historical data or persistance through a reboot for some reason.
I’ve been having this same issue, I’ve been re-flashing my SD card every 5-15 days lately. Has anyone been able to identify a root cause or fix this without needing to re-flash their card? I can’t tell if this is a raspberry pi stability issue, or a software bug
I already changed my power supply (bought a CanaKit 2.5A USB Power Supply) and bought a new class 10 card. I’m getting annoyed enough to consider purchasing a NUC.
I’m in the same boat. Also using a class 10 SD card of a renowned brand and the official RPI power supply (2.5A). Unlikely that the cause is in the hardware, but one never knows… I’m considering going back to hasspbian if this gives me a more stable environment.
Now suddenly in the same boat! How did you guys solve this?