# Suggestions for scenarios for failed system update

**URL:** https://hub.mender.io/t/suggestions-for-scenarios-for-failed-system-update/6029
**Category:** General Discussions
**Created:** [July 26, 2023, 9:10am UTC](https://hub.mender.io/t/suggestions-for-scenarios-for-failed-system-update/6029 "2023-07-26T09:10:42Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mister\_kanister](https://avatars.discourse-cdn.com/v4/letter/m/8edcca/32.png) [@mister\_kanister](https://hub.mender.io/u/mister_kanister)
#### Post date: [July 26, 2023, 9:10am UTC](https://hub.mender.io/t/suggestions-for-scenarios-for-failed-system-update/6029/1 "2023-07-26T09:10:42Z")

</div>

Good day friends!

I’ve implemented a custom update module for system updates due to limitations in my setup.  
Now I’m testing scenarios for a failed update to test my module.  
So far I’ve tested this scenarios I could recover from  
- Interrupt download (ArtifactDownload)  
- Interrupt installation (ArtifactInstall)  
- Corrupted .ext4 was installed  
I write an image.ext4 from artifact.mender with `ddrescue` tool to the B partition.

**Which other scenarios could I encounter?**

**Which test could I perform in ArtifactCommit phase to make sure my OS is working properly?**

PS:  
After I performed my first system update I see the kernel messages regarding my data partition. It happens consistently around 300s after boot.

```auto
EXT4-fs error (device mmcblk1p3): ext4_mb_generate_buddy:802: group0, block bitmap and bg desciptor inconsistent: 13761 vs 13762 free clusters
EXT4-fs (mmcblk0p3): error count since last fsck: 12
EXT4-fs (mmcblk0p3): initial error at time 1690279206: ext4_mb_generate_buddy:802
EXT4-fs (mmcblk0p3): last error at time 1690279206: ext4_mb_generate_buddy:802

```

System seems to run fine.

Thanks in advanced!