• @george1421

    No worries, its understandable. The target host is ubuntu server 18.04.5 and below is the output showing the existence of the /sys/fimware/efi directory.

    ls -la /sys/firmware
    total 0
    drwxr-xr-x 6 root root 0 Oct 21 17:07 .
    dr-xr-xr-x 13 root root 0 Oct 21 17:06 …
    drwxr-xr-x 6 root root 0 Oct 21 17:06 acpi
    drwxr-xr-x 3 root root 0 Oct 21 17:07 dmi
    drwxr-xr-x 6 root root 0 Oct 21 17:06 efi
    drwxr-xr-x 23 root root 0 Oct 21 17:07 memmap

  • Moderator

    @george1421 In the refind.conf (/var/www/html/fog/service/ipxe/refind.conf) There is settings
    scanfor internal,external,optical,manual make sure that is set.

    You might want to see if uncommenting helps uefi_deep_legacy_scan

    We have also seen some disks need a little settling time so setting scan_delay 5 may help.

    I may spin up a efi ubuntu system to see if I can get it to detect at leas on a VM. Ubuntu 20.04 may do things a new way.

    Also surely try @JJ-Fullmer suggestion too by rolling refind back to 0.11.0 that has also helped with some mobos. I would recommend that you don’t try everything all at once

  • Moderator

    @wmw509 Sorry to keep laboring the point but knowing what mode is helpful for debugging.

    If you have one of these systems booted into linux a quick check is this. ls -la /sys/firmware/efi if that file exists then its uefi boot.

    And your target OS is ubuntu 20.04?


  • @george1421

    I believe it is a UEFI system, I checked from the OS when I booted into linux. Its just a spare desktop I had laying around. Specs below, Let me know if there is any other info I can provide.

    ASRock H110 Motherboard with and Intel 1151 socket CPU with 8gb DDR4

  • Testers

    I would try switching the refind binary to version 0.11.0.

    I just posted how to do this in this forum post https://forums.fogproject.org/topic/14850/refind-not-working-properly

    I would then use the default efi REFIND_EFI exit type and it will likely do the trick.

    Hope that helps.

  • Moderator

    @wmw509 So this is a uefi based system then? If so what model computer?


  • @george1421

    This morning I was able to test those settings (I tested with these settings on the host specifically and just as global settings) however I am still not able to boot.

    When the fog menu exits and attempts to boot from the hard drive it hangs with a blinking cursor in the top left corner. If I change boot priorities the host image boots as expected. Any other settings I could be missing or information I can provide?


  • @george1421
    Thank you for the reply!

    I will make those changes and give it a test first thing in the morning. I also found “Boot Exit Type” settings under Fog Settings > Fog Boot Settings, should these be configured the same?

    The target systems are UEFI, right now I am just trying to boot a completely stock ubuntu server image to try and get familiar with fog.

  • Moderator

    There are two exit modes one for bios and one for uefi. Make sure you set the global settings to SANBOOT for bios and rEFInd for efi.

    Now for bios SANBOOT works 99% of the time. For UEFI refind works (out of the box) about 90% of the time. Refind does a pretty good job of finding the EFI boot partition. You many need to tweak the refind.conf settings to have it search more locations.

    So are these target system, uefi? What target OS are you trying to boot?

322
Online

8.4k
Users

15.2k
Topics

142.6k
Posts