Fedora 41->42 hangs at 31% done

[richard emberson]

Upgrading my systems from 41 to 42.
Three laptops and media server went smoothly.
So, decided to upgrade my desktop (main) machine:

# dnf upgrade --refresh
Success
# reboot
Success
# dnf install dnf-plugin-system-upgrade
Repositories loaded.
Package "dnf-plugins-core-4.10.1-1.fc41.noarch" is already installed.
Success
# dnf system-upgrade download --releasever=42
.... use "dnf5 offline reboot" ...
Just like other machines, seems to be Success.

# dnf5 offline reboot
...time passes ... stops at 31% completed ..
Waited 2 1/2 hours,
did reboot by hardware button
got me back to 41:
uname -a
Linux olympia 6.13.11-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 10 19:02:09 UTC 2025 x86_64 GNU/Linux

When I do a:
# dnf list --installed | grep kernel

abrt-addon-kerneloops.x86_64                         2.17.6-3.fc41                       updates
kernel.x86_64                                        6.11.4-301.fc41                     anaconda
kernel.x86_64                                        6.11.11-300.fc41                    updates
kernel.x86_64                                        6.13.11-200.fc41                    updates
kernel-core.x86_64                                   6.11.4-301.fc41                     anaconda
kernel-core.x86_64                                   6.11.11-300.fc41                    updates
kernel-core.x86_64                                   6.13.11-200.fc41                    updates
kernel-core.x86_64                                   6.14.2-300.fc42                     <unknown>
kernel-headers.x86_64                                6.13.3-200.fc41                     updates
kernel-headers.x86_64                                6.14.0-63.fc42                      <unknown>
kernel-modules.x86_64                                6.11.4-301.fc41                     anaconda
kernel-modules.x86_64                                6.11.11-300.fc41                    updates
kernel-modules.x86_64                                6.13.11-200.fc41                    updates
kernel-modules.x86_64                                6.14.2-300.fc42                     <unknown>
kernel-modules-core.x86_64                           6.11.4-301.fc41                     anaconda
kernel-modules-core.x86_64                           6.11.11-300.fc41                    updates
kernel-modules-core.x86_64                           6.13.11-200.fc41                    updates
kernel-modules-core.x86_64                           6.14.2-300.fc42                     <unknown>
kernel-modules-extra.x86_64                          6.11.4-301.fc41                     anaconda
kernel-modules-extra.x86_64                          6.11.11-300.fc41                    updates
kernel-modules-extra.x86_64                          6.13.11-200.fc41                    updates
libreport-plugin-kerneloops.x86_64                   2.17.15-3.fc41                      anaconda

The last couple of lines in /var/log/dnf5.log:

2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3-brotli-0:1.1.0-6.fc42.x86_64" amount 858484 total 858484
2025-04-20T17:03:15+0000 [745] INFO RPM callback close file
2025-04-20T17:03:15+0000 [745] INFO RPM callback open file "/usr/lib/sysimage/libdnf5/offline/./packages/python3-certifi-2024.08.30-2.fc42.noarch.rpm"
2025-04-20T17:03:15+0000 [745] INFO RPM callback install start "python3-certifi-0:2024.08.30-2.fc42.noarch" total 10604
2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3-certifi-0:2024.08.30-2.fc42.noarch" amount 10604 total 10604
2025-04-20T17:03:15+0000 [745] INFO RPM callback close file
2025-04-20T17:03:15+0000 [745] INFO RPM callback open file "/usr/lib/sysimage/libdnf5/offline/./packages/python3-chardet-5.2.0-16.fc42.noarch.rpm"
2025-04-20T17:03:15+0000 [745] INFO RPM callback install start "python3-chardet-0:5.2.0-16.fc42.noarch" total 2194948
2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3-chardet-0:5.2.0-16.fc42.noarch" amount 2194948 total 2194948
2025-04-20T17:03:16+0000 [745] INFO RPM callback start trigger-install scriptlet "filesystem-0:3.18-36.fc42.x86_64"
2025-04-20T17:03:16+0000 [745] INFO RPM callback stop trigger-install scriptlet "filesystem-0:3.18-36.fc42.x86_64" return code 0
2025-04-20T17:03:17+0000 [745] INFO RPM callback close file
2025-04-20T17:03:17+0000 [745] INFO RPM callback open file "/usr/lib/sysimage/libdnf5/offline/./packages/python3-click-8.1.7-7.fc42.noarch.rpm"

No error messages.

I have not tried to upgrade from 41 to 42 again.
If possible I'd like to know what went wrong first.
 From recent experience, it is a real pain to reinstall on this OLD system (if you have to replace the boot disk,
had to install DVD mint 2.0 on new disk in order to get /boot/efi/EFI/BOOT directory, then install DVD Xfce 4.1),
so, why would the upgrade hang?

