@george1421 worked like a charm when switching to REFIND.

Current Solution set Kernel to 4.19.64 and set global option in Fog Configuration–> FOG Settings --> General Settings --> Kernel ARGS to tsc=unstable

Luckly this is the last year for these machines.

Cerial is now Serial

For right now, I can only implement disabling auto-update based on global setting. This is because the client doesn’t return any identifying host information for us to filter by host.

However, this is, I think, a very needed “feature” of FOG and the new client.

My posting seems a bit strange I’m sure, but just know it’s trying to say this has now been implemented.

32-bit and 64-bit both work in the inits.

You just have to boot into debug mode right now and then type in the above commands. I will talk with Tom to see if we can change the compatibility check first as we do not want to mess up the current flow

@Wayne-Workman said:

I’ve had this issue on both Dell 7010s and on some older Lenovos. Every now and again I’ll find a machine that just won’t image.

Sometimes, pulling the network cable and power cable and then hitting the power button a few times, then hooking everything back up will fix it. 😕 It’s just strange.

WORKED for my one Dell E6400. Very odd. That trick is used for clearing corrupt RAM and I did a swap so it doesn’t exactly make sense. Whatever…it works now.

Still working on the D630 image will be done with it shortly.

x32 bit machines should now be fixed in the latest git.

x32 Upload times are slow but they will upload all the way. ~84Mib/s with lvl 9 compression (4:20:15) x32 Download times are “fast” ~1.8Gib/s lvl 9 compression (00:12:01) x64 Up 3.2Gib/s lvl9 (00:20:00) Down 7.3Gib/s lvl9 (00:09:00)

Full Description of problem:
1.)nfs mount issue was due to not getting an ip address during init boot.
2.)Not getting an ip was due to an addition of fixing VLAN issues for networks and sleep command was an “Illegal Instruction” (along with other commands essential to “init fog script”)
3.)sleep was not working due to a compiling issue in the glibc v2.21.

*Solution:
1.) Downgraded init’s to use glibc v2.20 (fixed sleep function).
2.) init’s now get ips from edits in files K40Network and S40Network.
3.)NFS mounts successfully now that init gets an ip address at boot.

These changes have been pushed to both init_32.xz and init.xz.

If you see this issue with your old 32 bit only processors please make sure you update to the latest version and this should be fixed.

P.S. @Tom-Elliott thanks for the remote sessions and time. Took us a while but we nailed down the problem

Issue:
Fog client service will not join AD domain.
…MAC is NULL!
…MAC does not exist!

Cause: MAC class issues

sry bad info. Tom says these are “normal” system accounts that should not be able to be removed. If i created test it was able to be deleted. See my test account![ATTACH=full]1616[/ATTACH]

[url=“/_imported_xf_attachments/1/1616_Untitled.png?:”]Untitled.png[/url]

MMMMM Updater script 😉

I know changing it to 3 for me has cut my upload times in half.

Confirmed thanks Tom.

All,

To add on to this thread, I want you all to be “warned” in sorts.

If you update to these recent builds, all nodes will need to be on the same level, not necessarily hence forth, but at least to the 2411 build. Maybe even 2403 build? There’s a lot of information that changed, but most notably the way hosts and their mac addresses are associated.

There is something similar in the wiki: [url]http://www.fogproject.org/wiki/index.php?title=Error_Messages[/url]. Could you try what they suggest and see if it makes a difference? They are suggesting that there is a problem in the startup scripts for debian but that temporarily removing the fog startup scripts from /etc/init.d seemed to work.

FIXED!

I truncated the entire tasks table, removed the bad member reference in groupMembers, and anything else related to this 'BAD HOST"…The Invalid OS ID is due to a small bug in r1799.

Issue resolved.

THANKS TOM!!!

Intel NUC: NUC6i5SYB

Last Captured
2022-07-28 04:06:48

Deploy Method
Partimage

Image Type
ImageType ID: 2 Name: Multiple Partition Image - Single Disk (Not Resizable)

PXE: undionly.kpxe

Ethernet: Elitegroup Computer Systems Co.,Ltd. b8:ae:ed:7f:eb:6d

System UUID f8493d3f-a111-8a17-c119-b8aeed7feb6d
System Type Type: Desktop
BIOS Vendor Intel Corp.
BIOS Version SYSKLi35.86A.0073.2020.0909.1625
BIOS Date 09/09/2020
Motherboard Manufacturer Intel corporation
Motherboard Product Name NUC6i5SYB
Motherboard Version H81131-502
Motherboard Serial Number GESY60400ECC
Motherboard Asset Tag .]/.
CPU Manufacturer Intel® Corporation
CPU Version Intel® Core™ i5-6260U CPU @ 1.80GHz
CPU Normal Speed Current Speed: 1700 MHz
CPU Max Speed Max Speed: 2900 MHz
Memory 7.66 GiB
Hard Disk Model ADATA SP550
Hard Disk Firmware O1015A
Hard Disk Serial Number 2G0920029548

True this has been added to host management. My mind just goes to Group Management when I want to add hosts to a group. However, [B]this does perfectly work fine in Host management.[/B] If you keep it the way it is then the user will just have to realize to go to Host Management for adding multiple machines to a group. Then to delete multiples from a group go to the Group Management.