Boot FOG on client PC using a special partition?
-
Sorry forgot to mention, the blotted ip is not received from DHCP rather set statically on the server. What is this step trying to do? Is it connecting to the FOG server to pull the menu?
EDIT: I think I see what is happening here. This step is calling the FOG server’s tftp service to retrieve the files to show the menu. problem is that the tftp/dhcp service is running on a different interface that is not on our production network. Maybe I can put the files it needs inside the NFS share and edit the script so that it points to the NFS share?
-
@brakcounty said in Boot FOG on client PC using a special partition?:
blotted ip is not received from DHCP rather set statically on the server.
I don’t understand this if you are just booting the iPXE boot loader you took from the FOG server then it is surely getting this IP address from dhcp, because that’s how it works.
What is this step trying to do? Is it connecting to the FOG server to pull the menu?
The ipxe.efi and all of the iPXE boot loaders delivered by FOG work the same way. They use the dhcp option 66 to locate the fog server once iPXE is loaded. So at this step iPXE is chaining (loading) the contents of default.ipxe from the fog server. The default iPXE file, which is just a text file, tell iPXE to call the boot.php file which builds the iPXE menu.
-
@brakcounty Ok so now you need to clarify a bit.
- Your FOG server has multiple interfaces?
- When you installed FOG you told it which interface is for imaging?
- You have a dedicated imaging network?
- The pxe booting computer (in this case) is connected to your imaging network?
-
- yes one for management, the other for imaging.
- eno1 is for management, on my production network. eno2 is for imaging, isolated with DHCP and TFTP.
- Yes refer to point #2/.
- The PC that I am testing with is on my production network, and I am using a USB drive with the ipxe.efi renamed to bootx64.efi in /BOOT/EFI.
I was wrong you were right I misread the blotted IP. It is actually the IP address of our SCCM server that provides boot files. Not sure how that happened. Maybe the PC requested a PXE packet and the DHCP server relayed that request to the SCCM server. Just a note, SCCM PXE booting only works on our department’s subnet so we can image using SCCM if we want, but only on our IT dept’s network. So this won’t work. I want to be able to get to the FOG menu via USB and pull images from the FOG server. Once that works, then I can figure out how to create a bootable partition and somehow get the FOG management client to do this automatically/magically.
-
I just confirmed that the images on the NFS share /images are accessible on the management interface which is on our production network. Now we have to find a way to get the FOG menu without using pxe or ipxe.
-
@brakcounty Ok everything then is working as it should. Not what you want, but how it should.
Now why are you attempting to image a computer on your business network and not the imaging network? The fog server is configured to only provide the correct IP address to things on the imaging network. The FOG program does not support imaging on two different interfaces (I say that knowing there is a hack not supported by the developers around the problem).
-
It is for convenience and also better workflow efficiency. Right now, I am the only one using Acronis pulling images from my NAS but the supervisors wanted me to build them a FOG server, so I did. Now we’ve all been using FOG here at our imaging lab but it would be nice to be able to image onsite at a clients office, instead of either pulling the drive/PC back to the lab to image. I can image a PC in about 7min across the network at a clients office with acronis. I want the rest of our team to be able to do that. I use an Acronis iso that is somewhat old now and that I paid for. Acronis doesn’t offer deployment unless we purchase Snap Deploy. FOG is free, so we are dedicated to that solution.
-
@brakcounty said in Boot FOG on client PC using a special partition?:
FOG here at our imaging lab but it would be nice to be able to image onsite at a clients office
A mobile fog server would work here (laptop loaded with FOG and dnsmasq). But this issue is beyond the scope of trying to deploy to a system not on the imaging network. iPXE and FOG is only designed (programmed to support a single interface for imaging). There are hard coded IP addresses in the fog configuration as well as in config files that point to the IP address of the designated imaging interface.
If you wanted to discard iPXE from the imaging process (and loose some functionality) you can boot FOS Linux (the OS/Engine that captures and deploys images) directly from usb. You see the FOS Linux engine being transferred to the target computer on the imaging network as bzImage and init.xz. With that said, in this hack you have to define the IP address of the FOG server since FOS Linux would normally get that from iPXE (which is not available in this solution). So its possible to define the management interface of the FOG server in the config file for this USB boot. The instructions are listed here: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Read through the instructions completely and watch out for the caveats.
Also look at the chat bubble for a few more hints.
-
@george1421 So I changed the IP in the grub.cfg file to my FOG server on the production side, and booted the USB, chose deploy/capture image (the first option on the boot menu), and got this error:
-
@brakcounty Ah you DID NOT read the caveats with this process. You MUST schedule the task first before picking option 1
-
Ok created a task and tried it again, and now it looks like the task is trying to mount the nfs share via the imaging (isolated network) interface 10.0.0.10
Is there a way to make FOG try to connect to two different nfs shares? Like if one fails try another? -
UPDATE!!!
I added a storage node and specified the interface and ip of my prod network and successfully deployed an image using the USB FOG. Now I added an entry to the GRUB menu called “Boot from HDD” but I don’t know the command line to boot from it. I have used “sanboot --no-describe --drive 0x08” in an ipxe menu file with a different setup but GRUB isn’t recognizing sanboot. -
@brakcounty As we usually don’t use GRUB in FOG for booting there are not that many resources on this topic in the forums. For that you need to search external sites. Here is a list of different GRUB configs used for chainloading to a Windows installation on disk: https://wiki.gentoo.org/wiki/GRUB2/Chainloading
I have not see the
ntldrused much yet. Most Linux installations that setup dual booting with windows use thechainloadercommand I think. Try different ones and you should be able to boot from disk through this. -
Great thanks! I already found and tried this:
insmod part_gpt
insmod chain
set root=(hd0,gpt1)
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
bootNo luck. Says the file could not be found.
The ls command shows hd0 hd0,msdos hd1 hd1,msdos, hd2 hd2, msdos. I tried all three hd entries and pointed to /EFI/Microsoft/Boot/bootmgfw.efi no go, but much further than I was thanks to you and @george1421.
-
@brakcounty said in Boot FOG on client PC using a special partition?:
The ls command shows hd0 hd0,msdos hd1 hd1,msdos, hd2 hd2, msdos.
Well then you have a legacy MSDOS partition layout and can’t use the GPT stuff! Have you tried the good old MBR chainloader style yet?
insmod part_msdos insmod chain rootnoverify (hd0,0) chainloader +1Play with the numbers (at line
rootnoverify) till you hit the right partition/disk. -
@Sebastian-Roth The windows partition I’m trying to boot from is a GPT-EFI bootable system. Is that “+1” always supposed to follow the chainloader entry?
-
@brakcounty Sorry, just updated my post again.
The windows partition I’m trying to boot from is a GPT-EFI bootable system.
On the GRUB command line run the following commands, take a picture of the screen and post that here:
set pager=1 insmod part_gpt insmod part_msdos lsIs that “+1” always supposed to follow the chainloader entry?
Yes, as far as I know.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
-
@brakcounty Don’t think there is a GPT partition layout on any of those three disks. While hd2 doesn’t even seem to have partitions at all. Maybe this is the USB key? Can you boot to Windows and post a picture of the disk management view? Shall see if it’s MBR or GPT there.
-
It probably is the USB drive. I don’t think this particular environment is seeing the hard drive in the PC. I know for a fact that the Windows drive is GPT and EFI because I converted it to GPT before I imaged it, also made sure the image itself was created as GPT. I am able to boot from the Windows EFI partition normally.
