Reboot Into Firmware only following update

Just ran update today and on reboot was greeted with “Reboot Into Firmware” as the only boot option.

I’ve been reading though posts and this one seems right on point, but I’m having trouble mounting boot partition.

Following this EOS guide, I’m mounting encrypted partitions and I have /dev/nvme0n1p1 mounted, but when I attempt to mount boot I see this:

sudo mount /dev/nvme1n1p3 /mnt/efi
mount: /mnt/efi: mount point does not exist.

Same thing happens if I use sudo mount /dev/nvme1n1p3 /mnt/esp.

In GParted on a live boot I can see boot partitiion is 1000MB, with 2.22MB used and 997.78MB unused.

I guess without mounting boot I can’t pull a bootlog, but here is the inxi -Fxxc0z
That of course is reporting from live, my system is running Gnome. I will need help if there are any other helpful logs that I can retrieve from where I’m at.

I will tremendously appreciate any help with this!

Can you share the contents of /mnt/etc/fstab after mounting the first partition?

This operation is exposing my lack of experience. :laughing:
Here’s what I’m trying, and I’ll go find that dmesg.

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
sudo cat /mnt/etc/fstab
cat: /mnt/etc/fstab: No such file or directory

This means you haven;t mounted the right thing on /mnt

Can you share sudo parted -l

sudo parted -l
Model: USB Driver (scsi)
Disk /dev/sda: 4008MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 2      2738MB  2901MB  163MB  primary  fat16        esp

Model: WD_BLACK SN850X 2000GB (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2000GB  2000GB

Model: WD_BLACK SN770 500GB (nvme)
Disk /dev/nvme1n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 3      1049kB  1050MB  1049MB  fat32              boot, esp
 1      1050MB  467GB   466GB
 2      467GB   500GB   33.6GB

I should add there are 2 SSD drives present.

What are you mounting on /mnt?

Also, what does ls /mnt show?

I mounted /dev/nvme0n1p1 using sudo cryptsetup open /dev/nvme0n1p1 mycryptdevice. Following that I used sudo mount /dev/mapper/mycryptdevice /mnt and then sudo mount /dev/nvme1n1p3 /mnt/esp because my boot partition shows boot, esp flags. That returned mount: /mnt/esp: mount point does not exist.

ls /mnt
irish  lost+found  timeshift

Feels like I got in a bit over my head, I have successfully used chroot many times before but never used encrypted drives until now.

That doesn’t look like your root filesystem. That looks like /home

Are you sure it shouldn’t be /dev/nvme0n1p2

What a mistake :man_facepalming: :man_facepalming: :man_facepalming:

Took a lunch break, all is well and I was able to run pacman -S dracut kernel-install-for-dracut linux linux-api-headers linux-firmware linux-firmware-whence util-linux

Thank you for your patience @dalto!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.