this post was submitted on 17 Jul 2023
17 points (100.0% liked)
Linux
48216 readers
645 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Only thing I can think of is the subvolumes left over might be causing an issue. I don't know how snapper performs a rollback and I've seen a couple ways to do it. Sometimes its modifying the default subvolume to the snapshot you want to rollback to. This is fine IF your kernel params are NOT specifying the subvol. That would look like this
rootflags=subvol=subvolume_name
.Usually I just rename the subvols and make sure the snapshot I'm renaming to replace the current root subvol is not set to read only.
So rename current root to root.broken Then rename snapshot to root Then set readonly prop to false.
Well, I tried rolling back to another snapshot and checked my kernel params and its not in there. My port issue seems to be fixed but i still do not boot into the new kernel after updating and rebooting. Edit: I think I need to clean up my /boot directory somehow since it's partition is not btrfs. But I'm unsure how to do it, or where to read up on it.
Well as long as you take a snapshot of your data and move that snapshot to another drive, you're free to tinker without real worry. Arch Linux wiki should have lots of examples of what you're trying to fix or modify. There's always a fresh install as well, which isn't ideal most of the time but as long as the data is safe, then its an option. Best of luck, hope you're able to resolve the issue.
Thanks, it's looking like I'll be doing a reset. It looks like grub-btrfs creates its own entries and points towards the boot directory within the /.snapshot/ directory, completely ignoring my boot partitions current files.
Ubuntu was never my first choice but was necessary for using my arc380 with plex transcoding. Might as well take this opportunity to move back to debian with bookworm. Only trouble is I would prefer a 6.2 over 6.1 kernel distribution, and while I enjoy arch on my laptops, I'm not sure I'd want to update my server so frequently.