Looks like we need to type very carefully until it’s fixed lol.

@george1421 FOS typically hangs at this spot when GPT remnants are present. Debug + fixparts /dev/nvme0n1 in this case will typically fix it.

Check /etc/exports

It probably got wrote over when you reinstalled for some reason… or changed…

Make sure NFS is running, also. usually, if you give NFS a restart, any syntax errors that is inside /etc/exports become glaringly obvious.

Some people set the fog grace time and checkin time to really extreme values (hours in some cases).

The display that the fog client gives might make users think they have to wait for the count down. If there was a “Restart now” button, they could just click it to get maintenance over with.

@robertd Windows has some magic to go from BIOS to UEFI. When you deploy a bios image to a UEFI machine, Windows will do this repair thing to convert the disk structure over. However - using this as part of your workflow is really sloppy and you’re probably just begging for trouble.

@blue_steel in putty, to copy you select text and just right click. To paste something from the clipboard, just right click.

You can take a look at this article: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

I’d highly recommend looking at the “Troubleshooting” bit and using Wireshark to see if your clients are even getting the correct info passed to them via DHCP. Of course, go through the other things in that article too.

@juice381 It’s been a hot minute since I’ve used this, but if any changes need made to work with the current, it will be easy and probably only take a few minutes. If you need help setting it up, just ask.
https://github.com/wayneworkman/FOGUpdateIP

@jherron You can try deleting your fogproject directory and then re-cloning.

@blue_steel said in Lenovo N22 PXE boot issues:

@george1421 Indeed, the linux user password here

vi /opt/fog/.fogsettings

Was not correct.

Well, that’s arguable. Anything set in the .fogsettings file is the ultimate definition of “correct” on your system. Everything is based around that file. All updates follow that file. It was correct as far as fog was concerned, it’s up to you to adjust that as you need.

Windows can connect via TFTP at the command prompt…

@george1421 that would be integrated into any script I write.

@manuel_mart You can import all hosts using a spreadsheet with the names you want set. Go here to get an example: FOG GUI -> Host Management -> Export Hosts. The file it gives you is the format it needs if you were to import hosts. Also, you could deploy the FOG Client to all boxes so that they register using the name they have now prior to imaging.

The file name should not be in all caps.

Sounds like the network adapter isn’t in the UEFI boot stack. You can either turn it on, or use BIOS based booting as those are it’s settings from the factory.

Ok. The next step is to run the compatibility checks that are on the FOG boot menu.

Delete any tasks you may have for the problematic PC model, and turn on your fog menu and run all the compatibility checks that are in there. If any fail, let us know.

@juice381 said in Making Fog Portable:

I’ll leave it for another day.

If you can post the contents of crontab -e we can probably figure out what’s going on. It’s been a good moment since I’ve used these scripts, but I promise they were working on Fedora and CentOS lol. They probably will work on RHEL just fine too.

@kduy1508 I wrote a script that fixes this, it will re-number the image IDs. Link is below. Very happy to provide this to you.
https://github.com/FOGProject/fog-community-scripts/tree/master/RenumberImageIDs

@george1421 said in Yoga 260 w/RTL8153 freeze (or black screen) after init.xz loads:

I remember seeing a post a while ago where there was no display, but the FOS engine was still working fine. I’m not saying that is the case here, but I would be interesting to know.

If kernel log level is set to zero, nothing will display.

I’d still say use TCPDump (in the troubleshooting section) and see what is going on between the client and server.

@networkguy All of our Moderators, Developers, and Senior Developer are trustworthy people. If you don’t want to upload the capture to the forums, I might suggest messaging them to get an email address you can send it to. If they are able and willing, they will look through it and then the conversation can continue here in this thread without anything sensitive being shared.