@coop90 Sounds like you got it all working again. Anything you still need help with?

@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

@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.

@KaiHerlemann Great you figured it out. Still something we should prevent from happening in the code.

@emreonder Sorry for my late reply. Lost track of this over the holidays.

I am still at a loss on why your partition looks like this. What is the extended partition actually used for?

Beside that I can’t really guess what might be special about this setup/layout that prevents it from chainloading to disk after iPXE is loaded on the Gigabyte motherboard. We know it works on other hardware and therefore I’d think the bootloader on disk is being properly imaged through FOG.

@tom-elliott said in Unit nfs.service could not be found:

To understand:
/dev/sdb = /images
/dev/sdc = /opt/fog/snapins

I 100% agree with this route AND to add create the partitions on the disk as standard partitions and not LVM volumes. If they are standard partitions you can expand them easier than a LVM volume (debatable) if you are running the fog server on a V and need to grow your storage.

@george1421 It worked. Thanks !

@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

@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.