Dnf version Hades During Upgrade from F43 to F44

Ask Fedora
, ,
1

Tried upgrading from F43 to F44, but while OS seems to think it is on F44, the dnf repositories and grub seem to think otherwise.

NAME="Fedora Linux"
VERSION="44 (Workstation Edition)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=44
VERSION_CODENAME=""
PRETTY_NAME="Fedora Linux 44 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:44"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f44/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=44
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=44
SUPPORT_END=2027-05-19
VARIANT="Workstation Edition"
VARIANT_ID=workstation

kernel: 7.0.12-101.fc43.x86_64

Grub option: Fedora Linux (7.0.12-101.fc43.x86_64) 43 (Workstation Edition)
Grub entry:

load_video
set gfxpayload=keep
insmod gzio
linux ($root/vmlinuz-7.0.12-101.fc43.x86_64 root=UUID=xxxxxxxxx ro rootflags=subvol=root rhgb quiet initcall_blacklist=simpledrm_platform_driver_init
initrd ($root)initramfs-7.0.12-101.fc43.x86_64.img $tuned_initrd

[editing on start-up by adding systemd.unit=muli-user.target because while I get the graphical login, it goes blank for a while and come back to a login.
Have a:
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
so I have to deal with
dnf install akmod-nvidia-580xx xorg-x11-drv-nvidia-580xx xorg-x11-nvidia-580xx-cuda --refresh
which is where I discovered the F43/F44 problem!]

Have tried
dnf clean
dnf makecache

dnf repoquery --duplicates shows all sorts of F43/F44 duplicates. Example

adobe-mappings-cmap-0:20231115-3.fc43.noarch
 duplicate with "adobe-mappings-cmap-0:20231115-5.fc44.noarch"
adobe-mappings-cmap-0:20231115-5.fc44.noarch
 duplicate with "adobe-mappings-cmap-0:20231115-3.fc43.noarch"
adobe-mappings-pdf-0:20190401-10.fc43.noarch
 duplicate with "adobe-mappings-pdf-0:20190401-12.fc44.noarch"
adobe-mappings-pdf-0:20190401-12.fc44.noarch
 duplicate with "adobe-mappings-pdf-0:20190401-10.fc43.noarch"
...
...

tried dnf reinstall $(dnf repoquery --duplicates --ltest-limit=1 -q)

but get “errors”:

Packages for argument ‘{F44 package name"’ installed, but not available.

Have also tried:
dnf system-upgrade download --releasever=44 --allowearasing
dnf system-upgrade download --releasever=43 --allowearasing
sudo dnf distro-sync

without success.

Suggestions will be very much appreciated!

3

You can try the following to try and recover from a broken/incomplete upgrade.
sudo dnf distro-sync --refresh --releasever=44 --setopt protected_packages=

4

That probably should be
sudo dnf distro-sync --refresh --releasever=44 --allowerasing --setopt protected_packages=

5

@computersavvy @moskimus unfortunately, neither dnf command worked. after reboot, still F43/f44 duplicates. sample of errors when commands are run:

dnftry20260622
dnftry202606221920×2560 997 KB

[tried using a tee on the command, but it did not capture the errors. looked in /var/log/dnf5.log but either it is not there or I missed it. How can I capture the output of the command with errors?]

Thank you for your suggestions!

6

Apparently your file system is mounted read only and cannot be altered.
Please run mount and show us the detailed output for every mounted file system.
The output should look something like this

$ mount
/dev/vda3 on / type btrfs (rw,relatime,seclabel,compress=zstd:1,discard=async,space_cache=v2,subvolid=256,subvol=/root)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=3999308k,nr_inodes=999827,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64,usrquota)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=600,ptmxmode=000)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate,memory_recursiveprot,memory_hugetlb_accounting)
none on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime,seclabel)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=1619892k,nr_inodes=819200,mode=755,inode64)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,nosuid,noexec,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=41,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=7279)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime,seclabel)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,seclabel,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,seclabel)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
none on /run/credentials/systemd-resolved.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
/dev/vda3 on /home type btrfs (rw,relatime,seclabel,compress=zstd:1,discard=async,space_cache=v2,subvolid=257,subvol=/home)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel,nr_inodes=1048576,inode64,usrquota)
/dev/vda2 on /boot type ext4 (rw,relatime,seclabel)
/dev/vda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=809944k,nr_inodes=202486,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
7

@computersavvy
Here is the result of mount:

mount20260623
mount202606231920×886 387 KB

Sorry about being a picture, but usb drive was uncooperative this morning and I have to head to work. Should note that the problem appeared mid-upgrade from F43 to F44. I’m guessing something happened due to the NVIDIA driver problem which broke the upgrade an left things the way they are.

Thank you for you continued interest!

8

As you can see, / is mounted read only (first line of output).

You might want to look at journalctl -b 0 for why it’s mounted read only… and then perhaps run a btrfs check on it. However, ascertaining WHY before trying to correct it is prudent.

9

@anothermindbomb
Yes, I saw that there was a read-only device.

btrfs check --force /dev/nvme0n1p3 produced an endless stream of errors. Typical is shown in the top of the image below.

Bottom of the image is the result of btrfs --grep "btrfs: -b 0

btrfs20260623
btrfs202606231920×790 345 KB

Any route to recovery at this point? Or should I just plan on making time to do a fresh install?

Thank you for you suggestions!

10

From the text at the top of the image, it looks like every consecutive inode is buggered. Has it had a head crash or something? Dropped down the stairs perhaps? :slight_smile:

I would defer any judgement on this lot, given the amount of errors you say it’s spewing out, to @chrismurphy - he may well fancy a copy of the output in order to try to diagnose the root cause of the issue (or he may just declare this to be a pretty knackered disk, and you should replace it as it will be a source of pain every day of the rest of your time with it).

Does it have a lot of hours on it? I ask this as I had a Samsung 970 soil the bed on me (3 weeks out of warranty) and it had basically done nothing other than sit in a desktop and be powered on - it had an OS installed on it but rarely used and it STILL died…

11

@anothermindbomb @chrismurphy

That 970 is several years old and probably has a lot of hours on it as at times the machine was on 24 hours a day for weeks at a time. The one thing I find odd is that this problem arose during the upgrade from F43 to F44. Off course, maybe that was the stresser that broke the camel’s back!

There isn’t anything really important on the machine as it is a hobby box, but I am sort of interested in the challenge of recovering it before I go for the reinstall.

Thank you for your insights!