So, the key point is succeed in chrooting.
I’m sorry I never had to use encrypted linux (only personal use at home…), so cannot provide real assistance.
How do you decrypt normally? Try with the CLI instead of GUI tools.
If you do something like:
sudo cryptsetup open /dev/nvme0n1p2 crypto_LUKS
That crypto_LUKS should be used (or whatever the name you use).
You could try:
sudo mount /dev/mapper/crypto_LUKS /mnt/broken
(or the different name used), but you could try also:
sudo mount -o subvol=@ /dev/mapper/crypto_LUKS /mnt/broken
I also just remembered a very long topic where arch-chroot worked instead of garuda-chroot:
You could give it a try. Just change the luks-xxx data with yours and sudo mount /dev/nvme0n1p1 /mnt/boot/efi.
Normally it prompts for the password after the Manufacturer Logo/BIOS (del,f12 screen) and after that It puts me to grub as usual. So I’ve never really had to use the CLI commands for it.
╭─garuda@garuda in ~ as 🧙
╰─λ sudo cryptsetup open /dev/nvme0n1p2 crypto_LUKS
Enter passphrase for /dev/nvme0n1p2:
Cannot use device /dev/nvme0n1p2 which is in use (already mapped or mounted).
╭─garuda@garuda in ~ as 🧙 took 5s
[🔴] × sudo mount -o subvol=@ /dev/mapper/crypto_LUKS /mnt/broken/
mount: /mnt/broken: special device /dev/mapper/crypto_LUKS does not exist.
dmesg(1) may have more information after failed mount system call.
╭─garuda@garuda in ~ as 🧙 took 0s
[🔴] × sudo mount -o subvol=@ /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@home /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/home
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@root /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/root
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@srv /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/srv
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@cache /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/var/cache
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@log /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/var/log
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount -o subvol=@tmp /dev/mapper/luks-c399d964-73af-4850-a7bc-afc679df7a06 /mnt/var/tmp
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ sudo mount /dev/nvme0n1p2 /mnt/boot/efi
mount: /mnt/boot/efi: unknown filesystem type 'crypto_LUKS'.
dmesg(1) may have more information after failed mount system call.
╭─garuda@garuda in ~ as 🧙 took 0s
[🔴] × sudo mount /dev/nvme0n1p1 /mnt/boot/efi
╭─garuda@garuda in ~ as 🧙 took 0s
╰─λ arch-chroot /mnt
==> ERROR: This script must be run with root privileges
╭─garuda@garuda in ~ as 🧙 took 0s
[🔴] × sudo arch-chroot /mnt
[root@garuda-dr460nized-gaming /]# garuda
bash: garuda: command not found
[root@garuda-dr460nized-gaming /]# ls
bin crypto_keyfile.bin efi home lib64 mt proc run srv tmp var
boot dev etc lib mnt opt root sbin sys usr
[root@garuda-dr460nized-gaming /]#
Okay so I ran garuda-update and it hung up on ttf-google-fonts-git, giving an error like this on a lot of fonts
ttf-google-fonts-git: /usr/share/licenses/ttf-google-fonts-git/LICENSE.zilla-slab-highlight exists in filesystem
Errors occurred, no packages were upgraded.
okay that ran better, there were a few errors here and there like:
File "/usr/lib/libkhotkeysprivate.so.5.27.10" from package "khotkeys" is missing dependency "libkworkspace5.so.5"
File "/usr/lib/qt/plugins/kcm_hotkeys.so" from package "khotkeys" is missing dependency "libkworkspace5.so.5"
File "/usr/lib/qt/plugins/kf5/kded/khotkeys.so" from package "khotkeys" is missing dependency "libkworkspace5.so.5"
File "/usr/lib/qt/plugins/plasma/applets/plasma_applet_windowappmenu.so" from package "plasma5-applets-window-appmenu" is missing dependency "libKF5Plasma.so.5"
Package "python-future" has files in directory "/usr/lib/python3.12" that are ignored by the current Python interpreter
and
Failed to open file "/sys/devices/system/cpu/cpu21/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu11/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu9/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu7/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu28/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu18/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu5/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu26/cpufreq/scaling_governor": Read-only file system
Failed to open file "/sys/devices/system/cpu/cpu16/cpufreq/scaling_governor": Read-only file system
...
also this:
23/39) GRUB update after transactions...
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/catppuccin-frappe-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
/usr/lib/os-probes/50mounted-tests: line 186: 23895 Segmentation fault (core dumped) grub-mount "$partition" "$tmpmnt" 2> /dev/null
/usr/lib/os-probes/50mounted-tests.orig: line 72: 23904 Segmentation fault (core dumped) grub-mount "$partition" "$tmpmnt" 2> /dev/null
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
but it ended up finishing!
(38/39) Performing snapper post snapshots for the following configurations...
fatal library error, lookup self
==> root: 1182
(39/39) Syncing all file systems...
Running in chroot, ignoring command 'start'
Running in chroot, ignoring command 'start'
System updated! 🐧