-
@george1421 excelent guide, all the linux guides was very good, had some problems with ubuntu because i did not use the vmlinuz and initrd from “http://archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/” which might be nice to have in the guide.
also:
im not sure if i have done something wrong following your Windows 10 guide, but i manage to boot into windows, but dont get past some driver issues in windows “A media driver your computer needs is missin. i also had to use tftp instead of nfs, because it was not supported… do you know whats going on hereg” -
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 .
- 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.
- 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.
- 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.
-
-
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.
-
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.
-
ok will have to try the win7 way
thanks for the quick response
-
-
@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.
-
This post is deleted! -
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
-
@taspharel
ref: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/11Please 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)
-
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 -
@taspharel So you have the kernel and init in the /tftpboot/os/… path and the entire DVD in the /images/os/… path?
-
Yes.
the DVD is extracted to /images/os…
The Kernel and init are in the tftpboot-pathThe kernel and init load when I select the Ubuntu Entry in my FOG Menu, but after that when Ubuntu seems to take over -> error.
-
I seem to have a similar problem when trying to run System Rescue Disk via PXE. Also something about not finding root or along those lines.
Will try booting on another machine to make sure that its not related to the Lenovo Laptop I am using …
-
@taspharel What are you having issues with, with SystemRescueCD? I just downloaded the ISO and you should be able to extract it and make it boot via pxe. There is a kernel file and an initrd file.
I’m currently in the process of downloading ubuntu desktop 17.10.1 to see if there is a difference.
-
@george1421 Hey, re: our pm’s with winpe and UEFI, I am still having trouble. Let me know if you would rather I create a new post for my issue or if its ok to carry on here.
kernel http://${fog-ip}/fog/os/win/wimboot gui initrd --name BCD http://${fog-ip}/fog/os/win/winpe/am64/media/Boot/BCD BCD initrd --name boot.sdi http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/boot.sdi boot.sdi initrd --name boot.wim http://${fog-ip}/fog/os/win/winpe/amd64/media/sources/boot.wim boot.wim boot || goto MENUIt loads the files, has about a dozen lines about patching the WIM file, says its loading ‘bootx64.efi’ and then just reboots (machine makes a single beep). It never gets to loading the winpe environment. BIOS it boots fine and moves on to winpe.
I tried with/without:
- ‘gui’ (on the kernel line)
- ‘pause’ (on kernel line)
- ‘rawbcd’ (on gui line)
None of the above changed anything. I also rebuilt my winpe files using copype amd64 /path and still had same issue. When re-creating (using copype) I didnt even bother adding the commands to connect to network and run installer.
I have seen others add 4 lines for fonts, I am going to give that a shot too. I also am searching for another viable test box to ensure its not just the specific hardware I am using.
I am running copype on a Windows Server 2016 box with newest MDT and ADK. wimboot is latest, 2.6.0 I think (on FOG machine).
Any help would be awesome, Thanks!
EDIT: ok must be something about the Dell Precision Tower 3620. UEFI boot worked on an R620. I even added the latest Dell Winpe 10 drivers to the boot.wim and still get the crash when UEFI booting. Still could use a solution, but it may end up just being that this specific model is allergic to ipxe/winpe
-
@zer0cool said in Problems with using-fog-to-pxe-boot-into-your-favorite-installer:
http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/boot.sdi boot.sdi
This is a risky path to place your files in. At the very least I would move them out of the /var/www/html/fog directory. The fog installer has been known to remove unexpected files in its path. My instructions suggest to use tftp protocol for testing.
-
@george1421 I symlinked my /tftpboot to var/www/html/fog/ so that everything i do under tftpboot in the os folder is available via http.
Turns out this works…
kernel http://${fog-ip}/fog/os/win/wimboot pause gui initrd --name segmono_boot.ttf http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf initrd --name segoe_slboot.ttf http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf initrd --name segoen_slboot.ttf http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/Fonts/segoen_slboot.ttf segoen_slboot.ttf initrd --name wgl4_boot.ttf http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/Fonts/wgl4_boot.ttf wgl4_boot.ttf initrd --name BCD http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/BCD BCD initrd --name boot.sdi http://${fog-ip}/fog/os/win/winpe/amd64/media/Boot/boot.sdi boot.sdi initrd --name boot.wim http://${fog-ip}/fog/os/win/winpe/amd64/media/sources/boot.wim boot.wim boot || goto MENUHad to add the 4 lines for fonts and now it boots in UEFI. I am amazed this was the issue and only on this machine. The fonts btw where in the locations, so its not like moving them into tftpboot was a problem. It was explicitly placing the initrd lines for the fonts in the ipxe entry that made it work…go figure.
-
Hi there,
@george1421
I just noticed that on Linux Mint 19 and newer it’s not possible to boot anymore before you change the Boot Parameter! I got it going on after setting this:imgargs vmlinuz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/var/www/html/iso/mint/ locale=de_DE.UTF-8 keyboard-configuration/layoutcode=de ip=dhcp toram -- || read voidKeep in mind, I got a different folder! But the parameter toram is damn important, otherwise it’s not able to mount /tmp and goes into emergency mode!
Maybe you want to update the wiki?
-
@Gamienator Thank you for the feedback and info, I will get the tutoral updated right away.
-
Hey peeps,
I’ve managed to get the installer portion running using a plethora of info out there but what really worked for me is this:
Downloaded vmlinuz and initrd.gz from the netboot version of Ubuntu and placed them into the tftp root folder:
Created a folder in /images/os called ubuntu and used 7z to extract Ubuntu 18.04 iso into this folder.
My menu entry now looks like this:
kernel tftp://${fog-ip}/ubuntu/vmlinuz initrd tftp://${fog-ip}/ubuntu/initrd.gz imgargs vmlinuz initrd=initrd.gz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/ubuntu splash ip=dhcp rw bootIt now boots on any machine into an Ubuntu Installer BUT!
This is great but not my final wish.
Is there a way to avoid the straight to install process and at least load a Live CD so that I could use Ubuntu to say scan the PC’s drive with clamav?
Any help would be great!
Thanks.
-
-
@jam1987 FWIW: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/12
The linux mint 19 maybe a bit closer to the kernel used in 18.04: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/17
