When I run :

SELECT * FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%'; SELECT * FROM hosts WHERE hostID IN (SELECT hmHostID FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%');

I get output pertaining to the host that I had deleted via the GUI. Is there a way to delete those records from the DB using the MAC?

@rfrancisco said in Certificate validation failed:

Data::RSA ERROR: Trust chain did not complete to the known authority anchor.

Please re-install the fog-client in this machine to fix the error.

@kbell I only see that problem when i use incorrect ipxe file, uefi/legacy independent. the pxe file must match with nic drivers, and firmware type, (.efi for efi systems), (.pxe, .kpxe, .kkpxe for legacy systems), and not all ipxe files have all nic drivers, some realtek cards not works with undionly.kkpxe and you need to use realtek.kpxe, same on uefi i have nics that require snp.efi instead of ipxe.efi.

@george1421 You were correct. Was able to locate the password for the fogproject account and that account was able to upload the file to the tftp directory. Thank you for your guidance.

@fog8923 said in Trying to "Push" CentOS7 image on Lenovo P620:

I will modify the dhcp settings to use snponly.efi

I would at least try the built in card with the snponly.efi driver. Make sure the firmware (bios) on the lenovo is up to date. We’ve also seen flaky first generation firmware from lenovo.

@junkhacker interesting, even if i don’t understant all the concept

@tesparza Yeah, todays log is full of “No need to sync …” messages. Seems all fine.

The replication process does check file size and checksum of the files on master node and each storage node. In case they don’t match the replication deletes the file on the storage node and resyncs that file over. So in general there shouldn’t be a case where replication is “stuck” with one file not in sync even if it was broken half way.

@btoffolon You might want to search the forums for dc7800 to find many posts on this hardware. Here is one post that might help your: https://forums.fogproject.org/post/137220

When I first encountered DC7800 problems I rolled the kernel way back to one even older than 4.15.2 […]
With 4.15.2 I have been able to image, capture, etc etc all different kinds of laptops and workstations via legacy and UEFI PXE boot without any problems.

Old hardware, old kernel…

@sebastian-roth said in Lenovo T15 Gen2 Slow Imaging:

@jconway1006 We have reports with Lenovo T14 Gen2 being slow as well: https://forums.fogproject.org/topic/15433/lenovo-t14-gen-2 - see @saad-naeem’s post in this topic for a possible solution.

Yeah I ended up reading that post after I posted mine. Same exact issues. Tried some of the suggestions in there (upgrade BIOS) and all that stuff with no success. I’m making due right now with a little work around. Its just a pain when ya have more than a few laptops to setup.

@bruce-stewart said in 21H1 imaging issue-variables do not populate:

My variables don’t seem to get populated.

Well that’s pretty normal when you don’t use bash command export to make those available globally.

@WillingMost7 Usually the fog-client software does autoupdate but due to the certificate issue it won’t. You’ll need to deploy the 0.12.0 fog-client using other methods like GPO or so.

@jyost Search the forums for snapin order. You’ll find several threads. Here’s one that probably will help:
https://forums.fogproject.org/topic/12784/snapin-order

@stu There’s a wiki article all about passwords: https://wiki.fogproject.org/wiki/index.php?title=Password_Central

Though, if you cannot log in via terminal or SSH, you might could try a Linux password reset boot utility. Use your favorite search engine to search for reset Linux password. Highly advise to backup / create snapshot before trying anything you find.

Disregard - problem has been solved. I renamed a .msi setup file but forgot to edit the filename in the snapin configuration.

@brmitmhart @Wayne-Workman Just want to add a little warning here. FOG does not support downgrading as of now. Depending on the versions it might work but could also break things.

I don’t have enough time to look into this the next few weeks. Maybe @Tom-Elliott can?

@george1421 said in Storage nodes or Master nodes?:

Storage nodes can only send images via unicast images.

What’s the technical reason for this? Just wondering. Like, why can’t it be done? Or, has it simply not been implemented?

@sebastian-roth I found the machine in hosts and approved it and now it worked out thanks

@gn_ro Hi and thanks,

You have solve my problem, disk was already in thick mode but i change the NIC and capture going to the end.

So thanks again, have a good day.