According to this commit, GRUB 2.02 no longer supports relative paths from set-default subvolumes. This is no issue in first place, as we control what the mount handler is doing.
The only confusing case is, when we use the setup dialog to initialize /active and afterwards manually delete the original /boot. GRUB continues to use the original /boot directory until we execute grub-mkconfig, which detects /active/boot correctly and changes the grub.cfg accordingly.
This also results in using the old kernel and initrd + hook from /boot.
We need to add a note to the setup dialog and to the install script to ask the user to re-install GRUB to the MBR and regenerate its config.
According to this commit, GRUB 2.02 no longer supports relative paths from set-default subvolumes. This is no issue in first place, as we control what the mount handler is doing.
The only confusing case is, when we use the setup dialog to initialize /active and afterwards manually delete the original /boot. GRUB continues to use the original /boot directory until we execute grub-mkconfig, which detects /active/boot correctly and changes the grub.cfg accordingly.
This also results in using the old kernel and initrd + hook from /boot.
We need to add a note to the setup dialog and to the install script to ask the user to re-install GRUB to the MBR and regenerate its config.