On 5/4/20 12:15 PM, Andrew Wood wrote:
I had Fedora 31 installed on my laptop and I decided to update it to
Fedora 32.
After the reboot then Fedora stops and brings up a terminal session. I'm
invited to inspect the system log with 'journalctrl'.
Looking through the log then I have:
May 04 17:03:09 localhost systemd[1]: Starting File System Check on
/dev/mapper/fedora-root...
May 04 17:03:09 localhost systemd-fsck[544]: /dev/mapper/fedora-root
contains a file system with errors, check forced.
May 04 17:03:18 localhost systemd-fsck[544]: /dev/mapper/fedora-root:
Inodes that were part of a corrupted orphan linked list found.
May 04 17:03:18 localhost systemd-fsck[544]: /dev/mapper/fedora-root:
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
May 04 17:03:18 localhost systemd-fsck[544]: (i.e., without -a
or -p options)
Any suggestions of how I might fix this? One thing which I don't
understand is the device here. Is it systemd[1]??
You're using LVM for your file system partitions, nothing to do with
systemd.
You just need to run "e2fsck /dev/mapper/fedora-root" to fix the file
system.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
