Upgrade HAOS to 13.2 does nothing

Hello,
last week I’ve installed HAOS into a new RPI5 with an SD Card, and set a data disk to an external USB SSD
I’m now trying to upgrade from HAOS 13.1 to 13.2, but whenever I click on install, after some time the system reboots and I’m still on 13.1 with the upgrade notification.
I can’t see anything in logs, probably because the system is rebooted.

Any suggestion on how to properly upgrade?
Thank you

not much help, but I’ve just updated from 13.1 to 13.2 on PI5 without issue…so at least we know it works…

from past experience I think your Supervisor logs will tell you about maybe failed downloads, etc so in http://homeassistant.local:8123/hassio/system or similar (tho maybe that’s for Core only)

I’m under the impression that this is related to the usage of a microSD card plus an external SSD data disk.
Can it be that the installer is upgrading the SSD, but the system boots from the microSD card?

not really sure TBH so not of much help to you…
I run HAOS direct from a SSD so just installed direct to that from the start and bypassed the SD card, and thankfully haven’t had an issue…

looking here Behind the scenes of the "move data disk" feature it seems that the OS remains on the SD…

Anybody can help understand why there are 2 boot slots?
And how to understand if boot A and B are on SSD or SDCard?
I guess I’d better restart from scratch

➜  /config ha os info
board: rpi5-64
boot: A
boot_slots:
  A:
    state: booted
    status: good
    version: "13.1"
  B:
    state: inactive
    status: bad
    version: "13.2"
data_disk: Lexar-SSD-xxx
update_available: true
version: "13.1"
version_latest: "13.2"

The two boot slots are used for recovery if something goes wrong with an update. Boot loop 3 times → revert to previous slot.

Look at your logs to see what is going on as already suggested.

My guess is you have a DNS issue and the supervisor can not reach the download. This is what 99% of issues turn out to be.

Thank you for sharing! How do I access logs for slot B?

For some unknown reasons, executing the update via cli succeeded…

Could have just been a momentary github issue. Without logs we will never know :man_shrugging:

Indeed this is the case and a recommended way to run HA/HA OS (hybrid mode), as you will avoid all the issues so many users run into when booting from an external SSD and performing HA OS upgrades.

cheers…knew that…was being “nice” to OP rather than just saying RTFM :smiley:

FWIW I’ve run HAOS on one of these https://www.amazon.co.uk/SanDisk-Extreme-128GB-Solid-State/dp/B01MU8TZRV on various PI models without issue for last~4 years (and hopefully not jinxing it now by saying it out loud)