Comes in two patches. Behaviour is described in comment of 2/2 patch, and corresponds to 3) from https://www.redhat.com/archives/anaconda-devel-list/2009-July/msg00157.html I tested the patches for these configs: disks sda, sdb, sdc /boot: grub target: -> grub was installed on: sdb1 sda (MBR) sda sdb1 sdb1 sdb1 md0 (sda1+sdb1) sda (MBR) sda, sdb md0 (sda1+sdb1) md0 sda1, sdb1 md0 (sdb1+sdc1) sda (MBR) sda, sdb, sdc md0 (sdb1+sdc1) md0 sdb1, sdc1 without /boot partition, /: grub target: -> grub was installed on: md0 (sda1+sdb1) sda sda, sdb md0 (sda1+sdb1) md0 sda1, sdb1 all boot OK, but I didn't tested behaviour after disk removals much (I got grub> prompt in cases I tried) Note: - UI (grub target selection wording) should be perhaps fixed to reflect the changes - Update of grub should be fixed to reflect the changes: up to this patch (f11) boot=/dev/md0 we wrote into /etc/sysconfig/grub or grub.conf meant that bootloader was installed on mbrs, and after patching it would mean that it is on raid device (partitions). We use this value in upgradeGrub. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
