# Tutorial Deploy System update Failure **URL:** \ **Category:** General Discussions\ **Tags:** raspberry-pi-4\ **Created:** [January 28, 2021, 11:30am UTC](https://hub.mender.io/t/tutorial-deploy-system-update-failure/3146 "2021-01-28T11:30:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![henrik\_go](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@henrik\_go](https://hub.mender.io/u/henrik_go)\ **Post date:** [January 28, 2021, 11:30am UTC](https://hub.mender.io/t/tutorial-deploy-system-update-failure/3146/1 "2021-01-28T11:30:06Z")
Hello Im trying to go through the Get Started tutorial on a Raspberry Pi 4, and reached the **Deploy a system update** step, where I get the following failure error: 2021-01-28 10:49:18 +0000 UTC info: Running Mender client version: 2.5.0 2021-01-28 10:49:18 +0000 UTC info: State transition: update-fetch [Download\_Enter] → update-store [Download\_Enter] 2021-01-28 10:49:19 +0000 UTC info: No public key was provided for authenticating the artifact 2021-01-28 10:49:19 +0000 UTC info: Opening device “/dev/mmcblk0p3” for writing 2021-01-28 10:49:19 +0000 UTC info: Native sector size of block device /dev/mmcblk0p3 is 512 bytes. Mender will write in chunks of 1048576 bytes 2021-01-28 10:52:48 +0000 UTC info: All bytes were successfully written to the new partition 2021-01-28 10:52:48 +0000 UTC info: The optimized block-device writer wrote a total of 3565 frames, where 4 frames did need to be rewritten (i.e., skipped) 2021-01-28 10:52:48 +0000 UTC info: Wrote 3737124864/3737124864 bytes to the inactive partition 2021-01-28 10:52:48 +0000 UTC info: State transition: update-store [Download\_Enter] → update-after-store [Download\_Leave] 2021-01-28 10:52:49 +0000 UTC info: State transition: update-after-store [Download\_Leave] → update-install [ArtifactInstall] 2021-01-28 10:52:49 +0000 UTC info: Enabling partition with new image installed to be a boot candidate: 3 2021-01-28 10:52:49 +0000 UTC info: State transition: update-install [ArtifactInstall] → reboot [ArtifactReboot\_Enter] 2021-01-28 10:52:49 +0000 UTC info: Rebooting device(s) 2021-01-28 10:52:49 +0000 UTC info: Mender rebooting from active partition: /dev/mmcblk0p2 2021-01-28 10:52:50 +0000 UTC info: Daemon terminated with SIGTERM 2021-01-28 10:53:07 +0000 UTC info: Running Mender client version: 2.5.0 2021-01-28 10:53:07 +0000 UTC info: State transition: init [none] → after-reboot [ArtifactReboot\_Leave] 2021-01-28 10:53:07 +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 2021-01-28 10:53:07 +0000 UTC info: State transition: after-reboot [ArtifactReboot\_Leave] → rollback [ArtifactRollback] 2021-01-28 10:53:07 +0000 UTC info: Performing rollback 2021-01-28 10:53:07 +0000 UTC info: No update available, so no rollback needed. 2021-01-28 10:53:07 +0000 UTC info: State transition: rollback [ArtifactRollback] → rollback-reboot [ArtifactRollbackReboot\_Enter] 2021-01-28 10:53:07 +0000 UTC info: Rebooting device(s) after rollback 2021-01-28 10:53:07 +0000 UTC info: Mender rebooting from inactive partition: /dev/mmcblk0p2 2021-01-28 10:53:08 +0000 UTC info: Daemon terminated with SIGTERM 2021-01-28 10:53:25 +0000 UTC info: Running Mender client version: 2.5.0 2021-01-28 10:53:25 +0000 UTC info: Mender shut down in state: rollback-reboot 2021-01-28 10:53:25 +0000 UTC info: State transition: init [none] → verify-rollback-reboot [ArtifactRollbackReboot\_Leave] 2021-01-28 10:53:25 +0000 UTC info: State transition: verify-rollback-reboot [ArtifactRollbackReboot\_Leave] → after-rollback-reboot [ArtifactRollbackReboot\_Leave] 2021-01-28 10:53:25 +0000 UTC info: State transition: after-rollback-reboot [ArtifactRollbackReboot\_Leave] → update-error [ArtifactFailure] 2021-01-28 10:53:25 +0000 UTC info: State transition: update-error [ArtifactFailure] → cleanup [Error] 2021-01-28 10:53:25 +0000 UTC info: State transition: cleanup [Error] → update-status-report [none] The Pi complains about failing to check for Raspberry Pi EEPROM updates This is the output of systemctl status rpi-eeprom-update.service: ● rpi-eeprom-update.service - Check for Raspberry Pi EEPROM updates Loaded: loaded (/lib/systemd/system/rpi-eeprom-update.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-01-28 10:58:21 GMT; 29min ago Process: 340 ExecStart=/usr/bin/rpi-eeprom-update -a (code=exited, status=2) Main PID: 340 (code=exited, status=2) Jan 28 10:58:20 raspberrypi systemd[1]: Starting Check for Raspberry Pi EEPROM updates… Jan 28 10:58:20 raspberrypi rpi-eeprom-update[340]: BCM2711 detected Jan 28 10:58:21 raspberrypi rpi-eeprom-update[340]: BOOTFS: “/boot” contains no .elf files Jan 28 10:58:21 raspberrypi systemd[1]: rpi-eeprom-update.service: Main process exited, code=exited, status=2/INVALIDARGU Jan 28 10:58:21 raspberrypi systemd[1]: rpi-eeprom-update.service: Failed with result ‘exit-code’. Jan 28 10:58:21 raspberrypi systemd[1]: Failed to start Check for Raspberry Pi EEPROM updates. Does anyone know what is going on? ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [January 29, 2021, 7:54pm UTC](https://hub.mender.io/t/tutorial-deploy-system-update-failure/3146/2 "2021-01-29T19:54:55Z")
It looks like the check for eeprom updates is failing as there are no files to be updated. Are you intentionally trying to update that? Drew ---
**Author:** ![henrik\_go](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@henrik\_go](https://hub.mender.io/u/henrik_go)\ **Post date:** [February 1, 2021, 9:56am UTC](https://hub.mender.io/t/tutorial-deploy-system-update-failure/3146/3 "2021-02-01T09:56:48Z")
Hello Drew No, im not trying to update eeprom. It is the standard mender rpi4 image, and I tried doing a system update by following the Getting Started Tutorial. So I dont understand what is going on? ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [February 1, 2021, 4:00pm UTC](https://hub.mender.io/t/tutorial-deploy-system-update-failure/3146/4 "2021-02-01T16:00:56Z")
Hmm. I wonder if that is a separate issue unrelated to Mender? How did you generate that log? Is it the Mender-specific log (ie journalctl -u mender-client) or the whole system log? My guess is that it’s the whole system log and the rpi-eeprom update error is a red herring. I _think_ the issue at hand is: `2021-01-28 10:53:07 +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` This can happen if the system has an issue during the first boot and it fails for some reason. Do you have a serial adapter? Can you provide a full serial log starting from when you initial the deployment until you get the error? That may help us spot something. Drew