Unable to log into the system and redirected to Emergency TTY

Hello everyone, I have a dual boot system of Garuda Linux and Windows 10. I haven’t used Garuda for a few days, and when I boot into the system, I can’t log in and I’m taken to the Emergency shell. It seems that the system is unable to mount directories including /root.

Boot a garuda live session and post your garuda-inxi.

Have you ever looked in there?

You are in emergency mode. After logging in, type "journalctl -xb" to view system logs

Did you voluntarily participate in Windows Patchday yesterday? If so, then Windows probably updated its bootloader and kicked out Garuda.

2 Likes

Use last working snapshot or use live ISO, chroot, update.

4 Likes

Recently my Windows OS update itself on patchday, but I don’t think it related to the problem because I could still see the GRUB menu when booting.
I have chrooted into a live USB and this is the output of journalctl -xb :

[root@garuda-dr460nized-gaming /]# sudo journalctl -xb
No journal files were found.
Failed to get boot id: Function not implemented

And garuda-inxi:

[root@garuda-dr460nized-gaming /]# garuda-inxi
12System:
12Kernel 6.8.7-zen1-2-zen 12arch x86_64 12bits 64 12compiler N/A 12clocksource N/A
12Console N/A 12Distro Garuda 12base Arch Linux
12Machine:
12Message No machine data: try newer kernel. Is dmidecode installed? Try -M --dmidecode.
Can't use an undefined value as an ARRAY reference at /usr/sbin/inxi line 10852.
Garuda (2.6.26-1):
System install date:     2024-05-08
Last full system update: 2024-04-22 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager connman dracut
Windows dual boot:       No/Undetected
/proc/ is not mounted. This is not a supported mode of operation. Please fix
your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
Your mileage may vary.
Running in chroot, ignoring command 'list-units'
Failed units:

It’s too late for that, you should have done that in emergency mode when you took the photo. But you can do this again if you are in emergency mode.

inxi cannot read dmi data and when I look at the mount errors and the btrfs error in your photo, it smells strongly of a killed file system…or hardware error.

Can you load a snapshot?

2 Likes

Be sure to disable the “fast startup” feature from your Windows installation.

Have you tried starting from a cold boot? (As opposed to a reboot.)

2 Likes