In FOG Settings there are question marks with descriptions about things.
In a host’s “Service Settings” there are also question marks with descriptions.
Can we get question marks that show descriptions for a host’s “Active Directory” area?
In FOG Settings there are question marks with descriptions about things.
In a host’s “Service Settings” there are also question marks with descriptions.
Can we get question marks that show descriptions for a host’s “Active Directory” area?
@george1421 FOS typically hangs at this spot when GPT remnants are present. Debug + fixparts /dev/nvme0n1
in this case will typically fix it.
Why are you using option 150? Do you plan to have multiple TFTP servers on the same network? Normally option 066 is set for this.
Do you have an old computer to put FOG on instead of testing in a virtual box? I only ask because I haven’t used virtual box and a physical system on your network would greatly simplify your testing.
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.
@blue_steel in putty, to copy you select text and just right click. To paste something from the clipboard, just right click.
Samba is not the carrier for imaging in FOG, NFS is. FTP access to the images is also required.
You can setup a sperate linux server as a storage node, and all the images can reside on there, and have another VM as your main controlling FOG server if you like. The main server orchestrates everything. Storage nodes are just storage nodes.
You can use an actual full Debian server/computer as a storage node or a Synology NAS or FreeNAS or other similar types of storage. It’s possible to also create a storage node using Windows - but it hasn’t been done in a while.
Or…
You could set everything up self contained on one VM. And as far as how much storage space you need, well that depends on how many images you need to have, how big they are, and so on.
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
@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.
@pstoric There’s a web GUI. if you have a GUI or not on the base OS by default depends on what distribution of linux you install. For example, Ubuntu server doesn’t come with a GUI by default but Ubuntu workstation does. Both work fine, but of course server distros are more lean.
It wouldn’t be a bad idea to nuke and re-pave. I started over and over as well when I was just getting going. Overtime you learn to fix things instead of nuking and paving
Windows can connect via TFTP at the command prompt…
@george1421 that would be integrated into any script I write.
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.
@Connie I’d start off by deleting everything in /images/dev
because probably an upload was attempted but not completed due to insufficient space. A lot more work is probably needed though. This is what inevitably happens when you put everything on one partition. There are walk-throughs in the wiki that show how to partition a drive in order to avoid this.
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.
@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.
Well this needs a video for sure. I like to think I’m a little seasoned at this - but I stumbled hard. I’ll put together a video.
I’d still say use TCPDump (in the troubleshooting section) and see what is going on between the client and server.