-
-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazzite not updating grub after upgrade to 41 (stuck in 39) #2188
Comments
Hello ! And also : |
Hi @jbtrystram , right away: Output of findmt /:
And finally, here's journalctl:
I hope it helps, let me know if there's anything else I can provide. Thanks for your help! |
since youre updating from fedora 39 to fedora 41, did you read https://universal-blue.discourse.group/t/important-announcement-regarding-system-updates-action-needed/2689 ? rebase to a bazzite version based on fedora 40 before july 2024 then run the script from the announcement, then rebase to latest and it should work possibly. |
Describe the bug
My system seems to be stuck in Bazzite 39, I can't seem to be able to upgrade to 41. I suspect a problem updating the grub menu.
What did you expect to happen?
I expected the Bazzite 41 option to appear on the Grub2 boot menu after updating, but it has not.
ujust update
on the console right now.Output of `ujust upgrade`
Pressing "quit" I get the message "topgrade finished successfully". I have rebooted afterwards. Grub2 only shows 2 fedora 39 options
I have looked at my
/etc/grub.d/grub.cfg
file. It does look like 41 is trying to source its config from a separate file (/boot/grub2/custom.cfg
), while 39 puts its config menuitem options directly on the file:Output of `sudo cat /boot/grub2/grub.cfg`
That seems to be part of the issue; assuming
config_directory
for grub means/boot/grub2
, there's a/boot/grub2/grubenv
file there, but there's nocustom.cfg
file:It definetly looks like there's a problem in writing to grub2, I got a warning when running
rpm-ostree status
(pasting that below, on the next section). It suggests runningjournalctl -b -1 -u ostree-finalize-staged.service
, which I did:There is a couple warnings there about a version mismatch (10.42 vs 10.44) which I don't know what to do with.
Output of
rpm-ostree status
Hardware
This is a desktop PC.
Extra information or context
No response
The text was updated successfully, but these errors were encountered: