@george1421 The keymap is useful for Full registration, hardware compatibility, debug mode. Perhaps a few other cases as well.

Might want to change undioonly.kpxe to undionly.kpxe

I’m not 100% about partimage, I think partclone has a wrapper for it or something.

At any rate, you may be able to change the default under FOG Configuration -> FOG Settings -> General Settings -> IMAGE COMPRESSION FORMAT DEFAULT

On the old one go to Images and then choose Export Images.

You would download a csv file, import that file on the new server (delete the images you created, the file will import them)

Also make sure the folders have the exact same name as before.

@Sebastian-Roth At home now, but the error I got on the fog schema updater was :

Access denied for ‘root’@‘localhost’. Please check if the database is running.

Using sudo mysql -u root through ssh gave me access no problem.

Using mysql -u root gave the Access denied for ‘root’@‘localhost’ error (I believe it was number 1696 or so?)

But your comment gave me an idea to move the var/lib/mysql and reinstall.

Tom had a brief join.me session before my internet cut out and after that I had to sort out our dhcp server first since apparmor didn’t allow it to create new dhcp lease files (still doesn’t, but it’s in complain mode now), so we’re guessing this error has something to do with ubuntu 16.04 specifically.

Aside from what Wayne said, you seem to be having the FOG client on your PC. The FOG Client allows the server admin to push software installations remotely using snapins, force logoff, order imaging, etc.

It cannot see what you’re doing or any passwords/usernames you enter or use. That doesn’t mean you should expect privacy on a library PC though.

See also:

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#MySQL_credentials_for_FOG_Main_and_Storage_Nodes

I believe there was a chainloading issue earlier which got fixed, so try updating to the latest.

Although, in your situation that seems unlikely given how this didn’t happen because of a FOG update.

What Junkhacker suggests could work, if it doesn’t I’d have to guess that something in your network was altered to cause this.

ipxe uses a different ‘console’ for BIOS and UEFI by default.

Afaik at the moment in UEFI (perhaps only certain UEFI implementations) not everything quite works as it should, so it falls back to ‘default options’ in order to still display the menu.

I’m guessing you also have no background image, correct?

So from my understanding of this process, you login remotely to the server and then FTP tries to do its thing locally on the server.

As such, login credentials should be fine and seeing as permissions are fine too…

This will take some time to get to the bottom, but I’d like to note that a segmentation fault is generally caused by running out of RAM. How much is in your system?

Can you also post the output of

df -h

It might have something to do with disk space running out.

I also tried adding option tftp-server-name X.X.X.X; to my dhcpd config file, but no luck.

The correct option is next-server X.X.X.X

That’s probably already correctly set judging by your post.

Your problem may be resolved by trunk, maybe not, but you’d need to install newer Ubuntu version for it.

@zer0cool The settings are the same, I’m only trying to explain why it works fine in BIOS, but not UEFI.

There isn’t necessarily a fix currently.

Try the fallback method, maybe:

Not all consoles support full RGB colours. You can use the basic ANSI colour as a fallback. For example, to define colour 6 as turqouise, falling back to cyan if RGB colours are not available:

colour --basic 6 --rgb 0x40e0d0 6

Could you share the Apache Error logs?

Upgrading always has the potential to screw some things up, the package handler seems to struggle doing it properly in one go, at least in my experience.

There are some steps to take to get FOG to play nice on Ubuntu 16.04 though, because it removed PHP5 from its repository and made PHP7 the default one.

https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_16.04

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

I recommend the git method. Replace dev-branch for master if you want the latest stable version.

@ttrammell You can find them on the FOG WebGUI, under FOG Settings - Log viewer - Apache Error Logs

@finvader Just to confirm: Did you upload the image to the server (overwriting the old data) after upgrading to RC23?

@Junkhacker The following commit changed UUID stuff https://github.com/FOGProject/fos/commit/f49b0f7d5b0c90866a6dcdbbd5d59e529857242e

On MBR, the label-id is in the form of what appears to be an error code (0xrandomnumbersandletters) hence the output that you saw.

I don’t know for sure why it would fail, but something in that direction possibly.

edit: Ok, so, in d1.partitions it’s saved as 0xlabelid whereis sgdisk expects it as labelid

The original method used blkid -po udev which does not put 0x in front.

Shouldn’t be too hard to fix

@Artur You can remove dhcpd and disable the relevant dhcp options in /opt/fog/.fogsettings

Then run

yum install dnsmasq -y

if I’m not mistaken and follow the dnsmasq instructions. I don’t believe DHCPD has proxy support.

All of this sounds weird to me given that Mariadb is a drop-in replacement for mysql.