Fresh install & dup of TW in which I erased the entire disk. I’ve tried a few of the solutions I found around online but no luck so far.
TW version : 20221117
[FONT=monospace]Kernel: 6.0.8-1-default
[/FONT]For what it’s worth, the .iso I used was Gecko Linux Rolling KDE, following all the standard installation settings (including that it’s set up as btrfs). Curiously, I had installed the same iso before and it did have the option to boot from a snapshot, but on this installation it was never there even before running any updates. (I think it ships with kernel 5.19).[FONT=monospace]
[/FONT]I tried updating the grub timer in YaST, and another method in which I ran an mkconfig command (can’t find in my history right now).
That would make sense, but on a previous install (I had to abandon because I broke something else entirely different), it was working just fine. I’m asking the owner of that project on a github discussion and they seem also perplexed why I haven’t got it, since it was installed from the same snapshot (I think he only makes a new rolling snapshot a few times a year). Let me know if there are any terminal queries I could run that might help diagnose this,
I normally use “ext4”, and boot to a snapshot depends on “btrfs”. But your “btrfs” subvolumes are different from what an normal openSUSE provides. In particular, a normal setup has subvolumes for “/boot/grub2/x86_64-efi” and for “/boot/grub2/i386-pc” (if I recall correctly). And I think those are important for booting a snapshot (so that grub2 is not also rolled back for the snapshot).
That is not Tumbleweed, please do not mislead others. You should have selected “Other Version”.
There is nothing to diagnose. During installation snapshot support was disabled. There could be any reason why, including you accidentally disabling it. Your btrfs mount options are not default (default installation most certainly does not enable compression on root filesystem), so either your distribution does something differently, in which case we have no way to guess why it decided to disable snapshots, or you manually changed proposed disk configuration - see above
Do new installation, document every step with screenshots, and if it turns out that snapshots are enabled during installation but become disabled after installation - then this is a bug in installer.
The whole subvolume layout is different when booting from snapshot is enabled during installation. It is not about just creating a couple of additional subvolumes.
RESOLUTION
I ended up getting a little frustrated and just installing standard tumbleweed, so now I have snapshots working.
When troubleshooting the issue with the creator of geckolinux on their github discussions, they suggested : “The different subvolume layout is to be expected, as the configuration that I found to work best within the constraints of the Calamares installer is slightly different from what the openSUSE YaST installer uses. But you definitely have a Btrfs filesystem. The problem is that for some reason your system is using a @ subvolume for the root partition, whereas the Snapper config expects it to not have a subvolume…”
Thanks for the feedback. It’s always a good idea to start with a minimum default configuration. When making changes to the defaults do it step by step and always check the ramifications prior to making another change.