Hi, I’m new with Endeavours, I came from Manjaro Testing branch (their gurus don’t want use snapper, for my opinion) and with Arcolinux (they have snapper during install) but this is a confusing distro for me,
but I may say that I’m in love with this EOS.
After a fresh install of Endeavouros with gnome DE, I’ve installed snapper as follow (following a tutorial found here for a post install with gnome DE):
yay -S snapper-support btrfs-assistant
snapper-support will automatically install snapper, grub-btrfs, snap-pac from official Arch repos and configure Snapper for you, and the BTRFS Assistant is a GUI Tool made by r/GarudaLinux team by which you can easily manage and restore your Snapshots and BTRFS Subvolumes. grub-btrfs will enable accessing Snapshots from GRUB Menu.
I’ve NOT made any changes to volume that are automatically created by Endeavour with a BTRFS file system during the installation.
I would like to know if this procedure is correct or if I must change something else, I’ve made a couple of test all has worked good
Thank again and I apologize since now for this request but I’ve not found nothing on the web that may convince me that I’m in a correct way with snapper
On my other laptop with two ssd I’ve noted that btrfs-assistant hasn’t volume home
also on this laptop, I’ve made standard installation with btrfs but I’ve choosen on first hd just /boot/efi and /root
on second hd I’ve created as mounting point /home
the two disks are in btrfs
[robertocannito@roberto-gl753vd ~]$ sudo btrfs subvolume list /
[sudo] password di robertocannito:
ID 256 gen 3133 top level 5 path @
ID 257 gen 3130 top level 5 path @cache
ID 258 gen 3131 top level 5 path @log
ID 259 gen 25 top level 256 path var/lib/portables
ID 260 gen 26 top level 256 path var/lib/machines
ID 261 gen 3130 top level 256 path .snapshots
ID 386 gen 2721 top level 261 path .snapshots/125/snapshot
ID 387 gen 2722 top level 261 path .snapshots/126/snapshot
ID 388 gen 2723 top level 261 path .snapshots/127/snapshot
ID 389 gen 2725 top level 261 path .snapshots/128/snapshot
ID 390 gen 2901 top level 261 path .snapshots/129/snapshot
ID 391 gen 2903 top level 261 path .snapshots/130/snapshot
ID 392 gen 3035 top level 261 path .snapshots/131/snapshot
ID 393 gen 3037 top level 261 path .snapshots/132/snapshot
ID 394 gen 3041 top level 261 path .snapshots/133/snapshot
ID 395 gen 3042 top level 261 path .snapshots/134/snapshot
[robertocannito@roberto-gl753vd ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 238,5G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 238G 0 part /var/cache
sdb 8:16 0 931,5G 0 disk
└─sdb1 8:17 0 931,5G 0 part /home
sr0 11:0 1 1024M 0 rom
You don’t need a subvolume called @home, it is fine either way.
You mounted your /home on the root of the filesystem. There is nothing wrong with that. Although, it is perhaps a little limiting later on. I would probably have created a subvolume for /home instead of mounting it directly on the root of the filesystem in case you wanted to do more with that SSD later.
Oh my gosh, I think systemd-boot, I’ve not seen the possibility to install grub
What do you suggest, keep systemd or reinstall with grub?
in first case btrfs-assistant work good?
the only solution for eventually restore is to use btrfs-assistant, isn’t?
Obviously i know this. I’m just trying to figure out how it could be made fool proof? As you say people are just too much in a rush and not following and reading and understanding the choices available.