I figured it out, i needed some new command line arguments I had added from the
wiki, but it had appeared to not be working because as part of my
troubleshooting i had installed the normal arch Linux lts instead of my custom
one, made the edit to my custom one, and it was still trying to boot th
El jue, 16-03-2023 a las 02:47 -0700, nihilistzsche escribió:
> Yes when I mount them while in the rescue environment they are
> writable and data persists so I don’t see any corruption.
>
In that case the only thing I can think of is that for some reason the
disk identifier has changed. When you
Yes when I mount them while in the rescue environment they are writable and
data persists so I don’t see any corruption.
As for btrfs on lvm i understand it’s unnecessary but I’ll just say it’s
personal preference and I don’t normally need to ask for help but as i can’t
get my systems to boot I
El jue, 16-03-2023 a las 01:45 -0700, nihilistzsche escribió:
> Since I updated a few days ago with kernels 6.2.6 and lts 6.1.19 all
> of my systems (a pc acting as a headless server with normal kernel, a
> server with lts kernel, and a laptop with normal kernel) refuse to
> boot. While trying to
Hi,
If it can help, I got a similar issue a few months ago, the culprit
was a corrupted btrfs log and the solution was to clear this log with a
rescue USB:
btrfs rescue zero-log
I think it was a dmesg message that helped me
Le jeudi 16 mars 2023 à 01:45 -0700, nihilistzsche a écrit :
> Si
