I have been procrastinating this for a long time. I have three operating systems on my Surface Laptop 3 13.5”: Windows, Linux Mint 21.1 Cinnamon, and Fedora Linux (6.4.14-200.fc38.x86-64) 38 (Workstation Edition). Fedora was installed after Linux Mint. When I installed Fedora, Linux Mint wouldn't boot from the GRUB installed by Fedora, but it would still boot from the GRUB installed by Linux Mint (but that's not the issue I am concerned with here).

One day (around 6 months ago), I wanted to allocate more storage to the Windows partition and less to the partition containing Fedora. I did this from GParted on a live USB containing Fedora Linux 37 (Workstation). It worked, but after doing so, I noticed that my Fedora would no longer boot from GRUB. Because Windows would still boot, I didn't give this much attention for a while.

Now, around six months later, I've come back to this issue. I notice that Fedora will still not boot, but for some reason Linux Mint is able to boot from the GRUB installed by Fedora now. Using Linux Mint as well as the GRUB (version 2.06) command line, I was able to see that the partition used to access vmlinuz-6.4.14-200.fc38.x86_64 and initramfs-6.4.14-200.fc38.x86_64.img still contained those files and retained the same UUID. The root partition for Fedora also contained the same files and retained the same UUID as before. When I boot Fedora without the "rhgb quiet" option, the boot hangs at "Booting a command list".

Perhaps more concerning is the fact that I could no longer boot from the exact same live USB as before. Thinking it might be a live USB issue, I tried using Fedora Media Writer to create a live USB with the same exact version of Fedora that it contained previously, but the result was the same (hangs when trying to boot from GRUB).

Any ideas?

(for tldr, just read the title of this post)

Maybe update UEFI or try with rEFInd.

>stealthbumping

>>1522046 (OP)
man, i just dualbooted first time recently
didn't know you could triple boot
still wondering why i can't access windows w/o turning off secure boot, even did the weird key thing as perplexity.ai suggested
maybe my windows went not updated for so long
/unrelated

>>1522046 (OP)
Get your hex tools out, you have to reshuffle some bytes, happened to me but recovered boot locations pretty easily. Good luck, ask deepseek for help because I'm not going to "Please wait a while before posting"

>>1528269
>Good luck, ask deepseek for help because I'm not going to "Please wait a while before posting"
You already did.

b

>>1522046 (OP)
Doesn't surface need a special kernel to work fully on Linux?

https://wiki.ultramarine-linux.org/en/anywhere/surface/

what if you copypaste op post into https://www.perplexity.ai

b

b

b

>>1529282
buy an ad

b

b

b

b

b

>>1522046 (OP)
Can you post “parted -l” output

>>1526378
you probably got a rootkit or bootkit, it won't boot without secure boot because the OS or bootloader on the drive have been tampered with

>>1533004
i meant with secure boot***

b

b

b

b

>>1522046 (OP)
Two recommendations:

First, try chrooting into your Fedora partition from Linux Mint or a live CD and then running update-grub (mkconfig-grub if you don't have update-grub) with os-prober enabled in /etc/default/grub. This should regenerate the GRUB entry in /boot or /efi and fix the mistakes introduced when you shrunk the Fedora partition and then GRUB will just work. Now, if that doesn't work, you can manually boot/chainload from GRUB, where you issue a series of commands issue options, the kind of stuff GRUB is meant to automate. I did this a few times to get into a FreeBSD partition and it was a bit of a hassle but you can figure it out.

Worst case scenario, take what's valuable from the Fedora partition and reinstall it.

b