search

uszie / systemd-boot-snapshots

Snapshot support for systemd-boot
GNU General Public License v3.0
16 stars 0 forks source link

Does it work on Arch based distro ? #1

Open HanM23 opened 1 year ago

HanM23 commented 1 year ago

Hello, I am really interested in systemd-boot-snapshots. Does it work in Arch based distro ? What i understood is that it's only working on Ubuntu based distro for now, just to make sure I understood well. Regards

adamensler commented 1 year ago

I would also like to know this. So far the only bootloaders I've found that support booting from a snapshot are grub-btrfs and refind-btrfs, which are both explicit about Arch support. If this can support Arch-based distros that would be great.

PureIncompetence commented 1 year ago

I tried it with an Arch installation, as I was curious, too. It was set up with a seperated fat32 efi boot partition, and seperated btrfs subvolumes for @ (root) @home and @var_log.

sudo make install gave me the following output: Created symlink /etc/systemd/system/multi-user.target.wants/timeshift-snapshots.path ? /usr/lib/systemd/system/timeshift-snapshots.path. Created symlink /etc/systemd/system/multi-user.target.wants/snapper-snapshots.path ? /usr/lib/systemd/system/snapper-snapshots.path. Created symlink /etc/systemd/system/boot-efi.mount.wants/systemd-boot-entries.path ? /usr/lib/systemd/system/systemd-boot-entries.path. Unit /usr/lib/systemd/system/systemd-boot-entries.path is added as a dependency to a non-existent unit boot-efi.mount. Failed to start systemd-boot-entries.path: Unit boot-efi.mount not found. make: *** [Makefile:29: install] error 5

Since update-initramfs appearently doesn't exist on Arch, I skipped it.

update-systemd-boot-snapshots outputs Creating snapshots based on loader entry: /boot/loader/entries/arch.conf Added 3 snapshots to the systemd-boot loader After that, the snapshots are bootable from the systemd-bootmenu. Even though my timeshift btrfs snapshots contains the @home subvolume, it is not mounted from the snapshot when booting a snapshot. Only @ (root) is mounted / booted from the snapshot, while the regular / current @home subvolume is used. I dont know if thats by design or an error with my setup. Probably that could be suited to my needs (by also mounting the @snapshot/xxxx/home subvolume using some boot parameter) with a better understanding of the systemd-boot configuration options.

Tldr; What works for me:

What doesnt: