On 16:39, Fri, 7 Jul 2023 Reco <recoverym4n@enotuniq.net wrote:
>
> On July 7, 2023 6:01:23 PM GMT+03:00, Mick Ab <recoverymail123890@gmail.com> wrote:
> >Twice, when trying to reboot my PC, I have had error messages which
> >indicate the root file system is corrupted and needs the manual use of fsck
> >to fix the root file system before a reboot can be done.
> >
>
> Typically, running fsck requires an unmounted filesystem (or at least readonly one). Achieving this before the reboot is a pretty hard trick.
>
> Thus, more information is needed. What does the message says exactly? What is the type (ext4, xfs, whatever) of the problematic filesystem?
>
> >Any thoughts please as to what might cause the above problem ?
>
> A hardware fault. A kernel bug. Overprotective software.
> Could be anything.
>
> Reco
> Hi.
>
The error messages were of the form :-
"/dev/mapper/vgpcname-root contains a file system with errors, check
forced.
Inodes that were a part of a corrupted orphan linked lost found.
/dev/mapper/vgpcname-root : UNEXPECTED INCONSISTENCY; RUN fsck
manually.(i.e .,
without -a or -p options). fsck exited with status code 4. The root
filesystem on /dev/mapper/vgpcname-root requires a manual fsck
There is then a flashing prompt after "(initramfs)".
The following command was thus run :-
sudo fsck -y /dev/mapper/vgpcname-root
The PC could then be rebooted.
The file system is ext4.