Tom is right, we need more details.

Is this setup at home? Are you using a consumer grade router combo-device ?

Are you in a private network? 172.16.x.x is a reserved range for private networks… So I’m assuming you’re either working for a very well established employer - or this is a home setup and you chose that range just to be slick 🙂

@moto_ryan Comment out the exit code for that line in the script code - for debian.

trunk/lib/ubuntu/config.sh

(or is there a directory in 1.2.0 just for Debian, I have no clue)

Search for “exit 0” where the failure code is and just put a hashmark in front of that line, like this:

#exit 0

Be sure to comment out the correct exit line.

This will allow that part to fail, but the script to continue.

Might I ask why you’re using an off-the-beaten-trail version of Linux?

@dustindizzle11 This is a well known issue with 1.2. I fixed it almost two revs after releasing 1.2.0, but had many other bits that made it unfeasible to come out with another fix (and it was mid imaging season.)

@Wayne-Workman I checked that, but I’ll check @tom-elliott’s suggestion next time I’m working with it.

@Wayne-Workman yes, as long as I set the local server storage node to master, the create new image page works.
I also have my fognode1 server, in a different storage group, set to master.

Can you be more specific on where to enable the “size on server” setting? I’ve looked in the FOG settings and am not seeing it.

EDIT: Nevermind, found it! FOG_FTP_IMAGE_SIZE. Thanks!

@Raymond-Bell Is anything not working?

@kverkiss Good !!! The next time I see a jumble of nonsense errors such as this I’ll recommend trying a different drive.

@Tom-Elliott
Yes all the nodes are on the same version as the main server. They had the files/folder in the path /var/www/html/fog/service/ipxe, but the clients booting from one of the storage nodes would not display the menu until we copied over the folder from the main server. We did make some modifications to the main server’s FOG_TFTP_PXE_KERNEL so that is why I had to copy it over to the clients.

I’m sorry that I’m not right on the case.

I wonder about this issue. The specifics of the problem you’re running into seems, to me, to indicate that there is no Storage groups with a master node within the group. Normally it should default to return the relative node that IS in that particular group, but if there is no node associated, this could occur, I suppose. I don’t know all the specifics. I’m working, hopefully, to figure out a solution, but I feel I may need access to a problematic system so I can work on it live. Sometimes, and there are multiples who can verify this as needed, I simply can’t replicate so seeing the problem on a known “bad” target is really the best option.

Thank you.

OK, I will try this. Thanks!

@mrzo For the record - my organization has had a whole lot of problems with the Lenovo M72e. And when I say problems - they are (currently) absolutely not working with FOG Trunk.

The strange thing is - the 30 or so that we tried every method in the book with - one of them always succeeded while every single other one always failed… we have sat down and compared Firmware settings, we’ve restored firmware defaults… we can’t figure it out, it’s a mystery at the moment. We are currently using WDS and/or Norton Ghost for that particular lab.

We have no M83 models in our environment - but I wanted to just shed a little light on my experience with Lenovo. I think some of their other models don’t quite like San-Boot style HDD exits either… Lenovo is… a PITA.

AHCI is the preferred operating mode, it’s a best-case scenario that you have a mechanical drive.
You say that the system is configured to boot via UEFI ? What boot file are you using? Have you tried others?

@Wayne-Workman said:

Just to make it clear, Secure Boot is currently required to be OFF to network boot with FOG. Can you provide us with a screen shot of the error ? You might need to take a video to capture the error, often times the errors are only displayed for fractions of a second. What happens if you try to boot using ipxe.efi ??

At first, I didn’t know what you were talking about–the only efi file in my /tftpboot folder was snponly.efi. But then I read another suggestion from you elsewhere that maybe upgrading to trunk might help, so I tried that.

And, lo, my /tftpboot doth overflow with efi files! So I tried ipxe.efi, and it WORKS.

Also - see my old post below on the subject of using a USB dongle.

That looks like really useful info once I get this host registered. Amazing.

As you requested elsewhere, I will experiment with co-existing EFI and BIOS hosts using DD-WRT and see if I can’t contribute to the Wiki to pay it forward.

@hlcstudy Very happy you got it fixed and glad we could help.

@johnomaz said:

Yes, it can be flagged as solved.

Good 😉

@Wayne-Workman That is much more elegant than either of my solutions. I doubt you will need my help, but give me a poke if you want me to look at anything with you.

I’m going to solve this only because it seems a very particular set of information was causing the problem. While I was concerned my recent changes were the main cause, it seems they really weren’t, potentially.

I’m only solving because the problem was relatively easy to correct for.

Also - when did this failure start? Was it working before? What changed?

Have you checked the mysql settings inside of /opt/fog/.fogsettings on the problematic storage nodes?

Are you refering to Wake On Lan ?

I should explain a little perhaps - and then explain a few options.

When a computer is configured in it’s firmware to boot to the network first, It will try that. DHCP hears the request and sends info. The PC confirms it’s received info - there’s a fraction of a second’s wait - then DHCP sends a “Use it” command once no other computer reports “no don’t use that, I’m using that IP”.

Then the computer network boots to FOG - as it was told. If it is registered - it will look for any active tasks and do those - if there are no tasks it will either (A) Show the boot menu for a specified time and then try to boot to the HDD or (B) not show a menu at all and immediately boot to the HDD.

Just depends on how you have it configured.

By default, non-registered hosts will show the menu so that you see it’s not registered. This menu also has a countdown that elapses - after it elapses, the machine tries to boot to the HDD.

Now - if you don’t like seeing the menu for registered machines - the very best that can be done is to set the timeout to 1 second. You can do that here:
FOG Configuration -> iPXE Boot Menu -> Menu Timeout (in seconds):*

Now, do not set this to 0 because 0 makes the menu stay up forever… 1 is as low as you can go.

@Developers is that normal? 0 causing the menu to just stay up?