What does one do in the new environment to run different versions of linux on different drives of a system. One system has f31 on sda and centos7 on sdb. With legacy grub I could call the boot of one system from the other and vice versa. No more. Switching drives in the bios no longer works. I can kludge things by putting the boot files from the centos7 system in the f31 boot and putting the boot stanza in the as a custom entry in grub.d along with the stanza for Windows. All the entries in /boot/1oader point to the f31 system. grubenv is only appropriate for f31.
Second system has f32 on sda and f31 on sdb. The f32 system is the only one that will boot. There are entries in /boot/loader for both. but only f32 will boot. Seems to be an issue on boot in the root versus boot in a boot partition.
Robert McBroom
On 8/27/20 5:01 PM, Robert McBroom via users wrote:
What does one do in the new environment to run different versions of linux on different drives of a system. One system has f31 on sda and centos7 on sdb. With legacy grub I could call the boot of one system from the other and vice versa. No more. Switching drives in the bios no longer works. I can kludge things by putting the boot files from the centos7 system in the f31 boot and putting the boot stanza in the as a custom entry in grub.d along with the stanza for Windows. All the entries in /boot/1oader point to the f31 system. grubenv is only appropriate for f31.
Boot a CentOS 6 live image and install GRUB legacy (assuming that your system is configured for legacy/BIOS boot). Totally deprecated, unsupported, politically incorrect, etc., etc., and far more functional than GRUB 2.
On 8/27/20 3:01 PM, Robert McBroom via users wrote:
Second system has f32 on sda and f31 on sdb. The f32 system is the only one that will boot. There are entries in /boot/loader for both. but only f32 will boot. Seems to be an issue on boot in the root versus boot in a boot partition.
UEFI or legacy boot?
You say there are entries in /boot/loader for both, but are they all in the same directory or two different /boot/loader directories? If this is a legacy boot, you should be able to chainload the other GRUB, but I'm not sure about UEFI. With either boot method you should be able to add an entry that loads the config file from the other GRUB.
On Thu, 27 Aug 2020 at 19:02, Robert McBroom via users < users@lists.fedoraproject.org> wrote:
What does one do in the new environment to run different versions of linux on different drives of a system. One system has f31 on sda and centos7 on sdb. With legacy grub I could call the boot of one system from the other and vice versa. No more. Switching drives in the bios no longer works. I can kludge things by putting the boot files from the centos7 system in the f31 boot and putting the boot stanza in the as a custom entry in grub.d along with the stanza for Windows. All the entries in /boot/1oader point to the f31 system. grubenv is only appropriate for f31.
Second system has f32 on sda and f31 on sdb. The f32 system is the only one that will boot. There are entries in /boot/loader for both. but only f32 will boot. Seems to be an issue on boot in the root versus boot in a boot partition.
There are boot managers for UEFI, https://rodsbooks.com/refind/ is one example that I have used (but not with the latest incarnation of grub2).
On 8/28/20 2:15 PM, Samuel Sieb wrote:
On 8/27/20 3:01 PM, Robert McBroom via users wrote:
Second system has f32 on sda and f31 on sdb.?? The f32 system is the only one that will boot. There are entries in /boot/loader for both. but only f32 will boot.?? Seems to be an issue on boot in the root versus boot in a boot partition.
UEFI or legacy boot?
You say there are entries in /boot/loader for both, but are they all in the same directory or two different /boot/loader directories??? If this is a legacy boot, you should be able to chainload the other GRUB, but I'm not sure about UEFI.?? With either boot method you should be able to add an entry that loads the config file from the other GRUB. ___________________________________________
Pre UEFI bios systems. Used chainload with grub for a long time but missing something to do it with grub2. The configurations in /boot/loader previously had the UUID for the root partition in the kernel line but lately that is not the case. Can get?? boot of the other install to work by using the old grub2 description in a custom file in /etc/grub.d
-
George N. White III -
Ian Pilcher -
Robert McBroom -
Samuel Sieb