Btrfs-assistant not showing snapshots to restore to when booted into a snapshot

[BluishHumility]

Ah, you must be Cheeto from the Arch forum then.

I believe your issue is coming from this part of your process:

@EmeraldEnigma

• sudo umount /.snapshots
• sudo rm -rf /.snapshots
• sudo btrfs subvolume delete /.snapshots
• sudo mkdir /.snapshots
• sudo mount -a

I’m not sure why you are doing that, but I am guessing you have your reasons.

Your setup places the snapshots in a top-level subvolume:

@EmeraldEnigma

sudo btrfs subvol list /
ID 256 gen 132 top level 5 path @
ID 257 gen 132 top level 5 path @home
ID 258 gen 131 top level 5 path @log
ID 259 gen 92 top level 5 path @pkg
ID 260 gen 122 top level 5 path @.snapshots

This deviates from the default nested subvolume layout used by Snapper (where if the root is @, then the snapshots would be @/.snapshots–not @.snapshots).

To use Btrfs Assistant with a custom subvolume layout like this, you need to announce the mapping you have chosen in /etc/btrfs-assistant.conf according to the notes in the configuration file:

# In this section you can manually specify the mapping between a subvol and it's snapshot directory.
# This should only be needed if you aren't using the default nested subvols used by snapper.
#
# The format is <name> = "<snashot subvol>,<source subvol>,<UUID>"
# All should be paths relative the root of the btrfs volume and the UUID is the UUID of the filesystem
# For example, a line might look like this:
# root = "@snapshots,@,48bee883-0eef-4332-9bc5-65f01295e470"
[Subvol-Mapping]

In your case, I think you would set it up like this:

root = "@.snapshots,@,8421b3f7-7a99-4db1-818b-86762a56b09e"