# \[Feature Request\] fixing "dirty" filesystem automatically

**URL:** <https://community.ipfire.org/t/feature-request-fixing-dirty-filesystem-automatically/3941>\
**Category:** Installing & Running IPFire\
**Created:** [3 December 2020 09:55 UTC](https://community.ipfire.org/t/feature-request-fixing-dirty-filesystem-automatically/3941 "2020-12-03T09:55:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![devaux](https://community.ipfire.org/user_avatar/community.ipfire.org/devaux/32/2414_2.png) [@devaux](https://community.ipfire.org/u/devaux)\
**Post date:** [3 December 2020 09:55 UTC](https://community.ipfire.org/t/feature-request-fixing-dirty-filesystem-automatically/3941/1 "2020-12-03T09:55:52Z")

</div>

Hi there,  
Having some APU-based devices running with IPFire and facing sometimes the problem of non-booting system after power fail.  
Running fsck -fy /dev/sda3 always fixed this problem within seconds. But as i am using APU-based devices without in- or output, it’s a bit annoying.

As a workaround i added

> fsck.mode=force fsck.repair=yes

into /etc/default/grub  
Not sure if this will solve the problem permanentely or there are some more elegant solutions.

**EDIT:** After forcing multiple reboots, it looks like this “solution” doesn’t work.

Now trying with adding

> FSCKFIX=yes

to /etc/default/rcS