# Mender OS artifact deployment shows - ArtifactVerifyReboot exits with status 1 **URL:** \ **Category:** General Discussions\ **Tags:** deployment\ **Created:** [January 27, 2026, 9:23am UTC](https://hub.mender.io/t/mender-os-artifact-deployment-shows-artifactverifyreboot-exits-with-status-1/8178 "2026-01-27T09:23:14Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sushil](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@sushil](https://hub.mender.io/u/sushil)\ **Post date:** [January 27, 2026, 9:23am UTC](https://hub.mender.io/t/mender-os-artifact-deployment-shows-artifactverifyreboot-exits-with-status-1/8178/1 "2026-01-27T09:23:14Z")
Hi, I’m using Mender rootfs-image OTA updates on a Rasp Pi 4. The provisioning image/mender artifact is built from an official Rasp Pi OS 64-bit Lite (Debian trixie) golden image using `mendersoftware/mender-convert:5.1.0`. Application update is working but during an OS update:The artifact downloads successfull then partition is written , the devices starts reboots, after reboot, the deployment always fails with: ```auto 2026-01-27 09:39:22.162 +0000 UTC info: Sending status update to server 2026-01-27 09:39:23.29 +0000 UTC info: Installing artifact... 2026-01-27 09:43:06.732 +0000 UTC info: Update Module output (stdout): ================ STATISTICS ================ 2026-01-27 09:43:06.753 +0000 UTC info: Update Module output (stdout): Blocks written: 45 2026-01-27 09:43:06.753 +0000 UTC info: Update Module output (stdout): Blocks omitted: 5995 2026-01-27 09:43:06.753 +0000 UTC info: Update Module output (stdout): Bytes written: 47185920 2026-01-27 09:43:06.754 +0000 UTC info: Update Module output (stdout): ============================================ 2026-01-27 09:43:07.445 +0000 UTC info: Sending status update to server 2026-01-27 09:43:07.745 +0000 UTC info: Sending status update to server 2026-01-27 09:43:08 +0000 UTC info: Calling `reboot` command and waiting for system to restart. 2026-01-27 09:43:08.096 +0000 UTC info: Termination signal received, shutting down gracefully 2026-01-27 09:46:07.787 +0000 UTC info: Running Mender client 5.0.3 2026-01-27 09:46:07.823 +0000 UTC info: The update client daemon is now ready to handle incoming deployments 2026-01-27 09:46:07.932 +0000 UTC error: Process returned non-zero exit status: ArtifactVerifyReboot: Process exited with status 1 2026-01-27 09:46:08.129 +0000 UTC info: Calling `reboot` command and waiting for system to restart. 2026-01-27 09:46:08.417 +0000 UTC info: Termination signal received, shutting down gracefully 2026-01-27 09:48:34.291 +0000 UTC info: Running Mender client 5.0.3 2026-01-27 09:48:34.326 +0000 UTC info: The update client daemon is now ready to handle incoming deployments 2026-01-27 09:48:34.48 +0000 UTC info: Sending status update to server ``` The device always boots back into the original rootfs, and the update is marked as failed. No explicit kernel or filesystem errors appear in system logs.What conditions must be satisfied for ArtifactVerifyReboot to succeed on Raspberry Pi rootfs-image updates? Thanks Sushil ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 27, 2026, 12:17pm UTC](https://hub.mender.io/t/mender-os-artifact-deployment-shows-artifactverifyreboot-exits-with-status-1/8178/2 "2026-01-27T12:17:33Z")
Hi @sushil, There is a 3 minute gap in your log: ```auto 2026-01-27 09:43:08.096 +0000 UTC info: Termination signal received, shutting down gracefully 2026-01-27 09:46:07.787 +0000 UTC info: Running Mender client 5.0.3 ``` A simple reboot should not take 3 minutes, so my guess is that there is something happening in between there. The most obvious thing would be **two** reboots, and the device not connecting to the server in between. So I’d suggest to watch a device which exhibits this behavior, and try to see what’s going on. Greetz, Josef ---
**Author:** ![sushil](https://avatars.discourse-cdn.com/v4/letter/s/e19adc/32.png) [@sushil](https://hub.mender.io/u/sushil)\ **Post date:** [January 28, 2026, 8:14am UTC](https://hub.mender.io/t/mender-os-artifact-deployment-shows-artifactverifyreboot-exits-with-status-1/8178/3 "2026-01-28T08:14:26Z")
@TheYoctoJester Yes, you are right thanks for the clue there is 2 reboots `1075:Jan 20 14:31:21 rc.local[858]: Please reboot ` `1077:Jan 20 14:31:22 systemd-logind[523]: The system will reboot now!` Its comes because I shrink my initial image using PiShrink and then used that image in mender-convert, PiShrink updates `/etc/rc.local` to expand the root filesystem on the first boot, then reboots to apply the partition and filesystem changes. For more details found a similar issue faced by user and discuss in mender community [https://hub.mender.io/t/there-is-an-extra-reboot-during-artifactreboot-and-it-causes-update-failure/3740/3?u=sushil](https://hub.mender.io/t/there-is-an-extra-reboot-during-artifactreboot-and-it-causes-update-failure/3740/3) Thanks Sushil ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [January 28, 2026, 8:32am UTC](https://hub.mender.io/t/mender-os-artifact-deployment-shows-artifactverifyreboot-exits-with-status-1/8178/4 "2026-01-28T08:32:04Z")
Thanks for the report @sushil, I’ll then mark this as solved. Greetz, Josef