BTRFS corruption reports on Fedora 44 yet?

[kenryo (Kenric Young)]

To clarify, this didn’t happen to me but are there any reports of kernel 6.19.14-300.fc44.x86_64 causing btrfs corruption?

BTRFS error (device nvme0n1p3): parent transid verify failed on logical 12435308 mirror 1 wanted 95 found 16
BTRFS error (device nvme0n1p3): parent transid verify failed on logical 12435308 mirror 2 wanted 95 found 16

Just got a report of a clean installs of both F44 KDE Plasma and F44 Workstation showing BTRFS corruption after offline upgrades over on the Fedora Discord, same user on the same PC
Basic system specs:
CPU: Ryzen 5 4500
Motherboard: Gigabyte B550 Gaming X V2
GPU: RX 5500XT

Nothing helpful to diagnose so I’ll summarize

• User states they installed F44 KDE without running the self-integrity check
  • 20 minutes in they used Plasma Discover to update the system.
  • Reboots to the offline updates before completing and rebooting again
  • System boots the new kernel, and the system is left on the spinner splashscreen for 10 minutes
  • The user hops into the discord for help
  • I had them press ESC to view the boot log which gave the gave the error as in the 2nd screenshot below
    • 
    • 
  • System was unresponsive so I had them force reset the system and try all three kernels, which gave the same errors as above.
• Given it was a brand new install, I directed them to do a clean install of F44 Workstation
  • F44 Workstation Installation USB passed the self-integrity check and Erase Disk was chosen to wipe the previous system
  • They run an offline update with GNOME Software
  • Boom, it fails with the same error as with the F44 KDE install previously

[computersavvy (Jeff V)]

In both cases the updates were done with the gui using packagekit.

Have they tried another new install then performing the update with cli dnf?

[bitsailor (Tarmo)]

I am not sure if this could be related, it draw my attention that I had a similar problem with an AMD Ryzen 5 computer too, the Intel upgrade was fine. It could be a coincidence who knows.

Fedora Atomic rollback gone after upgrading to Fedora Atomic 44

Fedora Atomic 44 GNOME, fully encrypted I have to computers running Fedora Atomic GNOME, the upgrade in the Intel computer is fine but after upgrading to 44 the AMD Ryzen 5 PC now when I boot the computer it has no rollback option and it boots directly into Fedora 44. I looked into Gnome files and I discovered two new partition that Fedora placed there, I mounted them and I think it is the rollback partitions that somehow ended up there. Rolling back is not an option obviously. Screenshots of…

[orionfluxx (Orion Jackson)]

@computersavvy I’m that person. I have not tried updating through dnf as I’m not very used to Fedora yet. I have installed Fedora 43, and am going to test updating through dnf. I should also mention I ran into an error after pulling out the install media once the install completed.

I am currently upgrading all packages through dnf and am about to restart to see if the issue persists through Fedora 43.

Edit: I have just upgraded all system packages through dnf and nothing has crashed yet. It seems to only be an issue in F44 as far as I have been able to tell.