19-08-29 10:29:12 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.98.0
19-08-29 10:29:12 INFO (SyncWorker_0) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.97.2 to homeassistant/qemux86-64-homeassistant:0.98.0
19-08-29 10:29:12 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.98.0.
19-08-29 10:31:00 ERROR (SyncWorker_0) [hassio.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.98.0 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.98.0: No such image: homeassistant/qemux86-64-homeassistant:0.98.0”).
19-08-29 10:31:00 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
After two previously working installations succumbed to this particular issue I went to wipe and rebuild a third time, but I have yet to have a successful install since then. In other words, I flash my SD card, add a CONFIG/network/my-network file, and plug it into my 3B+ Pi. I’m able to get it to respond to pings, so I have network, but Home Assistant never comes up.
I’ve done this now more than half dozen times, with three separate SD cards (two SanDisk 32GB Ultra Plus cards and one 64GB SanDisk Extreme Plus). About half the time I don’t get anything when I visit 192.168.1.34:8123 and the other half of the time the process hangs on “Processing Hass.io”. I waited for several hours before finally giving up and checking the logs.
Every time I plug it into a monitor and check logs it’s always readlink /mnt/data/docker/overlay2/l: invalid argument. Most of the time it’s the supervisor container, but other times it’s the actual home assistant container, which explains why sometimes I get nothing on port 8123, and sometimes I get the “Processing” page.
What could be causing this constant Docker filesystem corruption? Why is Linux able to run with no issues, but Docker is so incredibly flakey? I’m about to give up on Hass completely as I can’t even get a base install up and running.
There’s a new repair command for that particular issue, but I have no idea why you would hit it so soon on a fresh install. Are you using the HassOS based images for your board or are you installing some alternative way?
I have indeed been installing the HassOS based image. I believe the 32 bit version for the Raspberry Pi 3B+. I would use balenaEtcher to flash hassos_rpi3-2.12.img.gz onto my SD card, remove and reinsert it in order to save a CONFIG/network/my-network on there, and then took the SD card and put it into the Pi and plugged it in. I was always able to ping the device, and sometimes I got the “Processing” screen, but never a successful install.
Anyway, the good news is that I was finally able to make progress! After having tried pretty much every else before going back to Hassbian, I decided to make one last attempt by swapping out power supplies again. Although I’d tried multiple USB chargers (and successfully run on one of them for months), I went ahead and got a fast charger and plugged into that. Sure enough, my install was successful and I’m finally able to turn on/off my bathroom lights again!
I was completely stable when running Linux, no restarts or reboots like when I’ve run off an inadequate charger in the past; given this experience though, I suspect that Docker is extra sensitive to any power delivery issues. It could have just been a fluke, but if anyone else is experiencing issues with readlink /mnt/data/docker/overlay2/l: invalid argument, make sure you are using a quality 2.5A USB charger. I’ve also plugged my device into a UPS so hopefully I won’t get corrupted by a brief power outage either.
This happened to me again (3rd or 4th time?) and I limped along with sporadic freezes and reboots and no updates for several months. I broke down and ordered a fancy new “high endurance” card. The day it was to be delivered, I was tinkering and tried the update a few times and it worked. It’s been running fine ever since. I still haven’t set up the new card, but I do take regular backups when I’m making changes.
I just got caught up with this thread and will be saving this one for next time…
So, you could procrastinate and then order a new card and see what happens
Same issue here with a brand new card with a brand new 3.8 Hassio downloaded 1/24/2020 because I couldn’t upgrade my previous version. Ran su repair with no success. Between emulated Hue issues and now this, I am losing a lot of faith in HA.
I was running Home Assistant 0.98.4 and wanted upgrade my addons (configurator, MQTT, Samba, etc.). The updates would fail with the Server 500 error. I then tried to upgradefrom .98.4 to 0.104.3. This also received the 500 errors. So I got a new card and did a new install of 0.104.3. Any attempt to do an upgrade or install any add-ons, caused the server 500 error.
@cogneato - I did figured out what my new install failed to install add-ons. Pilot Error
On my router I had bound an old Pi to the IP address I tried to use for the new Pi. I never did figure out why I could not upgrade my old .98 install that had another IP address and I had been able to do upgrades in the past. I will focus on the new install and use this from now on. Thank you for working with me.
