Attachment 2302 Details for Bug 5809 – Adventures in chainloading.

Adventures in chainloading.

previous.txt (text/plain), 1.89 KB, created by William Murphy on 2012-05-14 08:03:20 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: William Murphy

Created: 2012-05-14 08:03:20 CEST

Size: 1.89 KB

patch

obsolete

>This was my primary machine. Now only used for testing. 
>
>Before I set it up for testing, there were 3 sata drives installed
>sda, sdb, sdc along with an IDE DVD-RW. 
>
>Mageia1 (sda1), Mandriva 2010.2 (sda2) and a shared boot partition
>(sda3) had been installed for some time and were using grub from the
>Mageia1 install. The BIOS id for sda was correct and there were no
>bootable partitions on sdb or sdc, so errors in the device.map went
>unnoticed. 
>
>I agreed to test out the chainloader installer help for the doc team
>and decided to install Mageia2 (sdc1) and Debian (sdb1) which uses
>grub2. That didn't work, so I started installing bootloaders onto 
>separate mbr's and root partitions:
>
>Mageia1: sda, sda1
>Mageia2: sdc, sdc1
>Debian:  sdb, sdb2
>
>On the first attempt, the device.map for the Mageia1 menu (sda) didn't
>agree with BIOS, so chainloading to the Mageia2 menu (sdc1) tried to
>boot sdb1, which would have been otherwise uninvolved in all
>this. That failed. Chainloading to the Mageia2 menu (sdc) brought up
>the Debian menu (sdb). Chainloading from Mageia1 (sda) to the Debian
>menus (sdb and sdb2) both failed. 
>
>Using rescue, I tried to reinstall the Mageia2 grub. The device.map
>for Mageia2 was the same as Mageia1, so I ended up overwriting the
>Debian grub2 (sdb) and re-installed it on sdb1. Now chaining from the
>Mageia1 menu to the Debian menu brought up the Mageia2 menu in text
>mode and from that, only chainloading back into the Mageia1 menu was
>possible.
>
>The shell game continued until I switched sdb with sdc on both Mageia1
>and Mageia2's device.map's and reinstalled grub for both. The Debian
>grub2 device.map, using UUIDs, was correct.
>
>Chainloading between all the menu finally worked with both the
>instructions in the install docs and also using settings described in
>the grub info.
>
>A problem arises if mcc is used for either Mageia1 or Mageia2, since
>it seems to reorder the device.map to a broken state.

This was my primary machine. Now only used for testing. 

Before I set it up for testing, there were 3 sata drives installed
sda, sdb, sdc along with an IDE DVD-RW. 

Mageia1 (sda1), Mandriva 2010.2 (sda2) and a shared boot partition
(sda3) had been installed for some time and were using grub from the
Mageia1 install. The BIOS id for sda was correct and there were no
bootable partitions on sdb or sdc, so errors in the device.map went
unnoticed. 

I agreed to test out the chainloader installer help for the doc team
and decided to install Mageia2 (sdc1) and Debian (sdb1) which uses
grub2. That didn't work, so I started installing bootloaders onto 
separate mbr's and root partitions:

Mageia1: sda, sda1
Mageia2: sdc, sdc1
Debian:  sdb, sdb2

On the first attempt, the device.map for the Mageia1 menu (sda) didn't
agree with BIOS, so chainloading to the Mageia2 menu (sdc1) tried to
boot sdb1, which would have been otherwise uninvolved in all
this. That failed. Chainloading to the Mageia2 menu (sdc) brought up
the Debian menu (sdb). Chainloading from Mageia1 (sda) to the Debian
menus (sdb and sdb2) both failed. 

Using rescue, I tried to reinstall the Mageia2 grub. The device.map
for Mageia2 was the same as Mageia1, so I ended up overwriting the
Debian grub2 (sdb) and re-installed it on sdb1. Now chaining from the
Mageia1 menu to the Debian menu brought up the Mageia2 menu in text
mode and from that, only chainloading back into the Mageia1 menu was
possible.

The shell game continued until I switched sdb with sdc on both Mageia1
and Mageia2's device.map's and reinstalled grub for both. The Debian
grub2 device.map, using UUIDs, was correct.

Chainloading between all the menu finally worked with both the
instructions in the install docs and also using settings described in
the grub info.

A problem arises if mcc is used for either Mageia1 or Mageia2, since
it seems to reorder the device.map to a broken state.

Actions: View

Attachments on bug 5809: 2290 | 2298 | 2299 | 2300 | 2302 | 2323