I would suggest creating a pre install script that finds the correct
boot device by querying all available devices until you find one
that meets your constraints. You can use either udevadm or try to
find some information directly in /sys.
i.e.
for i in /sys/block/[sv]d?
do
dev=$(basename $i)
# next if it's an usb device
if udevadm info --query=path --name=$dev | grep -q -e '/usb'
then
# Ignoring $dev since it's an usb device
continue
fi
# do something else
done
Cheers
Richard
On 02/01/2016 02:22 AM, Hajducko, Steven wrote:
> Can you speak more to that? I'm not understanding how that would
> work out. Doesn't the assignment of the label happen during the
> partition configuration - where as I need to know which disk is the
> first drive in the boot order before that ( so we can tell it that
> it has the / partition )
>
> This all needs to be done in a strictly automated fashion as well.
>
> From: <kickstart-list-bounces@xxxxxxxxxx
> <mailto:kickstart-list-bounces@xxxxxxxxxx>> on behalf of Andrew
> Simpson <simpsonar77@xxxxxxxxx <mailto:simpsonar77@xxxxxxxxx>>
> Reply-To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx
> <mailto:kickstart-list@xxxxxxxxxx>>
> Date: Sunday, January 31, 2016 at 5:10 PM
> To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx
> <mailto:kickstart-list@xxxxxxxxxx>>
> Subject: Re: Detecting boot drive
>
> have you thought about trying to find it by UUID or Label? I had a
> similar issue in a kickstart where I could not determine the boot
> drive while making a USB boot image. I ended up formatting the
> drives with a specific LABEL and using that in the kickstart instead
> of using sda/sdb/etc...
>
> Andrew Simpson
>
> On Fri, Jan 29, 2016 at 12:53 PM, Hajducko, Steven
> <Steven_Hajducko@xxxxxxxxxx <mailto:Steven_Hajducko@xxxxxxxxxx>> wrote:
>
> Is there a way to consistently detect the boot-drive, across
> multiple hardware platforms?
>
> We have several different hardware types - but it remains
> consistent that we always want the OS installed on the first
> drive in boot order. We played around with --on-bios-disk, but
> that doesn't always work ( it fails, for instance, on Dell
> R820's with the PERC RAID controller ). We've also tried
> specifying /dev/disk/by-id/edd-int13_dev80, which works on the
> Dell's, but fails on VMs. ( And then throw HP and it's cciss
> into the whole mix.. ). /dev/sda isn't always the boot disk -
> this happens to us with certain RAID configs like 1 logical
> drive and 8 JBOD's. The JBOD's get detected as /dev/sda-h and
> the RAID drive ( which is the boot drive ), ends up as /dev/sdi.
>
> Just curious if anyone else has come up with a solid way to
> always figure out what the boot drive is.
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx <mailto:Kickstart-list@xxxxxxxxxx>
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
--
/dev/null
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
