please go back and edit/reformat your posts
highlight the output and then format it with the </> button
If you don’t format it, the # marks at the start of each line are interpreted as “print it big and bold”.
please go back and edit/reformat your posts
highlight the output and then format it with the </> button
If you don’t format it, the # marks at the start of each line are interpreted as “print it big and bold”.
Yep it starts every time.
Btw I don’t know about the font I just copy pasted
see my post - now you know
Let me see mm
Thanks for helping bro
Can you describe which screen / process this happens during?
Do you see the Manjaro logo (or your PC’s vendor logo) while it tells you it’s checking the file-system?
How long does it take? Can you actually see a percentage “progress” that eventually reaches 100%?
There is a way to disable it, either in the fstab or with mkinitcpio, but I think it’s better to figure out why it checks your file-system at every boot.
While in Manjaro, can you type:
sudo tune2fs -l /dev/sdxx | grep -i “last checked”
Replace sdxx with root partition.
This will tell you when the file-system was last checked.
This will hide yr file system check msg…just send it to another tty.
[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.
I don’t know how to do that see I’m newbie to manjaro so …
ok wait.
You can see a list of partitions with:
lsblk
or
cat /proc/partitions
[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
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
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
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.
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.