Problems with using-fog-to-pxe-boot-into-your-favorite-installer

  • Yes.

    the DVD is extracted to /images/os…
    The Kernel and init are in the tftpboot-path

    The kernel and init load when I select the Ubuntu Entry in my FOG Menu, but after that when Ubuntu seems to take over -> error.

  • Moderator

    @taspharel So you have the kernel and init in the /tftpboot/os/… path and the entire DVD in the /images/os/… path?

  • My fog ipxe menu item has the following parameters:

    kernel tftp://${fog-ip}/os/ubuntu/Desk17.10/vmlinuz.efi
    initrd tftp://${fog-ip}/os/ubuntu/Desk17.10/initrd.lz
    imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/ubuntu/Desk17.10/locale=de_AT.UTF-8 keyboard-configuration/layoutcode=de quiet splash ip=dhcp rw
    boot || goto MENU
  • Moderator


    Please post what you have for your fog ipxe menu configuration. The error basically means that the kernel doesn’t understand the virtual hard drive (initrd.lz)

  • Hi George1421.

    Thanks for the great tutorials.

    Two questions:

    Do you have an up to date tutorial for using SystemRescueCD (recent version is 5.2.2 i believe)

    And more pressing:

    When I follow your Ubuntu 17.10 Desktop instructions, everything works fine until I actually try to boot, when the boot process starts I get a Kernel panic:

    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)

    Then some more lines and at the end again the same error message.

    Any idea on what could be causing this?

    Edit: Just noticed that I used 17.10.1, not 17.10, will try with 17.10 and report back - aaand, there is no 17.10 “non-.1” on the official ubuntu download page 😞

  • This post is deleted!
  • Moderator

    @tmgard Ok thank you for the feed back. So I guess that ubuntu is in the same state as debian (not really suprised) where we need to use the netboot version of the inits and kernel to deploy. I’ll setup my test environment and confirm, then update the tutorial accordingly.

    Thank you for your feedback.

    the win7 way should work for you. You will need to setup samba on your fog server (see very last post in thread) to complete the install. OR you could use a windows server and just use the FOG server to deliver the winpe image to the target computers. You have a few options, when I wrote the tutorial, I made the decision to keep it all in FOG.

    1. it was having problems in booting with /init and would crash to busybox, when i then downloaded the netboot kernel it worked like a charm.

    2. i was scratching my head at this as well, but i could not for the life of me get nfs to work, i made a copy to /tftpboot/mswindows and it worked. i guess i did not read it was broken, but thanks for the info.

    3. ok will have to try the win7 way

    thanks for the quick response

  • Moderator

    Hey, I forked your question from the tutorial to avoid adding extra discussion in the thread (just trying to keep it clean). I’m going to create a document that references questions about the thread, because your feed back is important for when the wiki page is created.

    So first of all thank you.

    I’m interested because I setup each one, except where noted. I did test ubuntu installer as I documented it.

    So I have a few questions for you .

    1. Why didn’t you use vmlinuz and initrd from the installer disk? I know certain distros have a nfs based installer but ubuntu worked right out of the box. So I’m interested in why you had to use a different kernel.
    2. I’m a bit confused about nfs since that is a function of iPXE to transfer the files. I’m not sure why you needed to switch to tftp. When you switched to tftp you would have needed top copy the needed files from /images/os/mswindows/10-1607 to /tftpboot/mswindows/10-1607 since the different communication tools use different base directories.
    3. The win10 instructions are broken. Well they work to boot the recovery image, but the recovery image doesn’t have access to the wim files in the image. I need to get back to that thread, but the win7 process will work for remote installing win10. You need to boot into WinPE and then connect to the FOG server using cifs (windows SMB). And then execute the setup.exe from there.