Perhaps you should check the contents of this file to find the exact cause of the failure.
Or you can try to manually force the file system check.
Use Live USB if necessary.
Glad to hear you were able to clear up the problem.
You should be aware, however, that the -c option to fsck (or, actually, to e2fsck, the filesystem scanner for ext{2,3,4}-type filesystems) adds a bad-block test to the scan, and excludes any blocks with read errors from active use.
Bad blocks normally shouldn’t occur on a filesystem, and their appearance can be warning signs of failing storage hardware. On a spinning-platter hard drive, the media can degrade so that a few bad blocks today become hundreds, then thousands… And on an SSD, they really shouldn’t happen at all unless the flash storage is nearing the end of its useful lifetime. In either case, replacing the hardware to avoid data loss is usually a good idea.
If nothing else, I’d recommend installing the smartmontools package and using smartctl to examine the SMART data for the hardware device(s) hosting the fedora-root logical volume.
# Install smartmontools
$ sudo dnf install smartmontools
# Determine physical volume(s) containing LV
$ sudo lvdisplay -m /dev/mapper/fedora-root
# (Look for 'Physical volume' lines and take device name(s) without
# partition, e.g. for 'Physical volume /dev/sda2' use '/dev/sda')
# Overall health assessment for device
$ sudo smartctl -H /dev/sda
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
# SMART attributes for device.
$ sudo smartctl -A /dev/sda
# Some important fields:
# Error_Correction_Count
# Reported_Uncorrect
# Current_Pending_Sector
# Offline_Uncorrectable
# For hard drives:
# Reallocated_Sector_Ct
# Power_On_Hours
# For SSDs:
# Percent_Lifetime_Remain
# Reallocated_Event_Count
# Reallocate_NAND_Blk_Cnt
# Unused_Reserve_NAND_Blk
# All SMART data (including above, plus identity, capabilities,
# and error/selftest logs)
$ sudo smartctl -a /dev/sda