Arch Linux

promitheas

Member

Registered: 2019-02-24

Posts: 38

[SOLVED] Failed to start File System Check on startup

Hey all, when i try to boot into arch i get a black screen that says Starting version 241.7-2-arch
/dev/sda6: clean, 109564/1638400 files, 1262548/655360 blocks
Thats all normal more or less, i usually get something like that on starting, but this time theres more:

[FAILED] Failed to start File System Check on /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78
See 'systemctl status "systemd-fsck@dev-disk-by and then a really long number separated by backslashes
[DEPEND] Dependency failed for /home
[DEPEND] Dependency failed for Local File System
Then a bunch of green [    OK.     ]  lines
Then
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot inti default mode. Give root password for maintenance
(or press Control-D to continue):

Ive logged in with root and tried out all the options to no avail. I cant understamd most of whats in the logs and everytime i reboot it just brings me here again.
Heres an image if you need it:
https://pasteboard.co/I3HZpEv.jpg
Thanks!

Last edited by promitheas (2019-03-03 13:51:45)

seth

Member

Registered: 2012-09-03

Posts: 58,712

Re: [SOLVED] Failed to start File System Check on startup

There's a problem w/ your home partition.
Check whether /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78 is there as well as the systemctl status (or attempt a manual fsck on the device)
Also log your desired partition scheme (/etc/fstab, fdisk -l and lsblk)

Something like https://grml.org/ is maybe more convenient to deal with this kind of issue than the systemd emergency shell.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

promitheas

Member

Registered: 2019-02-24

Posts: 38

Re: [SOLVED] Failed to start File System Check on startup

There's a problem w/ your home partition.
Check whether /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78 is there as well as the systemctl status (or attempt a manual fsck on the device)
Also log your desired partition scheme (/etc/fstab, fdisk -l and lsblk)

Something like https://grml.org/ is maybe more convenient to deal with this kind of issue than the systemd emergency shell.

I am a total moron. Without realising it, i was trying to run fsck on the root partition instead of home. Your comment woke me up... Fixed, thank you!
After i check if everything is fine i need to grab some sleep