I have always upgraded using dnf-plugin-system-upgrade without issues. This time I decided to format my SSD and do a clean installation. I booted with Fedora-Workstation-Live-x86_64-37-1.7.iso image and installed it. Now I am getting ‘No Bootable Device’ message after reboot.
The boot records are as follows:
[[?2004h[liveuser@localhost-live ~]$ efibootmgr^M
^[[?2004l^MBootCurrent: 0001^M
Timeout: 0 seconds^M
BootOrder: 0001,2001,2002,2003^M
Boot0000* Unknown Device: HD(1,GPT,05687703-a52a-4d71-bba9-a7c8581da8fa,0x800,0x12c000)/File(\EFI\fedora\shim.efi) File(.䍒)^M
Boot0001* Linux HD(2,GPT,ac25d109-653f-46d5-99c1-9890086ba449,0x3c65d8,0x4f7c)/File(\EFI\Boot\grubx64.efi)RC^M
Boot0004* Fedora HD(1,GPT,05687703-a52a-4d71-bba9-a7c8581da8fa,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)^M
Boot2001* EFI USB Device RC^M
Boot2002* EFI DVD/CDROM RC^M
Boot2003* EFI Network RC^M
I have tried to set the bootnum to use to Fedora with efibootmgr -n 0004, but it does not help.
gdisk output for the SSD:
[[?2004h[liveuser@localhost-live ~]$ gdisk /dev/sda
^[[?2004l^MGPT fdisk (gdisk) version 1.0.9^M
^M
Partition table scan:^M
MBR: protective^M
BSD: not present^M
APM: not present^M
GPT: present^M
^M
Found valid GPT with protective MBR; using GPT.^M
^M
Command (? for help): p^M
Disk /dev/sda: 1000215216 sectors, 476.9 GiB^M
Model: HFS512G39TND-N21^M
Sector size (logical/physical): 512/4096 bytes^M
Partition table holds up to 128 entries^M
Main partition table begins at sector 2 and ends at sector 33^M
First usable sector is 34, last usable sector is 1000215182^M
Partitions will be aligned on 2048-sector boundaries^M
Total free space is 2669 sectors (1.3 MiB)^M
^M
Number Start (sector) End (sector) Size Code Name^M
1 2048 1230847 600.0 MiB EF00 EFI System Partition^M
2 1230848 3327999 1024.0 MiB 8300 ^M
3 3328000 1000214527 475.4 GiB 8300 ^M
When I mount the ESP it looks normal to me.
$ ls -R /mnt/sda1/
/mnt/sda1/:
EFI mach_kernel System
/mnt/sda1/EFI:
BOOT fedora
/mnt/sda1/EFI/BOOT:
BOOTIA32.EFI BOOTX64.EFI fbia32.efi fbx64.efi
/mnt/sda1/EFI/fedora:
BOOTIA32.CSV BOOTX64.CSV gcdia32.efi gcdx64.efi grub.cfg grubia32.efi grubx64.efi mmia32.efi mmx64.efi shim.efi shimia32.efi shimx64.efi
/mnt/sda1/System:
Library
/mnt/sda1/System/Library:
CoreServices
/mnt/sda1/System/Library/CoreServices:
SystemVersion.plist
The boot and the main LUKS partitions also mount without issues and seem fine.
I also see the bootloader entry that also looks okay:
sudo cat /mnt/sda2/loader/entries/6d4297258cb245ebb2d463369bf8f02c-6.0.7-301.fc37.x86_64.conf
title Fedora Linux (6.0.7-301.fc37.x86_64) 37 (Workstation Edition)
version 6.0.7-301.fc37.x86_64
linux /vmlinuz-6.0.7-301.fc37.x86_64
initrd /initramfs-6.0.7-301.fc37.x86_64.img
options root=UUID=8b3920a3-fdf0-400d-b94f-730dc24d4945 ro rootflags=subvol=root rd.luks.uuid=luks-705d2626-7292-4509-91e1-21f7f29e793d rhgb quiet
grub_users $grub_users
grub_arg --unrestricted
grub_class fedora
Some hardware information that I can think of:
$ mokutil --sb-state
SecureBoot disabled
BIOS Information^M
Vendor: Insyde Corp.^M
Version: V1.10^M
Release Date: 12/13/2016^M
Address: 0xE0000^M
Runtime Size: 128 kB^M
ROM Size: 4608 kB
System Information^M
Manufacturer: Acer^M
Product Name: Swift SF514-51^M
Version: V1.10
SKU Number: Swift SF514-51_1126_V1.10^M
Family: KBL
Any guidance on how to further troubleshoot and fix it would be greatly appreciated.