this post was submitted on 27 Feb 2025
27 points (86.5% liked)
Linux Questions
1428 readers
1 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Short Answer: No, kernels are not snapshot ted
Long Answer: It's bit weird in my case.
Boot, EFI, Root are three separate partitions in my case.
Root mounts to /
Boot mounts to /Boot
Efi mounts to /boot/efi
It is this way because when I initially partitioned the EFI, I gave very less storage. But linux kernels are bigger than that. So, either I have move the partition. Which I didn't prefer because It'll take a lot of time and it said possibility of data loss.
So, I simply created new partition.
By default, CachyOS only snapshot /@ and /@/home. Which didn't include /boot because it's a separate partition it's own and not even BTRFS.