CachyOS

70 readers

1 users here now

https://cachyos.org/

founded 1 year ago

MODERATORS

hesburger@sopuli.xyz

I guess I borked my System (lemmy.today)

submitted 4 weeks ago* (last edited 4 weeks ago) by gpstarman to c/cachyos@sopuli.xyz

1 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)

top 1 comments

sorted by: hot top controversial new old

[–] Vinny_93@lemmy.world 3 points 4 weeks ago* (last edited 4 weeks ago)

I had this a while back, also to do with btrfs. I first checked if all the SATA cables were properly inserted. Ended up booting a fresh OS from a USB drive, cd into the OS disk to read out the journal, see what the issue was. Ended up having to fix the fstab but I could've reinstalled the filesystem if needed.