Why Manjaro Kde use fsck?

[frozen@frozen ~]$ sudo tune2fs -l / | grep -i “last checked”
grep: checked”: No such file or directory
[sudo] password for frozen: 
tune2fs: Is a directory while trying to open /
Couldn't find valid filesystem superblock.

Replace my sdxx with your actual root device/partition. Might be sda1, sda2, or etc.

1 Like

I don’t know how to do that see I’m newbie to manjaro so …:frowning:

ok wait.

You can see a list of partitions with:



cat /proc/partitions

1 Like
[frozen@frozen ~]$ sudo tune2fs -l /dev/sda2 grep -i “last checked”
tune2fs 1.46.2 (28-Feb-2021)
tune2fs: bad interval - “last
Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-f] [-g group]
        [-i interval[d|m|w]] [-j] [-J journal_options] [-l]
        [-m reserved_blocks_percent] [-o [^]mount_options[,...]]
        [-r reserved_blocks_count] [-u user] [-C mount_count]
        [-L volume_label] [-M last_mounted_dir]
        [-O [^]feature[,...]] [-Q quota_options]
        [-E extended-option[,...]] [-T last_check_time] [-U UUID]
        [-I new_inode_size] [-z undo_file] device

sudo nano /etc/default/grub

At the end of ‘grub cmdline linux default’ add ‘console=tty3’

Save and exit nano or ur text editor

sudo update-grub

How to save?

You typed it wrong. It’s missing a “pipe” before grep

Should be like this:

sudo tune2fs -l /dev/sda2 | grep -i “Last checked”

Ctrl+o then press enter then press ctrl+x

1 Like

Well I did typed it but nothing found

[frozen@frozen ~]$ sudo tune2fs -l /dev/sda2 | grep -i “last checked”
grep: checked”: No such file or directory
[sudo] password for frozen:
[frozen@frozen ~]$ sudo tune2fs -l /dev/sda2 | grep -i “last checked”
grep: checked”: No such file or directory

[frozen@frozen ~]$ cat /proc/partitions
major minor  #blocks  name

   8        0  488386584 sda
   8        1     307200 sda1
   8        2  479491009 sda2
   8        3    8583775 sda3
[frozen@frozen ~]$ lsblk
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0   300M  0 part /boot/efi
├─sda2   8:2    0 457.3G  0 part /
└─sda3   8:3    0   8.2G  0 part [SWAP]

Okay, so let’s just see how everything is configured for sda2, and you can change the “fsck” intervals to something less frequent. This might also help your boot-up times.

sudo tune2fs -l /dev/sda2

Forget the pipe or grep. Just make sure the text doesn’t get pasted in large font. :wink:

That’s a lowercase L in the command (as in “list”), not an upper-case i, by the way. On the forums, I and l look alike.

1 Like
[frozen@frozen ~]$ sudo tune2fs -l /dev/sda
[sudo] password for frozen: 
tune2fs 1.46.2 (28-Feb-2021)
tune2fs: Bad magic number in super-block while trying to open /dev/sda
/dev/sda contains `DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 976773167 sectors' data

sda2, not sda

Sorry, it’s late over here. Very sleepy. I made a typo.

1 Like
[frozen@frozen ~]$ sudo tune2fs -l /dev/sda2
[sudo] password for frozen: 
Sorry, try again.
[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:              115260083
Free inodes:              29680981
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 08:29:19 2021
Last write time:          Sun Apr 11 08:29:19 2021
Mount count:              8
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:       18489448
Default directory hash:   half_md4
Directory Hash Seed:      7192c4c0-fa8f-42b5-a44a-0eb02ced0df1
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x62334385

You’re saying you’ve seen a fsck on your root file system during bootup since that date/time?

1 Like

I think so, well I see Everytime I boot.

Are you able to reboot now, and come back here and redo

sudo tune2fs -l /dev/sda2

If the value for “Last checked” remains the same, it means you’re probably seeing something else during bootup.

By all accounts, according to tune2fs, it looks like automatic fsck has been disabled.

1 Like