this post was submitted on 27 Feb 2025

15 points (89.5% liked)

btrfs

118 readers

2 users here now

founded 2 years ago

MODERATORS

[email protected]

I guess I borked my System (lemmy.today)

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

10 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 10 comments

sorted by: hot top controversial new old

[–] Scholars_Mate 3 points 1 week ago* (last edited 1 week ago) (1 children)

What steps did you take to rollback your root subvolume?
Can you log into the emergency shell and share any logs?
Is your root partition mounted in the emergency shell, or is the initramfs still mounted in the emergency shell?

[–] [email protected] 1 points 1 week ago

I just used BTRFS Assistant to restore. I did while the OS is on.
I shared some on edited post. Pleae look.
Idk for sure. But it shows my user name after I enter password. So, I think root?

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

well, you can start by typing the journalctl command the system is instructing you to, after getting into the maintenance shell. always get the logs and error messages so you can understand what happened. if you need to, share it with us so we can have a go at deciphering what the computer is saying about it.

it would help if you could provide more details about what you were trying to do, and how it broke to make a restore necessary in the first place.

[–] [email protected] 1 points 1 week ago (1 children)

Journal is 2667 lines 🥲

Please look at edited post.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

i see it struggling to mount the boot device is the device id its referencing on the fstab and on refind matching its current id?

[–] [email protected] 1 points 1 week ago (1 children)

It does match.

I included refind_linux.conf and partition UUID already. Should I include fstab too?

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

does it mount correctly from a live usb?

alternatively, can you mount it manually from maintenance shell?

meaning: is the boot partition botched, or is it a bootloader config issue?

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

Please look at this reply https://programming.dev/post/26092542/15311163

[–] [email protected] 0 points 1 week ago

snaps are kind of terrible, but beyond that i cant help you because im not actually that familiar with btrfs and cachy. i hope someone can help you further fix it though.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

Did you try regenerating the initramfs after rolling back the root partition? That's what's wrong whenever my install is fucked. I'm unfamiliar with the recovery console but see if you can

manually unencrypt cryptsetup open /dev/nvme0n1p2 root,
mount mount /dev/mapper/root /mnt -o subvol=@root mount /dev/nvme0n1p1 /mnt/boot,
chroot into the system arch-chroot /mnt
and run mkinitcpio -P

Edit: Oh the screenshot just loaded in. The problem seems to be that you can't mount /boot? What happens when you try to mount it manually?