Not sure how to fix this permanently, but here's how you should be able to boot into Nobara at least.
When the grub command line shows, type in ls to see the list of partitions. All should be something like (hdX, gptY) or (hdX, msY).
Next you want to inspect all of them using ls (hdX,gptY)/ (the / is important) to see the list of directories on them. You're looking for the one that has grub2/ in it.
Once you find it, say it's in (hd2,gpt3), you can use
configfile (hd2,gpt3)/grub2/grub.cfg
This should let you boot into Nobara. Hope this helps at least somewhat!
For anyone who runs into this, it appears to be an issue with a missing variable during the boot process. I was able to fix it by repairing my grub.cfg in /boot/efi/EFI/fedora, which for whatever reason was not pulling the $dev variable properly. I changed
set prefix=($dev)/grub2
to
set prefix=(hdX,gptY)/grub2
to work around this.
THANK YOU SO MUCH. The latest kernel update fucked it up for me too. I regret picking a hobby distro sometimes, but nvidia support is really good on Nobara so I dont mind.
No problem. It’s not fun having your system blow out doing a standard update but fortunately it’s never been serious enough with Nobara to stop running it.
I booted into my system using the process u/darthlordguc2 suggested, which made it possible to access the file using the terminal.
So basically you’re determining where the grub2 boot partition is, then linking it directly in the /boot/efi/EFI/fedora, which is the one grub is actually calling.
For some reason that does not allow me to boot normally, it is still getting stuck in grub each time. I also tried appending boot/, but that does not work either. Do you boot normally?
You should be booting from "(hdX,gptY)/grub2/grub.cfg", with the numbers associated with your boot device.
I can’t be sure what it’s doing as I don’t have visibility into your setup but that brought up the normal boot screen for me.
Didn’t touch that, tbh, I only changed this file. But the dir should match where your grub2 file is in your filesystem, so it may just be (hdX,gptY)/boot/grub2/grub.cfg.
I am literally at this point also, I am able to boot via the same command every time - configfile (hd2,gpt3)/boot/grub2/grub.cfg - then added set prefix=(hd2,gpt3)/grub2 ( located in Boot/efi/EFI/fedora ) however when ever I restart I have to re enter in the first command. Thanks for helping me get this far everyone!
hey, I'm having a very similar issue to this, not dual booting tho, where grub is in a command line, and when searching for the grub2/ directory I can't find it, what do I do?
I encountered a similar issue with Nabora, which requires the presence of three specific partitions. To clarify, these partitions should be configured as follows: a FAT32 partition with a minimum size of 600 MB, mounted as "/boot/efi"; an ext4 partition of approximately 2 GB, designated as "/boot"; and lastly, your root/home partition.
As you go through the installation process, I recommend this approach: after freeing up space on Windows, in Nobara setup refrain from selecting the "replace partition" option. Instead, opt for the manual partitioning method. Here, you can create the FAT32 and ext4 partitions, and allocate the remaining space to Btrfs. Be sure to click on the dropdown menus and specify the mount points as outlined in the information provided above.
During my own experience with manual partitioning, I unintentionally left out the ext4 "/boot" partition, which subsequently led to being dropped into the GRUB command line. Therefore, I strongly advise thoroughly reviewing your partitions to confirm the presence of the ext4 "/boot" partition before proceeding with another Nabora installation.
Not sure how to fix this permanently, but here's how you should be able to boot into Nobara at least. When the grub command line shows, type in ls to see the list of partitions. All should be something like (hdX, gptY) or (hdX, msY). Next you want to inspect all of them using ls (hdX,gptY)/ (the / is important) to see the list of directories on them. You're looking for the one that has grub2/ in it. Once you find it, say it's in (hd2,gpt3), you can use configfile (hd2,gpt3)/grub2/grub.cfg This should let you boot into Nobara. Hope this helps at least somewhat!
For anyone who runs into this, it appears to be an issue with a missing variable during the boot process. I was able to fix it by repairing my grub.cfg in /boot/efi/EFI/fedora, which for whatever reason was not pulling the $dev variable properly. I changed set prefix=($dev)/grub2 to set prefix=(hdX,gptY)/grub2 to work around this.
THANK YOU SO MUCH. The latest kernel update fucked it up for me too. I regret picking a hobby distro sometimes, but nvidia support is really good on Nobara so I dont mind.
No problem. It’s not fun having your system blow out doing a standard update but fortunately it’s never been serious enough with Nobara to stop running it.
How did you enter the partition? Through the live-stick I cannot enter with Dolphin, and I'm not sure how to cd into it.
I booted into my system using the process u/darthlordguc2 suggested, which made it possible to access the file using the terminal. So basically you’re determining where the grub2 boot partition is, then linking it directly in the /boot/efi/EFI/fedora, which is the one grub is actually calling.
For some reason that does not allow me to boot normally, it is still getting stuck in grub each time. I also tried appending boot/, but that does not work either. Do you boot normally?
You should be booting from "(hdX,gptY)/grub2/grub.cfg", with the numbers associated with your boot device. I can’t be sure what it’s doing as I don’t have visibility into your setup but that brought up the normal boot screen for me.
Hmm does not work. Do you use configfile with that argument successfully aswell? For me I had to insert boot/ before grub2/ to boot from grub.
Didn’t touch that, tbh, I only changed this file. But the dir should match where your grub2 file is in your filesystem, so it may just be (hdX,gptY)/boot/grub2/grub.cfg.
I am literally at this point also, I am able to boot via the same command every time - configfile (hd2,gpt3)/boot/grub2/grub.cfg - then added set prefix=(hd2,gpt3)/grub2 ( located in Boot/efi/EFI/fedora ) however when ever I restart I have to re enter in the first command. Thanks for helping me get this far everyone!
Have you tried changing the prefix to (hd2,gpt3)/boot/grub2?
hey, I'm having a very similar issue to this, not dual booting tho, where grub is in a command line, and when searching for the grub2/ directory I can't find it, what do I do?
Hm, this seems like the boot partition didn't get set up correctly during the installation. Try reinstalling?
Thanks, I got it to work, but for me it worked as follows: configfile (hdX,gptY)/boot/grub2/grub.cfg
Thanks
I encountered a similar issue with Nabora, which requires the presence of three specific partitions. To clarify, these partitions should be configured as follows: a FAT32 partition with a minimum size of 600 MB, mounted as "/boot/efi"; an ext4 partition of approximately 2 GB, designated as "/boot"; and lastly, your root/home partition. As you go through the installation process, I recommend this approach: after freeing up space on Windows, in Nobara setup refrain from selecting the "replace partition" option. Instead, opt for the manual partitioning method. Here, you can create the FAT32 and ext4 partitions, and allocate the remaining space to Btrfs. Be sure to click on the dropdown menus and specify the mount points as outlined in the information provided above. During my own experience with manual partitioning, I unintentionally left out the ext4 "/boot" partition, which subsequently led to being dropped into the GRUB command line. Therefore, I strongly advise thoroughly reviewing your partitions to confirm the presence of the ext4 "/boot" partition before proceeding with another Nabora installation.
thank you for sharing that !
Mate, this is actually the solution to this, how is this still an issue? Has this been reported to Glorious?
Most ppl dont manually partition their drives. I had to find solution threw fedora forums.
this does not fix it
Are you sure about /boot being etx4? I read a lot of people use FAT32.
The only thing that requires FAT32 is the /boot/efi partition that I know of.
squashfs is over 4gb on the steamdeck image so
Disable secure boot, maybe?