Upgrade from 0.99.2 to 0.99.3 not working

I am running hass.io on a Raspberry Pi 3. Usually, the upgrades from one version to the next work smoothly meaning that after a while HA restarts with the new version. I have now been trying to upgrade to 0.99.3 at least 3 times, both from hass.io page and from the command line, but the upgrade doesn’t happen. I am stuck on 0.99.2. After a couple of the attempts, HA didn’t come back up again until after a reboot.

Anyone else experiencing this problem?

I’ve seen a lot of this issues with hassio updates when running out of disk space.

Here is what disk use looks like:

core-ssh:~# df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  13.9G      1.6G     11.6G  12% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                   458.7M         0    458.7M   0% /sys/fs/cgroup
/dev/root                86.9M     86.9M         0 100% /dev/init
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /data
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /config
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /ssl
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /addons
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /backup
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /share
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /etc/resolv.conf
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /etc/hostname
/dev/mmcblk0p8           13.9G      1.6G     11.6G  12% /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                   458.7M         0    458.7M   0% /sys/firmware

Nope I upgraded to 0.99.3 without issue.

Something in the logs?

Not in the home-assistant.log, but I guess that is not where to look. Any other log files I can access that could shed some light on the problem?

Hass.io -> System tab

19-09-30 13:04:00 INFO (MainThread) [hassio.host.info] Update local host information
19-09-30 13:04:00 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-09-30 13:04:00 INFO (MainThread) [hassio.host.services] Update service information
19-09-30 13:04:00 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-09-30 13:04:01 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-09-30 13:04:01 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-09-30 14:10:40 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-09-30 14:10:40 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-09-30 14:10:40 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-09-30 14:10:41 INFO (MainThread) [hassio.store] Load add-ons from store: 60 all - 0 new - 0 remove

Nothing that tells me anything meaningful, but the log level seems very shallow.

Also have the same problem. 0.99.3 is not starting…Cant find anything in the logs…Running hass.io

It may be worth posting/moving this thread to the hassio section of the forum, you may get more help there :slight_smile:

I have the same issue. Running HA on my Ubuntu server. Here’s my log:

[hassio.homeassistant] Update Home Assistant to version 0.99.3
19-10-02 05:21:37 INFO (SyncWorker_5) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.98.5 to homeassistant/qemux86-64-homeassistant:0.99.3
19-10-02 05:21:37 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.99.3.
19-10-02 05:22:14 ERROR (SyncWorker_5) [hassio.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.99.3 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.99.3: No such image: homeassistant/qemux86-64-homeassistant:0.99.3”).
19-10-02 05:22:14 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

my 5 cent

could be bad timing. sd-card dieing

I cloned my old SD-card to a new one and the upgrade finally worked with the new card. Ageing SD-card could have been the problem.

My only gripe now is that I cloned a 16GB card to a 32GB card, which hence makes use of only 16GB of the larger card. Is there a way to resize hassos partitions if I should need the space in the future?

Had the same problem on pi3 with v0.99.2
This thread helped me to get the update working

ssh into hassIO and enter

hassio su repair

I get “command not found” with that

I too had the same problem and think that it is not coincidentally a SD card failure. Initially discovered that 99.2 was a breaking update for Fully Kiosk Browser and after several attempts to update was getting a system error ->500. SSH update would also fail.

Solution for me was SSH hassio su repair, reboot, SSH hassio su update --version=0.99.3… reboot, reboot, hassio system update, reboot, and then patiently watch system logs. Evidentially after several connection refused errors, the WebSocket API initialized and the update occurred.

19-10-09 14:54:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from XX_appdaemon3
19-10-09 14:54:54 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.XX:8123 ssl:False [Connection refused].
19-10-09 14:54:59 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-10-09 14:54:59 INFO (MainThread) [hassio.api.proxy] WebSocket access from XX_appdaemon3
19-10-09 14:54:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.XX:8123 ssl:False [Connection refused].
19-10-09 14:55:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-10-09 14:55:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from XX_appdaemon3
19-10-09 14:55:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
19-10-09 14:55:05 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-10-09 14:55:05 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.99.3
19-10-09 14:55:05 INFO (SyncWorker_7) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-homeassistant:0.99.2']```

I did not have to reimage an SD card and I have not had any problems with updates until now.  Good luck!