Good news to hear.
I was not suggesting to start with restoring, but if you were in a hurry to get it back I understand.
As suggested by Reetp you need a power backup, corrupted filessytem is not a good situation.
For the completeness of the answer now that I am able to type on a regular user/ computer interface :
for reference here is from Red Hat the procedure to try to fix the filesystem
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guideafter rebooting on rescue mode from install disc, without mounting the filesystem, do ( if you use LVM)
xfs_repair /dev/mapper/main-root
lsblk command might help you to detect where is your root (/) partition
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
vda 252:0 0 30G 0 disk
├─vda1 252:1 0 500M 0 part /boot
└─vda2 252:2 0 29,5G 0 part
├─main-root 253:0 0 27,5G 0 lvm /
└─main-swap 253:1 0 2G 0 lvm [SWAP]
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,0T 0 disk
├─sda1 8:1 0 1023M 0 part /boot
├─sda2 8:2 0 4G 0 part [SWAP]
├─sda3 8:3 0 956G 0 part /
The xfs_repair utility cannot repair an XFS file system with a dirty log. To clear the log, mount and unmount the XFS file system. If the log is corrupt and cannot be replayed, use the -L option ("force log zeroing") to clear the log, that is, xfs_repair -L /dev/device. Be aware that this may result in further corruption or data loss.
The need to have a fresh backup is that sometime the issue is the disk, or the journal is broken and the error is not recoverable.
If the issue is a broken disk sector (or multiple) cloning the disk allow you to work on the cloned copy on a working disk and increase change to recover data, without killing the old disk faster with the recover procedure.