# Data partition not checked when fstab generated by mender-convert

**URL:** <https://hub.mender.io/t/data-partition-not-checked-when-fstab-generated-by-mender-convert/8197>\
**Category:** General Discussions\
**Tags:** debian\
**Created:** [February 19, 2026, 3:27pm UTC](https://hub.mender.io/t/data-partition-not-checked-when-fstab-generated-by-mender-convert/8197 "2026-02-19T15:27:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![iXo](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ixo/32/2658_2.png) [@iXo](https://hub.mender.io/u/iXo)\
**Post date:** [February 19, 2026, 3:27pm UTC](https://hub.mender.io/t/data-partition-not-checked-when-fstab-generated-by-mender-convert/8197/1 "2026-02-19T15:27:21Z")

</div>

Hi, I am quite new to mender, but I managed to create a Debian GOLD image and use mender-convert via docker on it.

I noticed that data partition in the fstab is declared like so :

```auto
/dev/sda4 /data auto defaults,x-systemd.growfs 0 0

```

I didn’t found how to make the last 0 to be a 2 to make the system pass the fsck.

I found this topic : [Boot partition not checked](https://hub.mender.io/t/boot-partition-not-checked/1591) but it seems that it was a correction for a tool that help create a gold image (?, sorry I am not sure where this PR changed something).

I can tweak the root\_a and root\_b fstab files in the .img file that mender-convert have generated, but doing the same for the .mender is way more difficult (even if I know it’s possible).

Is there a reason why the data partition is not fsck checked, or is there a way to make it so ?

Thanks for any help.