iPXE problems ... Could not start download: Operationn not supported



  • I’m getting an error when booting my clients. Running fog 1.2 on Ubuntu server 13.1. When the clients boot, they get the error message "Could not start download: Operation not supported (http://ipxe.org/3c092003). Using Windows 2012 DHCP server. Options 66 and 67 set.

    I feel like I’ve tried EVERYTHING!. I’ve verified that I can TFTP the file undionly.kpxe. There is a firewall, but nothing in-line between the clients and the fog server. I’ve checked permissions on the /tftpboot directory and /var/www/fog/service/ipxe directory.

    I can view the boot.php file (results posted below)

    Any help would be greatly appreciated!

    #!ipxe
    cpuid --ext 29 && set arch x86_64 || set arch i386
    colour --rgb 0xff6600 2
    cpair --foreground 7 --background 2 2
    console --picture http://10.50.0.48/fog/service/ipxe/bg.png --left 100 --right 80
    :MENU
    menu
    colour --rgb 0xff0000 0
    cpair --foreground 0 3
    item --gap Host is NOT registered!
    item --gap -- -------------------------------------
    item fog.local Boot from hard disk
    item fog.memtest Run Memtest86+
    item fog.reginput Perform Full Host Registration and Inventory
    item fog.reg Quick Registration and Inventory
    item fog.sysinfo Client System Information (Compatibility)
    choose --default fog.local --timeout 3000 target && goto ${target}
    :fog.local
    chain -ar http://10.50.0.48/fog/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
    :fog.memtest
    kernel memdisk iso raw
    initrd memtest.bin
    boot || goto MENU
    :fog.reginput
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.50.0.30 keymap= web=10.50.0.48/fog/ consoleblank=0 loglevel=4 mode=manreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.reg
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.50.0.30 keymap= web=10.50.0.48/fog/ consoleblank=0 loglevel=4 mode=autoreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.sysinfo
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.50.0.30 keymap= web=10.50.0.48/fog/ consoleblank=0 loglevel=4 mode=sysinfo
    imgfetch init_32.xz
    boot || goto MENU
    autoboot
    

    0_1451494846060_iPXE error.docx



  • Go to https://rom-o-matic.eu

    Click the drop down and choose
    UNDI only (.kpxe)

    Paste this script into the script box:

    #!ipxe
    
    dhcp
    cpuid --ext 29 && set arch x86_64 || set arch i386
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param product ${product}
    param manufacturer ${product}
    param ipxever ${version}
    param filename ${filename}
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    :bootme
    chain http://10.50.0.48/fog/service/ipxe/boot.php##params
    

    Click Proceed, save the new undionly.kpxe, transfer it to your FOG server’s /tftpboot and give it another whirl.


  • Moderator

    I’m sorry I missed this earlier today.

    I see the version you are using so that’s good. Is this a new FOG install or something that had worked in the past and now its broken?

    If you are getting to the FOG iPXE menu then the pxe booting process is working as expected, but it appears from the error it appears that its not getting that far.

    So far from the error I can see its PXE booting and downloaded the undionly.kpxe file, because that is clearly visible in your attachment. Where it is failing is chaining to the http://<fog_server_ip>/fog/service/ipxe/boot.php file.

    In regards to the target computer you are trying to boot, since you are telling the client to download the undionly.kpxe file your is your target computer configured for BIOS and not uefi/secure boot?

    And finally what is the make and model of the target computer generating this error message?


Log in to reply
 

481
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.