Checked my config and then hit install in configuration frame. Fifteen minutes later, whole device was dead (ssh was declined).
Rebooted. Found 88.2 running. Used ssh to hassio. Hassio ha info indicated 89 available, but 88.2 installed. Did hassio ha stop, then hassio ha update. 20 minutes later had to pull power cord and reinsert to get device to stop endless solid erd/green lights. Found 88.2 still installed and willing to run.
Anyone else, or just me?
I just updated a Hassio / Debian VM successfully. I think my HassOS VM imploded yesterday before I could upgrade,
Apparently by HassOS VM is OK I just successfully updated to 0.89.
This has happened to me over the past with various releases. Check you have enough space on you SD card. Quick fix delete all log files and HA.DB ( after stopping HA first). Reboot pi and try update again
Same issue for me. Tried to delete the database, and to force installation via SSH but no luck. 0.89 still won’t update.
From the log only this two rows:
WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
I’m running HASSos updated day before yesterday to 2.10… maybe this could be the problem?
HASSos is running in a VM, VHD 16GB and RAM 4GB, so I guess it’s impossbile I’m out of space.
How much free space is available on your SD card before a failing update?
Neither of those refer to disk space. If you used the default HassOS image of 6 GB you could very well be out of disk space. My very basic HassOs configuration is over 5 GB.
From the VM console login prompt type:
root
login
df -hl | more
Look for any mount points showing 95% user or higher.
I have the same question.0.88.2>> 0.89
19-03-08 13:38:23 INFO (SyncWorker_12) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.89.0
19-03-08 13:48:25 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!
19-03-08 13:48:25 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
19-03-08 13:48:25 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.2I have got the next error:
19-03-07 16:32:25 INFO (SyncWorker_10) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.89.0. 19-03-07 16:32:27 ERROR (SyncWorker_10) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.89.0 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”). 19-03-07 16:32:27 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running! 19-03-07 16:32:27 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.89.0
I would try again later. A 500 Server error indicates some server issue.
This the output of df -h | more command:
Filesystem Size Used Available Use% Mounted on
overlay 15.0G 7.0G 7.3G 49% /
tmpfs 64.0M 0 64.0M 0% /dev
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/root 85.5M 85.5M 0 100% /dev/init
/dev/sda8 15.0G 7.0G 7.3G 49% /data
/dev/sda8 15.0G 7.0G 7.3G 49% /config
/dev/sda8 15.0G 7.0G 7.3G 49% /ssl
/dev/sda8 15.0G 7.0G 7.3G 49% /addons
/dev/sda8 15.0G 7.0G 7.3G 49% /backup
/dev/sda8 15.0G 7.0G 7.3G 49% /share
/dev/sda8 15.0G 7.0G 7.3G 49% /etc/resolv.conf
/dev/sda8 15.0G 7.0G 7.3G 49% /etc/hostname
/dev/sda8 15.0G 7.0G 7.3G 49% /etc/hosts
shm 64.0M 0 64.0M 0% /dev/shm
tmpfs 1.9G 0 1.9G 0% /proc/acpi
tmpfs 64.0M 0 64.0M 0% /proc/kcore
tmpfs 64.0M 0 64.0M 0% /proc/keys
tmpfs 64.0M 0 64.0M 0% /proc/timer_list
tmpfs 1.9G 0 1.9G 0% /proc/scsi
tmpfs 1.9G 0 1.9G 0% /sys/firmware
No mount point over 50% for me…
@anon34565116: I don’t understand why you said “Neither of those refer to disk space”; Disk size is in fact “disk space” as the output before has shown
I’ve the same issue as @freddy_yu, no problem with the precedent update, only with 0.89 .
This may be totally unrelated, but have you checked.
Have read that some peoples updates fail if their configs are not compatible with the new version of hass.
I know it’s an older version, but something to look at.
Sorry I misunderstood what VHD meant. You indeed have the disk space.
I am personally moving away from a HassOs VM to a Hassio install on Linux. In my opinion HassOs is not a stable OS.
I had a similar issue a while back where HassOS would go back to an older version on reboot.
In the end I formatted the SD card and done a fresh install and it’s been fine ever since.
I had small issuue yesteday and could not figure out why automatic rollback was happening every time I was attempting to upgrade 0.88.2 -> 0.89.1.
After going through list of breaking changes in release notes and few experiments I discovered that in my case problem was caused by trusted_networks related changes.
In configuration.yaml I moved trusted_networks block from http: where it was for very long time to auth_providers: like so:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:
- 127.0.0.1
- ::1
- 192.168.0.0/24
- fd00::/8
After that upgrade went smoothly.
I think authors of change could have done a better work to make this failure more descriptive in logs.