Update from 11.0 to 11.1 does nothing

[BebeMischa]

Describe the issue you are experiencing

Got a message, new version is available. Click install, everything looks like it is installing. After the automatic reboot HA comes back alive with still OS 11.0 installed and a message about new version.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

11.0

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1. Try installing 11.1 by clicking on install

3. ...

Anything in the Supervisor logs that might be useful for us?

All green, no errors to be seen

Anything in the Host logs that might be useful for us?

Nope

System information

## System Information

version | core-2023.10.5
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.11.5
os_name | Linux
os_version | 6.1.56
arch | x86_64
timezone | Europe/Amsterdam
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.33.0
Stage | running
Available Repositories | 1331
Downloaded Repositories | 32

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | true
-- | --
subscription_expiration | 20 november 2023 om 01:00
relayer_connected | true
relayer_region | eu-central-1
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | true
remote_server | eu-central-1-10.ui.nabu.casa
certificate_status | ready
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 11.0
-- | --
update_channel | stable
supervisor_version | supervisor-2023.10.1
agent_version | 1.6.0
docker_version | 24.0.6
disk_total | 219.4 GB
disk_used | 43.0 GB
healthy | true
supported | true
board | generic-x86-64
supervisor_api | ok
version_api | ok
installed_addons | Z-Wave JS (0.2.1), Mosquitto broker (6.3.1), Terminal & SSH (9.7.1), File editor (5.6.0), VLC (0.2.0), MariaDB (2.6.1), Studio Code Server (5.13.0), Samba Backup (5.2.0), TimescaleDB (3.0.2), DSMR Reader (1.10.2), Music Assistant BETA (2.0.0b73), Samba share (10.0.2), motionEye (0.19.1), Dutch gas prices (2023.10.15.1)

</details>

<details><summary>Dashboards</summary>

dashboards | 2
-- | --
resources | 21
views | 56
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 26 augustus 2023 om 21:33
-- | --
current_recorder_run | 26 oktober 2023 om 23:04
database_engine | mysql
database_version | 10.6.12

</details>

<details><summary>Sonoff</summary>

version | 3.5.3 (a8c6d45)
-- | --
cloud_online | 27 / 27
local_online | 27 / 27

</details>

<details><summary>Spotify</summary>

api_endpoint_reachable | ok
-- | --

</details>

Additional information

No response

[asayler]

And here's the about from rauc status:

# rauc status
=== System Info ===
Compatible:  haos-yellow
Variant:
Booted from: kernel.1 (B)

=== Bootloader ===
Activated: kernel.0 (A)

=== Slot States ===
  [boot.0] (/dev/disk/by-partlabel/hassos-boot, vfat, inactive)

x [kernel.0] (/dev/disk/by-partlabel/hassos-kernel0, raw, inactive)
        bootname: A
        boot status: good
    [rootfs.0] (/dev/disk/by-partlabel/hassos-system0, raw, inactive)

o [kernel.1] (/dev/disk/by-partlabel/hassos-kernel1, raw, booted)
        bootname: B
        boot status: good
    [rootfs.1] (/dev/disk/by-partlabel/hassos-system1, raw, active)

So it has Slot A marked as active, but still boots into Slot B each boot.

Any ideas? Maybe an issue with the bootloader?

[asayler]

Okay, tried yet another 11.4 update and this time I actually did see it attempt to Boot Slot A and fail to boot. This seems to be the critical bit where it abandons the boot attempt:

[  OK  ] Finished HassOS AppArmor.
         Starting Docker Application Container Engine...
[FAILED] Failed to start Docker Application Container Engine.
See 'systemctl status docker.service' for details.
[DEPEND] Dependency failed for HassOS supervisor.
[  OK  ] Removed slice Slice /system/modprobe.
[  OK  ] Stopped target HassOS hardware targets.
[  OK  ] Stopped target HassOS zram targets.

Full log from one of the failed boot attempts: ha_boot_11.4_failed.txt

Interestingly, the rauc status still marks Slot A as good/active, so perhaps that's just the way the u-boot rauc integration here works.

[asayler]

I went ahead and opened a new issue for the 11.4 docker error ^^^ since it seems to be unique enough from this issue to warrant it: #3074.

[petervk]

I'm still on haos 11.0 as I've never been able to successfully install anything newer. I've connected a monitor directly to my host (a dell 7040 micro) and watched it boot up and it seems to fail somewhere and go back to 11.0. I'm only able to access the last two boots using the commands provided. I tried to run "rauc" but I get a command not found error.

I've attached the output of the following two commands:

ha host logs -b -1 -n 10000 > /config/last-boot.log
ha host logs -b 0 -n 10000 > /config/current-boot.log

current-boot.log last-boot.log

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[petervk]

No, I still can't update the OS and wish there was some help to update it without reinstalling and restoring from a backup.

On Tue, Apr 30, 2024, 1:40 AM github-actions[bot] @.***> wrote:

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/operating-system/issues/2870#issuecomment-2084421697, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAIIH3P6MXYSZXI57BLWBDY74VGJAVCNFSM6AAAAAA6R4I7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGQZDCNRZG4 . You are receiving this because you commented.Message ID: @.***>

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.