Ok, after lots of digging in the code and @JJ-Fullmer database we seem to have found out what happend. Turned out some of his PowerShell code messed things up by deleting the primary MAC address of some hosts and the fog-client did its share to kind of reset some of the hosts’ information and make them pending.

The PowerShell code is fixed already and I will work on adding some checks to hopefully not mess as much up with the fog-client as we did here.

Initially we thought the snapin hash problems were at fault but the evidence collected points to this being a coincidence.

Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

Hi,
try setting this parameter in /var/www/html/fog/service/ipxe/refind.conf:

# Delay for the specified number of seconds before scanning disks. # This can help some users who find that some of their disks # (usually external or optical discs) aren't detected initially, # but are detected after pressing Esc. # The default is 0. # scan_delay 5

and, if you need, this:

# Timeout in seconds for the main menu screen. Setting the timeout to 0 # disables automatic booting (i.e., no timeout). Setting it to -1 causes # an immediate boot to the default OS *UNLESS* a keypress is in the buffer # when rEFInd launches, in which case that keypress is interpreted as a # shortcut key. If no matching shortcut is found, rEFInd displays its # menu with no timeout. # timeout 5

Hey @Tom-Elliott

I confirm that now everything works correctly. The error message was on one of the 2 partitions on the hard drive was too full. I will refine the settings and make you a return on the minimum size of available space to deploy.

I confirm that I capture and deploy on the same machine and therefore even hard drive. So no space problem available.

We can pass the inviter in resolve
As soon as I have the information on minimum available space I will add them in this topic

@+

@melvinpaz Ok, this is a Mac client you are having problems with. Please tell us exactly which Mac you have (serial number!). The modifications you made are correct as far as I see.

I am wondering why it is saying “Could not open net1”. Are there two network cards in this client. Possibly wireless? Although I am pretty sure iPXE does not provide any wireless drivers. We need more information on the hardware (exact Mac model / serial number) to be able to help you.

Bonjour
Oui c’est bien FOG 1.2.0 et c’est bien la modification initrd=$imagefile qui à fait fonctionné sur MAC

#########
Hy
Yes it’s good FOG 1.2.0 and it is changing initrd=$imagefile who in fact worked on MAC

Bonjour @Sebastian-Roth

Mon problème était bien la version du kernel mais pour mettre à jour le kernel il fallait que je rentre le proxy donc oui tu avais raison.

Maintenant j’ai un nouveau problème voici le message d’erreur

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

############
Hello @Sebastian-Roth

My problem was indeed the version of the kernel but to update the kernel I had returned the proxy so yes you were right.

Now I have a new problem here is the error message

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

@Tom-Elliott looks like it is .ipxe that is showing up, I had to record a video and play it back to see it. Yes the thread has moved in the direction of some machines are booting and others aren’t. It was originally a thread about none of the machines being able to register due to a MAC issue.
I’ll change the boot file to .kkpxe and see if that works with the machines that won’t boot.