Thanks

Also, now when I change to root I get:

# su
Password:
/etc/selinux/targeted/contexts/files/file_contexts.bin:  Old compiled fcontext format, skipping
/etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin:  Old compiled fcontext format, skipping
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  Old compiled fcontext format, skipping

Rich

[Samuel Sieb]

On 4/20/25 12:53 PM, richard emberson wrote:
> Upgrading my systems from 41 to 42.
> Three laptops and media server went smoothly.
> So, decided to upgrade my desktop (main) machine:
>
> # dnf upgrade --refresh
> Success
> # reboot
> Success
> # dnf install dnf-plugin-system-upgrade
> Repositories loaded.
> Package "dnf-plugins-core-4.10.1-1.fc41.noarch" is already installed.
> Success
> # dnf system-upgrade download --releasever=42
> .... use "dnf5 offline reboot" ...
> Just like other machines, seems to be Success.
>
> # dnf5 offline reboot
> ...time passes ... stops at 31% completed ..

You can press the ESC key to get the text log of what's happening.
> Waited 2 1/2 hours,
> did reboot by hardware button

If it's not actually hung, you could CTRL-ALT-DEL to reboot.
> The last couple of lines in /var/log/dnf5.log:
>
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3- 
> brotli-0:1.1.0-6.fc42.x86_64" amount 858484 total 858484
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback close file
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback open file "/usr/lib/ 
> sysimage/libdnf5/offline/./packages/python3- 
> certifi-2024.08.30-2.fc42.noarch.rpm"
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback install start "python3- 
> certifi-0:2024.08.30-2.fc42.noarch" total 10604
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3- 
> certifi-0:2024.08.30-2.fc42.noarch" amount 10604 total 10604
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback close file
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback open file "/usr/lib/ 
> sysimage/libdnf5/offline/./packages/python3- 
> chardet-5.2.0-16.fc42.noarch.rpm"
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback install start "python3- 
> chardet-0:5.2.0-16.fc42.noarch" total 2194948
> 2025-04-20T17:03:15+0000 [745] INFO RPM callback install stop "python3- 
> chardet-0:5.2.0-16.fc42.noarch" amount 2194948 total 2194948
> 2025-04-20T17:03:16+0000 [745] INFO RPM callback start trigger-install 
> scriptlet "filesystem-0:3.18-36.fc42.x86_64"
> 2025-04-20T17:03:16+0000 [745] INFO RPM callback stop trigger-install 
> scriptlet "filesystem-0:3.18-36.fc42.x86_64" return code 0
> 2025-04-20T17:03:17+0000 [745] INFO RPM callback close file
> 2025-04-20T17:03:17+0000 [745] INFO RPM callback open file "/usr/lib/ 
> sysimage/libdnf5/offline/./packages/python3-click-8.1.7-7.fc42.noarch.rpm"

What's at the end of the journal?

[richard emberson]

On 20/04/25 13:30, Samuel Sieb wrote:
> What's at the end of the journal?

I rebooted at 12:01, I assume it hung at 10:03

As root: journalctl -S 2025-04-20

.....

Apr 20 10:03:13 olympia dnf5[745]: [1441/4424] Upgrading python3-libsemana 100% |   3.8 MiB/s | 383.6 KiB |  00m00s
Apr 20 10:03:13 olympia dnf5[745]: [1442/4424] Upgrading libnice-gstreamer 100% | 308.8 KiB/s |  28.4 KiB |  00m00s
Apr 20 10:03:14 olympia dnf5[745]: [1443/4424] Installing python3-dbus-nex 100% |   3.2 MiB/s | 600.0 KiB |  00m00s
Apr 20 10:03:14 olympia dnf5[745]: [1444/4424] Upgrading anaconda-widgets- 100% |   2.6 MiB/s | 270.6 KiB |  00m00s
Apr 20 10:03:14 olympia dbus-broker-launch[740]: Noticed file-system modification, trigger reload.
Apr 20 10:03:14 olympia dbus-broker-launch[740]: Noticed file-system modification, trigger reload.
Apr 20 10:03:14 olympia dbus-broker-launch[740]: Noticed file-system modification, trigger reload.
Apr 20 10:03:14 olympia dnf5[745]: [1445/4424] Upgrading blivet-data-1:3.1 100% |   1.8 MiB/s | 496.7 KiB |  00m00s
Apr 20 10:03:14 olympia dnf5[745]: [1446/4424] Upgrading crypto-policies-s 100% |   1.5 MiB/s | 394.5 KiB |  00m00s
Apr 20 10:03:14 olympia dnf5[745]: [1447/4424] Upgrading libwacom-0:2.15.0 100% | 810.8 KiB/s |  99.7 KiB |  00m00s
Apr 20 10:03:15 olympia dnf5[745]: [1448/4424] Upgrading libinput-0:1.28.1 100% |   2.2 MiB/s | 600.3 KiB |  00m00s
Apr 20 10:03:15 olympia dnf5[745]: [1449/4424] Upgrading python3-brlapi-0: 100% |   2.8 MiB/s | 321.5 KiB |  00m00s
Apr 20 10:03:15 olympia dnf5[745]: [1450/4424] Upgrading python3-brotli-0: 100% |   5.7 MiB/s | 838.4 KiB |  00m00s
Apr 20 10:03:15 olympia dnf5[745]: [1451/4424] Upgrading python3-certifi-0 100% | 100.5 KiB/s |  10.4 KiB |  00m00s
-- Boot 7a569ba6147048a1940091673a34aa50 --
Apr 20 12:01:37 olympia kernel: Linux version 6.13.11-200.fc41.x86_64 (mockbuild@fcf5690cacf1407ea15fadfe8861ad32) (gcc (GCC) 14.2.1 20250110 (R>
Apr 20 12:01:37 olympia kernel: Command line: BOOT_IMAGE=(hd0,msdos2)/vmlinuz-6.13.11-200.fc41.x86_64 root=UUID=1672397c-3dfc-4361-a89c-1b411587>
Apr 20 12:01:37 olympia kernel: BIOS-provided physical RAM map:
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dbff] usable
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x000000000009dc00-0x000000000009ffff] reserved
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bff6ffff] usable
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000bff70000-0x00000000bff7dfff] ACPI data
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000bff7e000-0x00000000bffcffff] ACPI NVS
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000bffd0000-0x00000000bfffffff] reserved
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 20 12:01:37 olympia kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
....

