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

Linux 101 stuff. Questions are encouraged, noobs are welcome!

1144 readers
1 users here now

Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.

founded 2 years ago
MODERATORS
29
submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/linux4noobs
 

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
[โ€“] [email protected] 18 points 1 day ago (2 children)

Achievement unlocked: master tinkerer.

Wait did you try to restore the root partition while it was mounted to root? If yes, then that was probably the problem. No OS likes its filesystem being replaced on the fly.

But I have no idea on how to fix it. Maybe boot up a linux from USB and restore the root partition from there?

[โ€“] [email protected] 2 points 1 day ago* (last edited 1 day ago)

did you try to restore the root partition while it was mounted to root?

If you mean to ask if I restored the OS subvol while I am on the OS itself. Then, yes.

But, I've done this before and it worked just fine.

Maybe boot up a linux from USB and restore the root partition from there?

(from live mint) I tried to rename the @ (root) to @_2 and original subvol backup to @. And booted. OS successfully boots. But now my root partition is @_2, which should be @ ?

And the OS was in the state of prior restoration i.e. after system update.

Also please look at the edited part of the post

[โ€“] ikidd 2 points 1 day ago

Years ago, I had a team of techs. I get this new guy, freshly minted MCSE, looking at a server we had pulled out of a clients after throwing down a replacement. I had looked at the server before and the easiest thing was just to nuke and pave, so I tell him to wipe it and install. I come back after an hour to find him repeatedly, from the command line of the NT4 installation I told him to replace, typing "fdisk c:" over and over again. I actually walked away for half an hour to see if he'd figure it out, only to find him at the same spot, typing it again and again.

He didn't last long after that.