Menu

Setting up PXE

Help
2010-10-06
2014-04-21
  • Ben Stonehouse

    Ben Stonehouse - 2010-10-06

    Hi Guy

    I’m having a little problem getting clonezilla to boot from PXE correctly.

    I have been messing for awhile and I’m using a mixture of my windows 2000 servers DHCP and a program called Tftpd32.

    I have successfully got the PXE working by using this web site and got it to boot to its main menu.

    http://www.lockstockmods.net/2008/05/26/easy-way-to-pxe-boot-windows/

    The problem I’m having is with the doc (Clonezilla Live with PXE Server) on the clonezilla.org web site.

    1. Prepare a PXE server. You may refer to some doc, e.g. this one or DRBL (Diskless Remote Boot in Linux). We assume the pxelinux config file is /tftpboot/nbi_img/pxelinux.cfg/default, and the image files are in /tftpboot/nbi_img/.

    I have looked and the docs and its all done in linux and I don’t have a clue, I have searched around the net and can’t find anything to help me.

    Any help would be great

     
  • Steven Shiau

    Steven Shiau - 2010-10-13

    Personally I am not familiar with MS windows services of dhcpd and tftpd. If anyone on the forum has such an experience, please share.
    Thanks.

    Steven.

     
  • Jim Silva

    Jim Silva - 2010-11-18

    Updating Clonezilla Live and PXELinux kernel

    TFTP directory (for us C:\PXEBoot
    Currently using Clonezilla 1.2.5.35 i486 and PXE from Syslinux 4.03

    I. Download Clonezilla{version}i486.zip or .686 determined by client that is being booted.
    (http://clonezilla.org/download/sourceforge/stable/iso-zip-files.php )
         Extract files from zip (really don't use many!)

    A. You need  -vmlinuz, initrd.img, and filesystem.squashfs- from the  live directory of zip distribution
    1. It is placed in the C:\PXEBoot\  directory (root)

    B. You also need the - syslinux.cfg - file from the syslinux directory from Clonezilla distribution
    1. It is placed in the C:\PXEBoot\pxelinux.cfg\ directory along with the default file used by the
        Menu
    II. Download newest syslinux distribution ( http://syslinux.zytor.com/wiki/index.php/Download )

    A. You need the - gpxelinux.0 - file from the gpxe directory
    1. It is placed in the C:\PXEBoot\ directory (root)

    Command line parameters for menu (default file - in our case C:\PXEBoot\pxelinux.cfg\default).

    (below is the menu's booting command so be sure the files you copied above match
    i.e.,  vmzlinuz1 not vmzlinuz (just rename)  - &  - initrd1.img not intrd.img - )
    (Also enter your PXE / TFTP servers IP Address at the fetch= line)

    label Clonezilla Live
    MENU LABEL Clonezilla Live
    kernel vmlinuz1
    append initrd=initrd1.img boot=live live-config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=788 nosplash fetch=tftp://192.168.x.x/filesystem.squashfs

    for some reason I also have a simple file named - f1.msg -  in the PXEboot root directory. In here I have the menu that is displayed. About halfway down the page of the file …

    |---| Boot Options |---------|
    |                                                   |
    | 1. Clonezilla Menu           |
    | 2. Duplicate 1          |
    | 3. From 25.35                        |
    |                                            |
    |-------------------------|

    <F1> Main | <F2> Help
    Default image will boot in 30 seconds…

    and my - default - file looks like this:

    default 1
    timeout 6000
    prompt 1
    display f1.msg
    F1 f1.msg
    F2 f2.msg

    label 1
    kernel vmlinuz1
    append initrd=initrd1.img boot=live live-config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_keymap="NONE" ocs_live_batch="no" ocs_lang="en_US.UTF-8" vga=788 nosplash fetch=tftp://192.168.x.x/filesystem.squashfs ocs_numlk="on"

    As shown above I am using 1.2.5.35 as both the 1.2.6.xx version don't seem to have the filesystem.squashfs support.
    I will be posting for help on this issue.

    Hope this helps. I have been using Clonezilla live for over a year - The version previous to this (although I think it was mainly the gpxelinux.0 file that needed updating) was having trouble completing the boot with INTEL PXE 1.3.51 but the older 1.2.51 worked - had to swap a NIC into the computer when I need to image / reimage.

    Hope this helps - It is truly a great utility!

    BTW I used the SourceForge document to setup the PXE / DHCP services
    http://unattended.sourceforge.net/pxe-win2k.html

     
  • Troye Johnson

    Troye Johnson - 2010-11-26

    Jnsilva1 Could you elaborate more on this topic like what tftp server did you use I am using tftp32 and I can not find where to enter the menu's booting command to get this to work.

     
  • frust

    frust - 2014-04-18

    google translater out of order sorry

    Funktioniert nicht.
    Windows XP und TFTP32

    Ob Acronis, UBCD oder Memtest etc. alles wird gestartet nur Clonezilla nicht.
    vmlinuz umbenannt mit 1 war auch nicht hilfreich.
    Vom USB Stick zu starten, kein thema, aber wir möchten gerne von den Sticks weg und folge dessen dachten wir so schwer kann es ja nicht sein.
    falsch gedacht. echt klasse freeware das clonezilla, aber völlig pxe inkompatibel wenn man nicht mit linux fährt. vielleicht weiss ja einer von euch weiter.

    gekürzte Ordnerstruktur
    C:\tftpd\amd64
    C:\tftpd\pxelinux.cfg
    C:\tftpd\i486
    C:\tftpd\i686pae
    C:\tftpd\ubcd
    C:\tftpd\menu
    C:\tftpd\mtools
    C:\tftpd\pxelinux.0
    C:\tftpd\memdisk
    C:\tftpd\menu.c32
    C:\tftpd\amd64\filesystem.packages
    C:\tftpd\amd64\filesystem.packages-remove
    C:\tftpd\amd64\filesystem.squashfs
    C:\tftpd\amd64\freedos.img
    C:\tftpd\amd64\initrd.img
    C:\tftpd\amd64\ipxe.lkn
    C:\tftpd\amd64\memtest
    C:\tftpd\amd64\vmlinuz
    C:\tftpd\i486\filesystem.packages
    C:\tftpd\i486\filesystem.packages-remove
    C:\tftpd\i486\filesystem.squashfs
    C:\tftpd\i486\freedos.img
    C:\tftpd\i486\initrd.img
    C:\tftpd\i486\ipxe.lkn
    C:\tftpd\i486\memtest
    C:\tftpd\i486\vmlinuz
    C:\tftpd\i686pae\filesystem.packages
    C:\tftpd\i686pae\filesystem.packages-remove
    C:\tftpd\i686pae\filesystem.squashfs
    C:\tftpd\i686pae\freedos.img
    C:\tftpd\i686pae\initrd.img
    C:\tftpd\i686pae\ipxe.lkn
    C:\tftpd\i686pae\memtest
    C:\tftpd\i686pae\vmlinuz
    C:\tftpd\menu\amd64.cfg
    C:\tftpd\menu\chain.c32
    C:\tftpd\menu\dban.cfg
    C:\tftpd\menu\default.cfg
    C:\tftpd\menu\i486.cfg
    C:\tftpd\menu\memdisk
    C:\tftpd\menu\menu.c32
    C:\tftpd\menu\vesamenu.c32

    Test Auszug aus der i486.cfg
    label ..
    MENU LABEL Clonezilla Live (Ramdisk)i486
    KERNEL vmlinuz1
    APPEND initrd=initrd1.img boot=live config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch="no" locales=de_DE.UTF-8 keyboard-layouts=de vga=788 nosplash noprompt fetch=tftp://192.168.225.10/filesystem.squashfs

    label ..
    MENU LABEL Clonezilla Live (Ramdisk)i486
    KERNEL i486/vmlinuz
    APPEND initrd=/i486/initrd.img boot=live config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch="no" locales=de_DE.UTF-8 keyboard-layouts=de vga=788 nosplash noprompt fetch=tftp://192.168.225.10/i486/filesystem.squashfs

    bei beiden der gleiche fehler zum schluss.
    entweder versucht clonezilla nochmals eine IP vom DHCP zu erhalten was der natürlich als völlig indiskutabel ignoriert, weil auf einer NIC kann man keine 2 offers bekommen. oder clonezilla ... ich schreibe die fehler mal ab.

    Clonezilla über PXE
    "Waiting for ethernet card(s) up ... If Fails, maybe the ethernet card is not supported by the kernel 3.13-1-486?"

    Im Windows XP - Progamm TFTPD32
    zu dem zeitpunkt erhällt der DHCP vom TFTPD32 eine zweite aufforderrung dem soeben über PXE IP erhaltenden rechner eine zweite zu geben.

    Clonezilla über PXE
    "using timeout of 15 seconds for network configuration."

    Selbst wenn da 100 Jahre stehen würden, eine Verbindung zwischen den beiden existiert, eine IP hat der Rechner schon erhalten, ergo besteht die verbindung und wird von keinem mir bekannten DHCP unterbrochen werden weil der Rechner nochmals eine IP haben möchte. Oder irre ich da ? egal.

    Clonezilla über PXE
    "/bin/sh: cant access tty: job control turned off"
    "(initramfs) IP-Config: eth0 hardware address mac adr. mtu 1500 DHCP RARP"
    "IP-Config: no responce after 15 secs - giving up"
    "Creating /etc/resolv.conf"
    "Begin: Trying tftp -g -b 65464 -r /filesystem.squashfs -l /live/medium/live/filesystem.squashfs 192.168.225.10 . . . tftp: sendto: network is unreachable"
    "unable to find a live file system on the network"
    "modprobe: module ehci.orion not found in modules.dep"

    ach und ich habe es auch mit einem ftp anstatt fetch probiert, per ftp programm sofort verbunden, user bzw. auch über http, egal bei wem und wo, sofort verbunden, nur über pxe clonezilla , keine chance.

    irgendwer eine idee ?

     
  • Fuchs

    Fuchs - 2014-04-19

    A short answer:
    Do not use so many systems simultaneously. There is not a dos system with commands step by step (e.g. Memtest).

    Obviously here it will be load 2 systems (or more).
    These systems are using message commands with priorities in windows, linux and sometimes programs with equal names of different directories.

    The best method is to separate: Use USB sticks (amd, i486, i686pae)
    or
    different partitions for the different clonezilla versions
    with bootfrom=/dev/sdb1 ../sdb2 ../sdb3 or so in the syslinux.cfg, grub.cfg
    to load the right 'filesystem.squashfs' and other files.

    That's the main thing in this case.
    Delete all other unnecessary files.

    Fuchs

     
  • frust

    frust - 2014-04-20

    i do it.
    i delete all other tools etc. only i486 on the tftpd but the errors are the same.

    and now ?

     
  • frust

    frust - 2014-04-20

    i find the error. physical error it was, you need a physical router, only a switch not works.

    done it work.

    i486
    amd64
    i686pae

    and many more. fine thx

     
  • Fuchs

    Fuchs - 2014-04-21

    It's very fine.
    Thank you for the information.

    Fuchs

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.