Can't Upgrade From HA 0.90.2 to 0.91.4 (Hassio)

AndrRap · April 21, 2019, 3:14pm

Hi there,
I have the same issue but with the follwong error:
19-04-21 15:10:37 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi-homeassistant tag 0.91.4.
19-04-21 15:10:51 ERROR (SyncWorker_0) [hassio.docker.interface] Can’t install homeassistant/raspberrypi-homeassistant:0.91.4 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi-homeassistant:0.91.4: No such image: homeassistant/raspberrypi-homeassistant:0.91.4”).
19-04-21 15:10:51 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

It looks like it cannot find the image…

sleeepy2 · April 21, 2019, 4:01pm

This was my error when I had no space left. I thought that that it was odd that it said that the image couldn’t be found but once I resized my vm it installed fine.

AndrRap · April 21, 2019, 6:13pm

It is a fresh installation on a 8Gb card. Disk check says it is 70% free…

anon34565116 · April 21, 2019, 7:11pm

So, df -hl says /dev/root is 70% free? What is the free amount?

AndrRap · April 22, 2019, 9:43am

…and last night, suddenly, the update was ok. Now I am on 0.91.4 and everything is working fine but Configurator: I cannot access it any longer.
Thanks for your help but this is really not deterministic!!!
PS df -h says /dev/root is 0% free but overlay is 30% used: I do not understand why it can’t adjust space… But yes, I’d probably need a larger card.

skritz · April 26, 2019, 5:47am

Interesting.

It’s got even weirder for me.

Still can’t update:

Think I’m gonna have to backup and rebuild a new Hassio instance.

I think there’s a corruption issue for those of us with this update issue.

anon34565116 · April 26, 2019, 9:08am

Yes, 0.92.0 has been released. Personally I am waiting a week or for 0.92.2 whichever comes first.

skritz · April 26, 2019, 4:10pm

Yeah, I hear you.

I have a feeling that a fresh install and restore is gonna be the only functional solution on my end.

anon34565116 · April 26, 2019, 4:13pm

The Hassio installation page says you can “upgrade to” a particular version but I have not tried that.

sleeepy2 · April 26, 2019, 6:03pm

make sure you back up your lovelace layout.
With me no longer using the yaml file that was what I forgot to backup when I did a clean install.
What a pain

anon34565116 · April 26, 2019, 6:20pm

and copy it off the card.
Last time I backed up the config and forgot to copy it off before reformatting the car.

radionerd · April 28, 2019, 2:12am

I have same problem. My SD is full all of a sudden. overlay 100%
Get an error “500 Internal Server Error” when trying to save config.yaml

debug1: permanently_set_uid: 0/0
core-ssh:~# df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  28.6G     27.9G         0 100% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                   463.1M         0    463.1M   0% /sys/fs/cgroup
/dev/root                90.1M     90.1M         0 100% /dev/init
/dev/mmcblk0p8           28.6G     27.9G         0 100% /ssl
/dev/mmcblk0p8           28.6G     27.9G         0 100% /addons
/dev/mmcblk0p8           28.6G     27.9G         0 100% /backup
/dev/mmcblk0p8           28.6G     27.9G         0 100% /share
/dev/mmcblk0p8           28.6G     27.9G         0 100% /data
/dev/mmcblk0p8           28.6G     27.9G         0 100% /config
/dev/mmcblk0p8           28.6G     27.9G         0 100% /etc/resolv.conf
/dev/mmcblk0p8           28.6G     27.9G         0 100% /etc/hostname
/dev/mmcblk0p8           28.6G     27.9G         0 100% /etc/hosts
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                    64.0M         0     64.0M   0% /proc/keys
tmpfs                    64.0M         0     64.0M   0% /proc/latency_stats
tmpfs                    64.0M         0     64.0M   0% /proc/timer_list
tmpfs                    64.0M         0     64.0M   0% /proc/sched_debug
tmpfs                   463.1M         0    463.1M   0% /sys/firmware
core-ssh:~#

anon34565116 · April 28, 2019, 8:46am

I know some people with cameras have found saved images consuming space.

radionerd · April 28, 2019, 6:24pm

I did resently add two cameras to motionEye before this problem started.
I deleted all of the cams, motionEye and several add-on’s that I can live without. Deleted logs, old backups… That opened up about 700mb of free space.

Then pushed latest release successfully.
32 GB SD is still full. The memory overload is in the blocks.

BrianM · June 6, 2019, 2:12pm

I just wanted to close the loop on this issue (for me anyways). I decided to wait to see what would happen with upcoming updates. The next update also failed on me with the same error message. However, the update after that went through without any problems. I now have an updated system with full access to the Configurator and other add-ons again. I still don’t know why the prior two releases failed and I’m not sure why I lost access to some add-ons like the Configurator, but it seems to have fixed itself with the most recent update.