bootloader command in kickstart

[Kun Huang]

Hi all

I have trouble with "--boot-drive=" and "--driveorder".

Backgroud is that I have 2 disks sda and sdb, and both has /boot as first
partition which 'should' be bootable. What will happen in following cases:

1. I use bootloader command but without any --boot-drive and --driveorder
. What will happen in sda and sdb

2. I use --driveorder=sda but no
 --boot-drive. What will happen on sdb?

Is the best usage "--driveorder=sda,sdb --boot-drive=sda,sdb"?

[David Lehman]

On Wed, 2013-11-20 at 14:46 +0800, Kun Huang wrote:
> Hi all
>
> I have trouble with "--boot-drive=" and "--driveorder".
>
> Backgroud is that I have 2 disks sda and sdb, and both has /boot as
> first partition which 'should' be bootable. What will happen in
> following cases:
> I use bootloader command but without any --boot-drive and
>
> --driveorder
> . What will happen in sda and sdb
> I use --driveorder=sda but no
>
> --boot-drive. What will happen on sdb?
>
> Is the best usage "--driveorder=sda,sdb --boot-drive=sda,sdb"?

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.
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Chris Lumens]

> > Is the best usage "--driveorder=sda,sdb --boot-drive=sda,sdb"?
>
> 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.

I have patched pykickstart to raise an error if this happens, and added
a test case for it too.

- Chris

[Kun Huang]

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

On Wed, Nov 20, 2013 at 11:02 PM, Chris Lumens  wrote:
> > > Is the best usage "--driveorder=sda,sdb --boot-drive=sda,sdb"?
> >
> > 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.
>
> I have patched pykickstart to raise an error if this happens, and added
> a test case for it too.
> Chris
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[David Lehman]

On Wed, 2013-11-20 at 23:32 +0800, Kun Huang wrote:
> 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

Anaconda will handle this regardless of your settings for boot-drive or
driveorder. If /boot is on an md mirror, we will install the bootloader
to the mbr of each member disk to provide a redundant boot setup. You
could safely omit both boot-drive and driveorder in your case, I think.

David

[Kun Huang]

On Wed, Nov 20, 2013 at 11:52 PM, David Lehman  wrote:
> On Wed, 2013-11-20 at 23:32 +0800, Kun Huang wrote:
> > 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
>
> Anaconda will handle this regardless of your settings for boot-drive or
> driveorder. If /boot is on an md mirror, we will install the bootloader
> to the mbr of each member disk to provide a redundant boot setup. You
> could safely omit both boot-drive and driveorder in your case, I think.

Does anaconda 13.21.195 handle this too?
> David
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[David Lehman]

On Thu, 2013-11-21 at 10:23 +0800, Kun Huang wrote:
> On Wed, Nov 20, 2013 at 11:52 PM, David Lehman 
> wrote:
>         On Wed, 2013-11-20 at 23:32 +0800, Kun Huang wrote:
>         > 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
>     Anaconda will handle this regardless of your settings for
>     boot-drive or
>     driveorder. If /boot is on an md mirror, we will install the
>     bootloader
>     to the mbr of each member disk to provide a redundant boot
>     setup. You
>     could safely omit both boot-drive and driveorder in your case,
>     I think.
>
>
> Does anaconda 13.21.195 handle this too?

It should -- yes.

[Kun Huang]

haha, thank you : )

On Fri, Nov 22, 2013 at 12:13 AM, David Lehman  wrote:
> On Thu, 2013-11-21 at 10:23 +0800, Kun Huang wrote:
> > On Wed, Nov 20, 2013 at 11:52 PM, David Lehman 
> > wrote:
> >         On Wed, 2013-11-20 at 23:32 +0800, Kun Huang wrote:
> >         > 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
> >     Anaconda will handle this regardless of your settings for
> >     boot-drive or
> >     driveorder. If /boot is on an md mirror, we will install the
> >     bootloader
> >     to the mbr of each member disk to provide a redundant boot
> >     setup. You
> >     could safely omit both boot-drive and driveorder in your case,
> >     I think.
> >
> >
> > Does anaconda 13.21.195 handle this too?
>
> It should -- yes.
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list