I only see one task.

The systemctl status FOGMulticastManager -l is outputting all things related to that call.

The php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager & lines appears that it started once and restarted it again.

The sh -c /usr/local/sbin/udp-sender is the process starting the real multicast task itself.

The /usr/local/udp-sender is the actually running command.

@sebastian-roth said in Best Process for Imaging with USB Nic's:

Download the patched init.xz here to set the UUID in the inventory DB table when registering a client from the FOG menu (this step will be gone very soon)

This portion is no longer needed. Installing the “working” will get you the patched init’s now.

@cojohnson Mind installing the working branch then? There was a problem only fixed in working, I haven’t had a chance yet to make it rc-10. Sorry. I’m 99% sure it will make your replication problems go away.

Most certainly they are able to be removed. I’ll try to post how on Tuesday

I should add that the mode of boot really matters a lot here.

DBAN does not have a UEFI bootable setup, so if your machines are booting via EFI/UEFI, then chances are this is part of the problem.

What version of FOG are you running? What does your current menu entry actually look like? What does your DBAN directory structure look like?

Please install the working branch.

I’ll try to get an RC 10 out this week when possible. That said, I’m aware of the problem in native RC-9 and I know that this issue has been addressed in the working branch from github.

Thank you,

@kubala as you captured the image as multi part all disks, is it possible it can’t put the partition table on the drive because the captured image was a larger drive than the one it’s being deployed to?

@jonathan-cool Remove the 2 in the fixed file and deploy the image to a client…

@george1421 switch to working branch. Copy the packages/tftp folder contents to /tftpboot. Switch back to dev-branch or master. Do not run the installer.

Install the working branch please?

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

@jay-bosworth did you provide a clients fog.log?

The problem, as far as I can see, is PHP installed is still older. 5.3 It would seem? (php -v to view the php version).
In particular, this is the line I think causing the issues:

[Tue Nov 14 18:04:50.525805 2017] [:error] [pid 8108] [client 10.30.4.8:55431] PHP Parse error:  syntax error, unexpected '&' in /var/www/html/fog/commons/init.php on line 132

@wayne-workman, @george1421 it is possible if the uuid for these hosts are the same. Which rc 10 should fix.

@uwpviolator I’m going to guess. The fact that you state it works for windows 7 kind of proves this is outside of something fog is actually doing. Not that we don’t want to help (I think you’re aware of this already), but we can’t fix other people’s “mishaps”. All we can do is provide, hopeful, workarounds.

@eliaspereira please open the storage node in the GUI. It looks like the path you have for images is /mint/images. Is this correct? By default fog sets up in /images.

@wayne-workman already known about and there’s a workaround fix for it somewhere around the forums. It has to do with replacing the plugin.class.php file

@wayne-workman three finger salute = CTRL+ALT+DELETE usually. Or at least in olden days.

I’d also recommend following the information here.

Which should help you remove the extra kernels.

With the information you’ve given us however, it appears your total disk space is about 150GB?

Did you have a mount for /images? Your disk space is completely used up currently. This means mysql can’t write the lock files to actually initiate itself, and cannot perform and updates to the database. This is why you’re seeing the message.

I’d also take a look in your /images folder and remove any images you do not need anymore to help you out a little bit.

@joe-schmitt This is indeed a server side error.

Basically it’s saying it cannot find your FOG Server’s private key, which is how it knows how to decrypt the information passed by the client.

Please re-run the FOG installer using the argument(s):

./installfog.sh -KY

You MUST NOT recreate the CA at this point as the client is already aware of it. The -K will simply recreate the missing private key using the current CA, and all should start working immediately.