What were you trying to do that didn't work?

During the `leapp upgrade` , the `leapp-upgrade.log` mentions the Filesystem check, The logs are very verbose and difficult to find in the Debug output captured in `leapp-upgrade.log`.

~~~

{{Feb 07 14:05:12 localhost kernel: EXT4-fs (xvda2): error count since last fsck: 12
Feb 07 14:05:12 localhost kernel: EXT4-fs (xvda2): initial error at time 1603935725: __ext4_new_inode:821
Feb 07 14:05:12 localhost kernel: EXT4-fs (xvda2): last error at time 1604344659: ext4_remount:5158
Feb 07 13:59:46 localhost kernel: EXT4-fs (xvda2): warning: mounting fs with errors, running e2fsck is recommended

2024-02-07 14:13:31.643 DEBUG PID: 1114 }}

~~~

As this is flashed in the `leapp-upgrade.log`, the `leapp-report.txt` comes clean with no error and inhibitor, upgrading such system leads the system to drop in emergency mode.

Please provide the package NVR for which bug is seen:

leapp

How reproducible:

1] The issue occurs if the system is facing filesystem error/inconsistencies before leapp upgrade.

Expected results

Expecting  the customer to be made aware of the filesystem check in `leapp-report.txt` before going for reboot may be a Warning, This will prevent the systems from being dropped to emergency mode post upgrade.

Actual results

The`leapp-report.txt` comes clean and the file system check is mentioed in `leapp-upgrade.log` which is a very big file customer to read.