What should I be looking for?
A couple of hours before I started the upgrade, I can see that 3 alacritty windows I had open in workspace 3
crashed. The Xterms I was using in workspace 1 for the upgrade were still up and running.
And there was a zram error:

....
Apr 20 07:38:36 olympia kernel: R13: 000055e92abaaa20 R14: 0000000000006010 R15: 00007ff1d4e25ac0
Apr 20 07:38:36 olympia kernel:  </TASK>
Apr 20 07:38:36 olympia kernel: ---[ end trace 0000000000000000 ]---
Apr 20 07:38:36 olympia kernel: zram: Decompression failed! err=-22, page=909461
Apr 20 07:38:36 olympia kernel: Read-error on swap-device (252:0:7275688)
Apr 20 07:38:37 olympia abrt-dump-journal-core[992]: Failed to obtain all required information from journald
Apr 20 07:38:37 olympia systemd-coredump[2556959]: [🡕] Process 1174080 (alacritty) of user 1000 dumped core.

Module libtinfo.so.6 from rpm ncurses-6.5-2.20240629.fc41.x86_64
                                                    Module libpciaccess.so.0 from rpm libpciaccess-0.16-13.fc41.x86_64
                                                    Module libedit.so.0 from rpm libedit-3.1-53.20240808cvs.fc41.x86_64
                                                    Module libffi.so.8 from rpm libffi-3.4.6-3.fc41.x86_64
                                                    Module libdrm_intel.so.1 from rpm libdrm-2.4.124-1.fc41.x86_64
....

#3  0x000055e8efdab64b _ZN3std3sys3pal4unix6thread6Thread3new12thread_start17haab6e853d6963ff>
                                                    #4  0x00007ff1d4cac148 start_thread (libc.so.6 + 0x71148)
                                                    #5  0x00007ff1d4d300cc __clone3 (libc.so.6 + 0xf50cc)
                                                    ELF object binary architecture: AMD x86-64
Apr 20 07:38:37 olympia systemd[1]: [e-mail]: Deactivated successfully.
Apr 20 07:38:37 olympia audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cor>
Apr 20 07:38:37 olympia audit: BPF prog-id=635 op=UNLOAD
Apr 20 07:38:37 olympia audit: BPF prog-id=634 op=UNLOAD
Apr 20 07:38:37 olympia audit: BPF prog-id=633 op=UNLOAD
Apr 20 07:38:37 olympia abrt-dump-journal-oops[993]: abrt-dump-journal-oops: Found oopses: 3
Apr 20 07:38:37 olympia abrt-dump-journal-oops[993]: abrt-dump-journal-oops: Creating problem directories
Apr 20 07:38:37 olympia systemd[1]: [e-mail]: Consumed 807ms CPU time, 126.6M memory peak.
Apr 20 07:38:38 olympia abrt-server[2556970]: Can't find a meaningful backtrace for hashing in '.'
Apr 20 07:38:38 olympia abrt-server[2556970]: Deleting non-reportable oops '.' because DropNotReportableOopses is set to 'yes'
Apr 20 07:38:38 olympia abrt-server[2556970]: 'post-create' on '/var/spool/abrt/oops-2025-04-20-07:38:37-993-0' exited with 1
Apr 20 07:38:38 olympia abrt-server[2556970]: Deleting problem directory '/var/spool/abrt/oops-2025-04-20-07:38:37-993-0'
Apr 20 07:38:38 olympia abrt-server[2556970]: Lock file '.lock' was locked by process 2556983, but it crashed?
Apr 20 07:38:40 olympia abrt-dump-journal-oops[993]: Reported 3 kernel oopses to Abrt
Apr 20 07:38:43 olympia abrt-notification[2557025]: [🡕] Process 1174080 (alacritty) crashed in realloc()
....

