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.
Thanks. I tried this, was able to get into my system. After playing around with WPA_supplicant and IP link, I was able to get internet and run the updates with pacman.
But I’m getting a similar problem as I was having at some point before, where I boot into a black screen, I can change the terminal with CTL + Alt + F1, then my login screen shows up, put my password, and the login freezes.
When I booted into my system earlier to do the updates, I used init=/bin/bash, but SystemD didn’t auto start then, hence why I used WPA_supplicant. Perhaps SystemD is still not starting, hence why I’m not able to log in or open other terminal window.
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:
sudo btrfs rescue zero-log /dev/mapper/luksrootAfter 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.
Thanks. I tried this, was able to get into my system. After playing around with WPA_supplicant and IP link, I was able to get internet and run the updates with pacman.
But I’m getting a similar problem as I was having at some point before, where I boot into a black screen, I can change the terminal with CTL + Alt + F1, then my login screen shows up, put my password, and the login freezes.
When I booted into my system earlier to do the updates, I used init=/bin/bash, but SystemD didn’t auto start then, hence why I used WPA_supplicant. Perhaps SystemD is still not starting, hence why I’m not able to log in or open other terminal window.
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.