Bazzite No Longer a Boot Option (for Dual Boot Windows/Bazzite on ROG Ally X)
Hi, I set up dual boot Windows and Bazzite on my new Ally X a few weeks ago using a partitioned SSD. It was working great until last night I booted into Windows to play some games on that side. Maybe Windows applied some automatic updates that messed up how Bazzite boots, because now I can only boot into Windows. Fedora/Bazzite is no longer an option in the BIOS boot menu.
Looking at Disk Management in Windows, the partition and files for Bazzite still look to be there and without issues.
I installed EasyUEFI to take a look, and the Fedora entry has a status of "Hidden" while Windows Boot Manager is "Normal." I don't know how to make Fedora unhidden. I tried making a new boot entry using this program, but the file paths I'm able to specify (like EFI\Boot\bootx64.efi) is different from what Fedora has (EFI\fedora\shimx64.efi). I can't seem to find a "fedora" folder in EFI when I try to make a new boot entry. Did it get deleted by a Windows update?
If I make a new boot entry I can see it on the BIOS and choose it, but when I do, it goes to a blue reset screen, but still only boots into Windows. I disabled SecureBoot, but that didn't change anything.
I'm a newbie at this stuff, so would appreciate anyone's help in being able to boot back into the Bazzite side. I was hoping to avoid a full reset and reinstall, but not sure if that's my only option now. Thanks in advance.
268 Replies
Is this a single disk configuration?
Yes, this is on one SSD
Check disk management
Are there like multiple EFI partitions?
May be named as System Partition or something like that, and less than 1G in size
There looks to only be a Single EFI System Partition of 260 MB. Disk Management says it's healthy.
You mentioned the fedora folder missing, so there is only Boot and Microsoft in the EFI folder?
Correct, only Boot and Microsoft
I had never looked carefully at these folders, so I guess I don't know if there's supposed to be a Fedora one. I just assumed, given the old file path
There should be one
And most likely the windows update cleared the partition for whatever reason
Can you get a hash of the current
bootx64.efi?
In windows the command will look like certutil -Hashfile E:\EFI\Boot\bootx64.efi
Do the same for EFI\Microsoft\Boot\bootmgfw.efiSorry, I'm dumb and new to this so I don't quite understand what it means to get a hash. Do I run that command in CMD on Windows?
Yes
Replace the drive letters and stuff as appropriate
Okay, I'll give it a try
And it only matters whether the two are the same
Okay, super embarrassing. How do I find out which drive these EFIs are on? I thought it was C drive because that's what Windows is on but CMD tells me it can't find the file when I do that
It’s fine
It should be whatever letter you assigned to the ESP
When I look at the EFI System Partition it doesn't have a letter. Is it on the... FAT32 SYSTEM instead? Is that possible?
It does not have a letter by default
mountvol P: /S should do the trick
And since you weren’t in the ESP in the first place, there’s a chance that fedora boot loading stuff is still there…hm, okay. so I ran mountvol P: /S
I'm not sure if anything happened
That should give you a drive with letter P
oh okay, and now back to getting the hash?
Check if there is fedora in that drive first
EFI still only shows Boot and Microsoft
Then do the hash
okay, so running the command certutil -Hashfile P:\EFI\Boot\bootx64.efi tells me that access is denied.
it does work for Microsoft though, although I'm not sure I understand what it threw out at me. CertUtil: Unknown arg: -P\EFI\Microsoft\Boot\bootmgfw.efi
Use an admin command line session
The error does not make sense tho… Probably a typo somewhere
okay, let me try it again running CMD as administrator
It worked, progress! The big string of letters and numbers that came out for the two are different
Does the bootx64.efi one start with
49dda and end with bbfc8?Yes
49dda68626b94ea6185ddd8498b4a14892cbbfc8?Yes
That’s interesting…
Try directly booting with bootx64.efi
Based on the checksum it is the file from fedora
Oh, so an EFI pointing towards bootx64.efi should work correctly to get into Bazzite?
I would believe so
okay, let me try it again
The lack of the Fedora folder may pose problems but I’m not sure
I get a blue screen that says "Boot Option Restored" at the top. Then it does a countdown to system reset and loops itself over and over. It says I can press any key to stop the reset. If I do that, I get options of "Reset System, Continue boot, and Always continue boot" in a little box
Try continue boot
it doesn't boot anything and loops back to the same blue screen
Ok so it’s the missing config files
oh, maybe those were in the Fedora folder?
Is there a 1G partition on your drive?
Windows should be unable to read it
Yes, it's just named "Primary Partition." I guess I don't know how to tell if it's readable or not by Windows
Do you have winbtrfs installed?
I’m trying to see if it’s possible to recreate the missing files but there’s an ID I don’t know how to get from windows
I've never heard of winbtrfs, so I assume I don't have it. is it something I can find and download?
It’s fine
Do you still have the installer drive for bazzite?
no, I reformatted that drive. I can redownload bazzite and flash it back onto it if needed
Ok so here’s an idea
Download the rpm for
grub2-efi-x64 and shim-x64okay, I Googled it and found a list of a lot. do I choose the one on top, presumably the newest one? Distribution listed as: "Fedora Rawhide for x86_64"
I’ll say go for F41
Fedora 41 updates for x86_64 or Fedora 41 for x86_64
Updates
nice, okay I'll get it now
Versions should be
grub2-efi-x64-2.12-15.fc41.x86_64 and shim-x64-15.8-3.x86_64 from what I'm seeingyep, I got both of them
Extract both of them
I'm not sure how rpms work but there should be some structure like
boot/efi/EFI/fedora in both of them
And mount the ESP in the same way as before since I presume you rebootedoh. when I downloaded them, they just showed up as single .rpm files. not like an extractable folder
They are essentially just archives
So any unarchiver software should be able to work with them
7-zip will be a solution for example
oh yes, I have that. when I extract them, now they're each a ZSTD file in a folder
That should be another layer of compression
oh, even more extraction? lol okay
7zip doesn't want to extract this second layer?
Hmmmm the one I found does not have the zstd layer it seems…
https://kojipkgs.fedoraproject.org//packages/grub2/2.12/15.fc41/x86_64/grub2-efi-x64-2.12-15.fc41.x86_64.rpm
https://kojipkgs.fedoraproject.org//packages/shim/15.8/3/x86_64/shim-x64-15.8-3.x86_64.rpm
Both are directly from Fedora, just in case
okay, let me try these ones out instead
oh no, I get the ZSTD layer again. is it something with my system
Try directly opening in 7-zip?
Or I’ll just copy my version ig
okay, I updated 7Zip and maybe it works now? it's a .cpio file
Yes that’s correct
whew, we made it
For both packages, copy everything from the
boot/efi/EFI/Fedora to your ESP
So that you have like P:\EFI\fedora\grubx64.efi for examplehm, okay so I have the packages. I also remounted to the P drive. but how do I actually access the P drive to copy the folders over? I can't find the P drive just through the normal Windows folders
It should be in explorer alongside C and everything else afaik
May need admin privileges
Or worst case just copy over the command line
okay! I think I did it successfully
is it time to try and reboot?
Just to be sure
You have grubx64.efi in the fedora folder right?
That should allow us to make some progress
yes. there's also mmx64.efi, shim.efi, shimx64.efi. and an Excel spreadsheet file of BOOTX64
Then try rebooting
Most likely we will be dropped to a grub shell since there should be a missing config file
I got that repeating blue screen again when trying to boot originally, but then I changed to trying to boot with grubx64.efi and it took me to a black grub screen, maybe this is the shell you're talking about?
GRUB version 2.12
Is there like a
grub > at the bottom?yes!
Ok progress
Now we need to find the boot partition
Try
ls
Should give you a list of partitions like (hd0, gpt1)(memdisk) (proc) (hd0) (hd0,gpt7) (hd0,gpt6) (hd0,gpt5) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1)
ls each of them until you find one that says filesystem is ext4
I would guess it’s gpt 3, 4, or 5
If one looks like a match, ls it again with an ending slash like ls (hd0, gpt3)/
The goal is to find a partition that has the folder grub2gpt7 - btrfs
gpt6 - ext2
gpt5 - fat
gpt4 - unknown
gpt3 - unknown
gpt2 - unknown
gpt1 - fat
Then try 6
that one returned as: lost+found/efi/loader.1/ostree/boot loader grub2/bootupd-state.json
That’s the one
set root=(hd0, gpt6)
set prefix=(hd0, gpt6)/grub2
insmod normal
normaloh! something's happening
If all goes well it should lead to the normal grub menu
oh it actually
booted me straight back into Bazzite
Nice
That is temporary though
oh no...
can we fix it permanently?
Try
rpm-ostree status
With some luck it should be able to restore grub to it’s original stateso I restart the device and make my way back to the grub shell with the grub> thing and then type in the rpm-ostree status?
Yes, for now you will need to do the four lines every time to get back to bazzite
And judging from the FAT partition in 5, I now believe I have overcomplicated the matter :clueless:
lol, well that's fine
but rpm-ostree status gives me
error: ../../grub-core/script/function.c:119:can't find command 'rpm-ostree.'
No not in the grub shell
In bazzite, once you have booted
ohhhh
let me get back into Bazzite with the magic four lines and then do that again
okay, I ran rpm-ostree status in the terminal on Bazzite. it said State: idle, and then a bunch of stuff in Deployments
do you want to know what it says, or should I just try rebooting and see if it fixed the problem now?
It won’t fix the problem yet
Try
mountoh, I'm getting ahead and too excited
Look for a line that mentions
/boot/efi
And check if the device name it mentions at the start of the line says 1 or 5
Probably like /dev/nvme0n1p1there's a lot of lines, trying to find /boot/efi in here somehow
Or just try
mount | grep /boot/efiokay, I did that. what should I be looking for on what it gave me?
The device name
It should be either
/dev/nvme0n1p1 or p5 I thinkdevice name is /dev/nvme0n1p1
Try
cat /etc/fstab
Also look for the line that mentions /boot/efi, which should say UUID= something at the beginningUUID=B013-75F3 /boot/efi
Then
sudo blkid /dev/nvme0n1p1
And do the same for p5
There should be one that matches the UUID abovep1 UUID matched
So p1 is the intended ESP all along…
Now just in case
sudo mount /dev/nvme0n1p5 /mnt
And check what’s in /mntcan't find in /etc/fstab
Shouldn’t need to be there
Just mount over the terminal
oh, I mean, I get that message after I type in that command. did I mount it wrong?
Did you include the /mnt at the end?
sudo mount /dev/nvme0n1p5 /mntlet me try again, maybe I typed it wrong
okay, when I typed in sudo mount /dev/nvme0n1p5 /mnt, I hit enter and I can't tell if anything happened. it just brings me to another command line
That’s normal
oh okay
Now check /mnt with your file explorer
Dolphin or whatever their gnome equivalent is
Again may ask for your password
Does it also have an EFI folder?
ah okay. I have folders "AsusWinRE", "AsusWinREBackup" and "System Volume Information"
I don't see an EFI folder
Hmmm so there is only 1 ESP all along…
sudo umount /mnt
Then mount | grep /boot
And find the line that does not say /boot/efi, just /boot
Most likely /dev/nvme0n1p6yep!
type ext4
sudo blkid /dev/nvme0n1p6
And keep track of the UUID
Will be much longer than the previous ones, just in casef26929fd-c2b2-43fe-9563-759c845d6249
sudo nano /boot/efi/EFI/fedora/grub.cfg
And write the following
It may help if you can directly copy from, for example, a web discord sessionokay, let me give this a go
Once done, Control-O, Enter, and Control-X
uh oh, Error writing /boot/efi/EFI/fedora/grub.cfg: No such file or directory
In another terminal tab,
sudo ls /boot/efi/EFIBoot Microsoft
That’s… majorly strange
rpm -qa | grep grubyep, there's a bunch of grub2 lines
sudo ls /boot/efiDroidSansFallback.atf, EFI, RC72LA.BIN, 'System Volume Information'
That’s also normal…
wait, I just had a thought. maybe I copied my files over stupidly way back then. is it possible the file path should be Boot/boot/efi/EFI if there are a bunch of nested folders
Makes sense
Check in your file explorer then
omg, there are so many nested folders
Just make sure you have
/boot/efi/EFI/fedorait's like boot>boot>efi>EFI>Boot>boot>EFI>fedora
Two layers of EFI is normal
Two of boot is usually not
maybe when I copied over the packages there were multiples or something
umm... how do I go about fixing it? can I just pull them out of some of these nested folders
ls /bootboot bootupd-state.json efi grub2 loader loader.0 lost+found ostree
Oh nvm /boot/boot is normal
Then
sudo find /boot -name fedora/boot/efi/EFI/Boot/boot/efi/EFI/fedora
sudo ls /boot/efi/EFI/Boot/boot/efi/EFI/fedoraBOOTX64.CSV grubx64.efi mmx64.efi shim.efi shimx64.efi
sudo mkdir /boot/efi/EFI/fedora
Then sudo mv /boot/efi/EFI/Boot/boot/efi/EFI/fedora/* /boot/efi/EFI/fedora/mv: cannot stat '/boot/efi/EFI/Boot/boot/efi/EFI/fedora/*': No such file or directory
Then
sudo -i
And do the mv without sudookay, I entered it. it didn't really show anything
ls /boot/efi/EFI/fedoraBOOTX64.CSV grubx64.efi mmx64.efi shim.efi shimx64.efi
ls /boot/efi/EFI/bootboot B00TIA32.EFI bootx64.efi fbia32.efi fbx64.efi
rm -rf /boot/efi/EFI/boot/bootdone
exit
The other tab is still running nano I think?yes, I think so
Then Ctrl-O, Enter, and Ctrl-X there
whee, it worked this time. after we sorted out the folders
Then we should be all set
Try rebooting into both systems
the moment of truth! let me give this a go now
Windows worked. Bazzite took me to the grub shell with the grub>
Hmmmmmm
Do the four line again
And
sudo grub2-install /dev/nvme0n1p1 in bazzite
Then ujust regenerate-grubI can't get out of the grub shell now with those 4 lines
it just kind of clears the black screen after the last line and goes back to what it originally looks like
Then go back to windows and delete the
P:\EFI\fedora\grub.cfgcan I boot to Windows from the grub shell? Bazzite is top priority for booting and I can't get to BIOS to get back into Windows
Or if your BIOS supports booting from file, choose the bootmgfw.efi from there
okay, I'm back into Windows now.
so have to mount to P and then deleted that grub.cfg
Yes
After that you should be able to return to bazzite with the 4 lines again
Then
sudo grub2-install /dev/nvme0n1p1 and ujust regenerate-grubokay, it said it was generating a grub config file and adding a boot menu entry
and then that it's done
time to give it another reboot?
Try
sudo cat /boot/efi/EFI/fedora/grub.cfg just in case
With some luck it will generate a correct versioncat: /boot/efi/EFI/fedora/grub.cfg: No such file or directory
is that the grub.cfg file I deleted earlier when I got stuck in the grub shell
It's probably normal...
Yes it is
Try rebooting then
okay
oop, this grub shell is back again to haunt me
I thought I deleted you
It should
The default config is not working for some reason so we have to like configure it on the spot every time
interestingly, when I do the 4 lines of code to get out of the grub shell, now it shows me more options. it used to be only Fedora on there, but now there's like 2 versions of Fedora, Windows Boot Manager, and an UEFI choice
That's what regenerate-grub does
ohhh
And would you mind giving the full output of
sudo blkid /dev/nvme0n1p6 in bazzite?
Again it would be the best to just copy/dev/nvme0n1p6: UUID="f26929fd-c2b2-43fe-9563-759c845d6249" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="00e4ac6f-ca5c-4f0a-acdc-3ee59e1a3c8c"
Then the grub.cfg we made is correct...
Let's recreate it and see exactly what is the error then...
sudo nano /boot/efi/EFI/fedora/grub.cfgyep, I'm in sudo nano again
do you want me to retype the
search --no-floppy --fs-uuid --set=dev f26929fd-c2b2-43fe-9563-759c845d6249
set prefix=($dev)/grub2
export $prefix
configfile $prefix/grub.cfg
Again, best to just copy
And Control-O, Enter, Control-X to exit
After that reboot, but keep an eye out for other information on the grub shell screen if it happens again
oh! it worked this time without any grub shell. I must have messed up the code the first time we were in sudo nano
Nice
And ofc check both systems
let me give Windows a try now
Ideally you can just choose the windows entry from the grub menu
Or from BIOS, a matter of preference here
I think we finally did it! I think it's working as it should now
Nice
do you know how to stop Windows from deleting what it did before?
Unfortunately no
oh no...
Windows works in strange ways
so in the future, someone may have to heroically spend 5 hours walking me through something like this again
I haven't seen this myself but there may be other discussions on this somewhere in this server
I saw a few posts on Reddit from the past few days with people also having this issue, so maybe it was related to a Windows update. but they didn't seem to figure out the problem from what I could see
Yeah Windows nuking a Fedora folder is... immensely strange
anyway, thank you SO MUCH for all your time and help. you spent a really long time with me walk through the issue
It may help to keep a copy of that folder just in case :happy_green_trees:
And np
save a copy of the Fedora folder?
I can do that
Yes
To somewhere your windows can read
Oh and there is this possibility that later bazzite updates will complain about missing stuff related to grub
It will be normal since we sort of just copied the bare minimum for booting up
oh, I see. Will Bazzite know what to do? or will it break?
It should be fine
ostree ensures that
And ig I will make a quick summary for closing the issue
Cause of problem is that a windows update nuked the Fedora files in the ESP for some reason.
Solution:
Manually back the main EFI files, under
EFI\fedora after mounting the ESP in windows.
As UUID cannot be found from Windows, boot up grub with the config missing, and manually set root and prefix for a temporary boot.
Once in Bazzite, use blkid to find the UUID for the Bazzite boot partition, and fill in EFI/fedora/grub.cfg accordingly.Windows updated yesterday and this happened to me as well. I haven't had time to go through all of this post but will try tomorrow to see if I can get the Bazzite boot option back.
would these instructions change in any way if I'm having the exact same issue but I do have two EFI partitions with a single drive configuration?
Note that oftentimes the Fedora files are still in the ESP, and just the boot option is deleted
This is especially likely if you have two EFIs
Yeah I was thinking along those lines but I don’t know exactly how to check if the files are there. Can I use the bazzite (Fedora) live USB to access the command line and mount one of the EFI partitions? If I can, which files should I look for to make sure everything is fine and it’s just the boot option missing?
The answer to that might be on this same thread, I just haven’t had a chance to go through it
Yes
Unfortunately the Fedora folder is missing from the EFI folder on the EFI partition I created for bazzite
What is on the EFI?
Just a BOOT folder
Not even Microsoft???
Oh separate ESPs
What's on the other EFI?
Let me check
Try hashing
boot/bootx64.efiBOOT and Microsoft, no Fedora
I don’t know exactly how to hash the file… I think you posted some instructions on this thread, I’ll try later today
49dda68626b94ea6185ddd8498b4a14892cbbfc8So it’s the same problem as OP
Manually populate EFI/fedora folder and you should be good
got it, I don't know if the steps will be same given I have two EFI partitions but I'll try to go through what you discussed with the OP
thanks!
Got it working now!!! Thanks :winku:
I'm having the same problem as OP, so I downloaded EasyUEFI and see my Fedora entry is also hidden. I plan on following the exact steps in earlier chats, but wanted to know if its normal to have two Windows Boot Manager entries and one is hidden?
I cannot recall if mine had multiple Windows Boot Manager entries, but as long as you have the Boot and Microsoft folders and no Fedora folder on your EFI partition (or on either of them if you have two EFI partitions like me), I think the method should still apply
It’s worth noting I didn’t need to do the very last steps of the process, after configuring and creating the grub.cfg file it worked for me
Can anyone tell me how do I do this?
Easiest way is an option in your BIOS, but that will be device specific
I'll write up the steps I took after sifting through the original thread in case it comes useful for anyone stumbling upon this:
NOTE: Mount your EFI partition(s) and confirm you only have either the
BOOT directory or a combination of both BOOT and Microsoft. If that's not the case these steps might not work for you.
1. Follow the steps to generate the hash of the bootx64.efi and bootmgfw.efi files (instructions here: https://discord.com/channels/1072614816579063828/1316221468581036055/1316229156232630333)
2. Confirm your hash starts with 49dda and ends with bbfc8
2. Download the rpm for grub2-efi-x64 and shim-x64 (I downloaded different ones but I don't think posting links would be a good idea, stick to the ones recommended by Linus: https://discord.com/channels/1072614816579063828/1316221468581036055/1316254125859541044)
3. Extract them and extract again the generated .cpio file, for both shim and grub2
4. For both packages, copy everything from the boot/efi/EFI/Fedora to your ESP: https://discord.com/channels/1072614816579063828/1316221468581036055/1316256352825245748
5. Reboot, you should be able to boot intro grub2 now (after selecting that boot entry in your BIOS for "Fedora"), otherwise you'll keep seeing the blue screen or booting into Windows
6. Do the steps starting from here until you can boot into Bazzite: https://discord.com/channels/1072614816579063828/1316221468581036055/1316264693597212672
7. Once in bazzite, go into Desktop mode and open a terminal
8. Type mount | grep /boot and find the line that says /boot (NOT /boot/efi) copy the partition name at the start of the line (/dev/nvme...)
9. type sudo blkid /dev/nvme.. where /dev/nvme.. is the partition name you copied last step
10. Copy the UUID
11. Follow the steps starting here until creating the /boot/efi/EFI/fedora/grub.cfg file: https://discord.com/channels/1072614816579063828/1316221468581036055/1316278476843778089, replacing the first line search --no-floppy --fs-uuid --set=dev f26929fd-c2b2-43fe-9563-759c845d6249 with your UUID after --set=dev
I tried copying the step links so follow the original thread as much as possible if you have any questions, glFor both packages, copy everything from the boot/efi/EFI/Fedora to your ESP: :ring_buoy:bazzite-helpBazzite No Longer a Boot Option… How do I do this? I can't find the P drive in my file explorer even after opening with admin priv.Have you mounted your ESP?
using
mountvol P: /S? Do I have to do it again after doing it the first time?You shouldn’t need to…
That usually works but I’m not sure how windows will handle two ESPs
You may need to tweak around with
diskpart in that caseI only have one ESP, let me just redo the steps I must've messed up at some point.
Or just try
P: in cmdJust to make sure, this is how it should look right?
Looks good to me
Okay, and then from there I reboot my device and enter my BIOS and should fedora appear again as a boot option or do I need to set up the path of it in the BIOS?
Again depends on the device
Booting into
EFI/boot/bootx64.efi should usually workLooks like everything is back to working like how it was before. I only have one final question, is having two Fedora boot options normal? One has a path that leads to
shimx64.efi (that's the one that is first priority when booting) and the other has a path that leads to bootx64.efi. Does it matter which one is higher priority?The two are usually the same file so I’ll say no
This may be a dumb question, but no as in its not normal? Or did you mean no, it doesn't matter which is higher priority?
The latter
Okay, just wanted to clarify. Thanks for all the help as well as you @phsxes!
Windows nuked my ability to boot into Bazzite as well. I get to a grub prompt and that's it. @Linus Xu @phsxes do you think the steps above will get it back for me?
Depends on how much damage windows has done
If grub is still there you should be able to start from https://discord.com/channels/1072614816579063828/1316221468581036055/1316268045995474954
Or https://discord.com/channels/1072614816579063828/1316221468581036055/1316264653461917788 to find your /boot first
Boo, that's just pops me right back to the grub> prompt
Grub prompt is when grub itself works but cannot find a valid config file
For bazzite it first loads the EFI/fedora/grub.cfg, which points to your /boot with the real config
Hello there, I'm also having this issue after a Windows update ... I've mounted the first EFI partition and after generated the hash on
\EFI\Boot\bootx64.efi and \EFI\Microsoft\Boot\bootmgfw.efi I get ... f416cfc3c840b619cf6f87bbcc7d5a0c9ecd46b1. Are the next steps of the fix (download grub2-efi-x64 and shim-x64 and copy the extracted file on the EFI partitions) relevant or should I just reinstall Bazzite?
I've tried to boot on the second EFI partition but it kept boot-lopping on a blue screen.Check the second EFI partition
Unfortunately the second EFI partition only contains
bootx64.efi
Ah, the hash on this one is indeed
49dda68626b94ea6185ddd8498b4a14892cbbfc8
Is it safe to carry on the creation of the boot/efi/EFI/Fedora folder on the first ESP using the RPM files linked by @Linus Xu ?Oh this finally explains some stuff oh thank god
(Excuse my ignorance, although I'm fluent in Linux, I'm clearly not a power-user)
I'm gonna ping people about this
Its same to make it, yes, make sure you create the boot entry as well
Oh yeah copy to the Second ESP, not first
That guide assumes hte boot entry has survived unaltered
Ok, so basically, I just fix the second ESP using these steps then selecting it should no longer bring me into a bootloop, right?
Yes, you'll at first be at the grub command line
Alternativally
You can check those
chk files, and rename each one to the correct nameIt would be hard to be to determine the original filenames. Unless someone knows, I'll try the Grub command line method later today.
10 is EFI/fedora/grubx64.efi
9 is EFI/fedora/grubia32.efi
2 and 3 are shimx64.efi and shim.efi
4 is mmx64.efi
1 is shimia32.efi
0 is mmia32.efi
5-8 are text files (BOOTIA32.CSV,BOOTX64.CSV, grub.cfg and I don't know the last)
And all these renamed files should be moved to the
boot/efi/EFI/Fedora/ directory of the secondary ESP?
BTw thanks for the support @Kasher_CS !Should be in EFI/fedora, yes
Verify the contents of the text files in order to know which name they are
They are not identical
shimx64.efi and shim.efi are identical for me, so that doesn't matter
Not boot/efi/EFI/fedora, that's the Linux location
ah right, on the
/EFI/Fedora directory of the ESP partition.Yes
fyi, content of
FILE0008.CHK is Secondary grub confgi?
Check the others
file 5 contains
6
7 contains a shell script begining with
After renaming these files (5 as
BOOTX64.CSV , 6 as BOOTIA32.CSV and 7 as grub.cfg ) I've moved them in /EFI/FEDORA of the second ESP. I've booted on this partition and got an error File 8 is bootuuid.cfg
Alright, let's put this file and boot again
ah well ...
The hash means shim checks out but other files may be damaged
Managed to get Bazzite up and running again last night. Made a copy of the fedora folder like was suggested just in case
If this issue happens to reappear and we have a backup of the Fedora folder, would it be a matter of placing the backup inside the ESP and reboot?
In the vast majority of cases yes
May need to update them accordingly if there’s a grub related update
Got it, thanks!
Ok, thanks to you, the other method is working.
Here is a little guide based on @Linus Xu and @phsxes
1. Identify the ESP
- Open the ESP (using EasyUEFI or by mounting it)
- Check the hash of the bootx64.efi file
It should be
49dda68626b94ea6185ddd8498b4a14892cbbfc8
2. Copy grub2 on ESP
- Download the 2 packages
https://kojipkgs.fedoraproject.org//packages/grub2/2.12/15.fc41/x86_64/grub2-efi-x64-2.12-15.fc41.x86_64.rpm
https://kojipkgs.fedoraproject.org//packages/shim/15.8/3/x86_64/shim-x64-15.8-3.x86_64.rpm
- Extract RPM packages and then the CPIO file.
- Copy the archives content of boot/efi/EFI/Fedora on the ESP EFI/fedora
3. Start Bazzite
- Boot on Fedora, you should reach grub2 prompt
- Find the EXT* partition with ls command, result should look like
- Type ls (hd0,gpt7) for each partition to identify the correct one.
- Find the grub2 directory on the correct partition using ls (hd0,gpt7)/, where you replace (hd0,gpt7) by the partition you previously identified
- Type the following command
(also replace (hd0,gpt7) here )
- Bazzite should boots up
4. Fix Bazzite boot
- Go in desktop and open a terminal
Identify the mount (line having /boot, NOT boot/efi)
- Get the mount UUID
where you replace /dev/nvme0n1p6 by the mount previously identified
- Create grub.cfg
- Put the following
Where <UUID> is the value you got from the previous step.
This should be it. You can reboot to test it.