Boot Menu & ISO File Size?



  • Hey guys :)

    Alright so I have my Fog server running on a old Dell computer with p4 pox / 2GB RAM / 300GB HDD / CentOS minimal 6.6 32bit FOG: v1.2.0 I just started editing the boot menu to addon some .ISO files to boot from an some are seen and same are not, like “clonezilla-live-2.3.1-18-i686-pae.iso” is seen and will load but if I try to use “BT5R3-GNOME-32.iso” I see an error flash for 0.1 sec saying something like file can not be found, I was reading on HERE (the forum) that some times the name can be an issue with this so I made a test ISO by using clonezilla got it to boot and then renamed the ISO file BT5R3 to clonezilla so I never moved the ISO’s or anything like that BUT it was a fail still the same error… Is there a set size the ISO file can be or something along them lines?

    My boot menu (I know it could be better)

    :MENU
    menu
    item --gap -- ---------------- iPXE boot menu ----------------
    item clonezilla-live    clonezilla-live-2.3.1-18
    item BT5R3-GNOME    BT5R3-GNOME-32
    item shell          ipxe shell
    item return        return to previous menu
    choose --default WIN7PE64BIT --timeout 5000 target && goto ${target}
     
    :clonezilla-live
    initrd http://${fog-ip}/iso/clonezilla-live-2.3.1-18-i686-pae.iso
    chain memdisk iso raw ||
    goto MENU
     
    :BT5R3-GNOME
    initrd http://${fog-ip}/iso/BT5R3-GNOME-32.iso
    chain memdisk iso raw ||
    goto MENU
     
    :ipxedemo
    chain http://boot.ipxe.org/demo/boot.php ||
    goto MENU
     
    :shell
    shell ||
    goto MENU
     
    :return
    chain  http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
    prompt
    goto MENU
     
    autoboot
    


  • http://fogproject.org/forum/threads/pxe-boot-problems-after-install-fog-1-0-0-on-ubuntu-dhcp-server.10478/[/quote]

    Thanks man but its not a PXE boot problem or DHCP server issue seeing to as I am not using FOG’s for DHCP & I’m not running Ubuntu (EWW & WTF lol)

    :D







  • @Tom Elliott, post: 42322, member: 7271 said:

    You got the same error if you change the clonezilla to BT5R3-GNOME-32.iso and boot from that menu as you got using the “real” BT5R3-GNOME-32.iso?

    Nope. If I rename the “real” clonezilla to BT5R3-GNOME-32.iso it works so it is not the name if that was the point in that test?!


  • Developer

    i found some instructions for setting up that version of backtrace for network booting over a mounted NFS volume using pxelinux. the instructions should be a good clue on what you could do with ipxe http://www.gtkdb.de/index_7_1786.html



  • @Tom Elliott, post: 42322, member: 7271 said:

    From what I’m gathering, it’s not a filesize issue. Rather the way the iso’s are being booted. You could add a pause or prompt to the menu to have it wait for your entry on failure.

    How do I add a pause or prompt to the menu to have it wait for entry on failure?

    @Tom Elliott, post: 42322, member: 7271 said:

    You got the same error if you change the clonezilla to BT5R3-GNOME-32.iso and boot from that menu as you got using the “real” BT5R3-GNOME-32.iso?

    … Hold on let me try that real fast…

    (Do note I dum down the names for testing to see if I can get it to work this is why they are not the same in the menu as posted up there…)

    What they are on my server.
    ""


  • Senior Developer

    @fmslick, post: 42321, member: 27446 said:

    Thanks Junkhacker for the info and yes Linux is case sensitive, however I don’t think this is the issue I am having here do to I was thinking that the name’s I had for the ISO file may have been the issue so this is why I renamed the “BT5R3-GNOME-32.iso” to “clonezilla” and the REAL clonezilla ISO to “clonezilla_.iso” seeing to as I know the real clonezilla.iso file would boot via from Fog and over my network but the rename however failed. So I try to use other ISO’z but they to fail, this led me to believe that it is maybe a file size issue?!?!o_O

    From what I’m gathering, it’s not a filesize issue. Rather the way the iso’s are being booted. You could add a pause or prompt to the menu to have it wait for your entry on failure.

    Also, not all disks work with chain memdisk iso raw. Some will work with chain memdisk iso, some will work with chain memdisk, some will work with chain raw. I don’t think this is the issue though.

    You got the same error if you change the clonezilla to BT5R3-GNOME-32.iso and boot from that menu as you got using the “real” BT5R3-GNOME-32.iso?



  • @Junkhacker, post: 42303, member: 21583 said:

    the biggest issue with names that people have is that they forget that Linux filenames and paths are case sensitive

    Thanks Junkhacker for the info and yes Linux is case sensitive, however I don’t think this is the issue I am having here do to I was thinking that the name’s I had for the ISO file may have been the issue so this is why I renamed the “BT5R3-GNOME-32.iso” to “clonezilla” and the REAL clonezilla ISO to “clonezilla_.iso” seeing to as I know the real clonezilla.iso file would boot via from Fog and over my network but the rename however failed. So I try to use other ISO’z but they to fail, this led me to believe that it is maybe a file size issue?!?!o_O


  • Developer

    the biggest issue with names that people have is that they forget that Linux filenames and paths are case sensitive


Log in to reply
 

349
Online

38746
Users

10569
Topics

100052
Posts

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