On Fri, Apr 18, 2025 at 9:23 AM Richard Shaw <hobbes1...@gmail.com> wrote:
> On Fri, Apr 18, 2025 at 8:01 AM Neal Becker <ndbeck...@gmail.com> wrote: > >> >> >> On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw <hobbes1...@gmail.com> >> wrote: >> >>> On Fri, Apr 18, 2025 at 7:29 AM Neal Becker <ndbeck...@gmail.com> wrote: >>> >>>> I just tried updating a lenovo laptop from F40 to F42 using >>>> sudo dnf system-upgrade download --releasever=42 >>>> sudo dnf system-upgrade reboot >>>> >>>> This machine is a bit slow (not a lot of memory) so I didn't hang >>>> around to watch, but about 10 min later it's running again, and still on >>>> F40. >>>> >>>> Any suggestions? >>>> Any ideas how to see the logs related to what happened? >>>> >>> >>> I've never tried to jump two releases although it's supposed to be >>> supported, but I've had this happen when I used to maintain a couple local >>> repositories and it wouldn't pull the updated packages into the transaction. >>> >>> More than likely the transaction check failed. Depending on how many >>> times you've booted since the upgrade attempt something like "journalctl -b >>> -1" should work and then search for when the upgrade started. >>> >>> >> pr 18 06:53:01 nbecker2 dnf-3[866]: Error: >> Apr 18 06:53:01 nbecker2 dnf-3[866]: Problem: The operation would result >> in removing the following protected packages: kernel-core >> Apr 18 06:53:01 nbecker2 dnf-3[866]: (try to add '--skip-broken' to skip >> uninstallable packages) >> Apr 18 06:53:01 nbecker2 systemd[1]: dnf-system-upgrade.service: Main >> process exited, code=exited, status=1/FAILURE >> Apr 18 06:53:01 nbecker2 systemd[1]: dnf-system-upgrade.service: Failed >> with result 'exit-code'. >> Apr 18 06:53:01 nbecker2 systemd[1]: Failed to start >> dnf-system-upgrade.service - System Upgrade using DNF. >> Apr 18 06:53:01 nbecker2 systemd[1]: dnf-system-upgrade.service: >> Triggering OnFailure= dependencies. >> >> When I had run sudo dnf upgrade --refresh I had trouble running because >> there wasn't enough space on /boot, so I edited /etc/dnf/dnf.conf to set >> installonly_limit=2 >> which allowed dnf upgrade --refresh to proceed. I now have 47% usage on >> /boot. But this error seems related, because I saw the same error when I >> tried to remove old kernels before I set installonly_limit=2. >> > > I don't suppose there's any useful output above the error? > > One option would be to update to the F42 kernel since they'll generally > work across releases: > > sudo dnf --releasever=42 update kernel > > I did: sudo dnf system-upgrade download --releasever=42 --allowerasing --best Note that it runs and passes transaction check and test before reboot. Then I also ran: sudo dnf --releasever=42 update kernel This time when rebooted I got: Apr 18 09:48:34 nbecker2 dnf-3[870]: Error: The following problems occurred while replaying the transaction from file "/var/lib/dn> Apr 18 09:48:34 nbecker2 dnf-3[870]: Cannot find rpm nevra "kernel-core-6.8.7-300.fc40.x86_64". Apr 18 09:48:34 nbecker2 dnf-3[870]: Cannot find rpm nevra "kernel-modules-6.8.7-300.fc40.x86_64". Apr 18 09:48:34 nbecker2 dnf-3[870]: Cannot find rpm nevra "kernel-modules-core-6.8.7-300.fc40.x86_64". Apr 18 09:48:34 nbecker2 dnf-3[870]: Cannot find rpm nevra "kernel-modules-extra-6.8.7-300.fc40.x86_64". Apr 18 09:48:34 nbecker2 systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
