Has anyone else have problems with snapper snapshot booting lately. I was using Stephen Tech Talks method to install it before (https://www.youtube.com/watch?v=_97JOyC1o2o) which works flawlessly and still does on the machines I previously installed it on. I tried a fresh install using the “Endeavour” edition and now whenever I boot into a snapshot from grub according to duf root is loaded as “overlay” and not btrfs. It does not do this on my other machines which boot up as btrfs.
I figured I messed something up and looked around the forum and found the write-up by @lorebett on the snapper-support package. I tried his method, which was so simple, and tried to boot from a snapshot but came up with the same issue.
Anyone else noticing something? I want to install Endeavour on a few of my friends computers but I can’t really push it until snapper is working flawlessly. This is the main feature that was allowing them to pull the trigger to leave M$.
That is terrible. You absolutely should not follow that video. What he is doing with subvolumes is not a good plan. /var should never be in it’s own subvolume on an Arch-based distro. Likewise, creating @snapshots is a questionable practice. Unless you have a specific reason for doing that, I would recommend against it.
That is what is supposed to happen. Why is that a problem for you?
I am confused on how to restore a snapshot. In the article by @lorebett it shows him restoring a snapshot using BTRFS Assistant, but when I load it I shows no snapshots.
That is because you created @snapshots. When you do that, you need to create a config file so Btrfs Assistant knows where to restore those snapshots to because you are keeping them at a non-standard location.
If you just did the install as normal, not worrying about any of that, it would “just work”.
I didn’t follow Stephens guide on this install and used @lorebett instructions: installed snapper-support and btrfs-assistant. It still does not seem to work. The screenshot above is from that install.
Quick question related to Stephens setup that in on my other machine that I need to go fix now. He has tge @images subvolume for /var/lib/libvirt/images which is where my vm’s for virtual manager are saved. If I use the new setup it looks like my VM’s will also be overwritten. Should i make a subvol for the images or is that what the @/var/lib/machines path is for and need to store the images there?
Can i make the @images subvol that mounts to the /var/lib/libvirt/images location on a existing install like the one I just did or do i have to reinstall and have calamares do it?
I use this all the time and it does work. I have no issues using this set up. I have btrsfs with btrfs-assistant, snapper-support and btrfsmaintenance. I also have grub-btrfs installed.
Just tried a restore after setting up the image subvol and it works flawlessly. So much better than the way it was before. Working on converting the other machines now.
How exactly are you doing a restore? Do you mean from within brtfs-assistant or from booting and entering a snapshot from the grub menu? or something else?
Edit: I only have a slim understand of all things btrfs and struggle to with nested or flat subvolume layouts and such. I try my best to wrap my head around stuff even though I’m using it myself.
Well, I was doing it what was called in the video “the arch way” which was a PITA. Now I just use BTRFS Assistant which I didn’t realize you could do. It is so easy like timeshift. @lorebett has a great article on it. Thought I already posted a link on here. Sorry:
Me too! … it’s a bit confusing to me as the Arch layout is different i think than EOS if I’m not mistaken. I’m doing exactly the same as you with btrfs-assistant which is how I have been doing it from early on.
What do you mean by Arch different layout? Do you mean the one created by archinstall? When I install Arch I do it manually and use the same layout as EOS, which I think is the suggested layout by Arch as well.
