Transient error: Reboot to the new update failed. Active partitions unclear

Hi everyone,

we do have sporadic issues with the deployment during a system update.

Can anyone help me understand the active partitions of each boot? Especially the active partition during the “after-reboot [ArtifactReboot_Leave]” phase. Please see the full deployment logs below.

I assume, that the switch of partitions was unsuccessful as suggested in the error message:
“Reboot to the new update failed. Expected “upgrade_available” flag to be true but it was false. Either the switch to the new partition was unsuccessful, or the bootloader rolled back”

Sadly there is no log line with shows the active partition during [ArtifactReboot_Leave].

However there’s a confusing log line in [ArtifactRollbackReboot_Enter]
“Mender rebooting from inactive partition: /dev/mmcblk2p2”

Can anyone confirm that device rebooted into partition /dev/mmcblk2p2 instead of /dev/mmcblk2p3?

2023-10-17 14:16:21 +0000 UTC info: Running Mender client version: 3.4.0
2023-10-17 14:16:22 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2023-10-17 14:16:22 +0000 UTC info: No public key was provided for authenticating the artifact
2023-10-17 14:16:22 +0000 UTC warning: Installer: Installing signed artifact without verification as verification key is missing
2023-10-17 14:16:22 +0000 UTC info: Opening device "/dev/mmcblk2p3" for writing
2023-10-17 14:16:22 +0000 UTC info: Native sector size of block device /dev/mmcblk2p3 is 512 bytes. Mender will write in chunks of 1048576 bytes
2023-10-17 14:19:08 +0000 UTC info: All bytes were successfully written to the new partition
2023-10-17 14:19:08 +0000 UTC info: The optimized block-device writer wrote a total of 1145 frames, where 527 frames did need to be rewritten (i.e., skipped)
2023-10-17 14:19:08 +0000 UTC info: Wrote 1199570944/1199570944 bytes to the inactive partition
2023-10-17 14:19:08 +0000 UTC info: State transition: update-store [Download_Enter] -> update-after-store [Download_Leave]
2023-10-17 14:19:08 +0000 UTC info: State transition: update-after-store [Download_Leave] -> mender-update-control-refresh-maps [none]
2023-10-17 14:19:08 +0000 UTC info: State transition: mender-update-control-refresh-maps [none] -> mender-update-control [none]
2023-10-17 14:19:08 +0000 UTC info: State transition: mender-update-control [none] -> update-install [ArtifactInstall]
2023-10-17 14:19:08 +0000 UTC info: Enabling partition with new image installed to be a boot candidate: 3
2023-10-17 14:19:09 +0000 UTC info: State transition: update-install [ArtifactInstall] -> mender-update-control-refresh-maps [none]
2023-10-17 14:19:21 +0000 UTC info: State transition: mender-update-control-refresh-maps [none] -> mender-update-control [none]
2023-10-17 14:19:21 +0000 UTC info: State transition: mender-update-control [none] -> reboot [ArtifactReboot_Enter]
2023-10-17 14:19:21 +0000 UTC info: Rebooting device(s)
2023-10-17 14:19:21 +0000 UTC info: Mender rebooting from active partition: /dev/mmcblk2p2
2023-10-17 14:19:55 +0000 UTC info: Running Mender client version: 3.4.0
2023-10-17 14:19:55 +0000 UTC info: State transition: init [none] -> after-reboot [ArtifactReboot_Leave]
2023-10-17 14:19:55 +0000 UTC error: transient error: Reboot to the new update failed. Expected "upgrade_available" flag to be true but it was false. Either the switch to the new partition was unsuccessful, or the bootloader rolled back
2023-10-17 14:19:55 +0000 UTC info: State transition: after-reboot [ArtifactReboot_Leave] -> rollback [ArtifactRollback]
2023-10-17 14:19:55 +0000 UTC info: Performing rollback
2023-10-17 14:19:55 +0000 UTC info: No update available, so no rollback needed.
2023-10-17 14:19:55 +0000 UTC info: State transition: rollback [ArtifactRollback] -> rollback-reboot [ArtifactRollbackReboot_Enter]
2023-10-17 14:19:55 +0000 UTC info: Rebooting device(s) after rollback
2023-10-17 14:19:55 +0000 UTC info: Mender rebooting from inactive partition: /dev/mmcblk2p2
2023-10-17 14:19:54 +0000 UTC info: Running Mender client version: 3.4.0
2023-10-17 14:19:54 +0000 UTC info: Mender shut down in state: rollback-reboot
2023-10-17 14:19:54 +0000 UTC info: State transition: init [none] -> verify-rollback-reboot [ArtifactRollbackReboot_Leave]
2023-10-17 14:19:55 +0000 UTC info: State transition: verify-rollback-reboot [ArtifactRollbackReboot_Leave] -> after-rollback-reboot [ArtifactRollbackReboot_Leave]
2023-10-17 14:19:55 +0000 UTC info: State transition: after-rollback-reboot [ArtifactRollbackReboot_Leave] -> update-error [ArtifactFailure]
2023-10-17 14:19:55 +0000 UTC info: State transition: update-error [ArtifactFailure] -> cleanup [Error]
2023-10-17 14:19:55 +0000 UTC info: State transition: cleanup [Error] -> update-status-report [none]
2023-10-17 14:19:55 +0000 UTC info: Device unauthorized; attempting reauthorization
2023-10-17 14:19:55 +0000 UTC info: Output (stderr) from command "/usr/share/mender/identity/mender-device-identity": using interface /sys/class/net/eth0
2023-10-17 14:19:55 +0000 UTC info: successfully received new authorization data from server <server>
2023-10-17 14:19:55 +0000 UTC info: Local proxy started
2023-10-17 14:19:55 +0000 UTC info: Reauthorization successful

Kind regards

3 Likes

Hi,
I got same random error messages with “No update available, so no rollback needed”, which makes update to actually stay on device.
For me, update is fully applied and working, but reported as failed to Mender server.