Why Manjaro Kde use fsck?

[frozen@frozen ~]$ sudo tune2fs -l /dev/sda2
[sudo] password for frozen: 
tune2fs 1.46.2 (28-Feb-2021)
Filesystem volume name:   <none>
Last mounted on:          /
Filesystem UUID:          e39a313c-b400-489e-924d-db45ae47bddc
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              29974528
Block count:              119872752
Reserved block count:     5993637
Overhead clusters:        2162364
Free blocks:              115255617
Free inodes:              29680773
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Fri Apr  9 14:39:57 2021
Last mount time:          Sun Apr 11 09:30:29 2021
Last write time:          Sun Apr 11 09:30:29 2021
Mount count:              9
Maximum mount count:      -1
Last checked:             Fri Apr  9 14:40:16 2021
Check interval:           0 (<none>)
Lifetime writes:          33 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
First orphan inode:       18483078
Default directory hash:   half_md4
Directory Hash Seed:      7192c4c0-fa8f-42b5-a44a-0eb02ced0df1
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0xc3bff6a4

Your file-system has never been fsckā€™d since you first created it, and it remains that way even now after you rebooted.

Maybe youā€™re seeing something else during bootup?

1 Like

No Iā€™m sure itā€™s fsck.

How come? Iā€™m genuinely confused. You can even see sda2 has only been fsckā€™d once, and that was just after you initially created it. Ever since then, itā€™s never been checked.

Your flags for -c (based on maximum mounts) and -i (based on time intervals) have also been disabled.

So Iā€™m not sure what youā€™re seeing at bootup.

1 Like

give me 5min iā€™ll find a example :slight_smile:

This is the message i gets everytime. X means numbers I didnā€™t include them :slight_smile:

/dev/sda2: clean, XXXXXX/XXXXXXXX files, XXXXXXX/XXXXXXXXX blocks

Here go for example :slight_smile:

I donā€™t see the problem, though? Itā€™s telling you that sda2 is clean (and was cleanly unmounted).

Is the bootup process notably slower during this time, as if itā€™s running through a full file-system check?

1 Like

Itā€™s slow down the boot time.
This is the only message i see during boot nothing else.
This shows like for 10 seconds then boot into manjaro kde login screen.

Iā€™m not sure that it is slowing the boot time down.

When that message appears, the check is already done - as the message says.

But, as has been said, your filesystem has never actually been checked since it was created.

btw:
You where asked to provide the contents of:

/etc/default/grub

but you never did.

cat /etc/default/grub

Unless you explicitly configure your filesystem to be checked every x times you boot your machine or every x days ā€¦ it will only be checked on existent errors - and probably not even then, if
/etc/default/grub
is not configured correctly.

To force a filesystem check once every 20 times the system is started, issue this command:

sudo tune2fs -c 20 /dev/sda2

Iā€™d recommend that or an even lower interval -
until you are sure that the filesystem check initiated by Grub actually can work in case it is needed.
The check (and possible repair) just takes a few seconds.
The consequences of a corrupted filesystem are nasty.

1 Like

What this command does?
Youā€™re saying it scans file system every 20min.
It will use lots of resources.

Are you even reading what people write?

3 Likes

Yes I do, But I have to know the impacts about what a command does before executing. :blush:

Read then.

Also most programs have man pages, or help switches

man command

command --help

1 Like

Iā€™ve read it but Iā€™ve got no idea about the impacts.

1st decide what do u want 2 do.
U want to hide the fsck msg or what?!
If u want to hide them then the solutions are already there in the forum & also in this conversation.

But I donā€™t wanna execute a command that runs every 20min :frowning:

It activates a feature in the filesystem itself, forcing it to be checked every x times the filesystem is mounted - basically: every x times you boot your machine.

man tune2fs
the -c option is the first one to be explained in that manual page

no, I did not say that
man tune2fs
the -c option
it checks every x times ā€¦ blah, blah - see above

no, it wonā€™t

1 Like

That says after 20 times u restart ur system

1 Like

That is not what the effect of the command will be.
You got to take some time to read and comprehend - also the references given.

1 Like

So what exactly do I have to do? I have no idea what @Nachlese talking about.
See Iā€™m new to linux. :pleading_face:
And also no programming knowledge :sob: