You are not logged in.
Hi
I started using Arch linux a few months back.
In the last two months, my laptop has crashed twice during boot.
I got the following message during boot:
[FAILED] Failed to start File System5-810f-de4c-b861-fea064fe538c
[DEPEND] Dependency failed for /sysroot
[DEPEND] Dependency failed for Initrd Root File System
[DEPEND] Dependency failed for Relo figuration from the Real Root
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 into default mode
Cannot open access to console, the root account is locked
See sulogin(8) man page for more details
Press Enter to continue"5-810f-de4c-b861-fea064fe538c" in the above message seems to be PARTUUID of /root partition
I am not sure if this is an fsck failure for the drive
I couldn't run any of the commands mentioned in the error message as I was not able to boot into the system.
Since I ran out ideas, I installed Fedora for the time being (on the same drive).
I am thinking the drive is ok since Fedora seems to be running fine.
On a bit more googling, I found this bug here
https://bugs.archlinux.org/task/67517
First comment here says
Source of the problem is a mkinitcpio systemd hook:
HOOKS=(base systemd block keyboard fsck filesystems)I was using the above settings to hide fsck message to get silent boot
https://wiki.archlinux.org/index.php/silent_boot
I am wondering if there is a more stable/recommended way to achieve silent boot
Last edited by anilms (2020-10-05 23:43:17)
Offline
Pls use [code] tags [/code] for your outputSource of the problem is a mkinitcpio systemd hook:
HOOKS=(base systemd block keyboard fsck filesystems)
Did you tried to reverse back to udev?
Changing systemd to udev fixes the problem:
HOOKS=(base udev block keyboard fsck filesystems)I wouldn't say the boot failure was caused by the HOOK, since I also changed this HOOK to systemd with no issue. Therefore I suggest reverse back to udev and see if you still get boot failure.
Last edited by solskog (2020-10-05 05:55:30)
Offline
To access the emergency shell please see https://bbs.archlinux.org/viewtopic.php?id=259250
How did you conclude https://bugs.archlinux.org/task/67517 is related?
Is there a line for fsck in the output before the section you quoted?
If you remove the fsck hook the filesystem specific fsck helper will not be added to the initrd, systemd-fsck will not be able to fsck the filesystem before it is mounted.
Last edited by loqs (2020-10-05 15:47:21)
Offline
@loqs, I am not sure https://bugs.archlinux.org/task/67517 was the cause of the issue.
Came across this while looking for a fix.
Thanks for confirming this is working for you @solskog.
Unfortunately I didn't think of changing the order back at that time and installed Fedora after couple of hours of debugging.
Since the order change is still working for you, I'll do the same and see if the crash happens again.
@loqs, There were no other messages from fsck, probably because of silent boot.
ExecStart=/usr/lib/systemd/systemd-fsck
StandardOutput=null
StandardError=journal+consoleOffline
Please do not mark your thread as closed which is used by moderators to mark locked threads.
Last edited by loqs (2020-10-05 22:31:43)
Offline
Sorry. I thought I read some rule to mark post as closed/solved
Offline
It is a rule to mark a thread [SOLVED]. Code_of_conduct#How_to_post
Threads that are not solved but you no longer have an interest in pursuing are more tricky to classify.
Last edited by loqs (2020-10-05 22:49:57)
Offline
Thanks. Updated
Offline