Linux questions Rules (in addition of the Lemmy.zip rules)
Tips for giving and receiving help
Any rule violations will result in disciplinary actions
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.
I would really appreciate URGENT help
If you need any more details I can provide.
Please post more details
Also I don't want to be that guy but for me personally I would stick to the beaten path. Stick with the mainstream stuff that is stable and well tested. CachyOS is Arch based and does not have anywhere near the stability of something like Linux Mint.
Have you resolved it yet? First thing would be finding out why did it kick you into emergency mode ie whats the actual error
Not yet.
I kindly request you to see the edited post too.
What did you do before hand?
Put in your root pw and then look at the logs. You might need to mount disks to do so.
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.
I saw similar error when I had a drive mounting line in /etc/fstab
When i commented out the line it went back to normal.
Give us your fstab and lsblk.
Or, the specific piece of information I want is where the kernels are located. When /boot is part of the root subvolume (not the default setup, sadly), then the kernels will be snapshpotted along with the rest of the filesystem. /boot/efi would be where the efi system partition is, and where the bootloader is installed.
If /boot is instead the efi parition (default setup lmao), then this means that when you restored a snapshot of your root subvolume, your kernels were not downgraded. I suspect that older kernels attempting to read/view newer kernel modules would cause this boot failure.
Start by following the instructions on the screen in order to get an error log.
If the root account is locked, which cachyos does by default, then you won't get anything from this screen.
I had to fix by usb booting and troubleshooting (a different issue though, I was playing with initramfs generation).
Maybe try ctrl-alt-delete?