It looks like you are using chaotic-aur.
See if this works.
sudu pacman -Syu nvidia-580xx-dkms lib32-nvidia-580xx-utils nvidia-580xx-settings nvidia-580xx-utils
You can’t stay on nvidia.
didn’t work
sudo pacman -Syu nvidia-580xx-dkms lib32-nvidia-580xx-utils nvidia-580xx-settings nvidia-580xx-utils
[sudo] password for neo:
:: Synchronizing package databases…
endeavouros is up to date
core is up to date
extra 8.1 MiB 9.43 MiB/s 00:01 [----------------------------------------------------------------------------] 100%
multilib is up to date
chaotic-aur 644.4 KiB 299 KiB/s 00:02 [----------------------------------------------------------------------------] 100%
warpdotdev is up to date
error: target not found: nvidia-580xx-dkms
error: target not found: lib32-nvidia-580xx-utils
error: target not found: nvidia-580xx-settings
error: target not found: nvidia-580xx-utils
I went with nvidia-open, finished the updates and landed again in Emergency mode.
Here are some logs from journalctl -xb
I clicked the sections that were highlighted: https://postimg.cc/gallery/5FFrV6J
@dalto I need help..
Please also send your kofi, liberapay any payment method except crypto.
ls -R /mnt/test_efi
[liveuser@eos-2025.11.24 ~]$ sudo su
[root@EndeavourOS liveuser]# mkdir -p /mnt/test_efi
[root@EndeavourOS liveuser]# mount /dev/nvme0n1p5 /mnt/test_efi
[root@EndeavourOS liveuser]# ls -R /mnt/test_efi
/mnt/test_efi:
d95a4396b9a144b981ff0d6325920b9f EFI loader 'System Volume Information'
/mnt/test_efi/d95a4396b9a144b981ff0d6325920b9f:
6.18.1-arch1-2
/mnt/test_efi/d95a4396b9a144b981ff0d6325920b9f/6.18.1-arch1-2:
initrd linux
/mnt/test_efi/EFI:
BOOT Linux Microsoft systemd
/mnt/test_efi/EFI/BOOT:
BOOTX64.EFI
/mnt/test_efi/EFI/Linux:
/mnt/test_efi/EFI/Microsoft:
Boot Recovery
/mnt/test_efi/EFI/Microsoft/Boot:
BCD cs-CZ fr-CA kd_02_1969.dll memtest.efi sk-SK
BCD.LOG da-DK fr-FR kd_02_19a2.dll nb-NO sl-SI
BCD.LOG1 de-DE hr-HR kd_02_1af4.dll nl-NL sr-Latn-RS
BCD.LOG2 el-GR hu-HU kd_02_8086.dll pl-PL sv-SE
bg-BG en-GB it-IT kd_07_1415.dll pt-BR tr-TR
bootmgfw.efi en-US ja-JP kd_0C_8086.dll pt-PT uk-UA
bootmgr.efi es-ES kd_02_10df.dll kdnet_uart16550.dll qps-ploc winsipolicy.p7b
BOOTSTAT.DAT es-MX kd_02_10ec.dll kdstub.dll Resources zh-CN
boot.stl et-EE kd_02_1137.dll ko-KR ro-RO zh-TW
cbmr_driver.efi fi-FI kd_02_14e4.dll lt-LT ru-RU
CIPolicies Fonts kd_02_15b3.dll lv-LV SecureBootRecovery.efi
/mnt/test_efi/EFI/Microsoft/Boot/bg-BG:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/CIPolicies:
Active
/mnt/test_efi/EFI/Microsoft/Boot/CIPolicies/Active:
{5DAC656C-21AD-4A02-AB49-649917162E70}.cip {CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip
{82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
/mnt/test_efi/EFI/Microsoft/Boot/cs-CZ:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/da-DK:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/de-DE:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/el-GR:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/en-GB:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/en-US:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/es-ES:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/es-MX:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/et-EE:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/fi-FI:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/Fonts:
chs_boot.ttf kor_boot.ttf meiryo_boot.ttf msjhn_boot.ttf segmono_boot.ttf wgl4_boot.ttf
cht_boot.ttf malgun_boot.ttf meiryon_boot.ttf msyh_boot.ttf segoen_slboot.ttf
jpn_boot.ttf malgunn_boot.ttf msjh_boot.ttf msyhn_boot.ttf segoe_slboot.ttf
/mnt/test_efi/EFI/Microsoft/Boot/fr-CA:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/fr-FR:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/hr-HR:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/hu-HU:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/it-IT:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/ja-JP:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/ko-KR:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/lt-LT:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/lv-LV:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/nb-NO:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/nl-NL:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/pl-PL:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/pt-BR:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/pt-PT:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/qps-ploc:
memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/Resources:
bootres.dll en-US
/mnt/test_efi/EFI/Microsoft/Boot/Resources/en-US:
bootres.dll.mui
/mnt/test_efi/EFI/Microsoft/Boot/ro-RO:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/ru-RU:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/sk-SK:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/sl-SI:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/sr-Latn-RS:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/sv-SE:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/tr-TR:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/uk-UA:
bootmgfw.efi.mui bootmgr.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/zh-CN:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Boot/zh-TW:
bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
/mnt/test_efi/EFI/Microsoft/Recovery:
BCD BCD.LOG BCD.LOG1 BCD.LOG2
/mnt/test_efi/EFI/systemd:
systemd-bootx64.efi
/mnt/test_efi/loader:
entries entries.srel keys loader.conf random-seed
/mnt/test_efi/loader/entries:
d95a4396b9a144b981ff0d6325920b9f-6.17.9-arch1-1.conf
d95a4396b9a144b981ff0d6325920b9f-6.17.9-arch1-1-fallback.conf
d95a4396b9a144b981ff0d6325920b9f-6.18.1-arch1-2.conf
d95a4396b9a144b981ff0d6325920b9f-6.18.1-arch1-2-fallback.conf
endeavouros.conf
/mnt/test_efi/loader/keys:
'/mnt/test_efi/System Volume Information':
[root@EndeavourOS liveuser]#
What GPU do you have?
NVIDIA GeForce MX130 [Discrete]
the update would have not proceeded if I had not accepted to replace nvidiapackage with nvidia-open. I had tried 2 times.
Yeah, that driver isn’t compatible with your GPU.
You needed to fix the driver issue and then update.
That being said, the wrong GPU drivers won’t drop you to emergency mode. It looks to me like your kernel modules are out of sync with your kernel.
I would boot off the ISO, arch-chroot into your system and try running reinstall-kernels.
Make sure you mount the EFI partition properly for the chroot.
The instructions for that are here:
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
It didn’t work and I am again in the emergency mode
[root@EndeavourOS liveuser]# mount -o subvol=@ /dev/nvme0n1p4 /mnt
[root@EndeavourOS liveuser]# cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1448-DD78 /efi vfat fmask=0137,dmask=0027 0 2
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
[root@EndeavourOS liveuser]# mount /dev/nvme0n1p5 /mnt/efi
[root@EndeavourOS liveuser]# arch-chroot /mnt
[root@EndeavourOS /]#
[root@EndeavourOS /]# ls
bin dev etc home lib64 nix proc run srv tmp var
boot efi gnu lib mnt opt root sbin sys usr write_test
[root@EndeavourOS /]# reinstall-kernels
Installing kernel 6.18.2-arch2-1
[root@EndeavourOS /]#
The UUIDs are matching
```
[root@EndeavourOS liveuser]# mount -o subvol=@ /dev/nvme0n1p4 /mnt
mount /dev/nvme0n1p5 /mnt/efi
[root@EndeavourOS liveuser]# lsblk -f /dev/nvme0n1p5
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1p5 vfat FAT32 1448-DD78 677.3M 34% /mnt/efi
[root@EndeavourOS liveuser]# cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1448-DD78 /efi vfat fmask=0137,dmask=0027 0 2
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
[root@EndeavourOS liveuser]#
```
@dalto sorry if I am disturbing you
Should I run bootctl install to force the bootloader to write a fresh .efi binary to the partition and update BIOS boot entries?
Found that /etc/kernel/cmdline file had duplicated text. removed duplicates.
Deleted the endeavouros.conf file, which was pointing to a kernel file (/vmlinuz-linux) that did not exist.
ran reinstall-kernels
updated /efi/loader/loader.conf to automatically select the newest valid kernel (using the d95a...*)
Now I am back in my system. Not sure if this will stay working until I make the next update.
Command outputs from working system and not from live iso:
cat /efi/loader/loader.conf
default d95a4396b9a144b981ff0d6325920b9f*
timeout 5
console-mode auto
reboot-for-bitlocker 1
❯ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1448-DD78 /efi vfat rw,relatime,fmask=0137,dmask=0027,errors=remount-ro,nofail 0 2
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
❯ uname -r && pacman -Q linux
6.18.2-arch2-1
linux 6.18.2.arch2-1
❯ bootctl status
Couldn't find EFI system partition. It is recommended to mount it to /boot/ or /efi/.
Alternatively, use --esp-path= to specify path to mount point.
System:
Firmware: UEFI 2.70 (INSYDE Corp. 22850.12322)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: systemd-boot 259-1-arch
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Support Type #1 sort-key field
✓ Support @saved pseudo-entry
✓ Support Type #1 devicetree field
✓ Enroll SecureBoot keys
✓ Retain SHIM protocols
✓ Menu can be disabled
✓ Multi-Profile UKIs are supported
✓ Loader reports network boot URL
✓ Support Type #1 uki field
✓ Support Type #1 uki-url field
✓ Loader reports active TPM2 PCR banks
Partition: /dev/disk/by-partuuid/e84bacb0-e2a0-48e4-879a-4c51602b8623
Loader: └─(null)//EFI/systemd/systemd-bootx64.efi
Current Entry: d95a4396b9a144b981ff0d6325920b9f-6.18.2-arch2-1.conf
Random Seed:
System Token: set
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0004
Status: active, boot-order
Partition: /dev/disk/by-partuuid/e84bacb0-e2a0-48e4-879a-4c51602b8623
File: └─(null)//EFI/systemd/systemd-bootx64.efi
Title: Windows Boot Manager
ID: 0x0003
Status: active, boot-order
Partition: /dev/disk/by-partuuid/e84bacb0-e2a0-48e4-879a-4c51602b8623
File: └─(null)//EFI/Microsoft/Boot/bootmgfw.efi
Title: Windows Boot Manager
ID: 0x0002
Status: active, boot-order
Partition: /dev/disk/by-partuuid/bfe28cd7-4eb1-48e1-911c-29ef1fa19d7e
File: └─(null)//EFI/Microsoft/Boot/bootmgfw.efi
❯ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
❯ findmnt /efi
TARGET SOURCE FSTYPE OPTIONS
/efi /dev/nvme0n1p5 vfat rw,relatime,fmask=0137,dmask=0027,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
❯ cat /etc/kernel/cmdline
nvme_load=YES nowatchdog rw rootflags=subvol=/@ root=UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 nvidia_drm.modeset=1
Ran an update an got these:
[root@matrix neo]# ls -l /efi/loader/entries/
total 8
-rw-r----- 1 root root 570 Dec 22 2025 d95a4396b9a144b981ff0d6325920b9f-6.18.2-arch2-1.conf
-rw-r----- 1 root root 534 Dec 22 2025 d95a4396b9a144b981ff0d6325920b9f-6.18.2-arch2-1-fallback.conf
[root@matrix neo]# cat /efi/loader/entries/$(ls -t /efi/loader/entries/ | head -n 1)
# Boot Loader Specification type#1 entry
# File created by /etc/kernel/install.d/90-loaderentry.install (systemd 254.1-1-arch)
title EndeavourOS
version 6.18.2-arch2-1
machine-id d95a4396b9a144b981ff0d6325920b9f
sort-key endeavouros-6.18.2-arch2-1
options nvme_load=YES nowatchdog rw rootflags=subvol=/@ root=UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 nvidia_drm.modeset=1 systemd.machine_id=d95a4396b9a144b981ff0d6325920b9f
linux /d95a4396b9a144b981ff0d6325920b9f/6.18.2-arch2-1/linux
initrd /d95a4396b9a144b981ff0d6325920b9f/6.18.2-arch2-1/initrd
[root@matrix neo]# ls -l /efi/$(ls -t /efi/loader/entries/ | head -n 1 | grep "linux" | awk '{print $2}' | sed 's/^\///')
total 16
drwxr-x--- 4 root root 4096 Dec 22 2025 d95a4396b9a144b981ff0d6325920b9f
drwxr-x--- 6 root root 4096 Nov 8 2024 EFI
drwxr-x--- 4 root root 4096 Dec 22 2025 loader
drwxr-x--- 2 root root 4096 Nov 8 2024 'System Volume Information'
[root@matrix neo]# bootctl list
Couldn't find EFI system partition. It is recommended to mount it to /boot/ or /efi/.
Alternatively, use --esp-path= to specify path to mount point.
[root@matrix neo]# ls -l /efi/d95a4396b9a144b981ff0d6325920b9f/6.18.2-arch2-1/linux
-rw-r----- 1 root root 16605376 Dec 22 2025 /efi/d95a4396b9a144b981ff0d6325920b9f/6.18.2-arch2-1/linux
reboot worked fine.
nvidia issue was also fixed with nvidia-580xx-dkms nvidia-580xx-utils nvidia-580xx-settings
That doesn’t matter. It shouldn’t hurt anything.
This could be the problem if you were booting off the old manual entry which was pointing to the wrong kernel.
@dalto there is only issue that I am seeing now:
❯ bootctl status
Couldn't find EFI system partition. It is recommended to mount it to /boot/ or /efi/.
Alternatively, use --esp-path= to specify path to mount point.
the full output is in Emergency Mode "Failed to mount /efi" during boot (systemd-boot + Btrfs + NVMe) - #51 by jet
Can you share the outputs of cat /etc/fstab, lsblk -o name,type,fstype,size,mountpoint,uuid and findmnt --real
You weren’t disturbing me but I was asleep so I didn’t see your message.
❯ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1448-DD78 /efi vfat rw,relatime,fmask=0137,dmask=0027,errors=remount-ro,nofail 0 2
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9 /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
tmpfs
❯ lsblk -o name,type,fstype,size,mountpoint,uuid
NAME TYPE FSTYPE SIZE MOUNTPOINT UUID
sda disk 931.5G
├─sda1 part vfat 300M 9A7C-4B62
└─sda2 part crypto_LUKS 931.2G b5e82aa0-1972-4910-8675-4d4fe303e6cd
└─luks-b5e82aa0-1972-4910-8675-4d4fe303e6cd crypt btrfs 931.2G /run/media/neo/a8e6e158-2bab-46ce-a a8e6e158-2bab-46ce-a493-31d3bd0e44f5
nvme0n1 disk 232.9G
├─nvme0n1p1 part vfat 100M 3A57-A5F0
├─nvme0n1p2 part 16M
├─nvme0n1p3 part ntfs 51.7G DA78585278582F8D
├─nvme0n1p4 part btrfs 180.1G /var/log 6cabd822-0bc4-4561-9fc2-deb1d7b6cfe9
└─nvme0n1p5 part vfat 1G /efi 1448-DD78
❯ findmnt --real
TARGET SOURCE FSTYPE OPTIONS
/ /dev/nvme0n1p4[/@] btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@
├─/gnu/store /dev/nvme0n1p4[/@/gnu/store] btrfs ro,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@
├─/run/media/neo/a8e6e158-2bab-46ce-a493-31d3bd0e44f5 /dev/mapper/luks-b5e82aa0-1972-4910-8675-4d4fe303e6cd btrfs rw,nosuid,nodev,relatime,space_cache=v2,subvolid=5,subvol=/
├─/home /dev/nvme0n1p4[/@home] btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home
├─/var/cache /dev/nvme0n1p4[/@cache] btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@cache
├─/var/log /dev/nvme0n1p4[/@log] btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@log
└─/efi /dev/nvme0n1p5 vfat rw,relatime,fmask=0137,dmask=0027,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
That all looks fine to me.
Does using sudo with bootctl status make any difference?
No. Still the same error message even with sudo.