@robertkwild said in updating fog on centos 7:

it took ages compiling the ipxe binarys but now its been succesfully updated

THat’s right. Usually takes a few minutes depending on the CPU you have.

@danibashkov said in Exec format error during network boot:

Could not boot image: Exec format error (http://ipxe.org/2e008001).

Most likely the kernel image is missing or corrupt. Please check using the following command: file /var/www/{html/,}fog/service/ipxe/bzImage

As well I may ask how your DHCP server is being setup? Did you say yes for FOG to install and setup DHCP for you on the FOG server or do you manage your own DHCP server in the network? Just asking because possibly this might be a 32/64bit issue as well.

@george1421 Once again sir, you are a legend. Fixed 🙂

@Warsonix Great you figured out how to switch to a different iPXE binary. You are welcome. Feel free to ask whatever issue you run into in a new topic.

@Can-eh-dian11 said in Kernel Panic - Unable to mount root fs on unknown-block:

As suggested I gradually brought the FOG server and the clients closer together until eventually they were on the same switch/subnet and I’m still encountering the error.

Good work! Although we have not found the root cause of this we did rule out a very important factor.

We’ve also done some more deployments and have found that the issue isn’t as limited to a specific hardware vendor as we initially thought. There have been some recent Dell laptops where we are starting to see this pop up.

So from what we know so far I would guess this is a driver issue in iPXE. Do all the devices showing this issue have the same or a similar network chip (same vendor)?

Try using a different iPXE binary. Which one do you currently use? Are the devices set to UEFI or legacy BIOS mode?

@cidy-long-0 You can setup FOG with firewall but really need to know what you are doing. E.g. kernel updates through the web UI and image capture can be a problem if you get the firewall rules wrong.

@rivaldydwi Snapins are utilities to run a script, install a program, or what have you…

Generally, speaking, you would use the Snapin Run With of cmd /c with .bat scripts, but this isn’t strictly necessary.

.bat scripts ARE executable by nature and can be completely void ofr SRW/SRWA.

If your bat file is expecting its own arguments, this is what you would run Snapin Run With Argument.

@terrigan You could try booting this particular model via USB key to get around the issue.

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/21

Let us know if you need further information on this.

@hummela Not sure if spacing in names could cause this. I have not had much time lately and couldn’t find the time to look into this. But it’s on the list. Will get back to you.

@cidy-long-0 In general FOG can be used for what you are trying to do BUT it’s not made for this. Personally I think you are way better of getting this done with Clonezilla or other imaging tools instead of making all the effort to get FOG up an running in your network. FOG heavily relies on PXE booting in the standard setup and that might even be a hassle with some server hardware.

Both FOG and Clonezilla use the same base - partclone. So technically you don’t miss out when you stick to Clonezilla.

@pingonicechap

What specifically do you have configured on your dhcp server for dhcp options 66 and 67? What device is your dhcp server for the network you want to pxe boot on? (Manufacturer and model)

@Tom-Elliott The /var/www/fog/management/other/ssl directory was reported in the error log for Apache2.

I think this discussion thread can be closed. I intend to document the steps needed to change the server IP without having to re-install and then post them to the forum.

Any assistance would be appreciated.

@Kureebow Which kernel version and FOG version do you use? Does the same happen on different computer models?

@chambie said in Fog Configuration Kernel Update not working:

I have this file in two directories, one that is updated and one that is not.

You seem to have a duplicated FOG docroot, one in /var/www/html/fog/ and another one in /var/www/fog/. In certain cases this happens - I think I have only seen this when the FOG installer runs for the first time but does not finish properly. Though I never had the time to look into this properly.

Now that you know the correct docroot path on your system I suggest you rename or move the wrong one. But instead create a symbolic link pointing to the correct one named just like the old wrong docroot directory.

@lostitguy Do you have any USB devices connected. If yes, then I suggest you disconnect all if possible or use different USB ports and try again.

I missed the step to run the installer again. That seems to have resolved my issue. Thank you very much!

@jfenner said in Changing Server IP in VirtualBox?:

I’ll check with our admins, but our environment is fairly rigid.

If you can’t run a second network, then there should be only two places outside of the web ui that you need to update.

a hidden file /opt/fog/.fogsettings and /tftpboot/default.ipxe Inside the web ui FOG Configuration->FOG Settings and hit the expand all button. Search for the old IP address and replace it with the new. Press the save button in each section where you find the replaced IP address Then in Storage Nodes -> Default storage node there is an ip address in there.

Once those three have been changed and then rebooted it should work on an isolated network. Its best to rerun the fog installer script but it should work without it as long as if you change the IP address in those locations.

@hammerc807 Hello.

We checked a bit more on some logs on the client, and turned out we enabled the FOG_LEGACY_FLAG_IN_GUI on the server, and we passed the image from “partimage” to “partclone Zstd” and problem solved.

Apparently with partimage the client wasn’t able to write on the disk (where it was perfectly fine on the other one)

Thanks a lot for you help.

@Sebastian-Roth
Thank you for the quick response, I was able to put the images back in place, only the hosts will remain.

Thank you so much