Hi David
I think my case is a little special. In my case, we build raid 1 on the first partition, which is /boot, of all disks, for example sda1 and sdb1. And we expected we can boot OS from any disk. (/ is on raid too) This is for the reason that we could still boot system after losing any disk.
But I build raid 1 for partitions, and the MBR isn't in it. So I try to use driverorder or boot-drive
I think my case is a little special. In my case, we build raid 1 on the first partition, which is /boot, of all disks, for example sda1 and sdb1. And we expected we can boot OS from any disk. (/ is on raid too) This is for the reason that we could still boot system after losing any disk.
But I build raid 1 for partitions, and the MBR isn't in it. So I try to use driverorder or boot-drive
On Wed, Nov 20, 2013 at 11:02 PM, Chris Lumens <clumens@xxxxxxxxxx> wrote:
> > Is the best usage "--driveorder=sda,sdb --boot-drive=sda,sdb"?I have patched pykickstart to raise an error if this happens, and added
>
> The best usage is to not use driveorder at all. boot-drive only takes
> one argument and that is the drive the OS you are currently installing
> will boot from.
a test case for it too.
- Chris
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
