@george1421 No, they were in proper failover config and the options replicated between the scopes. But it’s all good now and that’s the important thing ❤

@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!

@Tom-Elliott can confirm, this does now appear to work in 1.6 - huzzah! @george1421 looks like your hard work has paid off and it will eventually be in the stable branch!

@chevengur there is not enough information to help you in that picture. If we could see more of the error message that partclone threw (i.e. just above the top of your picture) we would know what happened. At the point in the script all we know is that partclone wasn’t happy.

Thank you!

Ok, nevermind, did the git thing, got it working, cheers 🙂

@Tom-Elliott Cheers, works as expected now!

@Tom-Elliott ah, that would work! Sorry, the documentation is such a mish-mash that it’s hard to find answers for some of this stuff!

@Tom-Elliott thx👍

@Tom-Elliott Yes, everything is working as expected. For the longest time, FOG would always show UTC time for when an image was captured or deployed, now it is correctly showing local time and no more zombie processes! Thanks

@JasonNaughton This is a strange one. The linux kernel just doesn’t just invent mac addresses. It would be interesting to look up the first 6 characters of the mac address to see if you could identify the manufacturer.

So are you saying there are 4 physical nics in this computer. LOM, PCie 1, PCie 2? Does that mac address belong to the LOM?

I can say that we are dealing with 2 kernels here. The iPXE boot loader, and FOS Linux. Its technically possible to get to the fog ipxe menu and then when you start up FOS it doesn’t get an IP address because either the nic order has changed or there is missing firmware that is needed to init certain nics.

@Clebboii https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

Please see if this helps? Specifically the task related items. Sometimes stale (old/bad items suddenly show up from long ago.) admittedly I’d love to know what caused (or causes?) this but it has so far eluded me this far.

@Tom-Elliott What’s the difference between the full and quick registration processes then? because AD join exists in full, but not in quick…

@DanCan Hi This is currently a known issue on some motherboards. Honestly not sure what is causing this to happen. I am working on a fix to this issue just haven’t had too much time lately.

@sloeckle You can use an older kernel for now, but I’ll work on a fix for this issue. I don’t have access to the hardware needed to reproduce this issue. Are you willing to help us test some kernels?

@Tom-Elliott cheers - looks like someone changed working branch in 2019 to add hdbios, and it’s not something that’s in the dev branch either!

@Tom-Elliott no stress, with so many posts it’s normal to miss some 😉

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

@george1421 Thanks, George.

@Tom-Elliott to note, this has been happening on all our Lenovo L14s laptops (with no LAN ports), tested with 3 different Lenovo USB-C LAN Adaptors

When booting back up, it brings the Blue screen error:

‘Recovery
Your PC couldn’t start properly
After multiple tries, the operating system on your PC failed to start, so it needs to be repaired.
Error code: 0xc0000001
You’ll need to use recovery tools. If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.
Press Enter to try again
Press F1 to enter Recovery Environment
Press F8 for Startup Settings
Press Esc for UEFI Firmware Settings’

As John mentioned, we used the same LAN adaptor previously and managed to image via FOG successfully before.

i even tried changing the mac address to the default internal laptop mac address after the initial fog image completed (when it shutdowns the laptop) and booted the laptop back up to see if it helps but no luck