Stuck in emergency mode

Issues & Assistance
1

After updating my PC today around 8pm, my PC locked itself in emergency mode, which I can’t get it out of.
Changing kernels does nothing, and neither does loading old snapshots.
I would post the results of Garuda-inxi but I can’t get that copied from my computer onto my phone to put here.

Here is a picture of the emergency mode screen that I’m talking about, it’s mentioning this error: failed to start Remount Root and Kernel File Systems. What does that mean? How do I do that?

IMG_20250520_233230792
IMG_20250520_2332307921920×1080 101 KB

It seems like this person had the same problem but it didn’t seemed solved.

This one said solved but I don’t understand how or what they even did.

I don’t understand what happened.

2

They all give you the same errors? Share fstab contents:

cat /etc/fstab

garuda-inxi | nc termbin.com 9999

will give you a link to termbin containing the output, which you can then put here

5 Likes
3

BTW, use live ISO. Maybe you can fix the upd with chroot.

Please, post also

lsblk -f
4 Likes
4

So loading my oldest snapshot gives a different error that results in something I’m not even sure what is.

Here’s the results of that cat command.

And also when using termbin command it just tells me it couldn’t resolve host “termbin.com”

IMG_20250521_010528546
IMG_20250521_0105285461920×1080 110 KB

IMG_20250521_010318316
IMG_20250521_0103183161920×1080 46.4 KB

5

I’m not sure what do with the chroot command but here is the output you asked for

IMG_20250521_011123554
IMG_20250521_0111235541920×1080 102 KB

6

fstab point to an empty or not mounted nvme0n1p2.
Must look like

└─nvme0n1p6 btrfs        Hyprland    afa097f0-7d25-4832-90df-9596386fadf5   61,5G    52% /var/tmp
                                                                                         /var/log
                                                                                         /var/cache
                                                                                         /root
                                                                                         /srv
                                                                                         /home
                                                                                         /

Try booting from BIOS , change boot order.

Use forum search for live ISO, chroot, black screen.

4 Likes
7

Looks like BTRFS is read-only with IO errors:

Boot a live.iso and chroot into your system (and post your garuda-inxi from there) and then first check how much free disk space is available (may be root is full). If root is full, then create enough free space, for example by deleting old snapshots, clearing the cache and removing other files that are no longer needed. Then try to repeat the update (from the live environment):

5 Likes
8

Not sure if this is helpful, but the chroot command is designed to “change root”. This means that if you’re booting off the live ISO, then you need to tell it to change the root to your BTRFS partition, so that further commands now operate on that storage location, and NOT on the iso.

Generally speaking, you’ll need to mount your BTRFS partition onto a directory, then issue the chroot command to the directory where you mounted it. For example, if you mounted /dev/nvme0n1p2 (the partition of your BTRFS install), onto /mnt/hd (that directory needs to exist first before you mount the drive there), and then use chroot /mnt/hd this will then change your root (i.e., / path) to /mnt/hd. Good luck!

6 Likes
9

On live ISO you can use the chroot tool in the Welcome App, or use terminal with garuda-chroot -a

 garuda-chroot -a
==> Mounting (Garuda_Linux) [/dev/nvme0n1p6]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
 --> mount: [/mnt/home]
 --> mount: [/mnt/root]
 --> mount: [/mnt/srv]
 --> mount: [/mnt/var/cache]
 --> mount: [/mnt/var/log]
 --> mount: [/mnt/var/tmp]
[root@y7p /]#

if you get no system, you can try the way @shayaknyc explained or read for more help the tutorial

4 Likes