@dangbird said in UEFI Boot Install of XenServer Close but no Cigar:

Let me know any specifics of how I can contribute in return.
I will work on a “Load XenServer from Scratch using FOG” write up at a minimum.

This is perfect payment in kind. Thank you

@itay Do you plan to update to CentOS 8 as well or keep 7 (still some years before end of life!)?

@george1421 Thanks, i will try that.

@john-l-clark Here are the exact key sequences I used to build this driver on a brand now Ubuntu 20.04 image in my virtual lab.

sudo su - apt update apt upgrade apt-get install wget git build-essentials -y reboot git clone https://github.com/acooks/tn40xx-driver cd tn40xx-driver make sudo make install modprobe tn40xx tail /var/log/syslog lsmod | grep tn40xx

When you review syslog look for errors regarding this network adapter. Ignore the one about the tainted kernel.

If everything goes ok then you will need to create a startup file in /etc/modules.d so that this network driver loads on every boot up. Once its there then reboot and it should pick up an IP address, if not make sure its listed with the lsmod command like above. For ubuntu you may have to use the network manager to assign an IP address for it. I’m not a big ubuntu user, so I’m just guessing. But it took me longer to install ubuntu than it did for me to build this network kernel driver. Keep the installer files because when you upgrade your linux kernel you will need to recompile this network adapter driver.

@yuma Ok, turns out that even though we use ufw disable it does not properly remove all the chains and rules it creates. This seems to be a known issue.

While we surely can add this block of iptables calles to clean it up I am wondering if we should actually do this as it’s really ufw’s job to do.

iptables -P INPUT ACCEPT iptables -P FORWARD ACCEPT iptables -P OUTPUT ACCEPT iptables -t nat -F iptables -t mangle -F iptables -F iptables -X

@yuma This is a bit miss-leading because the compile messages go to a different log file not directly displayed be the installer when it hits an error.

Please take a look at the log file you find in the directory you ran the FOG installer from ........../fogproject/bin/error_logs/fog_ipxe-build_1.5.9.log - upload that whole log file to a file hoster and post a link here.

@zaccx32 Find the database information in /var/www/html/fog/lib/fog/config.class.php - with FOG 1.5.9 the database user is called fogmaster instead of root that was used in earlier versions. So to login you run this command on the console:

mysql -u fogmaster -p ...

@Shiro228 said in Alt linux install:

How can i install Fog on Alt linux server

You’d need to modify the installer script and add support for this distro. Shouldn’t be too hard if you are good with bash scripting and we shall support your effort if you promise to maintain this part of the installer for some time down the road. Minor modifications are needed from time to time when new releases of a linux distro come out.

Ubuntu 14.04 has reached end of support / end of life 30 Apr 2019. It is no longer supported under FOG 1.5.8 and later. That doesn’t mean it won’t install that just means the needed ubuntu distribution repository files may not be available any more. The lowest version of ubuntu that is supported and tested daily is 18.04.

ref: http://fogtesting.theworkmans.us/

@DARUN974 said in Fog installation with ubuntu focal:

My problem is that I have a proxy and difficult to initialise.

This is the problem.

@Oratorian If your linux partitions are regular partitions then FOG can resize them. If the are LVM partitions then FOG can’t resize those yet.

@Blake_hill2020 The password you use is the one you see in the FOG web UI on the storage node settings, right?

@Sebastian-Roth Thanks Sebastian, that’s what I was wondering, I won’t bother with NAT in VirtualBox then. Hopefully I will have time tomorrow to try and get this set up and tested.

Yes, I do have two physical network interfaces. The machine is a Lenovo M92 with one network port. I’m using that for the imaging network and attached a USB to ethernet adapter for the business network. They are both in bridged mode.

The default (ubuntu) installer kernel [linux] and initrd [initrd.gz] does not support/know about network booting. Its possible that the debian installer kernel and initrd also doesn’t directly support network booting. Both bits needs to support nfs for netbooting to work. In the screen shots provided appear that the installer scripts are only designed for local cdrom booting.

You may be at a roadblock with this problem.

I did find the debian 9.2 buster netbooting kernel and initrd. I don’t know if you can slide those in place and get untangle to install correctly. I’m sure the netboot kernel will work correctly but the initrd may only install native debian and not the untagle you want. You will want the netboot,tar.gz file. Extract the .gz file in linux or use 7-zip in windows.

http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/

@Naline I just wish I could have found the post I used before. As I said it was 2 simple commands to expand the disk. Its just which two commands that were the stumbling block.

I agree I hope this thread help the next guy.

@jc35 Found some time to look into the client updater on Linux and seems like there are a few issues with that unfortunately. I was able to find and fix the first one but it still needs more work.

Thank you for your answer.
Your document is complete.

@Oleg said:

I don’t know if it has to do something with the timeout issue but in /etc/default/grub I added

We don’t use GRUB for PXE booting hosts usually! Seems like you have customized your setup a fair bit. I may ask you to tell us more about the customization to we are able to properly help you!

I changed manually the kernels in /var/www/html/fog/service/ipxe/ to the 4.15.2 Kernel.
With the older kernel the issue with the timeout is gone.

That’s interesting. So it seems like a Linux kernel network driver issue from what we know so far. Let’s start by trying to find out what driver is used. Please boot Windows on that machine, open device management and get us the device ID from there. Usually in the form 12c4:5f78.

@88fingerslukee said in FOG Server cannot connect to storage node:

I have put the correct mysql connections into the fogsettings file.

The fogsettings file is only used by the installer. Did you re-run the FOG installer after adjusting fogsettings? Or you can manually edit /var/www/html/fog/lib/fog/config.class.php for the DB settings.

The URL called is http://fog.server.ip/fog/status/kernelvers.php - be aware that this URL is called from your FOG master node. So if you can open this URL from your browser it doesn’t necessarily mean that it does work when called from the master node as well.

@beardedfool Which Linux OS and version do you use? Older versions of FOG before 1.5.8 did run with an empty DB root password. So you find a lot of dated information on this. We were adding more security in 1.5.8 but it hat minor issues on some Linux OSes. Will provide detailed information for you when we know what you use.