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

1144 readers

56 users here now

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

founded 2 years ago

MODERATORS

gyro

[email protected]

I guess I borked my System (lemmy.today)

submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/linux4noobs

8 comments fedilink hide all child comments

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

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 )

I pressed crtl+d and got 👇🏽

I typed my password and went into maintenance. Typed journalctl -xb and got 2667 lines 😵‍💫. While scrolling mindlessly, this looked like something 👇🏽

👉🏽

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"

This my OS partition 👇🏽

This is my subvol layout 👇🏽 (CachyOS default)

you are viewing a single comment's thread
view the rest of the comments

[–] 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.