Hello guys,
i recently installed volumio on a different drive on my pc alongside EndeavourOs. So if i just want to listen to music, i can start volumio and do so without distraction. It is volumio for x86 systems and it is based on debian and as far as i know it uses GRUB. On EOS (different drive) im using systemd-boot, fully encrypted with LUKS.
So, now i’m mighty confused, how to do this. At first i thought, that should be an easy task. But it seems, it is not, because it is on another physical drive and has another ESP.
The arch wiki has a an article for this kind of problem: https://wiki.archlinux.org/title/Systemd-boot#Boot_from_another_disk
But, to be honest, i dont really understand, what i have to do. Can sb point me in the right direction, what to do at first?
If you want to stick with systemd-boot, both installations should share the same EFI partition.
But that brings the hassle, that you would need to copy one of the kernels either of EOS or debian (volumio) manually into the shared EFI partition and edit/create the configuration files under “/boot/loader/entries/”. One for each installation i.e. “eos.conf” and “volumio.conf”.
You would have to repeat copying the kernel into the right partition every time you update the system to another/updated kernel.
In addition you should modify the “/boot/loader/loader.conf” to point to default boot entry configuration.
I personally wouldn’t recommend this.
It would be much easier and straight forward to simply use grub (with os-prober) for this kind of task.
After installing grub with os-prober enabled in EOS, you could then simply mount your volumio (debian) root partition to /mnt once and generate a new grub configuration file. You may have to repeat generating the config file, when updating volumios kernel.
Perhaps rEFInd could be an option too, it should be able to handle this full–auto, if I remember correctly.
Full disk encryption might cause some trouble in this case.
Thanks for your help, my friend. But i changed the plan, because it seems to be too difficult. I will use mpd now as music-server. But i want to do this in a second EOS install on the same disk.
First EOS as my main system, fully encrypted, second EOS as my music-box and entertainment-system without Encryption.
It did work quite allright. I installed EOS on a seperate Partition on the same SSD, copied the kernel images to the shared ESP and created the loader-entries. The only strange thing happening right now, is that the second install requires the LUKS-Key from my main System.