this post was submitted on 24 Jul 2025
35 points (92.7% liked)
Arch Linux
8987 readers
1 users here now
The beloved lightweight distro
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've had this exact error a couple of weeks ago. You have to clear the replay log (and lose potentially 30 seconds of disk writes). Let's see if I can find exact instructions before the end of my commute.
This is the command I used after unlocking the luks device in a rescue environment and confirming it not mounting further:
After that, I could mount again and boot.
Here's more info on the command, to verify advice is sound: https://manpages.debian.org/testing/btrfs-progs/btrfs-zero-log.8.en.html#zero
EDIT: For me it didn't happen during an update, btw. You might still need the chroot approach to make the system bootable again.
This worked for me. Thankfully, I didn't have a hard crash during an update, so my system proceeded to boot normally.
The craziest part is that I didn't google this. My computer crashed, I rebooted it via magic sysrq keys, and then booted to an error.
I went on Lemmy on my phone out of frustration and by sheer chance one of the first things I saw was a solution.