This is the command I used after unlocking the luks device in a rescue environment and confirming it not mounting further:

sudo btrfs rescue zero-log /dev/mapper/luksroot

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.

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.

Been using OsmAnd for years now, but I hear organic maps (or now CoMaps) mentioned way more often. What features does CoMaps have that OsmAnd lacks?

Haskell