Testers

@phishphan Well that’s a pretty good sign. Hope it works out.

@nsherin said in Booting Ubuntu 18.04 Live CD:

kernel nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/linux
initrd nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/initrd.lz imgargs linux root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.14:/images/os/ubuntu/18.04/mate/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb quiet splash toram ip=dhcp rw
boot || goto MENU

The one thing I noticed is this is wrong. Imgargs is an iPXE command not a command line parameter. I don’t know if it would throw the boot kernel off, but your iPXE menu item should look like this.

kernel nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/linux
initrd nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/initrd.lz 
imgargs linux root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.14:/images/os/ubuntu/18.04/mate/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb quiet splash toram ip=dhcp rw
boot || goto MENU

Also I didn’t reread my own warning message in the tutorial I linked. Here is what I said:
Note2: If your Ubuntu 16.04 disk image does NOT CONTAIN A NETBOOT DIRECTORY (some users are reporting this), then download http://archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/netboot.tar.gz file and extract the initrd.gz from ubuntu-installer/amd64 directory and copy to /tftpboot/os/ubuntu/16.04. The DVD I downloaded {ubuntu-16.04.3-server-amd64.iso} contained the netboot files

You need the initrd.gz file not the kernel from the netboot.tar.gz file.

Did you grab vmlinuz from the netboot directory on the iso? I have not personally tested 18.04, but I think you need to ensure that you are using a boot kernel that has nfs support enabled. The default cdrom kernel does not. The root= warning is the telling bit from the image you posted.

Look at my warning (note) here for 16.04: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/6

Will you place an unmanaged switch between the target computer and the building switch? Your issue could be spanning tree is enabled, but you are not using one of the fast spanning tree protocols (i.e. RSTP, MSTP, fast-STP, etc).

If that doesn’t work then schedule a debug deploy (tick the debug check box before you submit the deploy task). PXE boot the target computer. After a few enter key presses it will drop you to a linux command prompt on the target computer. Run the following commands.
ip addr show
Ensure eth0 has an IP address. Then attempt to ping your fog server.

Is this target computer in bios(legacy) or uefi mode? If its in uefi mode did you disable secure boot?

Where did you get the FOG USB boot image?

@smalltowntech You’re doing something wrong because Ubuntu 16.04 is currently passing the installation tests (see link in my signature) for the FOG master branch. I recommend you follow these instructions: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@zerpie Those firewalld rules in that article were out of date, I just updated them. Have you tried following along with this: https://wiki.fogproject.org/wiki/index.php?title=Fedora_25_Server
Yes, I know it’s for Fedora 25 but honestly the steps for Fedora 21 to 28 are pretty much identical.

@dsloan-ethra You could deploy a snapin that removes the fog client, and then do an ‘imediate image deploy’ from the web interface. That would accomplish what you’re wanting.

@phishphan said in Issue Imaging HP EliteDesk 800 G3:

On the machine that is working I have a boot option under UEFI that says M.2 Windows Boot Manager which does not exist on the machines that I’m attempting to image. I’m still getting the operating system not found on those.

This is interesting. What do you mean the other does not have this setting? Is it simply not available to choose, or is it there but not enabled? Can you post a photo?

@mpatel If you have a linux admin at your location then I would contact them, because you could login issues since you are changing the user’s home directory. It can be done, but if you are not taking care, logins will be disabled and the server will be lost.

The second method is to wipe your server and reload linux. This time don’t let the system pick the partition table, but allow it to set the defaults then you go in and change 1 thing. The linux installer by default will create a 50GB partition for the root partition and then allocate everything else to /home. I would go in to the partition layout tool, in the linux installer and edit the /home path to be /images instead. Then continue on with a normal linux installation.