Tried to update from 0.118.2 to 0.118.3 today and I get this:
20-11-24 19:00:08 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 0.118.3
20-11-24 19:00:08 INFO (SyncWorker_4) [supervisor.docker.interface] Updating image homeassistant/raspberrypi4-homeassistant:0.118.2 to homeassistant/raspberrypi4-homeassistant:0.118.3
20-11-24 19:00:08 INFO (SyncWorker_4) [supervisor.docker.interface] Downloading docker image homeassistant/raspberrypi4-homeassistant with tag 0.118.3.
20-11-24 19:01:35 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/raspberrypi4-homeassistant:0.118.3 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi4-homeassistant:0.118.3: No such image: homeassistant/raspberrypi4-homeassistant:0.118.3").
20-11-24 19:01:35 INFO (SyncWorker_4) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 98.8 GiB
20-11-24 19:01:35 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Space is definitely not an issue and have tried rebooting a few times but no luck.
Looks as though it can’t find the image?
Any ideas?
20-11-25 05:46:18 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image homeassistant/raspberrypi3-homeassistant with tag 0.118.3.
20-11-25 05:46:24 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.118.3 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.118.3: No such image: homeassistant/raspberrypi3-homeassistant:0.118.3").
20-11-25 05:46:24 INFO (SyncWorker_0) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 45.8 GiB
20-11-25 05:46:24 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Boot with the new image, and connect (note - the mDNS hostname changed from hass.local to homeassistant.local) to http://homeassistant.local:8123/
Instead of starting setup, restore from snapshot, upload and wait again for the restore to complete.
I found the full snapshot would not upload (think 503 Bad Gateway), but noticed that the file was 280MiB, rather than 15MiB for previous snapshot files. I think the issue was 200MiB of media uploaded to /media to test the recently added media player features. To get my install restored, I had to untar the BIG snapshot, delete the media.tar.gz archive, re-tar, and re-upload the much smaller backup.
So - you could try creating a snapshot backup, and try deleting any large files from (music, sound, video) from /media, create another snapshot backup (can’t have too many…) and re-try the upgrade. If it still fails, at least you have a small snapshot that has a better chance of rebuilding a fresh install.
Not so easy when HA is installed on raspbian via docker
Does hassio now work ok booting from USB SSD on a pi4 I wonder, that’s why I went with my current setup because at the time had to boot from SD and then move to the SSD
The Hassio is just a simple version of settings.No media is in use in my case.
My snapshot is not more than 400mb.
isn’t there a easier work around? I my case its not so easy the reinstall al of it.
too many dependencies on the system.
20-12-07 10:50:29 ERROR (SyncWorker_5) [supervisor.docker.interface] Can't install homeassistant/raspberrypi4-homeassistant:0.118.5 -> 404 Client Error for http+docker://localhost/v1.40/images/homeassistant/raspberrypi4-homeassistant:0.118.5/json: Not Found ("no such image: homeassistant/raspberrypi4-homeassistant:0.118.5: No such image: homeassistant/raspberrypi4-homeassistant:0.118.5").