Fedora I have to fsck every third time I wanna boot

Hello,
recently I’ve bought new RAM and everything was fine for few days.
In the mean time I’ve installed few stuff updated Fedora few times etc and now I have to
fsck manually on every boot.

Auto fsck shows “fsck failed with status code 4”.
Manual fsck on /dev/disk/by-uuid/[UUID] works and everything seems fine.
SMART is not showing any problems.
memtest is not showing any problems.

Basically I have same problem as this person:

Checking the man page for fsck (man fsck) tells me that status code 4 means Filesystem errors left uncorrected. When you ran fsck, did it report any errors?

1 Like

Ok, so this is in journal:

May 16 13:22:18 lapora systemd-fsck[569]: Fedora_30 contains a file system with errors, check forced.
May 16 13:22:27 lapora systemd-fsck[569]: Fedora_30: Inodes that were part of a corrupted orphan linked list found.
May 16 13:22:27 lapora systemd-fsck[569]: Fedora_30: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
May 16 13:22:27 lapora systemd-fsck[569]:         (i.e., without -a or -p options)
May 16 13:22:27 lapora systemd-fsck[569]: fsck failed with exit status 4.
May 16 13:22:27 lapora systemd-fsck[569]: Running request emergency.target/start/replace
May 16 13:22:27 lapora systemd[1]: systemd-fsck-root.service: Main process exited, code=exited, status=1/FAILURE
May 16 13:22:27 lapora systemd[1]: systemd-fsck-root.service: Failed with result 'exit-code'.
May 16 13:22:27 lapora systemd[1]: Failed to start File System Check on /dev/sda4.
May 16 13:22:27 lapora systemd[1]: Dependency failed for /sysroot.
May 16 13:22:27 lapora systemd[1]: Dependency failed for Initrd Root File System.
May 16 13:22:27 lapora systemd[1]: Dependency failed for Reload Configuration from the Real Root.

And here is picture of what is being fixed when fsck is ran manually:

Also I did not point out that I have to boot with filsystem mounted as “rw” for some reason. But I had to do it that way for quite a while, so I’m not sure if that’s separate problem.