Boot off another installed distro or a live ISO, restore the snapshot, chroot in and run reinstall-kernels.
That being said, I can tell you that personally, I have only once restored a snapshot outside of my testing for Brtfs Assistant. Even then, it was only done because I was working with a distro I wasn’t very familiar with(KDE Neon).
In normal operation, I have never restored a snapshot. That being said, I access my snapshots all the time. I am much more likely to restore files from a snapshot than an entire snapshot.
Sorry if this question was already answered, could not find it but as it is a very long topic it can exist already above. I am running already systemd-boot, installed with mkinitcipio a few months ago, following @dalto tutorial when we faced the grub issue last summer.
Now I’d like to switch to Dracut.
As per my understanding I don’t need to reinstall systemd-boot, all I need to do is the following:
Remove the Mkinitcipio package and install Dracut:
And … that’s it ? Or do I miss something ? (I also don’t remember having installed a package named “reinstall-kernels” but I assume it comes with the kernel-install-for-dracut, right ?)
@dalto, got an error while running sudo pacman -S kernel-install-for-dracut
It indeed does try to remove kernel-install-mkinitcpio but gives me also this error:
error: removing mkinitcpio breaks dependency 'mkinitcpio’required by mkinitcpio-openswap
So shall I first remove mkinitcpio-openswap ?
I believe it may break my Swap but at the moment I can live without…
Not familiar with dracut, reading the Github page now. Looks like it would mainly be used for more efficient boot up?
UPDATE: Ahh, I see the latest release has moved from mkinitcpio to dracut (and mkinitcpio maintainer is retiring?) so, I guess I should give this higher priority. Off from work for the week anyways so…tally-ho I guess
Well I tried and must of missed a step or fat fingered cuz it no booty. No worries, that is why /home is on it’s own partition. Reinstall and run my script to install all the software I use.
Probably so. Boot just took me to me to the BIOS screen. Reminiscent of when grub had to be reinstalled after update a few months back. The directories looked right but I must of missed something.
If you remount the ESP partition (which was previously mounted to /boot/efi) to /efi/, two things will happen:
the directory /boot/efi/ becomes empty (because it is no longer the mount point for the ESP partition). Since /boot/efi/ is empty and no longer serves a purpose, you can safely remove /boot/efi/ as stated in the tutorial.
all the contents in the ESP partition now appears inside the /efi/ directory (because /efi/ is the new mount point for the ESP partition). Previously, the initramfs files, etc. are inside /boot/efi/. After the remound, they will all appear inside the /efi/ directory. You no longer need all those files, so you can choose to clean them up by removing them.
Before these steps,
your /boot/efi/ directory will have the grub directory, the initramfs files, the vmlinuz files. After the remount, all thjat stuff will appear under /efi/. The tutorial simply suggests you remove all of them (/efi/grub/, /efi/initramfs*, /efi/vmlinuz*) since you no longer need them.
Nice. You simply performed the clean-up step before the remount, which is what I did at the time I was switching as well. That way it wouldn’t confuse users who choose /boot/ as the new mount point.
Nice tutorial; installed systemd-boot on arch. Just a question … Is it possible with timeshift to show the snaps during boot ?
Installed timeshift on cli arch with
yay -S --noconfirm timeshift timeshift-autosnap
.
The thing is with grub the snaps are shown during boot (grub-btrfs) and i like to know if this is also possible with systemd-boot.
I’ve successfully tried this tutorial on VM, and it works fine.
But when I try this on my laptop, the boot entries are somehow hidden. After 3 seconds, it automatically boots into the latest kernel.
