Universal Blue•2mo ago

My computer is no longer booting into Bazzite

Hi there. I've had a Bazzite/Windows setup in my computer for some time, but I can no longer boot into Bazzite. I've tried many methods to boot into it, but it seems that my computer isn't recognizing the OS. I think this happened after I updated Bazzite and booted Windows from GRUB. Since then, I've also updated Windows. It could be any of that, but I don't know what caused this problem, and I need help determining how to fix my computer. I've tried running Boot Repair from a pen drive with a live Linux environment. My home partition is encrypted, and I've de-encrypted and mounted it. Still, Boot Repair gave this warning:

You may want to retry after mounting your encrypted partitions so that the tool can verify their contents. (cryptsetup open)

You may want to retry after mounting your encrypted partitions so that the tool can verify their contents. (cryptsetup open)

I put the the report Boot Repair generated in this pastebin, in case it says something helpful. It didn't suggest any fix. My /home partition is in /dev/nvme0n1p6 and my /boot partition is in /dev/nvme0n1p5. Here are pastebins of terminal commands showing some files in my partitions, in case it's something related to missing files. (I am using pastebins because of the Discord post character limit. Let me know if I should do/use something else.) Boot partition Home partition Do you think this could be solved with something like running grub-install from a live Linux environment? If so, what command(s) should I use? And if not, what do you think I should do? Thanks in advance 🙂

Disroot Bin - Encrypted pastebin by PrivateBin

Encrypted note on Disroot Bin - Encrypted pastebin by PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

Disroot Bin - Encrypted pastebin by PrivateBin

Encrypted note on Disroot Bin - Encrypted pastebin by PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

Disroot Bin - Encrypted pastebin by PrivateBin

Encrypted note on Disroot Bin - Encrypted pastebin by PrivateBin

Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

Solution:

The problem was that I had messed up the boot partition's flags. That's why the bootloader fixer wasn't working.

Jump to solution

18 Replies

CheckYourFax•2mo ago

Did you do the boot repair using the Bazzite Live ISO? If you used anything else it'll break your entire system the way grub is set up is not the same as other linux distro's

nagito || Knight of Emilia•2mo ago

yeah it's pretty different though it shouldn't be hard to fix if just the bootloader is broken should it? it's not THAT different but it's pretty different in that normally the grub.cfg contains boot entries but that ain't the case here grub.cfg itself generic uses the blscfg command to read the actal entries generated by OSTree problem is normal grub doesn't even have blscfg fedora's grub does but only fedora's grub technically also OpenSUSE's but they're or at least were using fedora's patches

You can create temp accounts???OP•2mo ago

Hi. I tried it right now, but after selecting the partition, all I got was an error.

liveuser@bazzite:~$ /usr/bin/bootloader_restore.sh
### START LOG Mon Sep 29 22:05:54 UTC 2025 ###
mount: /tmp/mnt/boot/efi: fsconfig system call failed: /dev/nvme0n1p1
/dev/nvme0n1p5: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.
ERROR [bootloader_restore.sh:29]: Failed to mount EFI partition

liveuser@bazzite:~$ /usr/bin/bootloader_restore.sh
### START LOG Mon Sep 29 22:05:54 UTC 2025 ###
mount: /tmp/mnt/boot/efi: fsconfig system call failed: /dev/nvme0n1p1
/dev/nvme0n1p5: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.
ERROR [bootloader_restore.sh:29]: Failed to mount EFI partition

It seems the script failed to mount /dev/nvme0n1p5, even though I had it successfully mounted... (I tried the script before and after mounting the partition) I selected /dev/nvme0n1p5, so I don't really know why dev/nvme0n1p1 shows up in the error message. Thank you for looking into this :) Side rambling: And Mr. Komaeda, it is truly an honour to speak with you. The truth is I did not expect you to be interested in atomic Linux distributions, specially since you seem to have grown appreciation for chaos and despair... (Sorry for the side rambling) :)

CheckYourFax•2mo ago

weird this sounds like a broken EFI system partition

You can create temp accounts???OP•2mo ago

What should I do then? If it's what you're thinking about, is there a possible fix?

nagito || Knight of Emilia•2mo ago

sudo fsck /dev/nvme0n1p5

Solution

You can create temp accounts???•2mo ago

The problem was that I had messed up the boot partition's flags. That's why the bootloader fixer wasn't working.

You can create temp accounts???OP•2mo ago

I just set the flag back to boot_grub in GParted (I had messed with them when trying to fix the problem. Oops...)

nagito || Knight of Emilia•2mo ago

oh you're using GPT on a BIOS system?

You can create temp accounts???OP•2mo ago

I'm pretty sure it's UEFI...

CheckYourFax•2mo ago

you need esp flag for UEFI not boot_grub

nagito || Knight of Emilia•2mo ago

partition flags don't exist on uefi

CheckYourFax•2mo ago

esp+boot (boot should be automatically checked when you pick esp)

nagito || Knight of Emilia•2mo ago

GPT

You can create temp accounts???OP•2mo ago

I don't know how, but setting the flags from esp+boot to boot_grub made the script work... Could it be a bug in the script? And do you think I should switch the flags back?

nagito || Knight of Emilia•2mo ago

the BIOS_GRUB partition/flag is used to store some stuff for that was stored in the hidden sectors of the MBR partition scheme GPT doesn't "support" these hidden sectors so a partition is needed on UEFI GRUB can just sit on/load from the ESP no need to store anything in any hidden sectors or strange un formatted partitions

You can create temp accounts???OP•2mo ago

Let me try removing the flag from the partition to see if the computer still boots into Bazzite... As it should It did. It must be some kind of bug in the script I have one more question: is there any place in the Bazzite docs where it says something about fixing GRUB via the Bazzite live image? I didn't find anything about it in the docs...

CheckYourFax•2mo ago

It doesn't. It might be a good idea to add in the future when it replaces the current old images. Thing is we might not want to replace the images because with the upcoming Fedora 43 we will probably also start using anaconda-webui which is going to be a whole lot different again so having to rewrite the docs twice over is not very efficient right now. I think once the new installer UI becomes usable on GNOME and KDE, a rewrite of the installation guide is in order.

Gaming

Programming

My computer is no longer booting into Bazzite

Did you find this page helpful?