Bazzite boot option missing after booting in windows 10
Hi, I need help reinstall grub. I have 2 ssds. 1st one for Linux and second one I installed windows. After the windows update, my bazzite boot option does not show. I configured to boot bazzite drive first. If there way to recover the system without having to reinstall the os?
40 Replies
/dev/sda looks intact thankfully
I’ll try mounting its ESP in windows
How do we do that? Could u detail instructions? I Am new to Linux.
Boot into windows and start an administrator cmd
Is there any detail guide I can follow?
Super User
How to access efi partition on windows 10?
I am having trouble accessing the EFI partition on windows 10 I tried this method in cmd (I used Administrative privileges
):
open cmd as admin...
diskpart
sel disk 0
sel part 1 (efi part)
assign
I will try that tomorrow
Anyway
We have a ‘rescue a bazzite system’ option. Can we recover from this route?
I do not believe so
The system itself should be fine, just the bootloader
I have several assumptions in mind but there’s not enough information rn
I agree it is the boot loader not working. This is the second time it happened.
For starters do you have legacy boot enabled in BIOS?
May be named something like CSM
I have it but disable. I turn on secure boot and boot in UEFI.
That should be the right configuration
Try disabling secure boot if it’s not too much a hassle
I will try tomorrow and post the result. Thanks.
My system is Lenovo M82 desktop. I upgraded cpu to i7 3770, DDR3 16GB and amd 6600. I stressed test the system in windows and it works fine.
Hi if I disable secure boot, bazzite drive no show on boot list F12.
Disable secure boot and enable CSM legacy boot, bazzite drive is shown on F12 boot list but select it -> blank screen and no grub is shown.
I have mounted ESP in windows.
What to do next?
Compare the files EFI/BOOT/BOOTX64.EFI and EFI/fedora/shimx64.efi
In admin cmd it should work like
certutil -hashfile /path/to/fileSame hash
Have you trying physically unplugging the drive and plugging it in again? Or swaping the physical order of the sata cables? Also if you unplug the Bazzite drive and plug it into another computer does it boot?
Hi I don’t think the cable is loose or something. I can see the drive in bazzite rescue mode and windows.
I don’t have another computer. The SSD is new. I just bought it.
If we can’t fix it. I don’t mind reinstalling the os but I wanna know how to prevent this issue.
I had a situation where I could see the drive and it tried to boot it but randomly failed or sometimes took minutes to boot (couple of years ago, wasn't bazzite). The issue was that I had bumped the cable and it was very slightly loose. So very unlikely that it's the same issue but couldn't hurt to try.
Ok I will try that. Because I can copy file from it in windows , I strongly believe it is not the case.
yeah I doubt it will work but it sounds better than a reinstall in the off chance that it works
This is a wooden case I build it myself.
Nice!!
I believe the EFI entry for bazzite was deleted by windows
I used to use EasyUEFI whenever that happened
Dunno if there's a Windows OSS utility
So we need a live Linux os to use this program. Could u detail the steps? Thanks.
This program is a closed source Windows program fyi
You can use live linux to use
efibootmgr I believe
efibootmgr --create --disk /dev/sdX --part Y --label "Bazzite" --loader /\EFI\fedora\shimx64.EFI
Replace X and Y with your disk
I believe this is the right commandIt seem like there is no bazzite boot loader entry
Appreciate if u could guide me into creating one for bazzite
I got it to work now. Thanks u guys.
Download the program from easyuefi. com
Add a new entry point to EFI/BOOT/BOOTX64.EFI
How can we prevent windows from doing that again?
I don't know unfourtenatly
But It only happened once every few months for me, so I didn't consider it a big deal
That's certainly a useful tool. Good to know it exists for future reference.
Probably a bad bios update I'd guess that cleared the entries 🤷 . Fortunately, those don't happen too often
I did not flash any bios.
It is a free trial program.
windows does bios updates as part of windows update. not too often though
For my device I had to disable the windows entry and rely on other bootloaders to chainload it, or windows will overwrite the bootloader every boot
YMMV
I think I found the culprit. It is windows startup repair. when u unsuccessful boot ur system 3 times, it will repair the EFI drive. Because the bazzite drive is the 1st slot, it repair bazzite drive instead of windows drive. Solution: move Linux drive slot to 2nd one or disable windows service with bcdedit.
Ahhhh, that makes a lot of sense, I'll need to see if I can reproduce that. This is a similar issue that I have seen with Windows where I installed it on drive 2. And it put it's EFI partition my empty drive 1. I later removed drive 1 and ended up with an unbootable system.