Rpm-ostree upgrade core dump

Ask Fedora
1

I don’t know how to recover from this.

rpm-ostree cleanup --repomd
rpm-ostree refresh-md
rpm-ostree upgrade

rpm-ostree still core dumps.

I did an rpm-ostree rollback.
It still core-dumped from my previous pinned version.

I only have two versions. on my drive and both are in this “rpm-ostree core dumped” state.

I really don’t know what to do to recover from this.

Thanks for any help in these matters.

details follow:

root@cissy-flex5-fc40sb:/var/home/cissy# ostree admin status
* fedora 323b19711a9ca8637ba427fefc1275f8ec7a2d91b8cb21b3f4444ff9d8e1c95f.0
    Version: 40.20240822.0
    Pinned: yes
    origin: <unknown origin type>
  fedora 3dc72b544a6a9c1e01857f0f747e63dddfb7dbddb9e7148492fa8daad1a8df6a.0 (rollback)
    Version: 40.20240828.0
    origin: <unknown origin type>
root@cissy-flex5-fc40sb:/var/home/cissy# journalctl -xe
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-coredump@0-5867-0.service has successfully entered the 'dead' state.
Aug 31 10:58:14 cissy-flex5-fc40sb audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-5867-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? ter>
Aug 31 10:58:14 cissy-flex5-fc40sb systemd[1]: systemd-coredump@0-5867-0.service: Consumed 2.137s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-coredump@0-5867-0.service completed and consumed the indicated resources.
Aug 31 10:58:14 cissy-flex5-fc40sb audit: BPF prog-id=67 op=UNLOAD
Aug 31 10:58:14 cissy-flex5-fc40sb audit: BPF prog-id=66 op=UNLOAD
Aug 31 10:58:14 cissy-flex5-fc40sb audit: BPF prog-id=65 op=UNLOAD
Aug 31 10:58:14 cissy-flex5-fc40sb systemd[1]: rpm-ostreed.service: Main process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit rpm-ostreed.service has exited.
░░ 
░░ The process' exit code is 'dumped' and its exit status is 6.
Aug 31 10:58:14 cissy-flex5-fc40sb systemd[1]: rpm-ostreed.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit rpm-ostreed.service has entered the 'failed' state with result 'core-dump'.
Aug 31 10:58:14 cissy-flex5-fc40sb systemd[1]: rpm-ostreed.service: Consumed 3min 28.649s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit rpm-ostreed.service completed and consumed the indicated resources.
Aug 31 10:58:14 cissy-flex5-fc40sb audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=fa>
Aug 31 10:59:03 cissy-flex5-fc40sb systemd[1]: Starting rpm-ostreed.service - rpm-ostree System Management Daemon...
░░ Subject: A start job for unit rpm-ostreed.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit rpm-ostreed.service has begun execution.
░░ 
░░ The job identifier is 3954.
Aug 31 10:59:03 cissy-flex5-fc40sb rpm-ostree[5880]: Reading config file '/etc/rpm-ostreed.conf'
Aug 31 10:59:03 cissy-flex5-fc40sb rpm-ostree[5880]: In idle state; will auto-exit in 61 seconds
Aug 31 10:59:03 cissy-flex5-fc40sb systemd[1]: Started rpm-ostreed.service - rpm-ostree System Management Daemon.
░░ Subject: A start job for unit rpm-ostreed.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit rpm-ostreed.service has finished successfully.
░░ 
░░ The job identifier is 3954.
Aug 31 10:59:03 cissy-flex5-fc40sb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s>
Aug 31 10:59:03 cissy-flex5-fc40sb rpm-ostree[5880]: Allowing active client :1.110 (uid 1000)
2

I also tried
rpm-ostree cleanup -pbm

Then I ran
rpm-ostree upgrade
rpm-ostree remove langpacks-en

But they both still return me:

error: Bus owner changed, aborting. This likely means the daemon crashed; check logs with `journalctl -xe`.
3 
ostree fsck
Validating refs...
Validating refs in collections...
Enumerating commits...
Verifying content integrity of 487 commit objects...
fsck objects (44229/160937) [===          ]  27%
error: In commits 323b19711a9ca8637ba427fefc1275f8ec7a2d91b8cb21b3f4444ff9d8e1c95f, 1d44958df5f4a8d660614f8fdbe877c24d82253d67ef2342d9ccfb65440dcbf5, 32d34cc0f3c71a3b27b8e3c31a254e54515026d5edfec61d632d12059a7e2292, 3dc72b544a6a9c1e01857f0f747e63dddfb7dbddb9e7148492fa8daad1a8df6a, 6c1a2b17d306e1a6f81a37499ccf5d1fca0e8bc2dbaa9d43b1ab45942d9635f8: fsck content object 4b95e9f210724a5766c1ebee21913e006b52033131ce159365f2c6182b81f8b8: Corrupted file object; checksum expected='4b95e9f210724a5766c1ebee21913e006b52033131ce159365f2c6182b81f8b8' actual='7d4c851dc9fcb61fc58c00b3996255765739cadc534b94ef523d6a52f8cd3862'

How do I recover from this distrastrous situation?

4 
ostree ls fedora/40/x86_64/silverblue
d00755 0 0      0 /
l00777 0 0      0 /bin -> usr/bin
l00777 0 0      0 /home -> var/home
l00777 0 0      0 /lib -> usr/lib
l00777 0 0      0 /lib64 -> usr/lib64
l00777 0 0      0 /media -> run/media
l00777 0 0      0 /mnt -> var/mnt
l00777 0 0      0 /opt -> var/opt
l00777 0 0      0 /ostree -> sysroot/ostree
l00777 0 0      0 /root -> var/roothome
l00777 0 0      0 /sbin -> usr/sbin
l00777 0 0      0 /srv -> var/srv
d00755 0 0      0 /boot
d00755 0 0      0 /dev
d00755 0 0      0 /proc
d00755 0 0      0 /run
d00755 0 0      0 /sys
d00755 0 0      0 /sysroot
d01777 0 0      0 /tmp
d00755 0 0      0 /usr
d00755 0 0      0 /var

I don’t have solutions yet. I’m just trying to provide any information I could about the state of the ostree and the storage device.

5

there is a command to display the list of previous ostree releases.

you could rebase to that, if the rpm-ostree version really is the problem

6

Can you get us the backtrace from the journal or coredumpctl?

If ostree fsck gives you error, I would make backups ASAP and check if your disk is dying.