-
Notifications
You must be signed in to change notification settings - Fork 192
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
No Updated Grub Menu Entry After 'rpm-ostree upgrade' Finishes With No Apparent Errors #4664
Comments
Can you check the output of |
Looks like I am hitting this too on 2023.11
Looks like this might be a bit different from #3715 as the error I get from Grub seems different. I also tried the two workaround listed in that issue, with no luck. |
Do you actually need dual-booting? If not, you can stop using |
@jlebon when you say dual-booting you mean two different OSes? I just use grub to select the different ostree deployments. I just installed silverblue on this new laptop a few weeks back. If you mean it thinks It needs to support multiple OSes I wonder what I did different vs my previous machine. |
This is triggered by combination of composefs (which uses overlayfs) and the legacy case of not having WARNING: These instructions may cause failure
Now, this issue is quite similar to coreos/coreos-installer#1203 - we may need to teach os-prober to do the same. (See also containers/composefs#144 ) |
This left me without being able to boot and with a grub prompt. I will try to replicate the issue in a VM once I finish getting my machine running again. Given that I had enabled composefs I wonder if this is related at all from what the OP was experiencing. |
It's definitely a different triggering cause yeah. I hid the instructions above for now. |
I tried composefs due to https://blogs.gnome.org/alexl/2024/01/15/testing-composefs-in-silverblue/ and got similar results. Initially I wasn't able to create new deployments and it also apparently prevented me from getting new commits at all until I rebased. I also managed to bork GRUB and has to boot on a live session to tell it to regenerate the grub config. |
I find that it is not relevant to os-prober and setting # Device containing our userland. Typically used for root= parameter.
GRUB_DEVICE="`${grub_probe} --target=device /`"
GRUB_DEVICE_UUID="`${grub_probe} --device ${GRUB_DEVICE} --target=fs_uuid 2> /dev/null`" || true
GRUB_DEVICE_PARTUUID="`${grub_probe} --device ${GRUB_DEVICE} --target=partuuid 2> /dev/null`" || true |
Host system details
OS Name - Fedora Linux 38.20231012.0 (Silverblue)
OS Type - 64-bit
GNOME Version - 44.5
Windowing System - Wayland
Kernel Version - Linux 6.5.6-200.fc38.x86_64
Provide the output of
rpm-ostree status
.Expected
Expecting an updated menu entry to boot into after an update.
Actual Behavior
Update doesn't get added to grub menu and stays stuck on 38.20231012.0
Steps to reproduce it
rpm-ostree upgrade
systemctl reboot
Provide any additional data that may help debug this - which specific version of
an RPM is in the repo, or any host system configuration.
Please let me know what else is needed to add to help debug this. I have no layered packages installed. All the apps I have installed are flatpaks.
Would you like to work on the issue?
I won't be able to fix this myself as I don't have the skills. Would need help with this bug on my particular system.
The text was updated successfully, but these errors were encountered: