this post was submitted on 27 Feb 2025
29 points (87.2% liked)

Linux Questions

1541 readers
1 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 2 years ago
MODERATORS
29
submitted 1 month ago* (last edited 1 month ago) by gpstarman to c/linuxquestions@lemmy.zip
 

Context: I updated my CachyOS (Arch) BTRFS system. Some new things caused few problems especially brave browser(missing tabs), some icons missing.

So I wanted to go back to previous snapshot.

What I did: I first restored my home subvol which I saved before update. I worked.

Then I tried to restored my root partition. This is where I got the problem.

I got this error.

1001090084

I would really appreciate URGENT help

If you need any more details I can provide.

EDIT

  1. I used BTRFS Assistant to restore the root partition. And I did it while the OS is running.

( I previously did that and got no issues )

  1. I pressed crtl+d and got ๐Ÿ‘‡๐Ÿฝ

  1. I typed my password and went into maintenance. Typed journalctl -xb and got 2667 lines ๐Ÿ˜ตโ€๐Ÿ’ซ. While scrolling mindlessly, this looked like something ๐Ÿ‘‡๐Ÿฝ

๐Ÿ‘‰๐Ÿฝ

๐Ÿ‘‰๐Ÿฝ

  1. This is my refind_linux.conf ๐Ÿ‘‡๐Ÿฝ
"Boot with standard options"    "quiet zswap.enabled=0 nowatchdog splash rw rootflags=subvol=/@ cryptdevice=UUID=60ecb22d-7685-43c2-ae2a-a2ad0c531cc7:luks-60ecb22d-7685-43c2-ae2a-a2ad0c531cc7 root=/dev/mapper/luks-60ecb22d-7685-43c2-ae2a-a2ad0c531cc7"

"Boot to single-user mode"    "quiet zswap.enabled=0 nowatchdog splash rw rootflags=subvol=/@ cryptdevice=UUID=60ecb22d-7685-43c2-ae2a-a2ad0c531cc7:luks-60ecb22d-7685-43c2-ae2a-a2ad0c531cc7 root=/dev/mapper/luks-60ecb22d-7685-43c2-ae2a-a2ad0c531cc7" single

"Boot with minimal options"   "ro root=/dev/mapper/luks-60ecb22d-7685-43c2-ae2a-a2ad0c531cc7"


  1. This my OS partition ๐Ÿ‘‡๐Ÿฝ

  1. This is my subvol layout ๐Ÿ‘‡๐Ÿฝ (CachyOS default)

you are viewing a single comment's thread
view the rest of the comments
[โ€“] zero_spelled_with_an_ecks@programming.dev 4 points 1 month ago (1 children)

Put in your root pw and then look at the logs. You might need to mount disks to do so.

[โ€“] harsh3466@lemmy.ml 1 points 1 month ago* (last edited 1 month ago)

This. Enter your su password and have a look at the logs. Likely something you can fix without tooucj trouble. I've run into this a few times over the years and I've always been able to figure out and fix the problem based on the logs.

Edit: removed incorrect instruction.