Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • EFI KickStart + grub (partition) in versions 6.x

    Posted on

    I have come across an issue when working with Kickstarting EFI based systems. It seems grub (despite using the manual regarding the bootloader option) is not installing correctly as I must manually specify the bootable EFI partition post installation.

    This is what I am using for the kickstart option;

    bootloader --location=partition --driveorder=sda --append="rhgb quiet crashkernel=512M audit=1"
    

    When examining the disk I am unable to locate the traditional grub information.

    It is a valid GPT EFI partition according to parted;

    $ parted -sl | less
    Model: VMware, VMware Virtual S (scsi)
    Disk /dev/sda: 21.5GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    
    Number  Start   End     Size    File system  Name  Flags
     1      1049kB  525MB   524MB   fat16              boot
     2      525MB   1050MB  524MB   ext4
     3      1050MB  21.5GB  20.4GB                     lvm
    

    As you can see there is no grub information found

    $ dd if=/dev/sda1 bs=1 count=512 | xxd
    0000000: eb3c 906d 6b64 6f73 6673 0000 0210 1000  ..mkdosfs......
    0000010: 0200 0200 00f8 0001 3f00 ff00 0000 0000  ........?.......
    0000020: 00a0 0f00 0000 293f c4e8 1820 2020 2020  ......)?...     
    0000030: 2020 2020 2020 4641 5431 3620 2020 0e1f        FAT16   ..
    0000040: be5b 7cac 22c0 740b 56b4 0ebb 0700 cd10  .[|.".t.V.......
    0000050: 5eeb f032 e4cd 16cd 19eb fe54 6869 7320  ^..2.......This 
    0000060: 6973 206e 6f74 2061 2062 6f6f 7461 626c  is not a bootabl
    0000070: 6520 6469 736b 2e20 2050 6c65 6173 6520  e disk.  Please 
    0000080: 696e 7365 7274 2061 2062 6f6f 7461 626c  insert a bootabl
    0000090: 6520 666c 6f70 7079 2061 6e64 0d0a 7072  e floppy and..pr
    00000a0: 6573 7320 616e 7920 6b65 7920 746f 2074  ess any key to t
    00000b0: 7279 2061 6761 696e 202e 2e2e 200d 0a00  ry again ... ...
    00000c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    00000d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    00000e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    00000f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000100: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000110: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000120: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000130: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000140: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000150: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000160: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000170: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000180: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    0000190: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    00001a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
    512+0 records in
    512+0 records out
    512 bytes (512 B) copied, 0.00136578 s, 375 kB/s
    

    If I manually step through the BIOS to locate the grub.efi file I can boot the system. Am I just assuming that EFI will simply load the OS like the older 8086 BIOS ROM code?

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat