In kickstart, the 'bootloader' option does not obey the 'driveorder' parameter when pathes like /dev/disk/by-id/scsi-... are used

Solution Verified - Updated -

Issue

  • In kickstart, the 'bootloader' option does not obey the 'driveorder' parameter when pathes like '/dev/disk/by-id/scsi-...' are used
  • I kickstart a server. The system and the master boot record should be located on the SAN disk (with multipath) and the swap space should be located on the systems local disk. The boot controller order of the server BIOS is FC controller and then the Smart Array controller.

I start the installation with the following kernel parameters, so the smart array disk has always the name sda.

mpath rdloaddriver=hpsa,lpfc

The installation with my kickstart file is completed without error, but the master boot record is written to the wrong device. The following does not work as expected:

bootloader --location=mbr --driveorder=/dev/disk/by-id/scsi-3002112002fe500d0,sda

Environment

  • Red Hat Enterprise Linux (RHEL) 6
  • Minor release <=4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content