This is happening again - Re: [Client boot to HD goes to memtest.](/topic/6301/client-boot-to-hd-goes-to-memtest)


  • Testers

    After updating to just before 6285 the booting to memtest instead of harddisk after the countdown problem has returned.

    The issue seems intermittent and not on all devices though.
    I tried changing from SANBOOT to EXIT but that made it so chainloading failed on hosts that were working.
    Switched it back and still having the issue. Still testing though.

    Additionally are these settings supposed to be persistent in the gui after saving? because they’re not…
    0_1455640461020_Capture.PNG

    I’m still troubleshooting as it doesn’t happen on every host. But upgrading to the latest trunk (6285) and rebooting to make sure any and all related services got restarted didn’t do the trick and nor did editing the EXIT method.

    My boot.php in the browser of a registered host looks like this

    #!ipxe
    set fog-ip 192.168.100.117
    set fog-webroot fog
    set boot-url http://${fog-ip}/${fog-webroot}
    cpuid --ext 29 && set arch x86_64 || set arch i386
    goto get_console
    :console_set
    colour --rgb 0x00567a 1 ||
    colour --rgb 0x00567a 2 ||
    colour --rgb 0x00567a 4 ||
    cpair --foreground 7 --background 2 2 ||
    goto MENU
    :alt_console
    cpair --background 0 1 ||
    cpair --background 1 2 ||
    goto MENU
    :get_console
    console --picture http://192.168.100.117/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
    :MENU
    menu
    colour --rgb 0xff0000 0 ||
    cpair --foreground 1 1 ||
    cpair --foreground 0 3 ||
    cpair --foreground 4 4 ||
    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.quickimage Quick Image
    item fog.multijoin Join Multicast Session
    item fog.sysinfo Client System Information (Compatibility)
    choose --default fog.local --timeout 3000 target && goto ${target}
    :fog.local || goto MENU
    :fog.memtest
    kernel memdisk iso raw
    initrd memtest.bin
    boot || goto MENU
    :fog.reginput
    kernel loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=192.168.100.117/fog/ conosoleblank=0 loglevel=4 mode=manreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.reg
    kernel loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=192.168.100.117/fog/ conosoleblank=0 loglevel=4 mode=autoreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.quickimage
    login
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username ${username}
    param password ${password}
    param qihost 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    :fog.multijoin
    login
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username ${username}
    param password ${password}
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    :fog.sysinfo
    kernel loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=192.168.100.117/fog/ conosoleblank=0 loglevel=4 mode=sysinfo
    imgfetch init_32.xz
    boot || goto MENU
    :bootme
    chain -ar http://192.168.100.117/fog/service/ipxe/boot.php##params ||
    goto MENU
    autoboot
    

    Thoughts?
    Thanks,
    -JJ


  • Testers

    @Tom-Elliott This is true, it is indeed fixed because Tom is the best


  • Senior Developer

    @Arrowhead-IT The issue where it was displaying the wrong regmenu item setting is now fixed.


  • Testers

    I switched to GRUB_FIRST_FOUND_WINDOWS exit type and it seems to be working now.
    However normal EXIT still caused a PXE chainloading failed error.
    Is this a bug others are getting or is this a configuration issue?


Log in to reply
 

339
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

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