In the midst of a working evening, I ran into a problem that the logged in user was no longer able to edit his own files. Without thinking twice, I decided to reboot.
To my surprise, the system boot hung in one place ( initramfs ).
Due to " fsck exited with status code 4 ", the suspicion fell on the failure of the part of the SSD responsible for starting Linux. But the kernel has a recovery tool and backup files. I tried to use it.
My file system is ext4 , the system was on a single disk /dev/sda2 .
Further, everything that was offered was squeezing Y everywhere. At the end, it gave a log about the modified files. Having made reboot, the system was restored. It won't help everyone, but it might be your case.
More information, perhaps there will be more disclosed the problem and solution: