F40 -> F42?

[Neal Becker]

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?

Thanks,
Neal

[Richard Shaw]

On Fri, Apr 18, 2025 at 7:29 AM Neal Becker  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.

Thanks,
RIchard

[Neal Becker]

On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw  wrote:
> On Fri, Apr 18, 2025 at 7:29 AM Neal Becker  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.

[Richard Shaw]

On Fri, Apr 18, 2025 at 8:01 AM Neal Becker  wrote:
> On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw  wrote:
> > On Fri, Apr 18, 2025 at 7:29 AM Neal Becker  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

And then rerun the system-upgrade to take them out of the transaction.

Thanks,
Richard

[Neal Becker]

On Fri, Apr 18, 2025 at 9:23 AM Richard Shaw  wrote:
> On Fri, Apr 18, 2025 at 8:01 AM Neal Becker  wrote:
> > On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw 
> > wrote:
> > > On Fri, Apr 18, 2025 at 7:29 AM Neal Becker  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

[Richard Shaw]

On Fri, Apr 18, 2025 at 8:56 AM Neal Becker  wrote:
> On Fri, Apr 18, 2025 at 9:23 AM Richard Shaw  wrote:
> > On Fri, Apr 18, 2025 at 8:01 AM Neal Becker  wrote:
> > > On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw 
> > > wrote:
> > > > On Fri, Apr 18, 2025 at 7:29 AM Neal Becker 
> > > > 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

If that's the order you ran the commands you needed to reverse it. After
upgrading to the f42 kernel you need to rerun the system-upgrade so that
the transaction is updated so it knows it doesn't need to remove the old
kernel or install the new kernel.

Thanks,
Richard

[Felix Miata]

Richard Shaw composed on 2025-04-18 09:11 (UTC-0500):
> If that's the order you ran the commands you needed to reverse it. After
> upgrading to the f42 kernel you need to rerun the system-upgrade so that
> the transaction is updated so it knows it doesn't need to remove the old
> kernel or install the new kernel.

Include kernel* in dnf.conf's exclude= line and kernel processing will be skipped,
allowing issues with kernel to be handled manually after the rest of the upgrade
is /complete/, or removing the exclude and then running an ordinary F42 upgrade.

When I've done 37>40 or 40>42 I didn't skip. Instead I did an upgrade to next
first, skipping kernel entirely, which I do for every upgrade, until ultimate was
otherwise complete. I always do kernel manually, because dnf's continual changing
of cache directory names obstructs preloading the cache with the kernel previously
downloaded for my many other local installation(s).

[Suse Shi]

root#  sudo dnf system-upgrade download --releasever=42 -y
 root#  dnf5 offline reboot

run the 1st command to get all fc42 packages you need, checking no
conflicts or missing deps,  and as prompt, run the 2nd cmd to upgrade.

if you hit some dependencies broken issues, remove those packages
temporarily and retry.

Neal Becker  于2025年4月18日周五 21:56写道：
> On Fri, Apr 18, 2025 at 9:23 AM Richard Shaw  wrote:
> > On Fri, Apr 18, 2025 at 8:01 AM Neal Becker  wrote:
> > > On Fri, Apr 18, 2025 at 8:34 AM Richard Shaw 
> > > wrote:
> > > > On Fri, Apr 18, 2025 at 7:29 AM Neal Becker 
> > > > 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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

--
Regards,
-suse

[Samuel Sieb]

On 4/19/25 5:34 AM, Suse Shi wrote:
> root#  sudo dnf system-upgrade download --releasever=42 -y
>   root#  dnf5 offline reboot
>
> run the 1st command to get all fc42 packages you need, checking no 
> conflicts or missing deps,  and as prompt, run the 2nd cmd to upgrade.
>
> if you hit some dependencies broken issues, remove those packages 
> temporarily and retry.

I usually add "--allowerasing" to the upgrade command.  Just check the 
list of removed packages before agreeing.