Yesterday, I ran I think yay -Ssyu?? or pacman -Ssyu to update system packages. The terminal went blank after all the loading bars were finished only letting me enter to add more paragraph breaks and type without doing anything, so I closed the terminal thinking it was probably done. Rookie error, now I can’t boot.
Currently following this guide: https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/ and I can’t seem to mount either of my partitions. Here is what my terminal looks like:
sudo lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2.7G 1 loop /run/archiso/airootfs
sda 8:0 1 57.7G 0 disk
sda1 8:1 1 2.9G 0 part /run/archiso/bootmnt
sda2 8:2 1 248M 0 part
nvme0n1 259:0 0 931.5G 0 disk
nvme0n1p1 259:1 0 931.5G 0 part
sudo mount /dev/sda2 /mnt - no response, assumably works
sudo cat /mnt/etc/fstab
cat: /mnt/etc/fstab: No such file or directory
ls -l /mnt
total 2206
drwxr-xr-x 3 root root 512 Jan 12 20:26 arch
drwxr-xr-x 3 root root 512 Jan 12 20:26 boot
drwxr-xr-x 3 root root 512 Jan 12 20:26 EFI
drwxr-xr-x 3 root root 512 Jan 12 20:26 loader
-rwxr-xr-x 1 root root 1128000 Jan 12 20:26 shellia32.efi
-rwxr-xr-x 1 root root 1128000 Jan 12 20:26 shellx64.efi
sudo mount /dev/sda1 /mnt/efi
mount: /mnt/efi: WARNING: source write-protected, mounted read-only.
sudo cat /mnt/efi
cat: /mnt/efi: Is a directory
sudo arch-chroot /mnt
mount: /mnt/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
ls /mnt
arch boot EFI loader shellia32.efi shellx64.efi