23-10-23 05:48:52 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.10.5
23-10-23 05:48:52 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.3 to ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.5
23-10-23 05:48:52 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/generic-x86-64-homeassistant with tag 2023.10.5.
23-10-23 05:48:53 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.5: 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.5/json: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument")
23-10-23 05:48:53 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
#core update file log - 2023.10.3 to 2023.10.5
1 messages · Page 1 of 1 (latest)
Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
Apart from the excellent bot advice that I will most certainly consider the next time, Could the error actually be : 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.5/json: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument")
Indeed but the cause of that can have multiple reasons. The host log (top right) might show something about that, otherwise you might have to use SSH to debug further.
You can try docker pull ghcr.io/home-assistant/generic-x86-64-homeassistant:2023.10.5 via the advanced SSH addon (disable protection) which might give more information.
You can also try ha supervisor repair and reboot after 15 minutes or so if that doesn't do anything.
It could also be storage corruption which commonly happens on SBCs with SD cards or SSDs without a powered USB hub as storage.
i'll try those, thank you. brb
"supervisor repair" seems to have done the trick... ha appears to be updating now... I'll know more in a few moments.
HAOS uses a custom overlay2 path so googling for "readlink /mnt/data/docker/overlay2: invalid argument"mostly find HA related informatiion.
II you google "readlink /var/lib/docker/overlay2: invalid argument" rather than that you'll find a bit more.
What hardware are you using?
My ui just lost connection, I assumed that home assistant is going to reboot, but it has not. it's now just not responding. what is the console command to reboot it? ( if I still have a console )
If you have a keyboard and monitor you can use login and then reboot. You didn't tell me what hardware you're using
i'm using home assistant core on an intel nuc booting from a usb drive
I have to keep unplgging my keybaord dongle to use the ha console... so it takes a moment for me to switch back and forth
It looks more like you use HAOS. I'm not sure if NUCs also tend to corrupt when using a USB SSD without a powered USB hub
yes i am haos
I can't seem to reboot ha from the console... is the command different in haos?
I'm only this petty about it because it's kinda important we bot use the right terms: https://www.home-assistant.io/installation/#compare-installation-methods
Let me check
You can also type host reboot into the ha > prompt
one moment please...
I suppose you didn't enter login first?: <#1165952537585799229 message>
The prompt should look like # rather than ha >. If you do that then reboot will also work
it responded with ... client timeout while waiting... exceeding headers.. context deadline exceeded...
did not reboot
should I just power off and be done with it?
Oof. Try the reboot command then (see message above) but this doesn't look good. Might be faster/needed to re-flash and restore a backup. I hope you have off-site ones
hard reset of nuc completed haos back up... but still in core version 2023.10.3
and... I guess that's where it's going to stay for today at least
i'll wait for 2023.10.6+ and if those fail too, then ill make a new boot device
I have backups, but 2023.10.5 doesn't seem like it actually does much... so i'll wait