@george1421

rebooted, same results.

@julio This is a new error for me. If the destination is failing to deploy I think there should be a different error. But I give you steps to debug this.

Schedule another deploy task to this computer, but before you press the “schedule task” button, select the “debug” check box then submit the task. PXE boot the target computer. The computer will start into the imaging steps, but this time you will see many pages of text that you will clear by pressing the enter key. At the end of the text you will then be at the “FOS Linux” command prompt.

At the “FOS Linux” command prompt key in lsblk. This will show you if FOS Linux can see the local hard drive.

The next step you will start the imaging process. In debug mode the imaging process will pause at certain steps. This is done so you can read errors during imaging. I am guessing since your deployment is failing, there is an error message that is getting overlooked. I might think there will be an error message on the partclone screens (blue screen with text). To start the imaging process at the FOS Linux command screen key in fog and press enter. You will need to press the enter key at each pause to go to the next steps.

@george1421 The code works as expected now. I used your shortened fog.updateregbarcode that just echos the variable into the text file on the C; drive.

@george1421

Now you said that isc-dhcp server worked?? The reason why I ask is that isc-dhcp server and dnsmasq do the same thing. So why would isc-dhcp server issue IP addresses and dnsmasq does not respond?

To be honest, this is beyond me.

Initially, when I configured the FOG server I installed isc-dhcp server, configured pool of addresses and added “next-server” and “filename”. Then I set bootprelay of the switch to point to the FOG server and everything worked (and still works if I go back to this scenario).
Afterwards I realized that our expensive switch supports dhcp and decided to give it a shot (why use separate service for something that already runs on the switch, right?). Since then I’ve encountered this issue i.e. switch supporting only numerical option codes (66, 67 etc). Analyzing the frames turned out that my clients are unable to evaluate those options even though they do exist in the dhcp packets! Having “next-server” and “Boot file name” in the packet body seemed like the only way it works. I managed to confirm this by analyzing frames coming from my working isc-dhcp server.

Now, you can probably see how strange it is.

@george1421
Hi George!
I wanted to circle back and let you know that all is working now thanks to your help.

I have some other questions but I will open new tickets for those.
This crisis is complete and working now. I was able to boot one of the tablets
and gather an image off of it.

Thank you soooo much for the help.

Chris

@huecuva said in Hanging on ipxe initalizing devices.:

Can those iPXE binaries be changed in the webgui?

No because it all depends on the DHCP server you actually use in your network (quite often it’s not on the FOG server itself).

@rubensurtfe-0 As soon as the boot files are sent to the target computer, the FOG server is no longer involved with the target computer. SO this error is with what ever OS is running.

@george1421 @Sebastian-Roth Just wanted to give you an update. From what I can tell, the section of dhcpd.conf where you declare options, was missing a } so the file wasn’t reading the options I guess? I compared the file to an old server and that was the only difference I could find. I probably deleted it while editing the file at some point. Works like a charm now.

@Epsilon52 Thanks for the update and good to know. Maybe it just needed a cold boot or something like that.

Thank you!

@victor-r Interesting… there must be some other code that is doing that. Rerun the fog installer to put things back.

Just to be sure I’m looking in the right area, you are trying to replicate your images from the FOG server to the windows storage node or are you trying to capture directly to a windows storage node?

@tom-elliott
Originally I wanted to keep the image without installation as I did at the time … I will experiment with domain integrations. And the multicast (At the time it saturated the network … :))

@nil If you are interested in helping start out by writing a tutorial in the tutorial forum. Then once others have a chance to prove it out it will be converted to a wiki page.

Thank you for helping the FOG Project move forward by adding new options for installing FOG.

Let me try a different graphic to see if I can show how they are linked

@dominique said in Database engine MyISAM - upgrade FOG?:

Any idea when 1.6.0 will be general available?

There is no timeline for this yet. Many people use FOG but very few help working on it. So things are going very slow at the moment. We’ll bring out a last 1.5.x release (1.5.10) to finish up that line and then the next will be a first 1.6 release (months down the road).

If you are keen to get InnoDB earlier you can follow the topic Goerge posted. From my point of view this should be possible in 1.5.x setups as well. But we won’t officially support this and don’t want to push out for a major change in the 1.5.x branch anymore.

@nerdstburns Adjusting compression ratio with Zstd might help to speed it up.

@george1421

Hi George,

That’s exactly what im looking for! Thanks, this would work for me. When we get hardware on our departmend i connect always mostley one kind of machine, so that works for me.

thank you for your great help and quik respons. Im gonna build further with this in a few weeks, and now it is a lot easier.

gr

Paul

@quazz Ok, thank you for the answer.

@sebastian-roth

oui je veux de l’aide roth. je devrais normalement booter le images de ubuntu et débian. centos etais une erreur déseolé de mon retard

@seppim I have no idea since I did not test loading it with memdisk. I did not look but I suspect the iso image may be larger than 2GB (thinking memdisk is a 32 bit application and not a 64 bit app. But this is only a guess). I know when I was testing the boot.wim file on the iso was 1.3GB in size.
I was able to get it to boot in uefi mode here: https://forums.fogproject.org/post/140212 but in bios mode it complains about needing bootmgr.exe in the iso image.