Default GRUB boot entry not working.

Debian_SuperUser

Active Member
Joined
Mar 18, 2024
Messages
163
Reaction score
41
Credits
1,970
I installed Fedora 44 Sway Atomic and on the first boot itself it failed to boot. I found out that I have to boot from $root/boot/ostree and not $root/ostree. I was configuring my partitions and mount points manually. Did I mess up there? It seems that I can't permanently change the boot config as it is overwritten on every ostree deployment, so how should I fix it?

btw how are u supposed to install a C compiler without needing to reboot your system, use the potentially awkward --apply-live option, or use a toolbox which is more awkward and isn't good for scripts and AI agents?
 


You need to give more & detailed info of what you're doing.
I just installed Fedora. That's it. I configured my partitions and mount points manually during setup. Now it doesn't boot with the default settings using GRUB.

This for instance it's hard to tell what's your question, you install compiler with sudo apt install build-essential
I clearly listed Fedora Atomic not Debian.
 
I clearly listed Fedora Atomic not Debian.

While I didn't, likely due to how I read web pages, I could see where someone would read your post quickly and get confused because of your username.
 
During your manual partitioning are you sure that you allocated enough for the /boot, /root, swap, /var/home, /opt, /tmp....etc partitions?
Does your efi boot partition have the boot flag?

If Grub successfully installed to your hard drive then your fresh install should just boot to the log in.
Ostree should have updated grub.cfg to point to the current image.


Users have reported that they couldn't install Fedora Atomic Desktop on an EFI system.

Can you boot into the Live session of Fedora that you used to install it and run this and post back?
Code:
sudo fdisk -l
 

I just installed Fedora. That's it. I configured my partitions and mount points manually during setup. Now it doesn't boot with the default settings using GRUB.
It's impossible to determine cause of this without analyzing logs and conf files which you didn't provide. All we know is that you installed immutable (atomic) variant of Fedora.

I suggest to reinstall and use automatic partitioning, unless you are prepared to get technical, report bugs to Red Hat, and determine cause of this.
 
I was configuring my partitions and mount points manually. Did I mess up there? It seems that I can't permanently change the boot config as it is overwritten on every ostree deployment, so how should I fix it?
Fedora Atomic doesn't support custom partitioning.
But there's documentation if you want to try it, where it mentions again that manual partitioning is not supported.

btw how are u supposed to install a C compiler without needing to reboot your system, use the potentially awkward --apply-live option, or use a toolbox which is more awkward and isn't good for scripts and AI agents?
Fedora Atomic is a container based distribution and so is the workflow, so either toolbox or distrobox and if you have to layer something you will need to reboot unless you use --app-live.
 


Follow Linux.org

Staff online


Latest posts

Top