You are not logged in.
Pages: 1
Hi,
After few updates to the BIOS were made I no longer have the option to boot Arch in either the UEFI firmware settings. Is there a way to bring it back possibly by installing grub again to the ESP partition? My current setup is as follows:
sda 8:0 0 119.2G 0 disk
sda1 8:1 0 300M 0 part
sda2 8:2 0 118.9G 0 part
sdb 8:16 0 74.5G 0 disk
sdb1 8:17 0 512M 0 part /boot/efi
sdb2 8:18 0 74G 0 part /
sdc 8:32 0 232.9G 0 disk
sdc1 8:33 0 529M 0 part
sdc2 8:34 0 99M 0 part
sdc3 8:35 0 16M 0 part
sdc4 8:36 0 209.3G 0 part
where sda1 is the Arch ESP. Its contents are:
EFI/grub_uefi/grubx64.efi
efibootmgr -v:
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000
Boot0000* Windows Boot Manager HD(2,GPT,03ca6a2a-9467-45f1-9fd4-77c2dc85b966,0x109000,0x31800)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* ubuntu HD(1,GPT,b5478587-185d-4597-8c84-6276cc30c91e,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO
Thanks a lot
Offline
Output of
lsblk -f && cat /etc/fstab && grep vmlinuz /boot/grub/grub.cfg && ls -R /boot/efi
is:
sda
├─sda1 vfat FAT32 14BC-BB61
└─sda2 ext4 1.0 f8ba975f-9b05-45e9-b988-5eaac4f68f5c
sdb
├─sdb1 vfat FAT32 6A17-2FAA 504.9M 1% /boot/efi
└─sdb2 ext4 1.0 e10f2a1f-decd-4fe5-83e5-8b5571a7674b 55.1G 19% /
sdc
├─sdc1 ntfs 2E70EBF470EBC127
├─sdc2 vfat FAT32 869C-44E2
├─sdc3
└─sdc4 ntfs Windows D0789D53789D38E4
# /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>
# / was on /dev/sda2 during installation
UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=6A17-2FAA /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
linux /boot/vmlinuz-5.15.0-79-generic root=UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b ro quiet splash
linux /boot/vmlinuz-5.15.0-79-generic root=UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b ro quiet splash
linux /boot/vmlinuz-5.15.0-79-generic root=UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b ro recovery nomodeset dis_ucode_ldr
linux /boot/vmlinuz-5.15.0-76-generic root=UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b ro quiet splash
linux /boot/vmlinuz-5.15.0-76-generic root=UUID=e10f2a1f-decd-4fe5-83e5-8b5571a7674b ro recovery nomodeset dis_ucode_ldr
ls: cannot open directory '/boot/efi': Permission denied
Just wondering why does it say /boot/efi was on /dev/sda1 during installation when it is actually just efi? Am i reading something wrong here?
Offline
I chainloaded Arch to Mint's grub and it helped me boot into Arch. The entry is as follows:
menuentry "ARCH" --class gnu-linux --class gnu --class os {
insmod part_gpt
search --no-floppy --set=root --fs-uuid 14BC-BB61
chainloader /EFI/grub_uefi/grubx64.efi
}
I guess this a temporary fix as the disk (sda) is not in the boot list in UEFI although it shows as a storage device .
Offline
You seem to have multiple "efi" partitions. Have you looked in bios order of boot preferences?
Arch is home!
https://github.com/Docbroke
Offline
Pages: 1