@tom-elliott This is the part I didn’t know when I restarted. Im back on 1.5 and good now.

@slimzy said in ipxe with sanboot:

is there a way to bind a root-path per item in the menu or we can’t?

I’m not sure I understand this ^^

But, I think I have an understanding of what is going on. I can see at the end of the kernel init it attempts to contact the local cdrom. If it doesn’t find it the kernel then starts the network install bits. When you pxe boot I can get the kali linux loader to work (without the dvd iso image). It loads and the reaches out to the internet to download what it needs and completes the installation. I suspect that when you boot off the cdrom that it loads the files directly from the dvd and does not reach out to the internet.

After checking the log I saw that it was still looking at eno1. I found where I missed changing the interface under the default storage node under Storage Management. After changing the Interface setting from eno1 to enp7s0f0 all is good. Hopefully someone else will find this useful.

@sebastian-roth don’t worry, it’s an exception. I’m managing many fog servers and it’s great (and still my first choice).

@imagingmaster21 security chip disabled, usb nic allowed in host config, it’s atom: I don’t think it has virtualization support.

Unfortunately, I don’t have any device available to make further tests.

@bmorine said in DeepFreeze Snapin:

ERROR: Object reference not set to an instance of an object.

Host settings -> reset encryption data should solve this.

@sebastian-roth

Not to ignore you, but when I came in this morning, me and my boss had a conversation. He was messing around with another VM that was also having speed issues. He turned off VMQ under the Hardware Acceleration for the VM’s NIC on Hyper-V. His file transfer speed issue immediately went away. Naturally, I tried this for the FOG VM. When I booted up a machine, PXE boot ran as expected. I never saw the TFTP spinning, and both bzimage and init loaded instantly. However, I turned VMQ back on and tried again and the speed issue was still gone, so I don’t know if this was a problematic setting or not.

If the speed issue comes back, I will go ahead and do the tcpdump, unless you’d like me to do it now anyways just for sake of gaining info. FOG is running on the latest Ubuntu Server OS.

@sudburr said in TFTP error oh my (ESX Server):

PXE-T00: Permission denied

It looks like this might be a file permission issue (if not selinux). The permissions on the /tftpboot directory should be 655 or 755. Make sure the parent folder /tftpboot as well as all of the files have these rights.

@nrg Marking this as solved then. For the database connection issue, open up another thread please.

Hey! Thanks for the topic!

If it does not exist

mkdir /var/www/fog/iso

Copy ISO file

cp SOURCE_PATH/ISO_FILE /var/www/fog/iso

Add

/var/www/fog/iso * (ro, sync, no_wdelay, insecure_locks, no_root_squash, insecure )

in

/etc/exports

Run

sudo service nfs-kernel-server restart sudo service rpcbind restart

Add a new menu in FOG WEB GUI

initrd http://${fog-ip}/fog/iso/ISO_FILE.iso chain memdisk iso raw

WORKED PERFECTLY!

To add on to what @Sebastian-Roth is asking, is the machine efi or mbr booting?

@cedre It works ok for the other VLANS?

@wayne-workman

Very true but making the change in the live DB is a great plan B until a long term plan A is found. I checked the mysql mem calc link and I compared the mysqld.cnf settings for those calculations but many of those variables are not there. I think at this point it works and I don’t foresee needing many more storage nodes in the future for this fog server. I’m happy it’s working now. Thank you both for all your help.

@cnkpadobi

You might want to switch to the working branch.

FOG Install instructions on wiki

Here you will see instructions on how to install Git and switch to working branch. Hope this helps.

@tom-elliott thanks Tom! ok it’s working now, I forgot to change from dev branch to working one since my latest trouble. Everything is fine now! 🙂 keep on good work!

@coxm If you pxe boot the machine yes.

Thanks. I found the problem. Solved.

@sebastian-roth we had an extensive IM chat session. The OP found where the issue was and identified the need for snponly.efi for a specific hardware configuration. I had him start with the examples from the fog wiki and work from there. Where we left it was he was going to see if he could collect the system uuid to see if we could write a better dhcp filter to only send i386-efi/snponly.efi for that specific model and send ipxe.efi for the remainder of the arch 0007 hardware types.

well that really didn’t help readability at all.

But it looks like its a database issue. You might want to review this thread and see if it addresses the issue. https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

Especially if FOG was working one day and its broken the next day without any intentional changes.

@sebastian-roth Thank you very much! You are brilliant!

You saved to me an invaluable time!

I carried out the test of your procedure and all functions perfectly.

Thank you still for your assistance, and thank you for this software!

I love FOG ! It is the best !!

@sebastian-roth Thanks so much! That worked. ( I had those pre-config settings before when I ran the 1.4.0; however, I had reverted to a previous snapshot and didn’t re-configure them for round 2).

Thanks again,
Tamara