After update pc says there is no boot storage in fedora 35

Hi, i installed fedora 35 in my surafce 5. i installed it 2 times,

  • uefi off

  • uefi on with Microsoft + 3rd party key option.

But both installation, after i updated my system, device reboots and can’t find the boot storage, say there is not bootable storage.

what to do?

Hallo @rahmanshaber How did you install?
What do you mean by “uefi off”?
Could you look into the storage room via Microsoft?

installed using a usb flash drive,
uefi off means installed in legacy or BIOS mode.
i can see fedora option in the BIOS menu but when device boots it says the drive is not bootable.

Is the boot partition flagged as bootable. The output of “sudo fdisk -l” will tell you. In legacy mode the boot partition must be flagged as bootable. In uefi mode that is not required.

i can’t use the system to do the cmd as it says no bootable storage found. will it work in live disk?

Hi, I’m just curious. Why you turn off the UEFI on BIOS? I believe if your system with Microsoft Windows are using UEFI bios system, it would be more save if you installing Fedora with bios UEFI on (and easier to troubleshoot). It also will protect you if one of your operating system fail and will make sure the other still work by changing the list of first boot from the BIOS.

But before that, you could follow @computersavvy suggestion by using Fedora live disk. It will tell your current partition layout.

I just tried with both so i can make sure it’s not issue of UEFI or BIOS.

1 Like
Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: INTEL SSDPEBKF128G7                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B60D6DF3-73CC-418D-A1B0-482B7EE75673

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1230847   1228800   600M EFI System
/dev/nvme0n1p2 1230848   3327999   2097152     1G Linux filesystem
/dev/nvme0n1p3 3328000 250068991 246740992 117.7G Linux filesystem


Disk /dev/sda: 14.41 GiB, 15472047104 bytes, 30218842 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00bc5495

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1  *     2048 30218841 30216794 14.4G  c W95 FAT32 (LBA)


Disk /dev/loop0: 1.77 GiB, 1895727104 bytes, 3702592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 7.5 GiB, 8055160832 bytes, 15732736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-rw: 7.5 GiB, 8055160832 bytes, 15732736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-base: 7.5 GiB, 8055160832 bytes, 15732736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 3.74 GiB, 4016046080 bytes, 980480 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Ah I see. Could you check on the BIOS and find the boot order list? If there mention Microsoft or Windows things (or maybe you find mentioning Fedora), it tell us that your surface are running on UEFI system. But if it only mention disk without mentioning Microsoft or Windows, it must me BIOS legacy.

If this is the case, change the list as you want which on you want to boot, either Microsoft or Fedora.

Edit:

Please turn on UEFI on the BIOS.

here what the BIOS/UEFI menu looks like

here you can see which option of uefi is set

Here is the boot order

1 Like

Here is the problem

Your system are running UEFI. The last suggestion from me are by disable the secure boot.

On Change Secure Boot Configuration you could choose None.

Since the boot order already use Fedora as first boot, please try to boot again.

If this could not work, please stick around. I believe someone with more experiences will help you.

i tried it as i mentioned in my post. both BIOS or UEFI device says there is not bootable OS.

when the installation was finished and it rebooted to setup the system and all worked fine. then i updated the system and then i reboot the device then this crap.

@rahmanshaber because the problem is from after an update, updated apps could be the cause.
Could you try to boot from previous kernel in Fedora?
How to boot an earlier kernel on Fedora - Fedora Magazine.

1 Like

how can i do this if there is no os? or i will use a live disk?

EDIT: i see no grub menu or any kernel loading. i think that update messed up the grub.

I would just do a clean reinstall. Remember your machine is Uefi.

Actually there lots of way to troubleshoot, but I believe it’s much be easier to reinstall your laptop as suggested by @jpbn. Backup your files first by using Fedora live cd and copy-paste it to external drive.

Also from the internet it suggested to disabling the Secure Boot before installing linux on Surface laptop. I believe it could be done by choosing None to the option bellow:

Hello @rahmanshaber ,
Welcome to the discussion area. If you are using usb media to install, you can get to a command prompt and mount devices from the command line. I believe rsync will be available to you for copying your home directory to another storage device. If you have done this install originally from fresh, just reinstall after turning off secure boot in UEFI. Or if you are determined to run Fedora Linux under secure boot then you will need to use a shim loader as per https://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Boot_Guide/index.html