Trouble updating to 0.88/0.88.1

Little background first, I have Hass.io(v. 0.87.1) running in an Ubuntu VM with external access set up via the DuckDNS add-on.

I can’t seem to get the system to update to the latest releases. When I attempt the update process I get the following lines in the log:

19-02-22 13:42:28 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.1
19-02-22 13:42:28 INFO (SyncWorker_0) [hassio.docker.interface] Update Docker homeassistant/qemux86-64-homeassistant:0.87.1 to homeassistant/qemux86-64-homeassistant:0.88.1
19-02-22 13:42:28 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.88.1.
19-02-22 13:43:44 ERROR (SyncWorker_0) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.88.1 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.88.1: No such image: homeassistant/qemux86-64-homeassistant:0.88.1").
19-02-22 13:43:45 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running!
19-02-22 13:43:45 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.1

The 404 error I think bothers me the most. I have tried to perform the update via the local IP as well as the using the DuckDNS address. Neither one seems to work. I have been able to update in the past. I even doublechecked to make sure the VM had enough available storage space as a stab in the dark.

Thanks

1 Like

TLDR: I had the same issue. My vdisk had enough space, but my data partition was not expanded to utilize that space. I deleted the database file, updated, then expanded the data partition and made sure hassos could read the actual vdisk size.

I was experiencing the same issues and have unsuccessfully tried the same. No joy.

19-02-22 21:28:26 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.1
19-02-22 21:30:25 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.1
19-02-22 21:30:25 INFO (SyncWorker_4) [hassio.docker.interface] Update Docker homeassistant/qemux86-64-homeassistant:0.87.1 to homeassistant/qemux86-64-homeassistant:0.88.1
19-02-22 21:30:25 INFO (SyncWorker_4) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.88.1.
19-02-22 21:30:33 ERROR (SyncWorker_4) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.88.1 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.88.1: No such image: homeassistant/qemux86-64-homeassistant:0.88.1").
19-02-22 21:30:33 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running!
19-02-22 21:30:33 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.1

Additionally, pulling new images also rendered 404

19-02-22 22:28:33 INFO (MainThread) [hassio.addons.addon] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_unifi
19-02-22 22:28:33 INFO (SyncWorker_3) [hassio.docker.interface] Pull image hassioaddons/unifi tag 0.7.0.
19-02-22 22:28:51 ERROR (SyncWorker_3) [hassio.docker.interface] Can't install hassioaddons/unifi:0.7.0 -> 404 Client Error: Not Found ("no such image: hassioaddons/unifi:0.7.0: No such image: hassioaddons/unifi:0.7.0").

Furthermore the system seemed to have dropped my ESPHome container and I was unable to communicate with any sonos speakers. I will continue troubleshooting tomorrow.

System Health System Health
arch x86_64
dev false
docker true
hassio true
os_name Linux
python_version 3.6.6
timezone Europe/Oslo
version 0.87.1
virtualenv false

Lovelace

mode storage
resources 1
views 3
2019-02-22 23:39:08 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (sqlite3.OperationalError) database or disk is full [SQL: 'DELETE FROM states WHERE states.last_updated < ?'] [parameters: ('2019-02-12 22:38:23.001444',)] (Background on this error at: http://sqlalche.me/e/e3q8)
2019-02-22 23:39:08 WARNING (Recorder) [homeassistant.components.recorder.purge] Error purging history: (sqlite3.OperationalError) database or disk is full [SQL: 'DELETE FROM states WHERE states.last_updated < ?'] [parameters: ('2019-02-12 22:38:23.001444',)] (Background on this error at: http://sqlalche.me/e/e3q8).

I tried deleting home-assistant_v2.db and rebooting the host system which made the system drop all z-wave components. I forced a manual system update from the Hass.io menu which updated my system.

19-02-22 22:49:24 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.1
19-02-22 22:49:24 INFO (SyncWorker_3) [hassio.docker.interface] Update Docker homeassistant/qemux86-64-homeassistant:0.87.1 to homeassistant/qemux86-64-homeassistant:0.88.1
19-02-22 22:49:24 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.88.1.
19-02-22 22:49:57 INFO (SyncWorker_3) [hassio.docker.interface] Tag image homeassistant/qemux86-64-homeassistant with version 0.88.1 as latest
19-02-22 22:49:57 INFO (SyncWorker_3) [hassio.docker.interface] Stop homeassistant/qemux86-64-homeassistant Docker application
19-02-22 22:50:27 INFO (SyncWorker_3) [hassio.docker.interface] Clean homeassistant/qemux86-64-homeassistant Docker application
19-02-22 22:50:27 INFO (SyncWorker_3) [hassio.docker.interface] Cleanup Docker images: ['homeassistant/qemux86-64-homeassistant:0.87.1']
19-02-22 22:50:30 INFO (SyncWorker_2) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.88.1
19-02-22 22:50:40 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-02-22 22:50:40 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.1

I was now running 0.88.1 I forced another reboot which seemed to crash the whole VM resulting in a manual hypervisor initiated reset. Once complete, hassio came back online showing version 0.88.1 and all my z-wave devices back in play.

As this was clearly a space issue i put the following into configuration.yaml

sensor:
  - platform: systemmonitor
    resources:
      - type: disk_free
        arg: /home
      - type: memory_free

Which didn’t really work at all, but I got the disk_use working, which states usage in percent. Reported percent was 46.1% this was wrong. The hypervisor reported 9% drive usage. It is using 5,55 GB of 61 gb available.

I am guessing my issue has to do with some internal partitioning as i expanded the drive after i experienced these errors. I will continue troubleshooting tomorrow.

Update: I booted GNOME partition editor live CD and expanded the partition containing data successfully. Everything is normal and apparently working for me. I expanded stuff some more since i was already “in there”. Ended up with a 100 gb vdrive and 2.5% current disk usage.

Are you able to verify drive space from within the image @mchiass ? If not, see if you can delete something to free up space and see if it helps? Maybe Ubuntu is reporting same available space as the hypervisor/vdisk?

1 Like

Thanks a bunch. Deleting the db file did it. Somehow it was over 4 gig in size.