But, again, that was at least an hour before I started the upgrade (or touched the computer in the morning).

Richard

[Samuel Sieb]

On 4/20/25 2:23 PM, richard emberson wrote:
> What should I be looking for?
> A couple of hours before I started the upgrade, I can see that 3 
> alacritty windows I had open in workspace 3
> crashed. The Xterms I was using in workspace 1 for the upgrade were 
> still up and running.
> And there was a zram error:

That looks really bad.  I suggest you do a RAM test.

[George N. White III]

On Sun, Apr 20, 2025 at 7:06 PM Samuel Sieb  wrote:
> On 4/20/25 2:23 PM, richard emberson wrote:
> > What should I be looking for?
> > A couple of hours before I started the upgrade, I can see that 3
> > alacritty windows I had open in workspace 3
> > crashed. The Xterms I was using in workspace 1 for the upgrade were
> > still up and running.
> > And there was a zram error:
>
> That looks really bad.  I suggest you do a RAM test.

RAM issue should be at the top of the list of suspects.
> --
> _______________________________________________
> 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

[Jeffrey Walton]

On Sun, Apr 20, 2025 at 6:06 PM Samuel Sieb  wrote:
> On 4/20/25 2:23 PM, richard emberson wrote:
> > What should I be looking for?
> > A couple of hours before I started the upgrade, I can see that 3
> > alacritty windows I had open in workspace 3
> > crashed. The Xterms I was using in workspace 1 for the upgrade were
> > still up and running.
> > And there was a zram error:
>
> That looks really bad.  I suggest you do a RAM test.

++. The zram error jumped out at me, too.

Jeff

[richard emberson]

Back on 4/20 I tested the top 6.5 Gbs of the 8 Gbs on the system using /bin/memtester
and that passed.
Not knowing if my system would even come up if I tried to reboot, I decided to wait
until I had to reboot. I saw post stating that be easiest way to fix a failed upgrade
is to re-install - I'd like to avoid that right now.
The current system (12 years old) is backed up and
I plan to build a new desktop server in a couple of weeks so I would wait to reboot and
test all the RAM.
Well, earlier today the system froze, so during reboot I ran memtest86 on all the memory.
It all passed. So, it might be something else that caused the upgrade to fail.
No zram errors since reboot.

Richard

On 20/04/25 15:05, Samuel Sieb wrote:
> On 4/20/25 2:23 PM, richard emberson wrote:
> > What should I be looking for?
> > A couple of hours before I started the upgrade, I can see that 3 alacritty windows I had open in workspace 3
> > crashed. The Xterms I was using in workspace 1 for the upgrade were still up and running.
> > And there was a zram error:
>
> That looks really bad.  I suggest you do a RAM test.

[George N. White III]

On Sat, Apr 26, 2025 at 5:17 PM richard emberson 
wrote:
> Back on 4/20 I tested the top 6.5 Gbs of the 8 Gbs on the system using
> /bin/memtester
> and that passed.
> Not knowing if my system would even come up if I tried to reboot, I
> decided to wait
> until I had to reboot. I saw post stating that be easiest way to fix a
> failed upgrade
> is to re-install - I'd like to avoid that right now.
> The current system (12 years old) is backed up and
> I plan to build a new desktop server in a couple of weeks so I would wait
> to reboot and
> test all the RAM.

Power supplies (including motherboard components that manage low-voltage
supplies
to CPU and other chips) degrade with age. Random crashes can result.

Hope the Trump tariffs don't make it hard to source parts for a new build.
> Well, earlier today the system froze, so during reboot I ran memtest86 on
> all the memory.
> It all passed. So, it might be something else that caused the upgrade to
> fail.
> No zram errors since reboot.
>
> Richard
>
> On 20/04/25 15:05, Samuel Sieb wrote:
> > On 4/20/25 2:23 PM, richard emberson wrote:
> > > What should I be looking for?
> > > A couple of hours before I started the upgrade, I can see that 3
>
> alacritty windows I had open in workspace 3
> > > crashed. The Xterms I was using in workspace 1 for the upgrade were
>
> still up and running.
> > > And there was a zram error:
> >
> > That looks really bad.  I suggest you do a RAM test.
>
> --
> _______________________________________________
> 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