Changed Grub to systemd-boot, then no snapshots!

Sorry if this sounds a bit silly!
I just converted (again) to systemd-boot (BTRFS, BTRFS-Assistant, Snapper… installed - Had a few system snapshots and /home as well)
I followed instructions I did before ([Tutorial] Convert to systemd-boot and my post down there where I documented what I did step by step here and now I can boot to LTS thanks to @dalto and his instructions.

Now, when I start BTRFS-Assistant I can only see my /home snapshots, no profile for system or even eariler system snapshots!

Is this OK?
How can I get back system snapshots and snapshot as I did before under BTRFS (if possible under systemd-boot)?

Just in case so I can live boot, install BTRFS-Assistant, restore a previous snapshot, then reboot. (This is the right way to recover?)

Your kind assistance as usual highly appreciated.
Thank you.

( just thought maybe reinstalling BTRFS-Assistant and snapper sort this out?)

UPDATE:
Just curious I

yay -Syu snapper

I got

(1/5) Reloading system manager configuration...
(2/5) Arming ConditionNeedsUpdate...
(3/5) Reloading system bus configuration...
(4/5) Checking which packages need to be rebuilt
(5/5) Performing snapper post snapshots for the following configurations...
:: Searching databases for updates...
:: Searching AUR for updates...
 there is nothing to do

Performing snapper post snapshots for the following configurations... as I understand means it is already taking snapshots!

UPDATE 2:
Played with BTRFS-Assitant, created a new profile called it “system”, backup path “/” and took a manual snapshot.
I am not sure if it is really system snapshot.
In tab “Subvolumes”, selecting any snapshot → Restore/Backup Button → “The subvolume you selected is not a BTRFS Assitant backup”

Can we see a few outputs first:

sudo btrfs subvolume list /
sudo snapper list-configs
ls /etc/snapper/configs
1 Like

Again @dalto for the recue as usual!

[limo@lenovo ~]$ sudo btrfs subvolume list /
[sudo] password for limo: 
ID 256 gen 17854 top level 5 path @
ID 257 gen 17854 top level 5 path @home
ID 258 gen 17795 top level 5 path @cache
ID 259 gen 17854 top level 5 path @log
ID 260 gen 27 top level 256 path var/lib/portables
ID 261 gen 28 top level 256 path var/lib/machines
ID 264 gen 17848 top level 257 path @home/.snapshots
ID 265 gen 232 top level 264 path @home/.snapshots/1/snapshot
ID 289 gen 556 top level 264 path @home/.snapshots/5/snapshot
ID 346 gen 2054 top level 264 path @home/.snapshots/19/snapshot
ID 385 gen 3730 top level 264 path @home/.snapshots/35/snapshot
ID 420 gen 5380 top level 264 path @home/.snapshots/51/snapshot
ID 441 gen 6150 top level 264 path @home/.snapshots/60/snapshot
ID 491 gen 8923 top level 264 path @home/.snapshots/84/snapshot
ID 541 gen 11751 top level 264 path @home/.snapshots/108/snapshot
ID 559 gen 12712 top level 264 path @home/.snapshots/117/snapshot
ID 601 gen 13775 top level 264 path @home/.snapshots/126/snapshot
ID 635 gen 15126 top level 264 path @home/.snapshots/140/snapshot
ID 661 gen 16128 top level 264 path @home/.snapshots/149/snapshot
ID 665 gen 16249 top level 264 path @home/.snapshots/150/snapshot
ID 667 gen 16368 top level 264 path @home/.snapshots/151/snapshot
ID 669 gen 16444 top level 264 path @home/.snapshots/152/snapshot
ID 671 gen 16563 top level 264 path @home/.snapshots/153/snapshot
ID 673 gen 16682 top level 264 path @home/.snapshots/154/snapshot
ID 675 gen 16801 top level 264 path @home/.snapshots/155/snapshot
ID 677 gen 16920 top level 264 path @home/.snapshots/156/snapshot
ID 679 gen 17037 top level 264 path @home/.snapshots/157/snapshot
ID 681 gen 17060 top level 264 path @home/.snapshots/158/snapshot
ID 683 gen 17100 top level 264 path @home/.snapshots/159/snapshot
ID 685 gen 17219 top level 264 path @home/.snapshots/160/snapshot
ID 686 gen 17470 top level 264 path @home/.snapshots/161/snapshot
ID 687 gen 17590 top level 264 path @home/.snapshots/162/snapshot
ID 688 gen 17707 top level 264 path @home/.snapshots/163/snapshot
ID 689 gen 17848 top level 256 path .snapshots
ID 690 gen 17814 top level 689 path .snapshots/1/snapshot
ID 691 gen 17834 top level 264 path @home/.snapshots/164/snapshot
ID 692 gen 17834 top level 689 path .snapshots/2/snapshot
[limo@lenovo ~]$ 
[limo@lenovo ~]$ sudo snapper list-configs
Config | Subvolume
-------+----------
home   | /home    
system | /    
[limo@lenovo ~]$ ls /etc/snapper/configs
home  system
[limo@lenovo ~]$ 

Screenshot_20220909_141538

That all looks right to me.

The reason you aren’t getting transaction snapshots is probably because you named your / snapshots “system”. By default, snap-pac uses “root”. You need to change the spac-pac config to use “system”

You can see it isn’t taking snapshots during pacman operations here:

If it was taking snapshots, it would list at least one configuration there.

So, better remove this profile “system” and create another one called "root’?

You could do that. It seems easier to me to just change the spac-pac config to use “system” but either way works.

1 Like

Done! Deleted and created a new one named “root”
Will reboot to double check it will take snapshots upon boot.

But you see my current config is ok?
Are there a few commands to do to add booting to snapshots to systemd-boot?
(I know I might seem so greedy… but I think it is wise to get the most out of a powerful and stable, easy Linux system as EndeavourOS)

Feel free to skip this if it is too much. It is OK with me.
I don’t mind repeating when LTS kernel gets updated if it is not to much or can be done as a script.

Update:
Amazing as usual. Rebooted and got instantly a boot snapshot!
perfect BTRFS Assistant

It is possible to do this but there are a few things to consider:

  • When the kernel version changes, the boot will fail
  • Because of the above, it would probably only make sense to boot off very recent snapshots
  • You would have to write the scripts and automation to do this yourself. It certainly isn’t anything I am interested in working on. I see no appreciable value in snapshot booting.
1 Like

Oh no… no thanks… these stuff “to consider” are not for me.
I am OK this way. :rofl:

Thanks @dalto very much for your help and support as usual.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.