That's not good. Download Manjaro install CD and boot from it.

man e2fsck: linux.die.net/man/8/e2fsck

What a weird distro. OK, download and run system-rescue-cd.org/Download

In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux. The filesystem-specific checker is searched for in the PATH environment variable. If the PATH is undefined then fallback to "/sbin". Please see the filesystem-specific checker manual pages for further details.

Assuming you've already run e2fsck/fsck, you could now mount your EFI system partition and check whether GRUB has the correct UUID specified for your root FS.

I am out of ideas. Maybe you could upload a picture of the error.

No, your display when you're getting it. Also it would be great if you enabled verbose boot/disabled graphical boot.

Sorry, I've no ideas any longer. As a last resort you could try rebuilding your initrd but that's gonna be quite complicated. You need to mount rootfs /boot and /boot/efi, then mount bind /proc /sys and /dev into rootfs, then chroot into it, then run the command which rebuilds initrd.

I have uploaded a video of the boot here. Hope it helps. There's one more warning before the error, which says cannot change data node on remount. Maybe that'll help?

Erm, your system looks to have booted successfully into the graphical login manager - I'm not sure if you're still having any issues :-)

It does boot. That's what I am more puzzled about. It is not supposed to. I have said so in the question too: The system boots, but with an error Failed to start Remount Root and Kernel File Systems

Then I'd simply ignore the issue :-) It doesn't seem to be affecting you in any shape or form.

Who knows? It might just be a bomb waiting to explode ;). I have learnt that one is not supposed to assume that the error is not affecting one, the hard way ;)

Also, are rw,noatime,nodelalloc,data=writeback options correct? It might be that these options are causing the issue

It's unlikely. If I were you, I'd file a bug report against Manjaro - let the devs look into it. :-) I'd reduce it to just defaults,noatime. rw is redundant. nodelalloc makes things worse actually ( kernel.org/doc/Documentation/filesystems/ext4.txt ), data=writeback also looks wrong. If you have an SSD then having ,discard is a must.

Hmm.

So, you mean that my fstab should look like:

Its an HDD

Yep, looks correct and as I said if you have SSD, then you must add ,discard as well

do no discard?

and what actually is 0 1?

you don't need discard then

man fstab - don't want to repeat what's explained there :-)

Ah right ;)

For all other partitions I have 0 2

I have 0 0

read the manual you'll understand these digits

lemme reboot and check.

Also for partitions which are not crucial for booting I have ,nofail specified

In my case I have this option specified for all partitions except the rootfs

Ironically, rw is an option in default

you meant defaults

yeah

Defaults

It is

That's why I prefer to use defaults

hmm

lemme reboot and check

Out of all Linux distros, Fedora/RHEL/CentOS seem the sanest for me

and safest as well :) Not Fedora 33 unfortunately which is going to be released in a few months - they've decided to use BTRFS by default

Solved :)

Solved what? ;-)

No issue now

OMG

Yeah

I know

How stupid I've been

Where did those mount options come from?

Auto generated

Stupid manjaro I'd say, lol

I'm glad it's helped

Hey. Dare you call Arch stupid... grrr... XD

@ArtemS.Tashkinov Yeah. Thanks a lot

You're welcome :-)

Why don't you edit your answer so that I can accept it?

Now we know well what the error was

I'm doing it now

Don't forget to delete all the comments ;)

Done

Great

Just delete those comments now

they seem irrelevant, now that I've deleted mine :)

Nice :)

Well, there's another issue too

Do you want me to post it as a question or this chat will do?

Please describe it as shortly as possible and we'll see

Errm.. well

All my Linux systems, even live booted ones

when shutting down

give an error saying: watchdog0 did not stop

Ah, that's an ages old issue

Just disregard it

Ah well okay then

Anyways, gotta work now

Linux doesn't properly support too many devices including HW watchdogs

It should

You may want developers to know about that at bugzilla.kernel.org

actuall

*y

But I filed a bug report about mine 4 years ago and no one give a flying f

You may want to read the article: itvision.altervista.org/… :-)

Will be filing a bug report after lunch. (Food calling d4rk4ng31 the fatso). Thanks again for your help :)

@ArtemS.Tashkinov yeah I did

You're welcome

Bye

Also the one about antivirus

yeah?

that one's good

Which one?

People do overlook the fact

Ah, right

itvision.altervista.org/…

Well anyways, bye for now :)

Goodbye :-)

Nice chatting with you :)

Likewise

Byee

If you could post the article about AV to reddit/r/Linux I'd be thankful

I've tried to submit it three times but each time some overzealous moderator rejected it

For some weird reasons

Linux fans and fans in general are often very irrational and biased