I was reading about hecking the filesystem /

 

Seems the way is: touch /forcefsck

 

But this action does not fix, so we need 'somewhere': fsck.repair=yes

 

How do i have to do it?

 

Thanks.

Hi, you can start here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system

 

1 hour ago, Tido said:

Hi, you can start here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system

 

 

Thanks, but this is not the goal.

 

The goal is to fix any corrupt file at next startup sequence, damage done by an unexpected power off.

 

Already done in other OS, like dietPi or ubuntu on legacy kernels, but don't know the procedure here.

 

The target is an armbian set up on a hard-to-reach place, and i need reliability.

 

Thanks again.

1 hour ago, garfius said:

and i need reliability.

Check "man tune2fs", there the option "-c <n>" to call fsck.ext4 every "n" reboot.

2 hours ago, martinayotte said:

Check "man tune2fs", there the option "-c <n>" to call fsck.ext4 every "n" reboot.

Thanks!

 

The working commands:

#--locate which partition--
df -h
#--set check interval--
tune2fs -l /dev/mmcblk0p1
tune2fs -i 2 /dev/mmcblk0p1
tune2fs -c -1 /dev/mmcblk0p1

To check FS every boot:

tune2fs -l /dev/mmcblk0p1
tune2fs -i 1 /dev/mmcblk0p1
tune2fs -c 1 /dev/mmcblk0p1

 

2 hours ago, martinayotte said:

Check "man tune2fs", there the option "-c <n>" to call fsck.ext4 every "n" reboot.

But this only seems to check, not repair.

 

https://unix.stackexchange.com/questions/400851/what-should-i-do-to-force-the-root-filesystem-check-and-optionally-a-fix-at-bo

Says:

This DID a check, but to force a fix too, you need to specify fsck.repair="preen", or fsck.repair="yes

 

But not where to write this commands...

17 hours ago, garfius said:

But not where to write this commands...

Maybe you can try to add the line "extraargs=fsck.mode=force" into /boot/armbianEnv.txt and reboot.

This is a necro of an old threat, but my question fits perfectly:

I did like @garfius mentioned and changed my tune2fs setup to check my SD on every boot:

tune2fs -l /dev/mmcblk0p1
tune2fs -i 1 /dev/mmcblk0p1
tune2fs -c 1 /dev/mmcblk0p1

 

Now when I boot, fsck commences, but the system resets back to uboot after roughly 2 minutes and 10 seconds, give or take some seconds.

 

I tried adjusting the timeout in /etc/systemd/system.conf - but it doesn't change the issue.

 

Is there a way to prolong a potential boot timeout, prolong the boot time, due to a very long fsck?

It should be followed with fsck.repair=yes

BTW it causes lot of problems when you have lots of boars suddenly powered off.

Thanks a lot, It worked for me.

 

You should add `extraargs=fsck.mode=force fsck.repair=yes` to `/boot/armbianEnv.txt` to force scan and automatically fix file system problems. otherwise It just scan and break boot sequence into intfs console and you should manually enter the command.    

 

Finial instruction :

 

1) Set fsck to scan on every boot:

tune2fs -c 1 /dev/mmcblk0p1

 

2) Add bellow line to `/boot/armbianEnv.txt`

extraargs=fsck.mode=force fsck.repair=yes

 

 

Edited August 13, 20242 yr by mss

Please help me solve this problem.
After the power went out, I received this error.

 

 

6 minutes ago, wwwi64 said:

Please help me solve this problem.
After the power went out, I received this error.

You are not using Armbian but a fork. Ask where you got the image from. We don't support 3rd party OS.

4 часа назад, Werner сказал:

You are not using Armbian but a fork. Ask where you got the image from. We don't support 3rd party OS.

I didn't know it wasn't the original.

But even if it's a fork, maybe you can still help based on the original...

 

amlogic-s9xxx-armbian

No. This fork uses the name Armbian without permission and they do not contribute to the core development process. Instead they trick you into thinking that you'd get any sort of support here at our place whatsoever.