Rescueing Silverblue Installation

Ask Fedora
, ,
1

Hello, everyone.

I have a Silverblue system that no longer shows up in my bios menu. I can get into the system using another live Linux distro. (MX Linux has grub rescue)

How do I rebuild the MBR of the drive? I have read to not use mkconfig or grub-update. Once I’m in the system, everything seems fine. Why would the drive suddenly stop showing up in the bios?

HP Z840
Fedora Linux 40 Silverblue

Is there a command to have the system rebuild boot folders, and MBR or GPT?

Any help would be greatly appreciated.

2

UPDATE:

I created a Fedora 40 Silverblue USB and booted into Troubleshoot Rescue a Fedora system. It found my LUKS partition and ask for password. Entered password to only get 'No Linux system found.

Drop me to a shell that only shows the USB installation.

Any suggestions?

3 
02:25:03 james@HP-Z840 ~ → sudo bootctl status
[sudo] password for james: 
systemd-boot not installed in ESP.
System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (setup)
  TPM2 Support: yes
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Enroll SecureBoot keys
               ✗ Retain SHIM protocols
               ✗ Menu can be disabled
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─n/a

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/183be3ee-a4d3-4a0b-bd81-2b62e6e4431e)
         File: ├─/EFI/BOOT/BOOTX64.EFI
               └─/EFI/BOOT/BOOTIA32.EFI

Boot Loaders Listed in EFI Variables:
        Title: Windows Boot Manager
           ID: 0x0024
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/183be3ee-a4d3-4a0b-bd81-2b62e6e4431e
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

        Title: Linux Firmware Updater
           ID: 0x0025
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/183be3ee-a4d3-4a0b-bd81-2b62e6e4431e
         File: └─/EFI/fedora/fwupdx64.efi

Boot Loader Entries:
        $BOOT: /boot/efi (/dev/disk/by-partuuid/183be3ee-a4d3-4a0b-bd81-2b62e6e4431e)
        token: fedora

0 entries, no entry could be determined as default.
lines 11-56/56 (END)
4 
02:28:04 james@HP-Z840 ~ → efibootmgr
BootCurrent: 001D
Timeout: 0 seconds
BootOrder: 0009,0024,0025,001D,0011,000C,000E,0010,001E,001F,0020,0026,0012,0000,0001,0002,0003,0004,0005,0006,0007,0008,000A,000B,0013,0014,0015,0016,0017,0018,0019,001A,001B,001C,000F,000D
Boot0000  Startup Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)0000000049535048
Boot00000010* Hard Drive	PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/EDD10(0x4ff7f80)4eac0881119f594d850ee21a522c59b21000000049535048
Boot0001  System Information	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f1000000000049535048
Boot0002  Bios Setup	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)100f0000000049535048
Boot0003  3rd Party Option ROM Management	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f3000000000049535048
Boot0004  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)00f20000000049535048
Boot0005  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)01f20000000049535048
Boot0006  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)02f20000000049535048
Boot0007  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)03f20000000049535048
Boot0008  Boot Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f9000000000049535048
Boot0009* hp HLDS DVDROM DUD0N 	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)4eac0881119f594d850ee21a522c59b20900000049535048
Boot000A  Network Boot	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)120f0000000049535048
Boot000B  HP Recovery	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)110f0000000049535048
Boot000C* Samsung Flash Drive FIT 0374123070000227	BBS(USB,USB1,0x900)/PciRoot(0x0)/Pci(0x1d,0x0)13001908000049535048
Boot000D  hp TSST DVDRW SU-208HB 	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(1,0,0)4eac0881119f594d850ee21a522c59b20900000049535048
Boot000E* Samsung SSD 850 EVO 1TB 	BBS(HD,Harddisk1,0x400)/PciRoot(0x0)/Pci(0x11,0x4)01001000000049535048
Boot000F  Network Boot	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)120f0000000049535048
Boot0010* Samsung SSD 850 EVO 1TB 	BBS(HD,Harddisk2,0x400)/PciRoot(0x0)/Pci(0x11,0x4)02001000000049535048
Boot0011* hp HLDS DVDROM DUD0N 	BBS(CDROM,CDROM1,0x400)/PciRoot(0x0)/Pci(0x1f,0x2)03000900000049535048
Boot0012  hp TSST DVDRW SU-208HB 	BBS(CDROM,CDROM2,0x400)/PciRoot(0x0)/Pci(0x1f,0x2)04000900000049535048
Boot0013  Startup Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)0000000049535048
Boot0014  System Information	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f1000000000049535048
Boot0015  Bios Setup	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)100f0000000049535048
Boot0016  3rd Party Option ROM Management	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f3000000000049535048
Boot0017  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)00f20000000049535048
Boot0018  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)01f20000000049535048
Boot0019  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)02f20000000049535048
Boot001A  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)03f20000000049535048
Boot001B  Boot Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)f9000000000049535048
Boot001C  HP Recovery	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)110f0000000049535048
Boot001D* Samsung Flash Drive FIT 0374123070000227	PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(4,0)4eac0881119f594d850ee21a522c59b20908000049535048
Boot001E* #0100 ID09 LUN0 ATA      ST8000VN0022-2	BBS(HD,Harddisk1,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)15001000000049535048
Boot001F* #0100 ID0A LUN0 ATA      ST8000VN0022-2	BBS(HD,Harddisk2,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)16001000000049535048
Boot0020* #0100 ID0B LUN0 ATA      ST8000VN0022-2	BBS(HD,Harddisk3,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)17001000000049535048
Boot0024* Windows Boot Manager	HD(1,GPT,183be3ee-a4d3-4a0b-bd81-2b62e6e4431e,0x800,0x12c000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000033000100000010000000040000007fff04001400000049535048
Boot0025* Linux Firmware Updater	HD(1,GPT,183be3ee-a4d3-4a0b-bd81-2b62e6e4431e,0x800,0x12c000)/\EFI\fedora\fwupdx64.efi
Boot0026* #0100 ID0C LUN0 ATA      ST8000VN0022-2	BBS(HD,Harddisk4,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)18001000000049535048
5

That output with so many boot entries probably has the bios boot menu too full to allow new entries. I count ~36 entries there and that is probably mostly unneeded.

You could remove the excess with efibootmgr -B -f XXXX to delete the excess entries (one at a time), then the proper one could probably be selected.

6

Well, most of those are part of the bios boot list. The others are legacy items. At least 12 of them aren’t even boot devices but show up in the Boot Menu. That’s why I can’t understand why the Fedora drive doesn’t show up.

I can boot into MX Linux live distro with a USB and use the Boot Rescue Menu and get into the system. I wish Fedora had a bootloader os-prober like Debian. That’s the only way I can use the system now, without rebuilding it from scratch. I bet I have made over 2000 modifications. Even though I backup /var and /etc, the hassle of having to start over and restore any of the configs seems unnecessary.

The reason there are so many boot items is it is listing the UEFI and EFI. HP workstations do that. It will boot anything. Even SD Cards.

Thanks for the response.