Posts made by george1421

@bjonesqns If that fails we have other options. But for your sake, I hope that is the answer. Its a much cleaner solution when pxe boot works as it should. If snponly works for some and ipxe works for others we have options for that too, but make take a little IT magic to get it working cleanly.

Yep, you are stuck at the handoff between iPXE and starting up FOS. We see this all the time with crappy uefi firmware (not implying anything about your current hardware stack). The correct answer is the hardware manufacturer needs to fix their firmware and your problems will go away. We have a band-aid solution to this until the manufacturer releases working firmware. This involves booting directly into FOS from a usb boot drive. This by chance also takes the requirement about having a firmware supported usb network adapter away. As long as FOS supports the usb network adapter it will work.

@brad-schumann There is also a better log file in the bin/logs directory. The log directory is in the same directory you ran the installfog.sh script. That might give you a bit more detail into the install failure.

@brad-schumann Sorry reading toooooo dang fast. I read does not have internet access which would have tied nicely into the error message.

OK from the error message it says that the fog installer can’t install the php5-mcrypt package from your repository.

so if you drop to a linux command line and key in the following

sudo apt-get update
sudo apt-get install php5-mcrypt

Does it install correctly?

@brad-schumann well that explains the error then. The FOG server “needs” access to the internet only during installation to download the required packages from the OS’ repository as well as download the latest kernels from the FOG server. This IS a requirement. Once the install / upgrade has been completed it can return to its sheltered life.

So did you use git to clone the FOG repository?

Also does your FOG server have internet access?

@caw001 You will want to follow these instructions: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

I’m going to chat you some additional steps you can take. Look at the talk bubble on the FOG forums tool tray.

@caw001 said in Help trying to create USB PXE Boot - Where is ipxe.efi?:

I’m using WinSCP on a Windows client.

WinSCP will work to move that ipxe.efi file to the external computer.

Just for clarity, what instructions are you using to create this ipxe boot drive?

@caw001 The path you are going down will not work since you are trying to load iPXE which will then require dhcp I’m thinking the next server from dhcp will confuse the iPXE kernel.

If you can put the fog server and target computers on their own vlan (subnets) then we can make this work with FOG.

IF this path doesn’t work then we will take you through usb booting right into the FOS engine (the customized linux OS that captures and deploys to the target computers).

We have a number of options some are better than others.

Also understand that usb boot will only work for uefi systems. The bios / legacy is not supported by usb booting into the FOG menu. We have other ways to get there.

Why are you going this route? What problem are you trying to solve?

@msaglioc99 To repeat what Tom said. Using vlans (implies) using subnetting. What I’m looking for is to know IF there is a router between the fog server and the multicast clients? If there is you need to setup a multicast router to pass multicast traffic to the subnets. Otherwise most routers block multicast traffice by default.

We’ll need a bit more information. But on the surface it appears to be waiting for the rest of the systems to check in.

Are all of the target computers on the same subnet as the fog server? -or- is there a router involved to pass the traffic between the subnets.

@dirtyhandz lets start with how did you create this dvd to begin with? Did you have instructions?

-Or- My intuition just said; break that dvd into smaller bits. A win32 iso, a win64 iso and then utilities iso.

@dirtyhandz Well just thinking a bit more, this is an iPXE transfer error not the target OS just yet. iPXE isn’t liking that big dvd image. I’m still of a mind to have that dvd in a nfs(smb) drive share and let grubfordos or real grubforlinux connect to the share.

No space left on device

I have also seen this where what ever OS thinks the ISO image is a hard drive and tries to write back to the iso image, leaving no space left on device, error.

Also if there is a 32bit OS involved here there may be boundary issue trying to fit that whole DVD into memory and not leaving enough room for the OS. You may be better off exploding that dvd to a nfs share and mounting it that way. Use iPXE to get the kernel booted off the nfs share. It sure would make booting faster since it wouldn’t have to transfer the full 3.3GB file then boot from it.

@jacoboren Since you are having no luck with this, lets try to collect a bit more info. Can you please do the following.

1. Open “Active directory Users and Computers”
2. Select View->Advanced Features make sure its checked when done.
3. Navigate to the group and open the group.
4. Select the Object tab (only visible when the advanced features is enabled.
5. Copy the full conical path and post it here.

@krassus It will need interment access at least long enough to run the installer.

@krassus Does your fog server have internet access?

If so then this process is the preferred route to take: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@krassus Since you have an RC build already installed you should have a directory called fogproject. It should be in either /root/fogproject or /opt/fogproject.

Change to that directory and issue the following commands.

sudo git checkout master
sudo get pull

Then change to the fogproject/bin and execute sudo ./installfog.sh

@jle Please understand you didn’t fix the underlying networking issues you only masked them by artificially slowing down the pxe booting process. The underlying condition is still there (and has probably always been there). Will this work for you, probably.

So you have to decide, is it working good enough for your needs.